-
Benefits on touch some code as Engineering Manager once in a while 1. Sense of Technical Debt 2. Sense of Technical Maturity 3. Aligns expectations ⤵️On twitter.com
❤️ 4 Favorites Mood 0
-
First, I would recommend tasks with a small scope and well defined To dedicate few hours, but not dedicate too much Always push for pairing in this situation! The goal isn't coding but gathers a sense of the current code status and learning opportunitiesPermalink On twitter.com
-
1. Sense of Technical Debt - It helps me to see if the environment is easy to setup + run the tests - Understanding if we lack proper tooling - Major pain points in the development processPermalink On twitter.com
-
2. Sense of Technical Maturity - Is this code properly tested? - Is this code properly refactored? - Does this code the Ubiquitous Language?Permalink On twitter.com
-
3. Aligns expectations Maybe you are expecting the team to reduce the technical debt, or invest effort in refactoring and you don't have insights into this happening. Showing what you expect from them with code, helps to drive direction and align expectationsPermalink On twitter.com
-
And it helps you understand why they might not be able to achieve it. Sometimes is that we have an unreasonable sense of pressure or the feeling that we need to ship fast. By having a pairing or mob session you can put the focus on what mattersPermalink On twitter.com
-
But also, and more importantly, gaining context of why that's happening and you, as manager, be able to make more informed decisions to help the team move in the right direction. Still, few hours of coding shouldn't replace having conversations and hearing your peers.Permalink On twitter.com