January 10, 2026
Complexity is the new clout
Worst of Breed Software
The 'we make bad apps' site has devs laughing, crying, and rage-typing
TLDR: A parody site proudly celebrates making overcomplicated software to boost careers. The comments swing between laughter and war stories, with jabs at old tools, vendor vibes, and YAML nightmares, arguing whether it’s satire or a brutal mirror of why apps get slower and budgets bloat.
“Worst of Breed Software” showed up bragging it makes bad apps on purpose—and the internet couldn’t look away. The site worships needless complexity: turning a basic to‑do list into a sprawling Rube Goldberg machine, bragging about storing logins on a blockchain, and celebrating builds that take 40 minutes. The joke lands because it’s uncomfortably close to real life, where people pile on tools to look impressive. The comments instantly became the main event.
Some users cheered the takedown of past pain. One shouted that “L_tus N_tes” still deserves the heat, while another side‑eyed the whole vibe with “Oracle? Is that you?” A weary developer confessed that fiddly spacing in YAML—those finicky setup files—“keeps me at night.” Others called the site “Genius!” and “Hilarious,” but the laughter sounded like group therapy. Everyone’s seen a tiny website rewritten in a fancy language, split into a dozen mini‑pieces, then shipped slower than before.
The big drama: Is this just satire, or a mirror aimed at every team meeting? Fans say it’s a needed roast of “resume first, users later.” Critics say the jokes are hitting too close. Either way, the message sticks: complexity can be a career strategy, and the cost is slow apps, higher bills, and endless meetings
Key Points
- •The piece satirizes software teams that prioritize resume-driven development and over-engineering.
- •It mocks misuse of technologies, including using Kafka as a system of record and databases as IPC.
- •Testimonials exaggerate poor choices: blockchain for sessions, excessive microservices on Kubernetes, and bloated micro-frontends.
- •Additional examples include rewriting simple sites in Rust and spending most effort on YAML configuration.
- •A closing manifesto elevates complexity, process, and tools over simplicity, people, and value.