If you write code without tests, you're probably wasting your employer's money---because it'll break again right where you "fixed" it.

Yegor256 Blog offers insights, opinions, and discussions on software development, engineering practices, and technology trends. Covering topics such as object-oriented programming, code simplicity, and software design principles, Yegor256 Blog provides resources for developers and tech enthusiasts. Developers can explore unconventional ideas, challenge conventional wisdom, and broaden their perspectives on software craftsmanship through Yegor's blog posts and essays.

Yegor's Blog

Automated tests serve as a warranty system that protects business investments in code. When developers write code without tests, they risk breaking previously fixed functionality, essentially wasting employer money on repeated fixes. Test coverage ensures that paid-for code continues working during refactoring and modifications, making it a crucial business protection rather than just a development practice.

Write Unit Tests, Don't Waste Our Money!

Write functional tests or end-to-end tests, don’t waste your money with unit tests

It’s funny that I realized <a href="https://dly.to/oZDgj8SquIX" target="_blank" rel="noopener nofollow">the same thing</a> while working independently as a freelancer and using AI Agents. however the “cost” that I would have to pay is different: model tokens, and the time I spend to fix the mess the AI agents make.

TDD is a waste of money. Stuff’s gunna break anyway and you know it.

Testing isn’t just valuable for employers—it’s equally important for developers. Well-written tests act as a safety net, catching bugs and preventing the chaos that often follows when you add new features or make changes to your codebase.

write test driven development, profit says when users something want what tests say and profit don’t, tech something disagrees, world is cruel and test such thing is out of test driven development, industry says. human involvement maybe