Comments on: Considerate coding http://embeddedgurus.com/stack-overflow/2010/05/considerate-coding/ Thoughts on embedded systems by Nigel Jones Sun, 06 May 2012 10:34:02 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Nigel Jones http://embeddedgurus.com/stack-overflow/2010/05/considerate-coding/comment-page-1/#comment-776 Nigel Jones Thu, 13 May 2010 11:07:18 +0000 http://embeddedgurus.com/stack-overflow/?p=459#comment-776 I hadn't thought about that as a reason. I can't say I've ever run into someone who appeared to be intentionally making their code hard to follow / maintain so as to ensure their job security. However I have heard anecdotal reports that these people do exist. For me I take it as a a genuine success when a client of mine takes over code that I have written. I hadn’t thought about that as a reason. I can’t say I’ve ever run into someone who appeared to be intentionally making their code hard to follow / maintain so as to ensure their job security. However I have heard anecdotal reports that these people do exist. For me I take it as a a genuine success when a client of mine takes over code that I have written.

]]> By: groovyd http://embeddedgurus.com/stack-overflow/2010/05/considerate-coding/comment-page-1/#comment-774 groovyd Thu, 13 May 2010 02:05:42 +0000 http://embeddedgurus.com/stack-overflow/?p=459#comment-774 job security is the one big reason you might prefer to be a wanker... job security is the one big reason you might prefer to be a wanker…

]]> By: Kepa Diez http://embeddedgurus.com/stack-overflow/2010/05/considerate-coding/comment-page-1/#comment-747 Kepa Diez Tue, 04 May 2010 08:02:42 +0000 http://embeddedgurus.com/stack-overflow/?p=459#comment-747 I absolutely subscribe this article. Any time spent in keeping a project mantainable always saves lots of time in the future, even in the near future. It is better to do it right in the begining, even though the pace of most projects push developers to code fast. Fast in the short term, of course, because in the end, good code always saves time; and having a good quality code base is a big plus. Many times it is difficult to justify the "good code" vs "fast code" dichotomy. I absolutely subscribe this article.

Any time spent in keeping a project mantainable always saves lots of time in the future, even in the near future. It is better to do it right in the begining, even though the pace of most projects push developers to code fast.

Fast in the short term, of course, because in the end, good code always saves time; and having a good quality code base is a big plus. Many times it is difficult to justify the “good code” vs “fast code” dichotomy.

]]>