Live data from Hacker News

Doing the thing is doing the thing

softwaredesign.ing

101–110 of 196 posts

Re: Doing the thing is doing the thing

#102

[flagged]

Yes, but the experience you're describing is just getting stuck due to insufficient experience architecting a solution.

Not saying this is you, but it's so easy for people to give up and sour into hyper-pragmatists competing to become the world's worst management. Their insecurities take over and they actively suppress anyone trying to do their job by insisting everything be rewritten by AI, or push hard for no-code solutions.

Re: Doing the thing is doing the thing

#106

"Doing it badly is doing the thing." This one works for me, and I've learned it from a post on HN. Whenever I feel stuck or overthink how to do something, just do it first - even with all the flaws that I'm already aware of, and if it feels almost painful to do it so badly. Then improve it a bit, then a bit, then before I know it a clear picture start to emerge... Feels like magic.

> Whenever I feel stuck or overthink how to do something, just do it first - even with all the flaws that I'm already aware of, and if it feels almost painful to do it so badly. Then improve it a bit, then a bit, then before I know it a clear picture start to emerge... Feels like magic.

Funny how these things when done by a human is a positive and when done by an LLM is a negative. According to all the anti-llm experts... Humans generate perfect code on the first pass every time and it's only LLMs that introduce bad implementations. And this isn't a callout on this user in specific. It's a generalization to the anti-ai sentiment on HN. If incremental improvement works, incremental improvement works.

Re: Doing the thing is doing the thing

#107

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…

Rimmer planning for his astro-navigation exam sums up the "infinite loop" of preparation.

From the Red Dwarf book and quoted previously:

https://news.ycombinator.com/item?id=28033747

Re: Doing the thing is doing the thing

#109

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 agree that planning has diminishing returns, yet simultaneously nearly every software project I’ve been part of has been under-planned and ended up worse off for it.
Post reply on HN