McDonald’s Theory

Couldn't have said it better myself. All teams needs someone to break open productive meetings. I apply the same tactic: https://medium.com/what-i-learned-building/9216e1c9da7d

Don't be a sheep!

Excellent talk about innovation. It's in Dutch, sorry about that :) http://www.jefstaes.be/keynote-jef-staes/

CQRS

Nice slideshow that's easy to understand:
http://www.slideshare.net/jeppec/cqrs-why-what-how

The surprising truth about what motivates us

How to create an enterprise with staff that evolves from following orders to autonomy and motivation:
http://www.youtube.com/watch?v=u6XAPnuFjJc&feature=youtu.be

Finger pointing

In the Agile dev world, there is a rule saying 'no finger pointing'. This means not rubbing people's nose in something when they made a mistake. This to assure people don't become afraid of touching some code or making mistakes. I think it's also a way of being professional. Now here's the thing. Most people want to know when they made a mistake. So you need to tell them. It's about how you tell them of course. Polite and calm is the manner it should be. This works for most people, but the rule has a couple of disadvantages: What do you do when someone really doesn't give a f*ck? You already told him 10 times to run the tests before check in and he still doesn't do it. What do you do then? I say finger point away! Finger point till he cries :)

DevOps

Nice post explaining what DevOps is:
http://blog.csanchez.org/2012/03/13/infrastructure-as-code/

Existing principles interestingly explained

Here's an interesting video from Gojko Adzic stating that software quality is everyone's problem. Nothing revolutionairy, but I especially like the way he talks about removing team bottlenecks and the importance of job titles.

http://gojko.net/2012/02/17/sleeping-with-the-enemy-video/