If Everyone’s Responsible, No One Is

Mission

A developer’s slow descent into processless madness

Once upon a time, I thought processes were optional.

We were a startup. Three of us. We moved fast, broke things, fixed them later — if we had time.

No calendars. No sprint boards. No documentation. No ownership.

Just Slack threads, scattered TODOs, and blind faith that someone, somewhere, was handling it.

And somehow, it worked.

Until it didn’t.

One day I realized I wasn’t “moving fast” — I was just running in circles, burned out, juggling bugs, features, support, releases. I was the team. So was everyone else. And somehow — no one was.