The business wants their app yesterday but you are concerned with application performance, how do you determine the right thing to focus on? In this session we will discuss the pitfalls of solely focusing on application performance and the risks of premature optimization. Let's get the thing built, then worry about how fast it is!

The goal of this session is to encourage developers to pump the breaks on prematurely optimizing their applications. Do you really need micro-services and micro-frontends or will a monolith suffice? Do you absolutely have to have Docker and Kubernetes or can you run it on bare metal servers? These techniques can quickly become quicksand to any application and dev team. We will cover that, yes it is okay to ship temporary code to production. No, you don't have to have your end game architecture of micro-services and micro-frontends set up from the get go when your customer base doesn't warrant it.

As developers, we can tend to jump into the deep end without truly evaluating whether or not our project really needs to use the latest and greatest technology. Focusing on delivering business value first, then making the code maintainable, and only after those two issues have been addressed do we focus on optimization. Knowing when to say use micro-services or micro-frontends, Kubernetes, Docker, etc. is a very important distinction to make. Being able to identify when good enough is good enough for a first release can quickly become lost in a feature avalanche, so we will be learning how to focus on that MVP1 and then iterate through versions to not only deliver business value, but not swamp the tech team right at the start.