It's just that that's the biggest tradeoff you make with the Silicon Valley "go fast and break things" strategy.
You make something quick and dirty, and you either take the time to slow down and refactor it or it slowly rots and becomes riskier to run with time. You're borrowing time from your future or risking abandonment of the software to have something that works today.
Ah that makes perfect sense now. Guessing this thought is a response to the vibe coding meme of late. I tend to be too perfectionist leaning in things I do (not code so much), that I feel it slows me down a bit overall. I think I would benefit from more 80% juice in first squeeze mentality sometimes. Point taken though
Maybe I'm just thinking about it more now looking at the range of code quality across Nostr, but I've been for a long while now on the side of clean, maintainable code and a low time preference.
Though, like you said, you can totally get 80% on the first squeeze BUT, embody the functionality of what you just made in a test, then refactor and clean up the draft. What you have then is a capital asset you can iterate and build on, rather than a liability that'll you'll have to pay down later with interest when it breaks.
