this post was submitted on 12 Apr 2026
1166 points (99.5% liked)
Programmer Humor
31092 readers
738 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Another movie pitch:
Due to management decision, a code freeze has been mandated to the main branch. 50 feature branches have accumulated waiting to be merged.
Management has now finally approved to lift the code freeze - but only for 24 hours. Will the poor engineering team manage to merge all feature branches in time?
Here's one for a TV show.
In 2022, a crack quality assurance team was made redundant by a CTO for a botched product launch they didn't commit.
These men promptly escaped from a maximally unstable job market to the LinkedIn underground.
Today, still wanted by recruiters, they survive as soldiers of fortune.
If you have a broken codebase, if no one else can help, and if you can find them, maybe you can hire the QA-team.
DO DODO DO DOO DOO. DO DODO DO DO
You are amazing, you beautiful lemmy stranger, you.
I am ramping a vehicle onto its roof in celebration
Is there a robust test suite?
Merge, test, merge, test, patch, merge, test
Only some of the new code does. Unfortunately, most of the code base is 10 years old written in the good ol’ Anarchy Driven Programming paradigm.
The test suite takes 24 hours to run fully.
If by test you mean wait for customers to yell at us, it's super robust
Merging all the feature branches in time is easy.
Having the project compile afterwards is hard.
Merge/test/fix on a separate branch and then merge this into main when the freeze lifts?