3 ms·
That definitely has resonance for me. When I think back to the times I was putting in a lot of extra hours, I wasn't getting results in proportion to the time
by wpietri 6y ago
That definitely has resonance for me.
When I think back to the times I was putting in a lot of extra hours, I wasn't getting results in proportion to the time spent. Partly because being tired your capacity declines. Partly because, in retrospect, we were all performing hard work as a way of impressing clients, bosses, and each other. And partly out of some phenomenon related to "revenge bedtime procrastination" [1] where I just ran out of self-discipline and would secretly take the breaks I should have been taking anyhow.
Some years back I hired movers. Previously my experience moving had been the casual thing with friends and family. We took our time, joked around, took breaks, kept entertained. But these movers were relentless. They never rushed and never seemed stressed, but if there was work to do they were on it until the work was 100% done. And when there wasn't work to do, they were perfectly chill.
I keep coming back to the memory as how I want to work. No bullshit, hard work when it's time to work, and really letting go of it at quitting time. It's harder to achieve for software, but I will keep iterating in that direction.
[1] https://www.bbc.com/worklife/article/20201123-the-psychology-behind-revenge-bedtime-procrastination https://www.bbc.com/worklife/article/20201123-the-psychology...
- antisthenes 6y ago> They never rushed and never seemed stressed, but if there was work to do they were on it until the work was 100% done. And when there wasn't work to do, they were perfectly chill. That only works because their job is perfectly defined. The scope is finite and always in sight. I'm not quite convinced this would work for creative work or a project that's somewhat open-ended in features and/or scope. To give an example of this: I can do this type of no-bullshit relentless work when I exercise in a gym. 1.5hrs of a strict routine with a fixed number of reps. And a hard stop after that. Never found the same type of ability for deep work.
- wpietri 6y agoFor me, the right approach is what you'll see in Lean processes. You pick the next few clear steps and break them down into small units of work, each of which delivers value. Then you knock them off at a solid pace. We managed that here: https://williampietri.com/writing/2015/the-big-board/ https://williampietri.com/writing/2015/the-big-board/ And that's despite the fact that it was a startup. It helped that my cofounder had 3 kids under the age of 5. He came in on time and he left on time. We all busted ass while we were there, but when we left, we mostly left. One real test for me was when I had to take weeks off to help a sick relative. Even though I was the technical cofounder and had been involved in every bit of the code, I got maybe two calls where they really needed me. It was a sign that we're built a real cross-functional team.