4 years later with 80% generated code

About a decade ago I wrote a model driven code generator.
I've now had the honor of using it in practice for our architecture for almost 5 years.

About 80% of our code is generated. My developers focus primarily on architecture or business logic. Boilerplate code and patterns are covered by the code generator.

This talk is about what we've learnt during this time of using generated code, the benefits, and potential draw-backs.

Domain Driven Design - what is it and how is it to work with?

Domain Driven Design is an approach to software design that focus on modelling the business domain in your software.
The result is an architecture where developers and stakeholders can speak in the same language and quickly identify issues or new features.
It allows you to transfer knowledge from the software domain to the business domain and vice versa, making people on both sides of the equation grow.

The architecture that I set up for Flaivy (Order Impact) is primarily focused on Domain Driven Design.

In this talk I will talk about:
* What domain driven design is
* Suggestions on how to get started
* Some of the challenges that we've faced with 5 years of evolving domain knowledge

Domain Driven Design is an approach to software design that focus on modelling the business domain in your software.
The result is an architecture where developers and stakeholders can speak in the same language and quickly identify issues or new features.
It allows you to transfer knowledge from the software domain to the business domain and vice versa, making people on both sides of the equation grow.