3 ms·
I'm the programmer in my startup. I'm also the guy with the day job. We weren't making the necessary progress until we actually analyzed why I wasn't being as
by Travis 16y ago
I'm the programmer in my startup. I'm also the guy with the day job. We weren't making the necessary progress until we actually analyzed why I wasn't being as productive as we needed in the evening and weekend situations.
Turns out that I basically needed an assistant. Since I was building features for my cofounders, we decided that we should pair program (except they don't know how to program). So they act as the "feature manager" and come up to my apt for 2 hours a nights a week and we work together.
A few key points: the feature managers MUST have their thoughts detailed out. In order for me to crank out code, I need to know exactly what to do. I think there's a cognitive cost when you have to shift from implementation to design mode (and even testing mode). You'll be amazed how much it helps to push those responsibilities out of your brain (and yet still get fast feedback).
Doing this, we've gotten probably 4 months worth of work done in the last month, without me increasing hours. Seeing how efficiently I can implement features made my cofounders realize that it's worthwhile to pay me even 1/4 time, so that I can reduce hours elsewhere. Been a real game changer for our company.
- taa 16y agoI'm in the same boat as you and totally agree with you that it is necessary to separate design from implementation and assign these tasks to different people in order to maintain or boost productivity. We've done the same in my startup and it's working great. Further, we feed off each other's progress and try to stay in sync, which keeps us motivating and grinding.