Some people may know me as the author of an open-source project with almost 400 million downloads, but my real job is to help my clients to optimize everything that has to do with software development. This covers tools, the architecture, the way of working, the infrastructure, and sometimes even the culture of the development teams.

I usually do that by joining the development teams as a hands-on architect and working with them on their day-to-day tasks, while at the same time identifying anything that can be improved. This includes everything that is needed to make sure they don't only build the right thing for their business, but also apply the right engineering principles applicable to the stage of that "thing". In other words, train them on writing high quality fully testable code that is automatically deployed in the cloud.

In this talk, I want to share with you the mindset I follow in this endeavor, the tools I use, the practices, patterns & principles I follow and the heuristics I apply. In essence, everything I do to make the development teams successful with software development.

* Visualizing the development flow from idea to production
* Using an agile process
* How to document decisions
* Architecture styles
* Test Driven Development, Domain Driven Design, Event Storming
* Design heuristics such as "Reversible deciisons"
* NUKE for treating your pipeline as code
* Pulumi as infra-as-code platform
* Prettifying code
* Code quality tools (Roslyn, editorconfig, eslint, Sonar, Qodana)
* Coding and design guidelines
* Structuring code along functional boundaries
* Clean source control
* Code documentation
* Design patterns (and when NOT to apply them)