Build slow and methodical, not 'fix it in the first patch'
Quote
if you go into something with a slow, sort of methodical, built, you know, approach to building it, you don't you don't have to fall victim to a lot of that stuff.
Episode 129: Turkish Punk (episode page, opens in a new tab) 00:12:51 (play audio from this timestamp, opens in a new tab)
Speaker-labeled
Summary
After 15 years of VC-driven 'move fast and break things', the industry has gotten used to constant outages. A slow, methodical approach to building avoids falling victim to most of that.
Also said
Episode 149: Scrape my JSON (episode page, opens in a new tab) 01:12:13 (play audio from this timestamp, opens in a new tab)
when you got a day job and a bunch of different products to manage, you feel like you do a terrible job at all of it. And I think in the only way that you manage those expectations for yourself and your product, is by going slow, and taking time and doing very incremental
Speaker-labeled
Episode 150: Eshitification (episode page, opens in a new tab) 01:31:27 (play audio from this timestamp, opens in a new tab)
So I think the answer really is a general slowing down and focusing on the quality on tightening up the things that already exist.
Speaker-labeled