4 ms·
Developer productivity is nearly a solved problem. What isn't a solved problem is to convince the managers about the solution. Because the solution is radical.
by kamaal 14y ago
Developer productivity is nearly a solved problem. What isn't a solved problem is to convince the managers about the solution.
Because the solution is radical. Your ordinary corporate manager is made to believe that, team work + tools + a bit of odd micro management(without a clue about what he/she is managing) thrown around is what takes to win. The fact is that team work matters, but make-or-break deal for ambitious projects is mavericks working full steam for a good amount on project's net demands.This requires a total distraction free environment, a uninterrupted stretches of time(tuits), choice of tools(both hardware and software) and many times managers getting out of the way and letting the actual contributors do their job in peace.
I have thought this over many time, hacked and tweaked my schedule many times and this is what I have come to. Recently every time I decide to work from home. A day before, I write down clearly without any ambiguity the list of tasks I want to accomplish the next day. I start working insanely early. I start at around 3 AM in the morning, The energy level are really high in the morning. I also take in a lot of water. Apart from a break fast break at 8 AM. I work all the way up to 12 in the after. That's 8 hours of uninterrupted time.
The remaining day I generally work on a side project, or some thing I love doing- like play a musical instrument. Or I just continue doing my work. Then to go back to sleep for 6 hours at least.
The great thing about this schedule is, by the time somebody is up and running throwing distractions at you, you are done with your work.
Ironically despite manifest benefits of this schedule, management finds it 'not good team work'(Read- your idea is too radical and is a threat to my designation).
- wpietri 14y agoI'm excited to hear that you've found a schedule that works for you, but you too quickly dismiss teamwork. There are perfectly fine projects that only take a single developer. There are some that need a few people working as a loose group. But if you've got something that actually needs a team, then bad teamwork really is a problem.
- kamaal 14y agoI love team work too. Team work means knowing our mutual interests and how we need to work together to meet our common goal(Which is to make the project successful). But once I am done knowing that, I want space for myself to shut down all distractions and do my job. I believe that is what the managers want too, then they need to understand as a developer I'm most productive when I get at least two uninterrupted stretches of time during my work day.
- borski 14y agoPerhaps a better term for what the parent may have meant was 'collaboration' rather than teamwork. There are a lot of projects that truly require collaboration, and that's hard to do when you're only working when other people aren't.
- KurtMueller 14y ago> I start working insanely early. I start at around 3 AM in the morning, The energy level are really high in the morning. I also take in a lot of water. What contributes to these highly productive periods? How do you consistently get yourself "in the mood" to be productive? Do you find yourself getting distracted at all (i.e. the internet, music, news, etc.)? > Apart from a breakfast break at 8 AM. What do you eat for breakfast? What does your breakfast period look like?
- kamaal 14y agoBasically no external distractions is what contributes to scoring most productivity points at that time. I also pick and do the most interesting pieces of work first in the morning. Avoiding distractions really is a matter of self discipline. I think the best time to check HN/twitter/FB is when you totally tired, not when you are fresh and full of energy. I generally eat fruit + milk + cereal for breakfast.
- scott_w 14y agoI agree that working from home requires you to have a clear list of tasks to complete. However, I dispute that it's the best way to work. It puts a larger overhead on communication. I've noticed that extended periods of working alone cause development to drift away from the core requirements because of this. I find what works for me is being in the office most of the time. It allows you to pick up on a lot of stuff that you just can't do when you're not there. If the rare occasion comes where I need no distractions to blitz out a ton of code, then I arrange a day to work from home.
- kamaal 14y ago>> If the rare occasion comes where I need no distractions to blitz out a ton of code You must have super levels of concentration and be able to quickly recover from my context switches. In my case, Meetings fundamentally imply a good chunk of the day goes into doing nothing.