Technology rarely breaks by accident.
When a massive data breach occurs, when an app suddenly becomes unusable, or when a platform quietly prioritizes itself over users, the standard industry playbook is to blame a bug, a sophisticated hacker, or an unforeseen edge case. But if you look closely at the architecture, the outcome wasn’t a glitch. The system did exactly what its incentives told it to do.
Designedtofail.dev is a publication about the structural, architectural, and economic reasons why modern software is built to let us down.
It is a close examination of the perverse incentives that govern technology today: where margin dictates privacy, where security is treated as a compliance checklist rather than a duty of care, and where the fundamental safety rails of software engineering are quietly being engineered out of the room.
What You Will Find Here
If you are a software builder, an architect, a security researcher, or simply someone trying to understand why the tech industry operates the way it does, this newsletter is for you.
This isn’t a blog about typos in code or everyday bugs. When you subscribe, you can expect deep, analytical essays on:
Structural Flaws: How missing boundaries, lack of multi-tenancy, and bad architecture are sold as industry standards.
Perverse Incentives: Why building defensible moats and maximizing data extraction always seem to override user safety and privacy.
The Erosion of Duty: The legal and cultural loopholes that allow software companies to hold your life without owing you a standard of care.
The Reality of Modern Shipping: How trends like AI code generation and hyper-growth scale are automating our worst architectural habits.
About the Author
I am Badri Rajagopalan. With a background in software architecture, security, and technical research, I have spent my career analyzing how and why complex systems break down. My work spans examining the systemic architectural flaws in tech to high-level theoretical research involving the formal modeling of developer productivity and cybersecurity.
I write here to dissect the failures we are building on purpose, and to argue for the structures we should have demanded before anyone wrote a line of code.
Subscribe to get full access to the newsletter and never miss an essay.
Why subscribe?
Subscribe to get full access to the newsletter and publication archives.
Stay up-to-date
Never miss an update—every new post is sent directly to your email inbox. For a spam-free, ad-free reading experience, plus audio and community features, get the Substack app.
Join the crew
Be part of a community of people who share your interests. Participate in the comments section, or support this work with a subscription.
