Doing the thing is doing the thing
11–20 of 196 posts
Re: Doing the thing is doing the thing
#12Re: Doing the thing is doing the thing
#13This is very similar to [1] (as discussed here [2]). It is a good message though, which is why I remember the earlier post at all. 1. https://strangestloop.io/essays/things-that-arent-doing-the-... 2. https://news.ycombinator.com/item?id=45939431
Re: Doing the thing is doing the thing
#14Re: Doing the thing is doing the thing
#15At work we built something from a 2-page spec in 4 months. The competing team spent 8 months on architecture docs before writing code. We shipped. They pivoted three times and eventually disbanded.
Planning has diminishing returns. The first 20% of planning catches 80% of the problems. Everything after that is usually anxiety dressed up as rigor.
The article's right about one thing: doing it badly still counts. Most of what I know came from shipping something embarrassing, then fixing it.
Re: Doing the thing is doing the thing
#16I needed this today. Currently questioning my career choices, as I hit my first wall where people are involved. Gave me quite the headache.
Re: Doing the thing is doing the thing
#17"Everybody wants to be a bodybuilder but nobody wants to lift no heavy ass weights!"
Re: Doing the thing is doing the thing
#18As a person with ADHD, I feel personally attacked.
Re: Doing the thing is doing the thing
#19I used to think this. Then I noticed how often "preparation" became its own infinite loop. At work we built something from a 2-page spec in 4 months. The competing team spent 8 months on architecture docs before writing code. We shipped. They pivoted three times and eventually disbanded. Planning has diminishing returns. The first 20% of planning catches 80% of the problems. Everything after that is usually anxiety d…
"Preparation" isn't mentioned explicitly, but by my reading it would come firmly under "is not doing the thing".
Re: Doing the thing is doing the thing
#20I used to think this. Then I noticed how often "preparation" became its own infinite loop. At work we built something from a 2-page spec in 4 months. The competing team spent 8 months on architecture docs before writing code. We shipped. They pivoted three times and eventually disbanded. Planning has diminishing returns. The first 20% of planning catches 80% of the problems. Everything after that is usually anxiety d…