One of the observable results of adopting TDD is that by necessity the code base becomes not only "more tested" (coverage) but also more TESTABLE. It happens that well-architected application code and testable code are often similar...
this seems to be (at least in my experience) a pretty common take on such things these days...

but what I want to point out is something different.
CICD has a similar result... more Continuously Integratable code... lower turbulence in integration...

I think there are several things a play there... but...

it so happens that more integratable code is also similar to well-architected code, at a larger (systems) level.
( I don't believe that testable and continuously integratable code is inherently well-architected... but I can pretty much guarantee that untestable, difficult to integrate code, is poorly architected )
You can follow @cyetain.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled:
Those who think consciousness raising & movement building are disconnected, or even a distraction from electoral politics have not paid attention to the history of social change.In this thread, we
Read more
The 2020s will be known as the Remote Work decadeA few predictions of what is likely to emerge[ a thread ] Third Space: Office and Working from Home will
Read more
1/29: Have you ever had a concept explained to you that helps frame complex issues you’ve been wrestling with and opens your eyes to new possibilities? A concept that I
Read more
By continuing to use the site, you are consenting to the use of cookies as explained in our Cookie Policy to improve your experience.