As software engineers, we are faced with lots of choices. Additionally, when developing libraries or frameworks that are used by lots of other software engineers to build their products, then even small decisions can have unforeseeable and unintended consequences down the line.
From timeless classics like the importance of naming in software and the proper reuse of existing components, to the unknowns of build time optimization and all the way to bold decisions like rewriting the entire I/O layer and everything in between, this session will give you valuable insights into how and why important decisions were made when developing Quarkus, with the hope of helping you avoid our mistakes and leverage what we got right.
Although the story focuses on decisions made in the context of Quarkus, no actual knowledge of Quarkus itself is necessary to follow along this talk.