A Underappreciated Software Developer that proactively searches for and fixes bugs as soon as they find them.
Where most software developers can be compared to engineers, The Hunter is best compared to a surgeon. Hunters meticulously roam across a system looking for bugs, and when they find a bug, they perform a thorough evaluation to determine it’s relative priority and severity. If they conclude that an urgent fix is needed, they start working on a fix immediately.
Hunters are passionate about keeping the number of critical bugs in a system as low as possible. The Hunter’s true power lies in their combination of excellent judgment and extreme attention to detail. They utilize precise examination and verification cycles that exercise every conceivable scenario to direct their modifications to the codebase.
Hunters shine in situations where bugs are a challenge to find using traditional testing methods. They are particularly valuable when they identify and correct bugs related to security, performance, and scalability. While dedicated teams of testers might object to a software developer independently finding and fixing bugs, the Hunter is most appreciated when they are covering areas not included in normal testing procedures.
- Will find new bugs that no one knew even existed.
- Will not wait for permission to fix serious bugs.
- Will not create new bugs with their bug fix.
- Will fix the issue completely for all use-cases.
- Will only fix bugs that are of the highest severity and priority
- Hunters are not The Idealist as they are not working to improve code aesthetics, but to fix serious bugs.
- Hunters are not acting as The Random Clicker, as randomly exploring a system is only one of the tools they employ to find bugs, not their only tool.
- Hunters are not The Bull in the China Shop as they never introduce new bugs with their fixes.
- Hunters are often found working in legacy software, but they are not The Legacy Maintainer in that they can work in systems they are not familiar with.
Supporting Team Members
- The Healer can collaborate with a Hunter to refactor or rewrite a system riddled with bugs.
- The Mechanic can build frameworks that eliminate entire classes of bugs that the Hunter finds are constantly being introduced.
- The Wizard can partner with a Hunter to tackle particularly difficult types of bugs.
- The Tank can insulate the Hunter from questions regarding why they are taking the initiative to fix serious bugs.
- Hunters will appreciate any expression of gratitude from the testing department for their proactive efforts to improve the quality of the system.
- Hunters will enjoy expressions of gratitude directly from people who were impacted – or could have been impacted by – a bug they fix.
- Hunters appreciate public recognition of their efforts to reduce and eliminate high severity bugs.
Typical Soft Skills Scorecard
- Hunters will find it easier to explain why they fixed a bug as they improve their Communication.
- Hunters will often need to collaborate and partner with other software developers, leading to them to benefit from increased Teamwork.
- Hunters will be able to better classify and prioritize which bugs are most important as they increase their Business Focus and Deadline Focus.
- Hunters will still have work they have to complete beyond bugs, requiring them to develop techniques that maximize their Productivity.