6 ms·
I liken programmers to extremely expensive equipment for manufacturing software. When a company invests in expensive equipment like that, it is very important
by jimbokun 13y ago
I liken programmers to extremely expensive equipment for manufacturing software.
When a company invests in expensive equipment like that, it is very important to keep it producing output. So by sending programmers to meetings, your expensive equipment is sitting idle, offline, producing nothing.
Interruptions are like shutting down an entire assembly line. When you turn it in again, it will take time to be running smoothly again.
So to the managers and executives, it is your choice how to utilize this highly specialized, very expensive equipment. You can try to keep it running at full capacity, or frequently start it up and shut it down, take it offline, and leave it sitting idle.
- gbog 13y agoYes but no, because producing code is never smooth, or smooth code production is exactly the characteristic of these coding sessions you can interrupt without great loss.
- jimbokun 13y agoI agree this is the weakest part of the analogy, as software production is so highly variable. You can have days where you see very little come out of the machine, then a great amount of valuable software come out, seemingly all at once. I think, though, it does not invalidate the basic point of keeping the software producers on the task of software production as much as possible in order to maximize output.
- kalhank 13y agoOne client I worked for had a "heads down Thursday", where no one was allowed to schedule anyone in the app dev department for meetings; general consensus was that Thursday's were by far the most productive day of the week
- eru 13y agoMeetings' Thursday might be even more productive. (Ie nobody is allowed to schedule anything on any of the other days.)
- ljf 13y agoUntil it is discovered too late that you are working on the wrong thing.
- a-priori 13y agoIt's a trade-off. Stakeholders want to be able to discuss upcoming work and course corrections, but developers need uninterrupted time to get current work done. When I worked as a team lead I created a rule that there could be no meetings in the afternoons. The daily schedule was that we'd have a morning scrum where everyone would say what they did yesterday and plan on doing today. That was also an opportunity to schedule any meetings for the day, to be done immediately following the scrum. As team lead I considered it my job to take on that burden, when possible, and fill in the rest of the team with the pertinent details afterwards. It worked out fairly well: stakeholders could schedule time any day to talk to the dev team, but every afternoon (at least) was no-outside-interruptions development time.
- philsnow 13y agoDid you survey your team to see when their most/least productive times of the day are ? I usually get the most done in the morning. I would not be as productive if I had nothing but meetings until lunch. (It doesn't sound like "nothing but meetings until lunch" characterizes your team, I'm just making a point)
- a-priori 13y agoIn this case it was a distributed team with most the members in Romania (GMT+2) and Armenia (GMT+4) with myself in Ottawa, Canada (GMT-4/5). So our normal working day only overlapped for an hour or two in the morning. So, we didn't have a choice that way when to hold meetings. At some points in the project my day often ended up being half meetings, half development. Lunch ended up being a break where I'd switch modes from 'team lead' to 'developer'. It wasn't ideal for me, but it was ideal for the rest of the team and I considered that my top priority.
- zanny 13y agoMany programmers (at least me) have varying levels of peak output in a day. Some times I literally can't make my brain work after 2 - 3 hours of in-the-zone work. I just can't read lines off a screen anymore. Other times I can go 24+ hours without breaking a sweat. I think in practice your average programmer can't operate on the 40 hour a week traditional work schedule and actually output solid performance for all 40. On average, at least. So maybe the first businesses to start introducing meetings and such were attempting to pace their SE staff and actually saw positive results, since they still got whatever the maximum output one engineer could put out before their brain went to mush in a week but also had them talking to clients or discussing other things. It is just the industry latched on to bureaucracy without postulating why it might be useful. You want your SE coding whenever possible.
- dubcanada 13y agoThat's pretty much the same as me. But I do know people who can do the 7 hour full force ahead. And interrupting those people generally results in very little getting done. For the rest of us there is always code reviews and emails and other fun things that needs to be handled and requires less brain power (well code reviews should require more but let's ignore that).
- yeukhon 13y ago+1 here. There is also a pressure to get things done when I don't feel like getting things done - as in I don't have the inspirations to write that piece of code / that code is so ugly and hard to write. Then a day or two later I would come up with a better solution and boom, milestone achieved.
- Swizec 13y agoBut without forcing yourself to write that code, the breakthrough wouldn't come in a day or two. The breakthrough will never come. Writing that crappy code that feels like pulling barbed wire through your brain forces you to think about the problem. To look at the corner cases, to really figure out a solution. The breakthrough in a few days is just a cleaner solution you were able to come to after a deep understanding of the problem.
- mathattack 13y agoI think this is a good point. In addition to not "shutting down the assembly line" it's important to set the proper direction. Many interruptions come from poor planning. "Stop doing that, do this," frequently is the result of not thinking through things to begin with. Though I like your analogy, most programmers I know would rather say, "Don't interrupt Picasso" rather than "Don't stop the Lexus factory" :-)
- jimbokun 13y agoPicasso was a machine that produced masterpiece works of art! :)
- chris_mahan 13y agoYou can't stop the Lexus factory (robots). You mean the Toyota factory? (andon cord!)
- sillysaurus2 13y agoMeetings are rarely for communication. They're usually for a manager to validate his authority.
- eksith 13y ago"usually" Is a bit harsh IMO. It can be a lot of times, but then that's a symptom of a much bigger problem. It's hint, more often than not, that the environment is toxic and it may be time to dust off your CV.
- taude 13y agoOr to get an entire team onto the same page?
- jlgreco 13y agoWeird then that the overwhelming majority of meetings at my workplace are scheduled by programmers, not managers. Meetings scheduled by managers stand out from the crowd, but if you count them up, are actually a minority (at least for me).
- GrinningFool 13y agoThat's a sign that you're in a fairly unhealthy workplace culture. Get out! Meetings can be useful tools if you make sure to involve the right people and stay focused. This doesn't require anything special. Just define what you want to decide in the meeting, prepare for it ahead of time, and come to the required decision in the meeting -- discussing as necessary. If you do that, it was a useful meeting. I have one or two such meetings a week at work, occasionally even three. They're rarely scheduled by management, but instead by the engineers building the system. Meetings can also be used to disseminate information.
- govindkabra31 13y agoYou should explore other opportunities, if you feel that way for your current work place.
- jw_ 13y agoSadly true. I like a turn of phrase from Peopleware - "Status meetings are generally ways for the manager to assert their status as manager." I've had many an inexperienced manager sit there and rotate through talking to each minion in turn, while the other N-1 minions sat silently thinking about what they were going to have for lunch today. Even better are the "stand-up" meetings that have everybody sitting around for an hour every morning, totally killing any motivation or energy for the day. Thankfully I've escaped that sort of nonsense, but it seems like it can pop up anywhere.
- ljf 13y agoWhile I agree - the issue is when nearly everyone in a dept is 'expensive equipment' - do you send the most junior person? The most experienced? Get someone non-technical to go to meetings and collect requirements? But what happens when they are asked to estimate (on the spot) and discuss the possibility of new features? While I totally agree with not disrupting working people - I don't think you should ring fence them out of input in the process of defining product - we've all seen what happens in that case - "requirements" nailed down by a non technical team. And it's even more wasteful to have people working on the wrong things, or worst still being given so overly defined work that there is no room for them to add any value or find a better and faster solution. While good management can help shield teams from unwanted intrusion - everyone needs to get involved in the process of manufacturing great software - which doesn't just mean attending meetings, but taking time to actively plan and consider the issue before the session. If your company values your input enough to bare the cost of asking you to be involved, then you should look upon that as a positive thing (unless they REALLY are just wasting your time with 'busy' meetings, which are really just wasting everyone's time - and it's a sign of either having money to burn with limited direction or a company going the wrong way fast)
- jimbokun 13y agoWell 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.
- OvidNaso 13y agoNow if only we could install hardware upgrades...
- ljf 13y agoDon'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.
- moron4hire 13y agoI, on the other hand, liken programmers to people.
- deleted 13y ago[deleted]
- Finster 13y agoMy favorite is when I try to take my laptop to a meeting so I can, you know, actually get some work done. And then, I'm lucky to get 5 minutes of useful work done for each hour of meeting.
- alexchamberlain 13y agoI disagree; meetings are an opportunity to discuss architecture and allow your brain to relax between hardcore programming sessions.