4 ms·
I'd learn to think while you walk. Think through problems. Work out solutions. I find that driving/cycling/walking is really really valuable thinking time. I do
by axod 16y ago
I'd learn to think while you walk. Think through problems. Work out solutions. I find that driving/cycling/walking is really really valuable thinking time. I don't think trying to type at the same time would make it quite as useful.
I think one of the reasons driving/cycling/walking is so productive thinking time is precisely that you are constrained. You can't just waste time, you can't launch into stupid half thought out plans.
Edit: I forgot to mention, the same can be done with babies. When you have a baby, and have to feed it, rock it, clean up after it, change it etc. You're forced to just think about problems. It's excellent thinking time. Babies do come in useful after all!
- anthony_barker 16y agoI want to get some real work done. Like they are doing at the Mayo Clinic. http://www.youtube.com/watch?v=CPjN07JyVjo&NR=1 http://www.youtube.com/watch?v=CPjN07JyVjo&NR=1 http://www.youtube.com/watch?v=pcE_JHx5_gA http://www.youtube.com/watch?v=pcE_JHx5_gA
- CyberFonic 16y agoMode B is work! Personally, I carry a moleskin notebook and mostly think and jot down notes as I go. When I'm back at my desk, I can switch into mode A and be far more productive. All the planning, design has been done. If you are into bulk writing, then I'd pick a twiddler and text to speech rather than a heads-up-display.
- s-phi-nl 16y agoThis 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.