Context is king

You are a passionate programmer, knowing how to write clean code, how to keep cohesion tight and coupling loose, and maybe even using building blocks from DDD and structuring code according to Hexagonal Architecture. Still, from time to time you have that strange feeling that some parts of your code are more complicated than they intuitively should be? That your code could handle new business requirements better? Or that it should enable new business opportunities, but somehow it doesn’t?

The most probable explanation for all above is that your code does not take into account one thing: contexts. The system that you develop is used in different contexts, and so your code should be tailored to each one of them.

This talk will be full of real-world examples of such contexts and of troubles that a system that ignores them can fall into. But that’s not all, as I will also show you techniques on how these contexts can be identified, and finally how to fix your code to be context-aligned.

So fasten your seat belt and let’s dive together into a world where the answer to almost every question should be: “it depends (on context)” :-)