4 ms·

- No hour a day (conservatively…) lost to meetings and other activities that exist to generate data for managers to make pretty graphs out of. - No hour a day

- No hour a day (conservatively…) lost to meetings and other activities that exist to generate data for managers to make pretty graphs out of. - No hour a day lost on PR reviews (reviewing and being reviewed). - No hour a day pairing on someone else’s task. - No two hours lost because some part of your hellishly-complex stack and set of alpha-quality vendor tools decided to shit itself today for no reason. - No hour babysitting yesterday’s code through CI and testing et c. - No hour a day lost to context-switching from the above and a dozen other distractions. - Oh look there’s only an hour left in which to actually produce code in one eight-hour day.

moribvndvs 3y ago
I’m an architect at my company but we’re in a bind with a particular project that I had started a couple years ago, so they temporarily assigned me to basically one-man it over the finish line. Aside from the stress of the deadline and knowing that I’m going to get stuck being the expert on this project forever, it’s been pretty nice (and productive) just working in peace and quiet with no bullshit scrum ceremonies and navel gazing as distractions. Actually reminded me of why I like programming, and that the things I hate about my career is the fact the organizations spend a lot of time keeping you from actually performing it for some reason.
badsectoracula 3y ago
> No hour a day (conservatively…) lost to meetings and other activities that exist to generate data for managers to make pretty graphs out of. IIRC even in the Doom 3 and probably also Rage days Carmack had mentioned that they didn't really do any meetings, if they needed they just discussed things in the kitchen (or something like that). It did help that the team was small though (IIRC Doom 3 was made by ~25 people total).
another2another 3y ago
>- Oh look there’s only an hour left in which to actually produce code in one eight-hour day. Usually around 7pm, once everybody's left for the day.

moribvndvs 3y ago

I’m an architect at my company but we’re in a bind with a particular project that I had started a couple years ago, so they temporarily assigned me to basically one-man it over the finish line. Aside from the stress of the deadline and knowing that I’m going to get stuck being the expert on this project forever, it’s been pretty nice (and productive) just working in peace and quiet with no bullshit scrum ceremonies and navel gazing as distractions. Actually reminded me of why I like programming, and that the things I hate about my career is the fact the organizations spend a lot of time keeping you from actually performing it for some reason.

badsectoracula 3y ago

> No hour a day (conservatively…) lost to meetings and other activities that exist to generate data for managers to make pretty graphs out of. IIRC even in the Doom 3 and probably also Rage days Carmack had mentioned that they didn't really do any meetings, if they needed they just discussed things in the kitchen (or something like that). It did help that the team was small though (IIRC Doom 3 was made by ~25 people total).

another2another 3y ago

>- Oh look there’s only an hour left in which to actually produce code in one eight-hour day. Usually around 7pm, once everybody's left for the day.