ConfPad

During our work on Medicare implementing the largest change in the program's history, I've seen how requirements can shift drastically as features evolve. While this can be painful for an engineering team, architecture decisions like choosing an ORM can be used as a tool, rather than a crutch. We'll explain the reasons our team decided to write our own ORM and how this choice allowed us to support adaptation to feedback, ultimately better serving end-users. This talk will describe real-life examples of how an ORM choice can empower engineers to better adapt to shifting requirements and recommendations for writing your own mini ORM.