🚢 I Wasn’t Building—Just Performing

For years, I did what I thought I was supposed to do.

I chased side projects.

I bought domains like lottery tickets.

I tried to catch up with “tech”—as if falling behind was a moral failing.

I tried to fit in, speak the lingo, chase the titles, nod along in meetings that made no sense.

I even caught myself shutting people down the same way I’d been shut down—because that’s how the game seemed to work.

And at some point, I realized I wasn’t building.

I was performing.

Performing competence. Performing alignment. Performing innovation.

But something in me broke (or maybe clicked).

I stopped chasing.

And I started saying what I actually mean.

That’s where Ship It and Regret It comes from.

It’s not a place for cynicism.

It’s a place for clarity.

A place to explore why so many smart people end up doing dumb things in tech—under pressure, under optics, under the illusion of progress.

This isn’t a personal diary. It’s a weekly audit of the dysfunction we normalize in modern engineering orgs—and what it costs us.

You’ll find sharp takes, uncomfortable patterns, and occasional tools to push back—without losing your mind (or your job).

If you’ve ever felt like you were hired for your brain but paid to stay quiet—

If you’ve ever watched decisions unfold and thought, this isn’t wrong because it’s inefficient—it’s wrong because it’s dishonest— it’s wrong because it’s a high-cost workaround pretending to be a business decision.

Then you’re in the right place.

We ship.

We regret.

We learn.

We name it out loud.

Let’s go.

---

👉 Subscribe. Forward to the one engineer in your org who still dares to ask, “Wait—why are we doing this?”