You are a passionate programmer, knowing how to compose clean code, how to keep cohesion tight and coupling loose, and possibly even utilizing building blocks from DDD and structuring code according to Hexagonal Architecture. Still, from time to time you have that unusual feeling that any parts of your code are more complicated than they intuitively should be? That your code could handle fresh business requirements better? Or that it should enable fresh business opportunities, but someway it doesn’t?
The most probable explanation for all above is that your code does not take into account 1 thing: contexts. The strategy that you make is utilized in different contexts, and so your code should be tailored to each 1 of them.
This talk will be full of real-world examples of specified contexts and of troubles that a strategy that ignores them can fall into. But that’s not all, as I will besides show you techniques on how these contexts can be identified, and yet how to fix your code to be context-aligned.
So fasten your seatbelt and let’s dive together into a planet where the answer to almost all question should be: “it depends (on context)” :-)
Website: https://jdd.org.pl
Facebook: https://www.facebook.com/JDDconf
Twitter: https://twitter.com/JDD_Krakow
