The Five Phrases of Highly Annoying Programmers

Thu, 26 Oct 2006 13:10:00 GMT

Most of the bloggers on "The Pragmatic Architect" will give advice on what you should be doing. I'd like to point out some of the things you shouldn't. Here are some phrases that send a shudder down my spine.

- "It's what Martin Fowler does/says". Martin Fowler (or anyone well known, I'm not picking on him in particular) may or may not have a specific opinion on a subject but it isn't correct just because they have stated it. Can it be applied to your situation and is it the optimal solution for where you are? This is actually a classic logical fallacy called "Argumentum ad verecundiam" or "Appeal to Authority".

- "Pah, that's from Microsoft" - with a dismissive wave of the hand. This is another logical fallacy, called "Argumentum ad hominem" or "Argument against the man". Just because, for example, Microsoft Bob was a failure doesn't mean that C# will also fail. If you have a problem with a particular technical product or solution then argue against it rather than an individual or company associated with it. This is different though from arguing that a company in trouble may not be able to provide future support as this is a real attribute of the solution.

- "That's not my job". If you're the most appropriate person for the task then it is your job. For example, you may not be the DBA on a project but if you designed the data model then it makes sense for you to at least help with the SQL. The same goes for source control, release scripts etc.

- "In my last job we..." Repeat after me YOU NO LONGER WORK THERE. I know I'm being slightly unfair - if you had a good system, process, design etc that can be reused (within the limitations of intellectual property, of course) then that's great but don't turn into the girl from American Pie going on about band camp. Please don't point out every difference like a criticism.

- "Your code is broken." Please, oh please it's the code is broken. In any system, larger than a time-filling hobby, there will be a multitude of designers and programmers working on it over many years. It will also interface with a multitude of external products and systems. Unless you're talking about a build break from a check-in don't point the finger - or I may slam it in a door.

For more on logical fallacies: http://en.wikipedia.org/wiki/Fallacy

Coding the Architecture - programmers tag

The Five Phrases of Highly Annoying Programmers