The Secret of Fast Programming: Stop Thinking »
4 points by jkoppel
4 points by jkoppel
This is kinda shit advice. You should think more and code less.
Think for two hours and find a 4 line diff instead of mindlessly coding for 30 minutes to build a 400 line diff that you need to debug for 5 hours.
From reading only the title I had the same thought: “is this a defense of the tactical tornado? ugh”. But that’s not what the article says.
My reading is: “if you’re hesitating, notice what you’re uncertain about, and do work (research / experiment / talk to colleagues) to resolve that uncertainty”. Don’t try to armchair your way through a problem.
I think this is a long winded way of saying you should do research and think up front?