Comments on: The four golden rules to be a better software developer.

By: Becoming a pale, pasty programmer « Life in the Shell

Becoming a pale, pasty programmer « Life in the Shell — Mon, 12 Dec 2011 04:00:45 +0000

[...] order to become a great coder you need to practice great coding (yes, I’ve read All code is crap, but there are definitely varying degrees of crap and you want to be on the less crappy side). If [...]

By: 程序员的7大毛病 | Grow Up Diary-程序员成长日记

程序员的7大毛病 | Grow Up Diary-程序员成长日记 — Thu, 18 Aug 2011 11:32:36 +0000

[...] 我要告诉你一个坏消息，兄弟，所有的程序都写的很烂，包括你的。无论你在上面花多少功夫，其他大多数程序员总是会认为你写的代码很烂、他们能写出比你好10倍的程序。我在前几篇文章里已经讨论过了这个问题，你可以读读这篇文章和这篇文章，从中你可以理解我所说的所有的程序都写的很烂究竟是什么意思。 [...]

By: T.Suriyathep » How to think like a practical programmer

T.Suriyathep » How to think like a practical programmer — Thu, 30 Jun 2011 19:43:12 +0000

[...] The four golden rules to be a better software developer Philosophy & World View [...]

By: 【外刊IT评论】程序员的七大坏毛病 — 见贤思齐

【外刊IT评论】程序员的七大坏毛病 — 见贤思齐 — Sat, 25 Jun 2011 13:45:53 +0000

By: 程序员的7个坏毛病 | 程序员那些事儿

程序员的7个坏毛病 | 程序员那些事儿 — Wed, 15 Jun 2011 05:50:38 +0000

By: Top 7 programmers bad habits » OnnoRokom

Top 7 programmers bad habits » OnnoRokom — Sat, 11 Jun 2011 05:28:54 +0000

[...] posts, you can find more information of what exactly I mean when I say that all the code is crap here and [...]

By: Maruda

Maruda — Thu, 26 May 2011 09:45:05 +0000

In my opinion this is a wrong attitude. If I believed that all the code I create is crap, I wouldn’t bother improving it. Rule number 1 would mean that I’m never able to write a good code, even after series of refactorings. But if it’s not true, and refactorings can improve the existing code, then nothing stops me from creating a good code in the first place.

Which I believe I do.

If I wouldn’t believe it, I wouldn’t wasting my time learning design patterns, attending conferences, reading books like “Effective Java” and “Code Complete” or following Uncle Bob’s or Marting Fowler’s blogs. Or yours.

And if your manager knows anything about software engineering, he does care about the quality of your code. We don’t create a good code just for sake of it, we create it so that it would be possible to understand it and to modify (extend or fix) the existing solution in a reasonable time.

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

Thu, 17 Jun 2010 12:39:48 +0000

[...] The four golden rules to be a better software developer. [...]

By: PhiLho

PhiLho — Sun, 30 May 2010 08:22:31 +0000

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 件關於程式設計的事

大學沒教的 10 + 1 件關於程式設計的事 — Fri, 28 May 2010 15:36:41 +0000

[...] 在抱怨那些我碰到的程式碼10年之久後，我得到了一個精闢的結論：所有（包含我自己寫的）程式碼，都是鬼扯蛋。當然，就算鬼扯還是有等級之分，但即使是我看過寫得最好的程式碼，也是難以閱讀。 [...]