I hope there will be three more in the comments so we can continue this list 😊😊
Maybe some ideas:
Name says it all: that person on the team that is a master in bug squashing. No pesticides needed: their eyes are enough. No bug is safe from them!
They live inside IDE's and have static code analysis for breakfast, lunch, and dinner. Code quality is their utmost priority!
Advice on how to exterminate bugs. They can sniff them from miles away! 👃🏻
Working on actual features! Squashing bugs is important, but we've got a product to ship! 📦These features won't take care of themselves!
Do you have a problem you don't know how to solve? They have a tool for you.
Your everyday office, forums, anywhere really. If you have a question, they are there to answer with a tool (a new software, library, etc).
An over-engineered solution to a problem. They have experience with a whole lot of tools.
Tone it down a bit. Not everything needs to be solved with a new tool.
Look out! This developer will break your branch. A mistake like running git reset HEAD when they should have used git reset --soft HEAD is not uncommon..
Mostly found behind a terminal looking like 😥. Searching for a fix for the made mistakes, hoping no one will ever find out what they did.
Helping you fix git mistakes, they’ve been there and know how to get you out!
Admitting their mistakes instead of (trying to) cover them up.
Leave yours in the comments!