I know, I know it's been a minute. Want to know why?

I've been sitting on this newsletter for weeks because "it wasn't ready yet." The irony? It's about why perfectionism is killing our projects.

So screw it. Here we go. Typos and all.

I've been overthinking my code for years.

Then I saw what Linus Torvalds wrote in a README file.

Wait. What?

Linus Torvalds, the guy who built Linux. The guy who created Git. The legend whose kernel code gets scrutinized by thousands of developers. He’s the LeBron of programming

Just casually admitted vibing coding.

Linus was working on AudioNoise, a hobby project for random audio effects. He needed a Python visualizer, but doesn't really know Python.

So what did he do?

He prompted AI to write it for him. Then said it was "sure is better than I could do by hand."

No shame. No 500-line essay defending his approach. Just: I don't know Python → AI can help → it works → ship it.

That completely changed how I think about coding.

Fighting legacy bugs. Rewriting the same boilerplate. Googling syntax at 2am. Every side project dying because "it has to be clean first" or "I should already know this."

We worship "clean code" and "understanding every line"... but end up shipping nothing.

The fear of looking dumb leads to over-engineering, which leads to burnout, which leads to abandoned repos with "last commit: 2 years ago."

But watching Linus just vibe it out? That hit different.

Here's a guy whose real code gets scrutinized by thousands. But for a fun audio toy? He cuts himself out as the middleman, lets AI handle what he doesn't know, and moves on.

No ego. Just pragmatism + fun.

Code is a means, not a religion.

Now I ask myself: Does this spark joy (or at least curiosity)?

If yes → vibe, prompt AI for the boring parts, tweak, run, iterate.
If no → drop it guilt-free.

Even legends use shortcuts when it's not the main quest.

The result? More repos actually get finished. More experiments. Way less burnout.

I've been sitting on this draft for three weeks. Tweaking sentences. Debating structure. Making it "perfect."

Then I realized: I'm doing the exact thing I'm writing about.

So I'm hitting send. Right now. Because done beats perfect.

And honestly? You probably didn't even notice what I thought were "problems."

What project have you been overthinking? What are you not shipping because it's "not ready"?

Maybe it's time to just... vibe it.

Until next time,
Kermit

P.S. If you spot typos, consider it part of the aesthetic. I'm vibe-writing this newsletter now.