![PawCast with GeePaw Hill artwork](https://is4-ssl.mzstatic.com/image/thumb/Podcasts123/v4/f7/6a/bc/f76abc91-b6f4-eb95-39f5-ecae7658350c/mza_2663806889298342520.jpg/100x100bb.jpg)
Why Have a Change Strategy? | #102
PawCast with GeePaw Hill
English - January 22, 2021 10:00 - 7 minutes - 9.15 MB - ★★★★★ - 6 ratingsTechnology Homepage Download Apple Podcasts Google Podcasts Overcast Castro Pocket Casts RSS feed
Microtest Test-Driven Development is a strategy for *change*. To understand the case, we need to answer two questions: 1) Why have a strategy for change? 2) How does TDD provide one? Let's take up the first question today. Why is having a change strategy so urgent?
The TL;DR is dead simple:
Because continuous ongoing change is at the base of all software development, both before and after our software is in the field.
---
You can read the full transcription of this podcast over on GeePawHill.org. Any feedback, you can always tweet @GeePawHill on Twitter, or drop a voice message via the voice messages link here on Anchor. If you are interested in becoming more involved in the Change-Harvesting community, click here to learn how to join GeePaw's Camerata.
---
Send in a voice message: https://podcasters.spotify.com/pod/show/geepawhill/message