Yes, I find that sentence to be the highlight of the whole article. If TDD was an industry standard, then the software development industry would completely change, and then Continuous Delivery could become mainstream too.
Exactly, when we learn a new practice, we shouldn't just practice it solo but present it to a team and get team consensus, so that we can spread out the practices. Later, after it succeeds with one team, can scale out even further.
"TDD should be our industry standard" ---> I completely agree.
Yes, I find that sentence to be the highlight of the whole article. If TDD was an industry standard, then the software development industry would completely change, and then Continuous Delivery could become mainstream too.
"Lesson #5: Showcase TDD to other developers"
This is incredibly useful!
Exactly, when we learn a new practice, we shouldn't just practice it solo but present it to a team and get team consensus, so that we can spread out the practices. Later, after it succeeds with one team, can scale out even further.
Tests are CODIFied documentation of developer requirements..
#ArchUnit is fantastic to codify architectural intent and also Spring Modulith framework too for webapps
Exactly, tests are executable requirements... we take human-written requirements and translate them into a codified/executable form.