Re:The four golden rules to be a better software developer.
by bad_user on Tuesday November 10, 2009 @10:59AM
(#933261)
I think you just scanned the article.
Rule 1: My code is crap ... this means exactly what you are saying ... there are always better ways to do it, and when a problem arises it's probably your fault more often than not.
Rule 2: I care about my code ... programmers definitely should care about their code, but should care even more about their current projects. There, happy?
Rule number 3: My opinion about my own code is wrong ... this happens more often than you think, and not realizing that your mental model might be wrong is dangerous.
Rule number 4: My manager doesn't care about my code, and he pays me ... this is the norm. You're arguing semantics here.
The manager cares about the project. You could argue that the manager indirectly cares about the quality of your code, and you would be right, but then again I haven't seen many managers getting upset about a project with lots of duct-tape code, as long as it does the job.
Rule 1: My code is crap ... this means exactly what you are saying ... there are always better ways to do it, and when a problem arises it's probably your fault more often than not.
Rule 2: I care about my code ... programmers definitely should care about their code, but should care even more about their current projects. There, happy?
Rule number 3: My opinion about my own code is wrong ... this happens more often than you think, and not realizing that your mental model might be wrong is dangerous.
Rule number 4: My manager doesn't care about my code, and he pays me ... this is the norm. You're arguing semantics here.
The manager cares about the project. You could argue that the manager indirectly cares about the quality of your code, and you would be right, but then again I haven't seen many managers getting upset about a project with lots of duct-tape code, as long as it does the job.