Every Company Needs a Chris
With any luck, your company has a Chris.1 Every place I’ve worked at has one.
This is a developer whose intimate knowledge of the codebase takes years to build. This familiarity includes the dusty corners that few venture into — the code that works but has been untouched for eons. The modules whose original authors are long gone, written when the business requirements were completely different, when best practices and conventions were ignored (or more charitably, before they had been established). “Here be dragons.” Every codebase I work on has these areas, and they’re terrifying.
Chris to the rescue. If you have a question about why a class was designed the way it was, he knows the answer. During code reviews his insight is indispensable. With extra context on his side, he highlights flaws and unintended consequences that others miss. He’s a librarian and historian of the codebase, with a detailed mental map of the system that is impossible to replicate in a wiki alone.
The jury is out on whether 10x programmers exist, but with his ability to unblock others and make them more productive, Chris comes close.
If your company doesn’t have a Chris, you should get one.2 Better yet, get two.
Chris is figurative here, though I took the name from a past coworker who is very real, and very productive. A software engineering powerhouse. ↩
How do you hire somebody who will be a pillar of the dev team? You got me; I have no idea. It’s a role you can only grow into, and I’m unsure how you identify the person who will do that. ↩