Chapter 4. Safely Changing Design
I’ve frequently alluded to the fact that you should only design what you need for now because later you will safely be able to change your design. I thank you for keeping an open mind about that until this chapter, in which I cover how to actually make the right things happen.
Of course, I have to define “safe,” as you can never truly be 100% risk free. The cop-out definition would be “without introducing any more risk than the process you have now over any given period of time.” I think for the vast majority of people reading this book, I can hit that mark, but I want to set the bar a little higher.
For this process to work, you have to be able to change your data structures even though some inherent risk exists ...
Get Test-Driven Database Development: Unlocking Agility now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
