Developers are often caught between the needs of the business and the needs for creating a good technical solution.  Often, the good technical solution loses that battle.  This session will help developers identify the technical debt that they have accrued and fix that debt with pragmatic architecture solutions that won’t halt development or break the bank through the lens of two related principles -- Separation of Concerns (SoC) and Single Responsibility Principle (SRP).  By adhering to these two principles, your code will improve immediately and your application architecture will become cleaner!  See and discuss how these principles work in concert by walking through a practical example on how to separate presentation, business logic, and the database layers from one another by refactoring some existing code. Building on that example, you will then see how the codebase is flexible and resilient to common changes.