News for hackers. Stuff that matters.
Re:Why You Shouldn't Interrupt a Programmer by jimbokun on Monday October 28, 2013 @11:25AM (#6627486)
Well let's see if I can stretch my metaphor to address your points. :)

Equipment needs to be maintained to continue working at peak efficiency. Sometimes it needs to be taken offline for repairs or routine maintenance. Or maybe you realize you need to switch over an assembly line to build a different product or model more important to your bottom line.

So, yes, there are times when the software manufacturing equipment will not be manufacturing software. But you want to keep that time to a minimum and understand the cost to the business of having the equipment offline.

Re:Why You Shouldn't Interrupt a Programmer by ljf on Monday October 28, 2013 @04:07PM (#6629424)
Don't get me wrong, I totally agree with your point, but I meet a fair few devs who don't want to get involved in meetings - then complain about lack of information or clarity later in the project.

But other distractions as shown in the comic, I totally agree with doing everything teams, companies and individuals can do to remove all those distractions and keep people working however best works for them.

Re:Why You Shouldn't Interrupt a Programmer by DanBC on Monday October 28, 2013 @04:11PM (#6629445)
> but I meet a fair few devs who don't want to get involved in meetings - then complain about lack of information or clarity later in the project.

Send a manager to the meetings, and get that manager to do a nice write up, with action points, afterwards. Email that round the team.

The people with people skills do the people stuff, and the people with coding skills don't "waste" a couple of hours in a frustrating meeting.

Re:Why You Shouldn't Interrupt a Programmer by OvidNaso on Monday October 28, 2013 @02:03PM (#6628594)
Now if only we could install hardware upgrades...