Engineer Explains: Turning mistakes into wins with CHAOS ENGINEERING
We've asked experienced engineers to share how they would explain some tech terminology at three levels of experience - from junior developer to CTO.
Engineer Explains: The Benefits of Test-Driven Development
Test-driven development is not magic dust you just sprinkle around to get those benefits. It’s a practice you learn.
TDD has many benefits – improved code quality, better design practices, better code sustainability, saving time and effort, and even improved team collaboration. But test-driven development is not magic dust you just sprinkle around to get those benefits. It’s a practice you learn.
We’ve asked Ian Cooper, a software engineer with almost 30 years of experience, best known for his speech Test Driven Development: Where Did It Go Wrong, to share with us reasons to use TDD as a junior or senior engineer and a CTO.
For a junior engineer, test-driven development solves the problem of where to start. For seniors, he says, it’s the ability to change one’s mind about software design as the requirements evolve. CTOs, on the other hand, will appreciate the maintainability/sustainability of the code, as TDD makes it easy to modify software over time.
This video is a part of ShiftMag’s video series, Engineer Explains.
We’ve asked experienced engineers to share how they would explain some basic and some less basic tech terminology to different tech job titles or at three levels of experience — from junior developer to CTO.
More videos from the Engineer Explains series:
- Feature Flags Explained
- JAMstack Explained
- Observability Explained
- Large Language Models Explained
- DevOps Explained
- DevRel Explained
- Network APIs Explained
- Verifiable Credential Explained
- Mob Programming Explained
- Machine Learning Explained
- RUST Explained
- Career Tips for Tough Times ft. Pragmatic Engineer
More on Test-Driven Development:
