Artwork

Content provided by GeePaw Hill. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by GeePaw Hill or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ppacc.player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

Why Have a Change Strategy? | #102

7:59
 
Share
 

Manage episode 282906081 series 2644918
Content provided by GeePaw Hill. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by GeePaw Hill or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ppacc.player.fm/legal.

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
  continue reading

147 episodes

Artwork

Why Have a Change Strategy? | #102

PawCast with GeePaw Hill

22 subscribers

published

iconShare
 
Manage episode 282906081 series 2644918
Content provided by GeePaw Hill. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by GeePaw Hill or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ppacc.player.fm/legal.

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
  continue reading

147 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide

Copyright 2025 | Privacy Policy | Terms of Service | | Copyright
Listen to this show while you explore
Play