Thomas K├Ągi



Currently employed by ERNI AG. I have been working as a contractor for an international healthcare company for 2.5 years now. I've held various roles there as temporary cloud architect, tech lead and C# developer.
Before that I gathered experience as a test automation engineer (1y) refactoring a test framework written in python.
Immediately after completing my masters degree in mechanical engineering at ETH Zürich in 2014 I joined Sensirion as a software engineer.
I'm all about the quality of solutions. Be that from the foundation in code quality, through the intermediate step of component design to the abstract level of architectural concerns.
Oh, and I enjoy dancing and sailing when I'm not deeply involved in one of my (not so successful, yet) open source coding hobby projects.

Enabling a Culture of Code Quality

When systems created by classic engineering disciplines such as mechanical or electrical engineering fail, things physically break. This has historically been a strong motivator to "get things right" and has led to a well-established set of best practices - called norms - to be globally accepted. In the field of software engineering we're not quite as advanced yet as it isn't even as straightforward to understand what "quality" actually means for software systems.

In this talk I outline a notion of quality that goes beyond classic monitoring by tools like SonarQube and the likes. Tales from projects in the industry highlight the notion of what quality means and how it can positively affect performance of the software system itself and the teams that create these systems.
A model is proposed for establishing a culture of quality in teams that write software.