4 ms·
Do you do any of the following things? Start a project by "hitting the ground running" and writing code. Fail to write documentation unless under external pres
by contingencies 8y ago
Do you do any of the following things?
Start a project by "hitting the ground running" and writing code. Fail to write documentation unless under external pressure. Deeply aware of the powerful and superior features of your favorite languages. Have a considered view that long term systems maintenance irrelevant to most software design. Frequently roll performance optimizations in to your code.
If so, you are probably a bad programmer.
- occamschainsaw 8y agoI agree on the other points. Can you elaborate on how "Deeply aware of the powerful and superior features of your favorite languages" makes one a bad programmer? Not trying to be sardonic, just want to know how to improve my programming skills.
- contingencies 8y agoIt is generally accepted that "right tool for the job" is a desirable philosophy.
- AnimalMuppet 8y agoIf you are "Deeply aware of the powerful and superior features of your favorite languages", then you probably are too deeply caught up in language fanboy-ism to actually understand the merits and disadvantages of your favorite languages compared to the alternatives. (You're probably also being a jerk to people who aren't fans of your languages.) They're tools. They're not rock bands. Don't get caught up in fanboy-ism.