3 ms·
I average about 5.5 hours of focused coding per day. If I really really push hard, I can get to some 6.5, sometimes even 7. That's normal and I consider myself
by Swizec 13y ago
I average about 5.5 hours of focused coding per day. If I really really push hard, I can get to some 6.5, sometimes even 7.
That's normal and I consider myself very productive. But here's the real question, how do you present this info to clients/bosses/entrepreneurs without them throwing a big hissy fit?
This is a big problem when working with people who are heavily and directly invested in the business you're helping because they feel like they're productive 12+ hours a day and feel that you should be too. Most of the time they're just fooling themselves, or their idea of productivity is so different from an engineer's that it's nearly impossible to compare.
Furthermore, so far everyone I've said "Dude, you're not even half as productive as you think" to directly got grossly offended by my suggestion.
I've been trying to get to the bottom of these for a year and a half now (writing a book about this stuff) and I can't say I'm much closer to a solution.
PS: the worst part of this equation is that you're often asked to look productive for 8 or 9 hours a day because that puts people at ease. That makes them feel they're paying you fairly, even though you could easily do the same amount of actual focused work in 7 hours and spend the rest of that time doing other things.
- pedalpete 13y agoI bet if you get them to REALLY think about it, they know they are not productive more than about 4-5 hours per day. If they spend 20 minutes writing an e-mail, is that 20 minutes of productive time? I bet it's really only 5 minutes of what is considered 'productive', because they didn't write the e-mail for 20 minutes, they edited for 15, checked other e-mail, etc.etc. When they go to a meeting and it starts out with niceties, and talking about progress updates, etc. etc. Is that 'productive'? Necessary, yes, but productive? No. We need to look at programming the same way. When I'm setting up my environment, I'm not being productive. When I'm researching a bug I'm fixing, I'm not being productive. When I try a fix and it doesn't work, I'm not being productive. When I'm looking up the most efficient way to write a method, I'm not being productive. When I'm completely focused on coding, I'm at my most productive. I use a pomodoro timer, and if I really pay attention, I'm hopefully productive for 20 of the 25 minutes. If I get a few of those a day, I'm happy. That's the productivity of our job. The sad trap I fall into is that if I've been productive for 4 hours in a day, I normally stop being productive, rather than continuing to push through, which I know I should do.
- joshlegs 13y agoas a former journalist, I have to disagree that editing is unproductive time. Saying exactly what you mean to say is extremely valuable, well-invested time. "I would have written you a shorter letter, but I didn't have the time." Concise emails really ease the workload by reducing inefficiencies.
- bottled_poe 13y agoTotally agree with this. I'm a software engineer and I would estimate that half of the time I spend writing emails is formatting. I believe this is productive as it takes less effort to communicate. The point here being that communication requires effort by two parties.
- greenyoda 13y ago"When I'm setting up my environment, I'm not being productive. When I'm researching a bug I'm fixing, I'm not being productive. When I try a fix and it doesn't work, I'm not being productive. When I'm looking up the most efficient way to write a method, I'm not being productive." All the activities you mentioned are part of what you're being paid for as a developer, so you should consider yourself to be productive while doing them. If your employer thought that setting up your environment wasn't an essential part of your job, they'd be paying someone else to do it for you. And if they don't want you to write crap code, then finding an efficient way to write a method is also an essential part of your job, and thus productive. And how can you possibly fix a bug without first researching it to figure out the exact conditions that cause it to occur? Even meetings are productive, provided that they allow people to come to an agreement on how to solve a problem (rather just being for status reporting that could be done better with an automated tracking system). "When I'm completely focused on coding, I'm at my most productive." What if that code turned out to be the solution to a problem that didn't actually exist? Would you still think you were productive just because you were completely focused on coding at the time? Now, look at the other side: Let's say that during a meeting, you figured out that some piece of code that your company wanted you to write was completely unnecessary, and it saved them hundreds of hours and thousands of dollars. Wouldn't that be productive? And if you refactor 1000 lines of code to do everything it did before with just 100 lines of code, is your productivity negative because you threw lines of code away? As developers, we're paid to solve business problems, not just to generate lines of code.