Legacy code is code that makes money, as they saying goes. But we have an opportunity to refactor when tickets and feature requests come in. How are we going to make sure we don't break things?

Using a test first approach we will turn this dumb data container into a rich and meaningful domain model. This gives us the confidence to tackle new challenges, without fear of regression. We will create a safe path forward guided by test driven development and new feature requests only. If you know a bit about tests but don't know how to get started in your own code base, then this is the talk for you.

Comments

Comments are closed.

Great talk! You could maybe prepare bigger code examples. Like the test for the moved datetimes. Overal really liked your talk and I think its extremly useful!

It's a very optimistic assumption, that legacy code does have some tests. In my life it happened only once, so far...
Regardless, very interesting and educational talk, love the live coding session :thumbsup: