Comments on: Top 10 Things That Annoy Programmers http://www.kevinwilliampang.com/2008/08/28/top-10-things-that-annoy-programmers/ ASP.NET Developer. ALT.NET Supporter. Pragmatic Programmer. Published Writer. Thu, 02 Sep 2010 01:11:40 +0000 hourly 1 By: Simon2 http://www.kevinwilliampang.com/2008/08/28/top-10-things-that-annoy-programmers/#comment-3248 Simon2 Sat, 07 Aug 2010 23:33:33 +0000 /post/Top-10-Things-That-Annoy-Programmers.aspx#comment-3248 You should go read the top 10 list again. You're optimisation offers nothing and in fact makes it harder for a future developer to understand because if there were a bug here it less represents the original algorithm that the original coder copied (and the future coder will google it and find it), it is more obscure and harder to understand and most modern compilers are highly efficient at optimising code. Personally I would explain the algorithm in the comments if it were not obvious. Less lines does not make better code. You should go read the top 10 list again. You’re optimisation offers nothing and in fact makes it harder for a future developer to understand because if there were a bug here it less represents the original algorithm that the original coder copied (and the future coder will google it and find it), it is more obscure and harder to understand and most modern compilers are highly efficient at optimising code. Personally I would explain the algorithm in the comments if it were not obvious. Less lines does not make better code.

]]> By: Simon2 http://www.kevinwilliampang.com/2008/08/28/top-10-things-that-annoy-programmers/#comment-3247 Simon2 Sat, 07 Aug 2010 22:40:56 +0000 /post/Top-10-Things-That-Annoy-Programmers.aspx#comment-3247 Once I was allowed to because of a performance problem. I reimplemented a tree data structure implementation written by the lead developer which had >10 classes as a hashlist of hashlists. It was very rewarding because the performance issue was solved and with 1 class with less than a page of code was required. Once I was allowed to because of a performance problem. I reimplemented a tree data structure implementation written by the lead developer which had >10 classes as a hashlist of hashlists. It was very rewarding because the performance issue was solved and with 1 class with less than a page of code was required.

]]> By: Simon2 http://www.kevinwilliampang.com/2008/08/28/top-10-things-that-annoy-programmers/#comment-3246 Simon2 Sat, 07 Aug 2010 22:27:52 +0000 /post/Top-10-Things-That-Annoy-Programmers.aspx#comment-3246 Yes, I feel the same. Often you develop something under tight deadlines and with no real specifications or design and then the code creep; developers were never involved in the selling process of non-existent features so you can't go ask the customer what the specifications should be and the sales team has no idea. Lack of documentation means the developers then make best guess at interfaces and API's and make assumptions about business processes. So, when with hindsight, you can revisit something you did under those conditions you can rebuild it with better understanding. I so infrequently get that opportunity. Yes, I feel the same.

Often you develop something under tight deadlines and with no real specifications or design and then the code creep; developers were never involved in the selling process of non-existent features so you can’t go ask the customer what the specifications should be and the sales team has no idea. Lack of documentation means the developers then make best guess at interfaces and API’s and make assumptions about business processes. So, when with hindsight, you can revisit something you did under those conditions you can rebuild it with better understanding. I so infrequently get that opportunity.

]]> By: Elia http://www.kevinwilliampang.com/2008/08/28/top-10-things-that-annoy-programmers/#comment-3124 Elia Sat, 31 Jul 2010 16:30:36 +0000 /post/Top-10-Things-That-Annoy-Programmers.aspx#comment-3124 Perfect, man! Congratulations! Do you know if there is already a brazilian portuguese translation for that post? Perfect, man! Congratulations! Do you know if there is already a brazilian portuguese translation for that post?

]]> By: tan4eg http://www.kevinwilliampang.com/2008/08/28/top-10-things-that-annoy-programmers/#comment-2210 tan4eg Wed, 16 Jun 2010 06:28:08 +0000 /post/Top-10-Things-That-Annoy-Programmers.aspx#comment-2210 Hi Kevin! Russian version of your great list is here http://sly-and-fluffy.blogspot.com/2010/06/10.html Hi Kevin! Russian version of your great list is here http://sly-and-fluffy.blogspot.com/2010/06/10.html

]]> By: Johan Karlsson http://www.kevinwilliampang.com/2008/08/28/top-10-things-that-annoy-programmers/#comment-2126 Johan Karlsson Thu, 03 Jun 2010 06:39:35 +0000 /post/Top-10-Things-That-Annoy-Programmers.aspx#comment-2126 I really liked reading this article. I think that #10 is important. #7 is something that I have encountered a lot. I really liked reading this article. I think that #10 is important. #7 is something that I have encountered a lot.

]]> By: TheRealist http://www.kevinwilliampang.com/2008/08/28/top-10-things-that-annoy-programmers/#comment-2120 TheRealist Wed, 02 Jun 2010 02:54:13 +0000 /post/Top-10-Things-That-Annoy-Programmers.aspx#comment-2120 14. Receiving a tech/func spec that has more holes than swiss cheese and more loose ends than a persian carpet, then having to deal politically with the authour whilst I tear it up and start again talking directly to the stakeholder. True story: I worked for a company where salesmen got bonus on revenue brought in and not on profit. Salesman would sell projects under cost. (software costing, say, 10000 in coding time they'd sell for 1000 to make a commission of 100) One of these salesmen brought me a project to integrate all hardware and software within a conglomorate of 30 different companies (that had been bought up a single company). so thats Accounts, Human Resources, CRM, CMS, stock, inventory, servers, operating systems, licenses, everything. Tme allowed: 3 weeks. 14. Receiving a tech/func spec that has more holes than swiss cheese and more loose ends than a persian carpet, then having to deal politically with the authour whilst I tear it up and start again talking directly to the stakeholder.

True story:
I worked for a company where salesmen got bonus on revenue brought in and not on profit. Salesman would sell projects under cost.
(software costing, say, 10000 in coding time they’d sell for 1000 to make a commission of 100)

One of these salesmen brought me a project to integrate all hardware and software within a conglomorate of 30 different companies (that had been bought up a single company). so thats Accounts, Human Resources, CRM, CMS, stock, inventory, servers, operating systems, licenses, everything.
Tme allowed: 3 weeks.

]]> By: TheRealist http://www.kevinwilliampang.com/2008/08/28/top-10-things-that-annoy-programmers/#comment-2119 TheRealist Wed, 02 Jun 2010 02:34:53 +0000 /post/Top-10-Things-That-Annoy-Programmers.aspx#comment-2119 some more: 11. The fact that nobody above you and few if any at your level or the customer really realise the difference between whats involved in some serious problem solving with an elegant solution and a text change. If I worked 10 times harder or smarter it would not be seen. consequently to balance things you would have to work DOWN to your wage and not UP to your ability. 12. Bending over backwards for a single customer and adding layers of complexity to a system for a whim requirement that doesnt justify what it will take to make that happen, because no one (sales) wants to say no. then they never use it 13. Technical Triumph followed by Commercial Disaster due to being told to code something pointless in the first place. Followed by a rush for the next "Golden Egg" some more:

11. The fact that nobody above you and few if any at your level or the customer really realise the difference between whats involved in some serious problem solving with an elegant solution and a text change. If I worked 10 times harder or smarter it would not be seen. consequently to balance things you would have to work DOWN to your wage and not UP to your ability.

12. Bending over backwards for a single customer and adding layers of complexity to a system for a whim requirement that doesnt justify what it will take to make that happen, because no one (sales) wants to say no. then they never use it

13. Technical Triumph followed by Commercial Disaster due to being told to code something pointless in the first place. Followed by a rush for the next “Golden Egg”

]]> By: BlueCollarCritic http://www.kevinwilliampang.com/2008/08/28/top-10-things-that-annoy-programmers/#comment-2110 BlueCollarCritic Tue, 01 Jun 2010 15:12:27 +0000 /post/Top-10-Things-That-Annoy-Programmers.aspx#comment-2110 It would greatly benefit any sofwtare company to engage in teh pratice of using people with some development skills and more writing skills/education to produce documentation with the developer. The Developer knows teh code but not necessairly how to articulate it to others, in particular to non-programmers or in other words to end users. The professional writer can do this but they too need some understanding of development else they will not properly understand how to articulate what the developer is telling them. This would make a lot of people happy at every turn of this problem with software documentation. It would greatly benefit any sofwtare company to engage in teh pratice of using people with some development skills and more writing skills/education to produce documentation with the developer. The Developer knows teh code but not necessairly how to articulate it to others, in particular to non-programmers or in other words to end users. The professional writer can do this but they too need some understanding of development else they will not properly understand how to articulate what the developer is telling them.

This would make a lot of people happy at every turn of this problem with software documentation.

]]> By: Azonei http://www.kevinwilliampang.com/2008/08/28/top-10-things-that-annoy-programmers/#comment-2109 Azonei Tue, 01 Jun 2010 07:54:02 +0000 /post/Top-10-Things-That-Annoy-Programmers.aspx#comment-2109 I couldn't have come up with a more accurate list if I had a spec sheet. Even the cartoon was accurate. I can't count the number of times I've sat looking at the screen with a blank stare in my eyes while a program was compiling - or sometimes with just the blank stare in my eyes for no apparent reason (usually following one of the many interruptions to perform another task as mentioned in #9). My only complaint: You described me so accurately that I no longer feel unique. I'm just another sheep in the herd. I think I hate you. :) I couldn’t have come up with a more accurate list if I had a spec sheet. Even the cartoon was accurate. I can’t count the number of times I’ve sat looking at the screen with a blank stare in my eyes while a program was compiling – or sometimes with just the blank stare in my eyes for no apparent reason (usually following one of the many interruptions to perform another task as mentioned in #9).

My only complaint: You described me so accurately that I no longer feel unique. I’m just another sheep in the herd. I think I hate you. :)

]]>