– Room 8
Georgios works for IBM as a Senior Principal Software Engineer and is currently one of the most active contributors to Quarkus, where he works in all sorts of areas, including but not limited to LangChain4j, RESTEasy Reactive, Spring compatibility, Kubernetes support, testing, Kotlin, and more.
He is also an enthusiastic promoter of Quarkus, who never misses a chance to spread the Quarkus love!
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, 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 with this talk.
All people interested in how complex libraries and frameworks evolve would benefit from attending this. Guillaume and Georgios (the top 2 contributors in Quarkus) will attempt to show people how decisions are made and try to help users avoid the mistakes that Quarkus has made in the past (both technical and organizational).
Programmet er oppdatert.