25 ms·
I think one of the biggest errors a bad programmer makes is seeing 'bad' code everywhere. Sure, some code stinks but just because some code doesn't do something
by VBprogrammer 15y ago
I think one of the biggest errors a bad programmer makes is seeing 'bad' code everywhere. Sure, some code stinks but just because some code doesn't do something the way you would have done it doesn't make it bad.
If you do have to complain about some piece of code then do so in concrete terms:
- Presense of bugs
- Lack of error handling
- Preformance issues (real ones, that cause real problems)
- Security issues
- Poor robustness
- Redundancy
- jroseattle 15y agoYour username doesn't aid in your argument against criticism of bad code. Just sayin.
- VBprogrammer 15y agoActually, that was a username I've used for 13 years. Currently I'm mainly developing in TCL professionally and Python personally.
- jroseattle 15y agoIt's in jest. There's something funny about the username "VBProgrammer" in a discussion about identifying bad developers, from the stereotypical POV. Disclaimer: I started as a VB guy myself. Now I fall in the C# and Python camps.
- sophacles 15y agoI'd add: - bad factoring - overly complex or overly simplistic object model - not extensible (although this itself is not strictly bad, as spec changes are pretty hard to predict, but sometimes it is requires more effort to make something not extensible than it is to make it extensible these cases are a problem unless there is a good reason for it). - abstractions that introduce more effort (factory factories...)