Live data from Hacker News

Doing the thing is doing the thing

softwaredesign.ing

11–20 of 196 posts

Re: Doing the thing is doing the thing

#13
post #4

This 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

The discussion is going to be so similar, this really ought to be marked as a [dupe].

Re: Doing the thing is doing the thing

#15
I 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 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

#19

I 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…

I think you may have slightly misunderstood the article.

"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

#20

I 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…

Is it always like that? I worked in teams where we had some planning beforehand (months, like in your example). We shipped just fine and the product started to bring money. I guess it depends, as usual.
Post reply on HN