They call it “The Development Process”
<img src="https://media.daily.dev/image/upload/s--M9VjuRlR--/f_auto/v1747649945/ugc/content_50349766-9e3b-4814-80b3-67818784956e?_a=BAMClqUq0" alt="comic">
👇 Join the broken pipeline: <a href="https://www.miserablyemployed.com/products/the-development-process" target="_blank" rel="noopener nofollow">https://www.miserablyemployed.com/products/the-development-process</a>
You code sober.
You push drunk.
You debug hungover.
And you release out of pure, unfiltered spite.
It’s not agile. It’s not clean.
But it gets deployed — eventually — usually around 4:59PM on a Friday.
“The Development Process” is a t-shirt for the devs who’ve seen too much, fixed what should never have existed, and learned to navigate Jira like a war map.
Wear it to your next retro. Or your next resignation.

Get 1% better daily. Development resource sharing made easy. Post, comment, or upvote to show your contribution and support other developers! 🙌

⚠️ Please do not post any promotional resources.

Dev Squad

The post humorously describes a chaotic development process where coding is done sober, code is pushed while drunk, and debugging while hungover, with releases driven by spite. It contrasts this approach with agile and clean methodologies, highlighting the challenges faced by developers.

The Development Process

Sometimes I wish I could do pair programming with myself so I could understand what I do.

code fucked up, debug sober – thats the thing

My CEO loves it when I tell him how much of the core of our platform was written while I was drunk. LOL.