Today's post is unusual, because I turn it to the esteemed group of readers asking for help / favor. I was invited to this year's conference JDD as a speaker and thought about a subject that you could possibly (even if you do not want to go for the conference, just in general) interest.
Presentation Software dedicated craftsmanship and patterns have already reached the limit reużywalności, so I'm wondering about a new theme:) If you have any suggestions or specific requests as to what you want to hear feel free to write in a comment or priv (address in the panel "a me "on the right).
//===============================
Looking at the overall trends, which this year also with Polish conferences, can be observed that rather a move away from further endorsements of dozens of web frameworks in the direction of more general issues, usually by synthesizing section several aspects. I wonder what you think about this trend.
So far I have an idea for a presentation on approaches to the Inversion of Control. Yes, I know that the subject is trite but how about a review of the application architectures based IoC. The review which is kind of a trip to architectural solutions.
zastanowilibyśmy the first being in general is architecture, what are its types and the arch is different from the design. Later, after another trip approaches to architecture based on IoC 3 techniques in order of their "strength."
So first the "weakest" (in the sense of strength and not in the sense that it is bad) approach: injecting depending - what and when you need to inject. Because injecting the DAO / Repo to Servisów is boring. Next
technique "harder" - because apart from not only a colleague, but also their quantity and time - arch oriented events. Examples use the event to increase trading capacity and "events" of business - all in the context of the sourcing and event-query Command Responsibility Segregation.
At the end of the most powerful technique IoC: Aspect Oriented Programming .
At each "stop" of our trip zastanowilibyśmy what results from the application of the approach and when you need to use it - and when it is just fashion and stampede.
As you can see from the description of that presentation was designed for new applications architects - programmers who would like a hare in the design at the macro level.
