News for hackers. Stuff that matters.
Re:Why You Shouldn't Interrupt a Programmer by aidenn0 on Monday October 28, 2013 @11:36AM (#6627550)
This is the reason why my productivity has gone down since going from single to having a family. When I was single, I would just cut out early on the days I wasn't in the zone, and get some errands or housework done.

When I was in the zone, I would stay at work until right before I would go to bed.

This way I would spend nearly all of my "in the zone" time doing work.

Now that I have kids and such, I leave at 6 every day regardless of my productivity level, so even though I spend only slightly less time at work, my net productivity is way lower.

Re:Why You Shouldn't Interrupt a Programmer by javajosh on Monday October 28, 2013 @12:29PM (#6627892)
Anyone can take a great photograph. The professional photographer learns techniques to take great photos more frequently.

In a sense, "professionalism" in any field implies a certain "frequency of success". For a programmer, that means learning techniques to accomplish tasks even when you aren't "in the zone". This means learning to get in the zone, how to stay in the zone, and learning to produce when you're nowhere near the zone. This requirement is universal to all professionals, including all professional programmers[1]

I would add that learning to approach your work even when you don't feel like it can sometimes yield surprising insights. Your brain is recoiling from work, but only as it approaches it from certain directions. It is possible to approach a problem from other angles, and getting "in the zone" from another angle can sometimes yield unexpected improvements to the product for the simple reason that you're looking at it in a new way.

[1] There are two categories of professional programmers, the hired guns and the artists. They both want to build great things. The hired-gun wants to build things faster and to spec. To him, "great things" is unambiguously defined as 'the things that will satisfy the customer'. All businesses love a speedy, accurate programmer - especially if they can be speedy and accurate in a non-disruptive way. Such programmers are very good at understanding existing codebases, processes, and doing the minimum work to get the job done. Often they simply do not care about technical debt - (indeed, they are incentivized the other way, to maintain (and even increase) technical debt, every bit of which only improves their negotiating position with the client.)

Meanwhile the artist-programmer success is not defined by conformance to a spec. Success is harder to define - but the artist can define success as getting the time to perfect his creations, traveling ever higher up that diminishing returns curve, going higher than most people are willing to go. This kind of programmer is the dreamer, the architect, the creative. This can be a backend architect, or a front-end perfectionist. They share the common goal of mastery and beauty. Most, if not all, programmer heroes come from this category. And rightly so, I think.

Re:Why You Shouldn't Interrupt a Programmer by sateesh on Monday October 28, 2013 @01:00PM (#6628120)
Nicely put. Yes, programming is part art and we are not like machines that can work no matter in what state we are. But often we mask our procrastination/laziness blaming it on lot many things and waiting for a right moment to magically arrive get the work done.

I am reading 'Dune' now and I found this advice from Halleck to Paul so relevant :

'I guess I'm not in the mood for it today' Paul said.

'Mood ? Halleck's voice betrayed his outrage even through the shield's filtering.

'What has mood to do with it? You fight when the need arises - no matter the mood! Mood's a thing for cattle or making love or playing the baliset. It's not for fighting'

-- Dune, Frank Herbert

Re:Why You Shouldn't Interrupt a Programmer by Mithaldu on Monday October 28, 2013 @02:38PM (#6628854)
While this applies to many things people do, i don't think it applies to programming. Programming is a continuous activity of concentration done over the course of 8 hours, 5 days a week, roughly 45 weeks a year. Meanwhile fighting of many kinds is something that happens in short bursts of extreme focus and excertion.

In fact, programmers have to "fight" too, and it is highly different from their daily work: It is when the software is burning cash and they have to find the problem and implement a fix right now. Most programmers find that they deal with that extremely well, though it usually happens at the cost of the rest of the day.

Re:Why You Shouldn't Interrupt a Programmer by dasil003 on Monday October 28, 2013 @12:03PM (#6627736)
In the same situation I think my productivity is actually equivalent with fewer hours after having kids because it has created an ongoing sense of urgency to get done what I can in the 8:30-5:30 window. In the old days, 4pm was almost like the half-day mark, which personally led to a mental slackness about how much time I had left to accomplish a given task that day.

These days, I sometimes get cut out of the zone by quitting time, but more often than not I am mentally exhausted and ready to go. I'm sure that this would not apply to the most focused and driven programmers, but I'm also sure that a lot of young startup types are fooling themselves that the long hours they put in are giving them better returns than they would get with a bit more sleep, a bit more exercise and a bit more downtime.