Wiki › Work, teams and companies
Programmer Archetypes
Sean Goedecke’s two-axis heuristic for understanding engineers: grifter/believer and grinder/coaster, with complementary strengths and failure modes.
In “Grifters, believers, grinders, and coasters,” Sean Goedecke describes two independent dimensions of engineering work. The deliberately provocative labels name approaches to a job, not immutable personalities or levels of technical ability. His purpose is to make conflicts between colleagues more understandable.
Two axes, not four mutually exclusive boxes
- Grifter ↔ believer: navigating what the organization actually rewards versus prioritizing a mission, user interests and engineering values even at a personal career cost.
- Grinder ↔ coaster: operating at sustained high intensity versus doing the necessary work while preserving slack and time for reflection.
A person can therefore be both a grifter and a coaster, or a believer and a grinder. Context, career stage and working conditions can change the combination. The diagram illustrates positioning, not a validated measurement scale.
Contributions and failure modes
| Approach | Contribution in the author's account | Risk when dominant |
| --- | --- | --- |
| Grifter | Reads incentives, manages up, builds buy-in and unblocks large cross-team projects. Can deliver excellent code when that is rewarded. | Adapts to a weak culture instead of changing it; neglects unrewarded security, accessibility or performance work. |
| Believer | Protects users, quality and long-term maintenance even when incentives favor something else. | Can become inflexible when strategy changes; mission commitment alone does not ensure viability. |
| Coaster | Preserves calm, reflection and spare capacity for interruptions or urgent requests. Avoids unnecessary activity. | Less suited to a large queue of well-defined work requiring sustained throughput. |
| Grinder | Executes quickly, handles a large volume of code, reviews and operational tasks. | Tunnel vision, strain and severe burnout; activity can crowd out strategic judgment. |
These are not synonyms for fraud, gullibility, laziness or virtue. Goedecke explicitly allows all four approaches to be competent. His further claim that grinding is usually unsustainable, and that few staff+ engineers remain grinders, comes from personal observation rather than longitudinal evidence.
Practical use
Use the framework to distinguish different conflicts: incentives versus values, or urgency versus sustainable pace. Someone protecting spare capacity may be providing resilience rather than shirking; someone building leadership support may be enabling delivery rather than merely politicking. Conversely, a stated mission does not remove incentive problems, and high effort does not by itself establish impact.
The author's recommendation is a complementary mix: believers preserve standards, grifters secure organizational alignment, grinders absorb some intense execution, and coasters preserve calm and slack. This is not a demand that every team hire one of each, or a prescription to overload particular people. Role, consent, workload and context still matter.
Connections and limits
The framework gives Organizational Moats a team-composition lens: an organization needs both principled maintenance and the political mechanisms that let projects ship. It also qualifies the emphasis on ownership and technical productivity in Modern Engineering Values: quiet reflection and organizational alignment can be valuable work even when they produce few visible artifacts.
No independent study or predictive test is supplied in the source. Use the labels as prompts for discussion, not diagnoses, performance scores or an explanation of every workplace dispute.
Mentioned in 2 pages
Work, teams and companies
People & organisations