(Originally written for and posted by HI Digital Solutions )Anyone who works in software engineering has to deal with troubleshooting failures. Personally I like to approach failures as a challenge, a kind of treasure hunt that when complete leads you to the cause of the problem. This is great when all of the clues are there, but what happens when some are missing? You might get to a point where you can see multiple different paths to the end.
(Originally written for and posted by HI Digital Solutions )A while back I read a great article that outlines both the challenges and advantages of getting all necessary parties involved in a project early, including developers and other “tech” people. The content resonated with me, since my team was in the midst of this exact situation — we had started to participate in the “initiation” phase of projects. I am a software engineer and most of my team are also software engineers, my viewpoint here is getting people like us involved early.
We’ve all been in them. We’ve been in good ones, bad ones, meh ones, the bottom line is that they take time and a wise man instilled in me at a young age that if you are going to take time doing something then make it worthwhile. We’re being paid for our time, so let’s not waste it.
For some folks their entire day is just meetings (those poor souls), but for most others they are on an as needed basis.
