The Craftsman

The Bureau files this classification from a 30-item forced-choice examination. Nothing on this page describes you — it describes the type, so you can decide whether the description is worth filing. The examination is free and takes six minutes.

I.Documented strengths

• Catches in review the bug the tests were written to miss
• Error messages written by the subject have single-handedly de-escalated support tickets
• Writes code so readable the next hire assumes the codebase came easy

II.Known limitations

• The last 4% of polish reliably consumes 40% of the calendar
• Has rebuilt working software chiefly to stop feeling guilty about it
• 'Good enough' exists in the subject's vocabulary but not in the subject's behavior

III.Recommended assignments

Mature products fighting churn, developer tools, anything where trust is the actual product.

IV.Why this type fits the role

• Where churn is the metric, the subject's polish is the retention strategy. This is the cheapest engineering work nobody budgets for.
• Developer tools reward the last 4% disproportionately: the user's trust is the product, and trust is built at the edges.
• The subject documents as a by-product of caring, so onboarding cost falls without anyone scheduling it.
• In a mature product the danger is regression, not novelty. This is the only archetype whose instincts point at that danger unprompted.

V.What drains this type

• Permanent-hackathon cultures will use the subject as a finishing machine and then ship without them. Expect two such cycles before the exit.
• Scope-driven consulting pays per delivered feature and charges nothing for the correctness the subject adds quietly.
• Deadline-bound legacy triage rewards the fastest correct-enough patch. The subject will not produce one, and the scorecard will not notice why.