When you're starting to build an application, at what point should the database be designed? (To our non-developer listeners, hang in there—this is relevant to you!)
There are a lot of opinions on this topic in the software community, and many say the database should come first. But if you're building an application in an agile manner, why would you start with a piece of the project that the user can't interact with and give feedback on?
In this episode, host Phil Ledgerwood discusses why he thinks starting with the database can not only hold back your team's agility but also negatively affect the quality of the application in the long run. And he'll be giving some suggestions for better places to start that will help you create a more useful app for your users.
➡️ Connect with Agile Bites Host Phil Ledgerwood on LinkedIn