DEV Community

Discussion on: Skin in the Game: Hidden Asymmetries in Daily Life by Nassim Taleb

Collapse
 
raddevus profile image
raddevus

Great post and the book sounds very interesting. I will check it out.
I think this is related to Software Dev too because there are devs and higher level roles (software architects, etc) who may not have any skin in the game but may force things to be done a certain way.

There are other devs (usually higher level) who may even : produce the code to create a feature then walk away from it forcing others to support it when it breaks, make code fixes, etc. I call them Mic Drop Devs -- they be like "I finished it. I'm out!"
It is not helpful and only the real devs who fully "own" their code really have skin in the game. Only when you are the one who will be woke up in the middle of the night to fix it do you really have skin in the game.

Collapse
 
sandordargo profile image
Sandor Dargo

Thanks for your comment! That's an awesome analogy!

And that's actually the way our teams are taking these months. No more feature and maintenance teams, each team will be responsible for maintaining their own products. People will have some skin in the game!