3 ms·
This reminds me of edw519's comments on how he codes fast http://news.ycombinator.com/item?id=1544453 http://news.ycombinator.com/item?id=1544453: "Very fast.
by s-phi-nl 16y ago
This reminds me of edw519's comments on how he codes fast http://news.ycombinator.com/item?id=1544453 http://news.ycombinator.com/item?id=1544453:
"Very fast. Let me explain.
"I work in 2 modes: (A) At the computer and (B) Away from the computer.
"When I'm in Mode A at the computer, I'm cranking out lines of code, testing, revising, testing, revising, etc. This process must be very fast. Several hundred lines of code (or whatever) in less than an hour. A complete cycle in less than a couple of hours. My guideline is that if I'm not working that fast, then I must not be prepared to work that fast, so I don't deserve to be at the computer. I should be in mode (B).
"Mode B is generally much slower. Reviewing code, specs, or notes. Refactoring code. Laying things out with pen and paper. When I have enough work clearly laid out, I know it's time to get back to the computer and return to Mode A."
- thecircusb0y 16y agoI've seen/learned this from many programmers. Also just another point. don't over work yourself, we're all humans (except those damn bots) and you have to give yourself down time to let your brain simmer on the latest and greatest thoughts.