Skip to content
Why Have a Change Strategy? | #102 episode artwork

Jan 22, 2021 7 min

Why Have a Change Strategy? | #102

from PawCast with GeePaw Hill Hosted by GeePaw Hill

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.

Episode details come from the podcast's RSS feed.

Embed this episode

Ready to play

Why Have a Change Strategy? | #102

0:00 7:59

No transcript yet.

Requests help us decide what to transcribe next.

Frequently asked questions

How long is this episode of PawCast with GeePaw Hill?

This episode is 7 minutes long.

When was this PawCast with GeePaw Hill episode published?

This episode was published on January 22, 2021.

Can I download this PawCast with GeePaw Hill episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.