[Process] Lessons learned about Bus Factor (5/5): Detect it before it is too late

Published on

Dec 19, 2017


Last time we talked about why it's better to use the same language as your domain expert, and write tests that really describe business logic and not interface. Now, as a dev, one of the worst situations that can happen is when you have to dive into an unknown project to fix some critical bug or add some feature required for yesterday, and you encounter error after error or don't even know where to start. Quite the nightmare right ? Well, for this last post of the series, let's face our fears!

[Source adamprescott.net ]

Here is the link.

Thanks folks! And thanks a lot Yann!

Written by

Eve Vinclair-Berkemeier
Eve Vinclair-Berkemeier

People Manager @ KNPLabs

Scrum Mistress - AFOL at home and at work :D Helping hand for client projects and internal organization of our teams at KNP.