,
4 tweets,
1 min read
Read on Twitter
🔥(Senior) Dev Tip: Make devs 100% responsible for their contributions.
Did Fred push code that broke feature X? Rollback and tell Fred to fit it. He will learn to be more careful. He will learn to own his mistakes.
Keep going... 👇
Did Fred push code that broke feature X? Rollback and tell Fred to fit it. He will learn to be more careful. He will learn to own his mistakes.
Keep going... 👇
Your team will grow most if they:
- Are given the ability to fail without being "whipped"
- Are given the ability to fail so they can adjust how bold their changes are
- Are noticed and acknowledged when they have success
- Can learn from other's mistakes (😉)
Keep going...👇
- Are given the ability to fail without being "whipped"
- Are given the ability to fail so they can adjust how bold their changes are
- Are noticed and acknowledged when they have success
- Can learn from other's mistakes (😉)
Keep going...👇
What happens if Fred is notorious for breaking stuff? Over and over? His "fixes" almost always break other things? And he still does despite being told to stop?
Well, an environment that encourages responsibility will also allow a lack of responsibility to become apparent.
Well, an environment that encourages responsibility will also allow a lack of responsibility to become apparent.
What do you do in this case? Well, that's another topic for another day (I.e. it's a manager's / HR concern 😋)
Main Takeaway: Giving your team the ability to fail and learn from their failures in a safe environment is the best way to let them grow!
Main Takeaway: Giving your team the ability to fail and learn from their failures in a safe environment is the best way to let them grow!
