Comments on: Beware of the second worst programmer http://gojko.net/2008/10/07/beware-of-the-second-worst-programmer/ Building software that matters Fri, 12 Mar 2010 16:28:45 -0500 http://wordpress.org/?v=2.9.2 hourly 1 By: Mladen Stanojevic http://gojko.net/2008/10/07/beware-of-the-second-worst-programmer/comment-page-1/#comment-35586 Mladen Stanojevic Wed, 08 Oct 2008 14:50:33 +0000 http://gojko.net/?p=399#comment-35586 I had interesting experience....totally opposite but also interesting: "Software architect" as a best in team takes UML design tool, makes some diagrams as a foundation for code and db generation for big ERP software and then "second best" programmer takes this, remodel everything and generate code and database and system works perfectly for few years now. Of course "architect" sad that he is proud author of new model but who cares about this :). Pozdrav iz Srbije! I had interesting experience….totally opposite but also interesting:
“Software architect” as a best in team takes UML design tool, makes some diagrams as a foundation for code and db generation for big ERP software and then “second best” programmer takes this, remodel everything and generate code and database and system works perfectly for few years now.
Of course “architect” sad that he is proud author of new model but who cares about this :) .

Pozdrav iz Srbije!

]]> By: Arjan`s World » LINKBLOG for October 8, 2008 http://gojko.net/2008/10/07/beware-of-the-second-worst-programmer/comment-page-1/#comment-35585 Arjan`s World » LINKBLOG for October 8, 2008 Wed, 08 Oct 2008 13:37:46 +0000 http://gojko.net/?p=399#comment-35585 [...] Beware of the second worst programmer - Gojko Adzic ‘ Code reviews matter. Do them often, read code that other people wrote and get them to read your code ‘ A theory is presented here in a bit of a humorous way that teams know the worst programmer, but forget about the one following the worst. Though there may be truth in there it sounds ilke a negative theory when literally put into practice. I’d rather focus on what these individuals *can* attribute and make it posiible to use them at * their* level of competency. This way you can both use their knowledge and prevent them from doing additional harm to the overall code base [...] [...] Beware of the second worst programmer – Gojko Adzic ‘ Code reviews matter. Do them often, read code that other people wrote and get them to read your code ‘ A theory is presented here in a bit of a humorous way that teams know the worst programmer, but forget about the one following the worst. Though there may be truth in there it sounds ilke a negative theory when literally put into practice. I’d rather focus on what these individuals *can* attribute and make it posiible to use them at * their* level of competency. This way you can both use their knowledge and prevent them from doing additional harm to the overall code base [...]

]]> By: Kai Backman http://gojko.net/2008/10/07/beware-of-the-second-worst-programmer/comment-page-1/#comment-35572 Kai Backman Wed, 08 Oct 2008 03:08:50 +0000 http://gojko.net/?p=399#comment-35572 In my current job we use an internal review tool to do systematic code reviews on every single changelist submitted to the codebase. While immediately intriguing this took a few weeks to get used to in the beginning. Now I can't imagine how someone can live without it, code reviews are our strongest tool to keep the team cohesive and up to speed. In my current job we use an internal review tool to do systematic code reviews on every single changelist submitted to the codebase. While immediately intriguing this took a few weeks to get used to in the beginning. Now I can’t imagine how someone can live without it, code reviews are our strongest tool to keep the team cohesive and up to speed.

]]> By: MoffDub http://gojko.net/2008/10/07/beware-of-the-second-worst-programmer/comment-page-1/#comment-35569 MoffDub Wed, 08 Oct 2008 00:11:00 +0000 http://gojko.net/?p=399#comment-35569 Nice post. I'm so jealous that you got to meet Eric Evans. His DDD book is probably the single most-impactful book on how I design my software. Nice post. I’m so jealous that you got to meet Eric Evans. His DDD book is probably the single most-impactful book on how I design my software.

]]> By: Niels http://gojko.net/2008/10/07/beware-of-the-second-worst-programmer/comment-page-1/#comment-35566 Niels Tue, 07 Oct 2008 23:33:51 +0000 http://gojko.net/?p=399#comment-35566 > Clearly, from the example in publishing, to get acceptably low-error code the solution is to employ dedicated copy-editor/proof-read programmers who spend all day reading code and fixing code or design problems. Which is how NASA writes perfect code for the shuttle: http://www.fastcompany.com/node/28121/print Now, what's the difference. Well, I've never heard of any terribly innovative code concepts coming out of the shuttle program. Material science and electrical engineering, yes. Basic physics innovations? No. Comp Sci innovations. No. Hacking innovations? No. It's a great way to write safe, stable code in a fiercely controlled environment. It's also unbelievably expensive and slow to evolve. > Clearly, from the example in publishing, to get acceptably low-error code the solution is to employ dedicated copy-editor/proof-read programmers who spend all day reading code and fixing code or design problems.

Which is how NASA writes perfect code for the shuttle:

http://www.fastcompany.com/node/28121/print

Now, what’s the difference. Well, I’ve never heard of any terribly innovative code concepts coming out of the shuttle program. Material science and electrical engineering, yes. Basic physics innovations? No. Comp Sci innovations. No. Hacking innovations? No.

It’s a great way to write safe, stable code in a fiercely controlled environment. It’s also unbelievably expensive and slow to evolve.

]]>