4 ms·
Don't convince yourself it's not possible. I've done it and it was the norm at my last startup. For me, I can't do more than 60-70 hours a week, but certainly 3
by keefe 17y ago
Don't convince yourself it's not possible. I've done it and it was the norm at my last startup. For me, I can't do more than 60-70 hours a week, but certainly 30% is a low level of productivity.
- sausagefeet 17y agoI think it depends on how you define productivity. I have had jobs where people (even the programmers) felt that if you weren't typing code you weren't working. In my latest job I luckily don't have managers harassing me at all and find I spend a lot of time just thinking about how the system we are building should work and not much time coding, but I push solutions out just as fast, with less fixing down the road.
- abraham 17y agoIf a groups definition of working is just writing code it seems likely they will hit a wall where they are no longer improving. They might know their languages APIs better but they lose out on much of the larger communities gained knowledge.
- antirez 17y agoExactly, most of the time should be spent thinking about how to make the system simpler, writing less code.
- keefe 17y agoI'd define it as milestones per day. It's important to set small bite sized goals imho. Any programmer who has a boss thinking that !writing code -> !working needs to find a different job asap.