Friday, June 12, 2009
Developer Ignorance AntiPatterns
Here are but some of the ways that developers continue to remain ignorant.
- Ignoring the latest community techniques and continue to develop software the way folks did ten years ago.
- Abusing the phrase unit testing by referring to actually doing the testing. They may choose a list such as do A then B then C and then the output should be D, if it's not then something is busted.
- Developers who don't unit test their code then get upset with QA when bugs are found that demonstrate the fact that they don't unit test.
- Having stupid debates on tabs vs spaces.
- Copying code from another application they've worked on containing the functionality they want to use but not changing the variable names.
- Not understanding the difference between "I need to get this done" and "I need to get this done here".
- The phrase "runs on my box".
- Believing that their code is so clear that they don't need comments.
- Rebooting is the first line of defense.
- Spelling mistakes
- Lack of focus on the customer and their needs
- Thinking that customers know what they want.
- Believing that catching (and possibly ignoring) an exception means preventing a bug.
- The web is stateless and the browser isn't part of your application.
- Ignorance of socially acceptable bathing habits.
- Inability to take pride in making mistakes.
- Ignorance of threading.
- Complacency with duplicate code.
- The lack of desire to continually improve.
- Failure to appreciate that software has no value in and of itself, but only adds value when it is used for something.
Links to this post: