Jay @Jay - 14h
Good morning ✌️🧡
Jay @Jay - 13h
For now yeah 😂 I gain a lot of clarity from meditating on people's responses to those.
Oh wait I just thought of one.
Nah it fell flat. It's too hard to express. Basically, there's something to be said about the unmaintainability of code that's not written with the goal of being maintainable. But there's something very holistic about code that is.
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.
Jay @Jay - 12h
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.
