Slashdot Mirror
Finding the Programming Zone?
SlashDotDashDot asks: "As a developer for 20+ years, I've developed a fairly fine tuned way to find 'The Zone' for optimal programming - a combination of furniture arrangement (PC and chair), lighting
and music. I also have a pretty good sense of what time of day is best for working on a particular set of problems. But this is what works for me. My company is growing and I'm needing to mediate working conditions between my clients and consultants. This has me wondering what others have found important for finding 'The Zone' in their programming lives. How fast can you get there? How long does it last? What do you do that helps keep that state? What are the major interrupters?" We also touched on this issue in a similar article, last year. However, many of you may have ways of attaining "the zone" that don't depend on any of the factors listed above. If you have a method that works for you, please share. It may work for others.
I'd put $1,000 down right now - there are more people writing code for a living than writing novels. Which one is easier?
Let's stretch this a little farther, shall we? Which is harder, being a surgeon or a programmer? I'd put $5,000 down on that one, right now. But somehow, the surgeons end up motivating themselves to go to work and do their job whenever it's required, not just when they "can get into the mindstate".
When working with other people, professionals find a way to just do it.