Tag Archives: best practices

If someone asks you to use [StupidTechnologyDujour]

I had a fun conversation with a peer today. He asked me what I would say if a boss or peer wanted to use [Stupid-Technology-Dujour] (replace with technology of your choice). I know he was asking a rhetorical question, but … Continue reading

Posted in Lessons Learned, Programming | Tagged , , , , , | Leave a comment

Metal detector, for needles-in-a-haystack

A few weeks back, I had some good advice for someone on stack overflow https://stackoverflow.com/questions/49817985/htmlagilitypack-exception-has-been-thrown-when-used-in-deployed-ssis-package?noredirect=1#comment86732223_49817985 The guy was stuck with a bug and couldn’t figure it out. Sometimes, you can’t get any help on Stack Overflow because people are like “can we … Continue reading

Posted in Errors, Lessons Learned, Programming | Tagged , , , | Leave a comment

Grave naming

I just heard a new one today.  On the topic of “software development and coding standards” have you ever heard of “Grave Naming”? I guess it refers to the practice of standardizing specific domain (value) names across development layers.  (…from … Continue reading

Posted in Methodology, Programming | Tagged , , , , | Leave a comment

Showing Initiative vs Being a Cowboy

A few weeks ago, I fixed a bug without being asked to do so. Shortly afterwards, I was asked “Why did you fix that bug? Who told you to do it?”  The question arrived in email, so I couldn’t be … Continue reading

Posted in IT Psychology, Professionalism | Tagged , , , | Leave a comment

Wheels that need to squeak

I’m sure you have heard the phrase “the squeaky wheel gets the grease”. Basically, if you need something done and it is not just getting itself done, you should speak-up and complain, maybe even make a bit of a ruckus, … Continue reading

Posted in IT Horror Stories, IT Psychology, Lessons Learned, Methodology, Professionalism | Tagged , , , , | Leave a comment

Why Catch(exception) is usually a bad idea

I always like reading what other developers are suggesting as “best practices”.  Occasionally, I come across one that seems to defy logic, such as “don’t allow comments in your code”.  Initially the statement seems bonkers, but then you read-up on … Continue reading

Posted in .net, Errors, Lessons Learned, Programming | Tagged , | Leave a comment

The edge of scope

I don’t think I coined this term, but my colleagues think I might have. Imagine for a moment: you are working on a project with a hard deadline. You simply must hit your deadline. In that case, your greatest foe … Continue reading

Posted in Lessons Learned, Methodology, Requirements | Tagged , , , , | Leave a comment