Now Playing · New

Temp

00:00 / --:--

Sunk cost is a liar. In this one I talk about deleting eight months of work — twice — and why that turned out to be the most useful thing I did all year. We get into refactoring guilt, knowing when a rewrite is wisdom vs. procrastination, and the small reframe that finally let me ship.

Throwing code away isn’t failure. It’s tuition — and I’d already paid it.

If you’ve ever stared at a codebase you’ve outgrown and felt trapped by the hours you sank into it, this episode is for you. No hustle-culture pep talk — just an honest postmortem from someone learning in public.

Show notes

// the gist

  • 01 How to tell when a rewrite is genuine progress and not avoidance dressed up as productivity.
  • 02 The "tuition" reframe — counting thrown-away code as paid learning, not wasted time.
  • 03 A two-question check I run before starting any rewrite, so I don't loop forever.
  • 04 Why shipping the ugly third version beat perfecting the first two.

Transcript

// auto-generated

Jorge: So I want to start with a confession. Last month I opened the project I'd been building since summer, looked at it for about ten minutes, and then I deleted the whole thing. Branch, history, all of it.

// listen on

SP

Spotify

↗

AP

Apple Podcasts

↗

YT

Youtube

↗

RSS

RSS Feed

↗

◆ Resources & links

LV

Laravel Docs

Eloquent relationships guide

↗

BK

Refactoring (M. Fowler)

The book I keep coming back to

↗

RP

My repo (v3)

The version that finally shipped

↗

EP

EP 011 — Almost Quit

Referenced at 18:30

↗

◆ Resources & links

MP3

Full episode audio

mp3

PDF

Transcript

180KB

MP3

Rewrite checklist

92KB

JD

Jorge Díaz

Host of Beers & Code. Documenting the messy road from IT to full-stack, one episode at a time.

◆ Keep LIStening

More episodes

Temp

Sunk cost is a liar. In this one I talk…

Mindset