Return to site

CODING TEAM THEORY: The Busybody 🦋

· coding,team

The Busy Body is an engineer who skips all over the codebase:

they’ll fix a front-end problem here, jump to some refactoring,

then fiddle with the database over there. 

But the Busy Body is problematic over a long period

because these engineers end up without a strong sense of ownership.

There’s nothing for them to point at and say, “I made that.”🦚

Even if they can solve a wide range of problems, 

lacking something that they own can lead to attrition.🥺

𝐇𝐎𝐖 𝐓𝐎 𝐑𝐄𝐂𝐎𝐆𝐍𝐈𝐙𝐄 𝐈𝐓

Engineers exhibiting this pattern will show high levels of Impact

and lots of small pull requests without any identifiable home base in the code. 

They’ll show a high level of Involvement in the review process.🔎

And because they typically spend their time building

and spend less time bug fixing their own work,

they’ll show high levels of new work🆕 and relatively low churn.

𝐖𝐇𝐀𝐓 𝐓𝐎 𝐃𝐎

Give these engineers something to own top to bottom.

Whether it’s a module, a new feature, or a large project,

ask them to do more than just ‘get it done’.

Ask them to become an expert💪 in that particular area or on that specific project.

Then, double down on their strengths in that area:

assign them the 1.1 version, the bug fixes, the unit tests, and the documentation,

then give them the 1.2 and 1.3 versions as well.

Allow them the opportunity to get to know their domain, 

to work with it, to teach others about it, and to develop a mastery.🧙‍♂️

Ask them to give a presentation on the project to highlight lessons learned and best practices.

The key is to nurture a true sense of ownership.

All Posts
×

Almost done…

We just sent you an email. Please click the link in the email to confirm your subscription!

OK