Why Good Developers Write Bad Unit Tests · mtlynch.io
mtlynch.io · 2,386 words · saved by 1 readers
The standard techniques of good development can lead you astray if you don't adjust them for unit tests.
Congratulations! You've finally written so many lines of code that you can afford a beach house. You hire Peter Keating, an architect world-famous for his skyscrapers, who assures you that he has brilliant plans for your beachfront property. Months later, you arrive at the grand unveiling. Your new home is an imposing five-story behemoth of steel, concrete, and reflective glass. As you pass through the revolving doors, you track sand onto the opulent marble floor. Inside, you find a reception desk backed by an elevator bank. Upstairs, your master bedroom and three guest rooms are just four adj
saved by
related reading
- GitHub - mawrkus/js-unit-testing-guide: 📙 A guide to unit testing in Javascriptgithub.com
- Everything I know about good system designseangoedecke.com
- Crafting High Quality Unit Tests: Tips and Best Practicesmarclittlemore.com
- Write code that is easy to delete, not easy to... — programming is terribleprogrammingisterrible.com
- Fighting Distraction With Unit Tests | Matthew C Devmatthewc.dev
- How to write complex softwaregrantslatton.com
- How to Write Clean, Testable Codeyoutube.com
- Software Engineering at Googleabseil.io
- Ask HN: How bad should the code be in a startup? | Hacker Newsnews.ycombinator.com
- CSC 151 - Unit Testingeikmeier.sites.grinnell.edu
- Everything I know about good API designseangoedecke.com
- What is "good taste" in software engineering?seangoedecke.com