Beyond design principles - writing good code

I liked the talk, for me personally a lot of the talk really made sense afterwards. Not because the concepts were to difficult to grasp but when I started talking about it with other attendees we got into interesting conversations. Especially the part about immutable and returning a new 'cloned instance' of an object. Definitely food for thought. I didn't know the exact meaning of the term "Anemic" a very short explanation of the term would have been a nice little extra to get a better understanding of the concept.

Nice talk, interesting subject. Would perhaps suggest switching the content: start with boundaries, messaging, CQS, proceed into (im)mutability (supported by the former) etc and finally go towards the OO-is-nearly-functional as a conclusion, especially since you're referring back to it in the end.

nitpick: remove the quotes from the text-balloons, they seem to make the content less serious, while it is actually supportive or clarifying.

Nice abstract talk. It makes you think about how you write your code and it gives you some head ups again.

Sometime I wouldn't mind that you gave your opinion a bit more.
I'm doubting if it's better to have some examples in your talk. You make it less abstract and people are not translating into their own mind to "Is he meaning this or that in our code base.".
But adding them could break the power of the abstractness it have now, and for experience people it should not be a problem.

Very nice, high level abstract talk. It really got me thinking about using the guildelines that were presented. I would have liked some practical real-world examples but I guess that's for another talk ;-)

Matthias gave a really good talk about the basic thoughts behind OO. It was very clear, well structured, and really informative.

It mostly refreshed my memory as most things presented were already somewhere buried deep in my mind. Especially the way of preserving state through use of immutable objects has been an eye-opener.