You’ve been patient. Some of you have been patient. Last week on Thursday night, I presented Legacy Dependency Kata v2.2 at the SLC .NET User Group Meetup. You’ll notice the name change since then.
But wait– don’t know what a code kata is? Start here.
I’d like to give a quick thank you to the crowd that night and the one the day before at HealthEquity during one of our Lunch Learning sessions. You all are fantastic. Thanks for the great feedback!
What’s different? Not much, to be honest. Also, in some ways, a lot. But what I realized as I was going through the slides one final time, was this: this IS a major revision. I just didn’t realize it while going through all the multiple iterative changes.
What hasn’t changed? Legacy Code Kata 3.0 is still a code kata about dealing with dependencies in legacy code and getting it ready for unit testing. It still uses the same seed code as previous versions, and you can find that here on GitHub.
Changelog
So, what makes this version so great? Let me lay it out for you:
- Lost the lame presentation theme. I thought I accomplished this with v2.0. NOPE. You’re welcome.
- The intro slides have been honed down to only those 100% essential, and they were also prettied up, and some new notes added.
- Added the Kata Barometer (patent pending (not actually (maybe))). At any time you always know what state your tests and build should be in.
- Broke up quite a few slides that were too complicated and/or the font was too small to read effectively. Much more Kata Cup friendly now. What’s a Kata Cup? Maybe in a future post. Stop changing the subject!
If you want to see for yourself why this version is so much better, check out the old versions: Version 1.0 or Version 2.0.
Here it is.