Separation of concerns is one of the key foundations to make software scalable, maintainable and readable. So even though everybody agrees it's a "good thing"(tm), lots of object oriented code that is written does not follow this principle. How is it that this separation sounds easy in theory but is very hard in practice? During this talk, Joshua and Stephan will demonstrate through real life examples on various levels of code how separation of concerns will create better code for both you and the person that will be maintaining your code.
