2 ms·
There are a couple of implicit fallacies in the follow up comments that bug me. 1. Someone asked if the badly written code was really causing any problems, and
by jimbokun 17y ago
There are a couple of implicit fallacies in the follow up comments that bug me.
1. Someone asked if the badly written code was really causing any problems, and then everyone thereafter seems to just take as an assumption that badly written code does not create any real problems. Well, badly written code often does cause performance problems and disguise bugs. I have inherited code bases where things were taking ridiculously long because the code was a convoluted and almost incomprehensible mess. Making it simpler and more comprehensible was a necessary prerequisite to make it operate at a reasonable speed.
2. There seems to be an assumption that you can write code rapidly or comprehensible code, but not both. In my experience, programmers who write incomprehensible code are not more productive than the programmers who write comprehensible code, often the opposite. There is no polite way to say this, but incomprehensible code is more often the result of less knowledge or intelligence than it is the result of a desire to get a lot done. Furthermore, stopping to think before coding can often lead to much shorter development times than just diving in and typing the first thing that pops into your head.
When I have been in the role of technical person with non-technical management, my implicit approach is "evaluate me on what I produce and how quickly I produce it, but stay out of the code." If I am being hired because of my knowledge of how to make computers do what you want, evaluate me on that, and let me figure out the best route to get there.