Comments on: The four golden rules to be a better software developer. http://www.makinggoodsoftware.com/2009/11/09/the-four-golden-rules-to-be-a-better-software-developer/ Thu, 29 Jul 2010 10:36:55 -0600 http://wordpress.org/?v=2.8.3 hourly 1 By: Are you using too many technologies in your projects? The 7 anti-patterns for technologies, frameworks and other technicalities in software development. | Making Good Software | the leading lady http://www.makinggoodsoftware.com/2009/11/09/the-four-golden-rules-to-be-a-better-software-developer/comment-page-1/#comment-8845 Are you using too many technologies in your projects? The 7 anti-patterns for technologies, frameworks and other technicalities in software development. | Making Good Software | the leading lady Thu, 17 Jun 2010 12:39:48 +0000 http://www.makinggoodsoftware.com/?p=1075#comment-8845 [...] The four golden rules to be a better software developer. [...] [...] The four golden rules to be a better software developer. [...]

]]> By: PhiLho http://www.makinggoodsoftware.com/2009/11/09/the-four-golden-rules-to-be-a-better-software-developer/comment-page-1/#comment-8008 PhiLho Sun, 30 May 2010 08:22:31 +0000 http://www.makinggoodsoftware.com/?p=1075#comment-8008 Good remarks... I am lucky to have enough experience to know that even if I am proud of the code I just wrote, I might be horrified to see it some months (years) later! Blame my ego if I wrote "might", but still my experience allows me to write... (sometime!) good code on the first try. Well, by first try, I don't mean I type and it works, I mean I code, compile, test, debug, start again, go through the code review, the test team, etc. :-) Good remarks…
I am lucky to have enough experience to know that even if I am proud of the code I just wrote, I might be horrified to see it some months (years) later! Blame my ego if I wrote “might”, but still my experience allows me to write… (sometime!) good code on the first try. Well, by first try, I don’t mean I type and it works, I mean I code, compile, test, debug, start again, go through the code review, the test team, etc. :-)

]]> By: 大學沒教的 10 + 1 件關於程式設計的事 http://www.makinggoodsoftware.com/2009/11/09/the-four-golden-rules-to-be-a-better-software-developer/comment-page-1/#comment-7912 大學沒教的 10 + 1 件關於程式設計的事 Fri, 28 May 2010 15:36:41 +0000 http://www.makinggoodsoftware.com/?p=1075#comment-7912 [...] 在抱怨那些我碰到的程式碼10年之久後，我得到了一個精闢的結論：所有（包含我自己寫的）程式碼，都是鬼扯蛋。當然，就算鬼扯還是有等級之分，但即使是我看過寫得最好的程式碼，也是難以閱讀。 [...] [...] 在抱怨那些我碰到的程式碼10年之久後，我得到了一個精闢的結論：所有（包含我自己寫的）程式碼，都是鬼扯蛋。當然，就算鬼扯還是有等級之分，但即使是我看過寫得最好的程式碼，也是難以閱讀。 [...]

]]> By: Kevin http://www.makinggoodsoftware.com/2009/11/09/the-four-golden-rules-to-be-a-better-software-developer/comment-page-1/#comment-5287 Kevin Sat, 27 Feb 2010 03:43:25 +0000 http://www.makinggoodsoftware.com/?p=1075#comment-5287 Rule No 4 can be such a pain in the a** sometimes. It collides with rules 1, 2 and 3 many times. If only managers could understand how tricky it can be to get things write considering the time they require. Time estimates always seem to go haywire especially when trying to solve something you did not expect would occur in the first place. How do you estimate that? Rule No 4 can be such a pain in the a** sometimes. It collides with rules 1, 2 and 3 many times. If only managers could understand how tricky it can be to get things write considering the time they require.

Time estimates always seem to go haywire especially when trying to solve something you did not expect would occur in the first place. How do you estimate that?

]]> By: On the 8 Spot » rePost::The four golden rules to be a better software developer. | Making Good Software http://www.makinggoodsoftware.com/2009/11/09/the-four-golden-rules-to-be-a-better-software-developer/comment-page-1/#comment-1880 On the 8 Spot » rePost::The four golden rules to be a better software developer. | Making Good Software Wed, 11 Nov 2009 01:29:03 +0000 http://www.makinggoodsoftware.com/?p=1075#comment-1880 [...] via The four golden rules to be a better software developer. | Making Good Software. [...] [...] via The four golden rules to be a better software developer. | Making Good Software. [...]

]]> By: Jim Danby http://www.makinggoodsoftware.com/2009/11/09/the-four-golden-rules-to-be-a-better-software-developer/comment-page-1/#comment-1874 Jim Danby Tue, 10 Nov 2009 15:51:42 +0000 http://www.makinggoodsoftware.com/?p=1075#comment-1874 You seem to have missed the point of your own title. Good title, meaningless content. How does knowing my code is crap improve it? You seem to have missed the point of your own title. Good title, meaningless content. How does knowing my code is crap improve it?

]]> By: Cujo http://www.makinggoodsoftware.com/2009/11/09/the-four-golden-rules-to-be-a-better-software-developer/comment-page-1/#comment-1872 Cujo Tue, 10 Nov 2009 15:23:37 +0000 http://www.makinggoodsoftware.com/?p=1075#comment-1872 Nice. My code isn't always crap when I first write it, and in those cases I will hunch over it and mutter about "my precious." But I can be sure that soon enough, I (or someone else) will need some functionality that I didn't quite figure into the initial architecture, and the crapification will begin. Nice. My code isn’t always crap when I first write it, and in those cases I will hunch over it and mutter about “my precious.” But I can be sure that soon enough, I (or someone else) will need some functionality that I didn’t quite figure into the initial architecture, and the crapification will begin.

]]> By: Tweets that mention The four golden rules to be a better software developer. | Making Good Software -- Topsy.com http://www.makinggoodsoftware.com/2009/11/09/the-four-golden-rules-to-be-a-better-software-developer/comment-page-1/#comment-1869 Tweets that mention The four golden rules to be a better software developer. | Making Good Software -- Topsy.com Tue, 10 Nov 2009 14:53:59 +0000 http://www.makinggoodsoftware.com/?p=1075#comment-1869 [...] This post was mentioned on Twitter by RoadHouse and Ben Armstrong, Steve Levine. Steve Levine said: Four rules to be a better developer: http://bit.ly/16AH6v [...] [...] This post was mentioned on Twitter by RoadHouse and Ben Armstrong, Steve Levine. Steve Levine said: Four rules to be a better developer: http://bit.ly/16AH6v [...]

]]>