3 ms·
Very well written article. Very amusing commentary threads. But let me suggest something that I have tried. In one of my most intense coding periods in my care
by wglb 12y ago
Very well written article. Very amusing commentary threads.
But let me suggest something that I have tried. In one of my most intense coding periods in my career, I kept a log of the bugs that I created and had to fix. My bug rate declined measurably. (This is one of the old notebooks that i dearly wish I kept--was left at that job when I moved on.)
There is a relevant quote that I can't locate from someone famous who said that he would keep a list of his mistakes in his wallet and refer to it from time to time. A boss of mine who was adventurous about experimenting with new technology said "I don't know very much about it, but I do know 50 ways that wont't work". This has led me to asking someone who claims to be an expert "Tell me three (or five) things that won't work" in their field of expertise.
The advice from the article For individuals, the trick is to be your own devil’s advocate: to think through how your favored conclusions might be misguided; to ask yourself how you might be wrong, or how things might turn out differently from what you expect seems spot on.
- jameshart 12y agoA coaching tip I always give to developers: you don't know enough about a topic if you can only think of one way to solve a problem. If you only know one way to do it, how do you know it's not the worst one? Take the time to sit back and enumerate a few ways of solving the problem and figure out which one's best in this situation. Why are you rejecting those other solutions? Are you sure those reasons are sound? Are you sure they don't apply equally to the solution you've selected?