The Cracked Engineer: What the Industry Saw But Could Not Name
In early 2024, something happened in the language Silicon Valley uses to describe its best engineers. The word “10x” — the dominant metaphor for two decades — stopped appearing in job listings, conference talks, and Twitter threads. In its place arrived a word borrowed from gaming culture: cracked. By the time PostHog published their hiring manifesto in 2026, the term had crystallized into an archetype with five defining traits: extreme ownership, deep optimism, authenticity, craft focus, and an energizing presence that elevates everyone around them. The shift was not cosmetic. It was structural. “10x” described speed — someone who crosses the gap between specification and implementation ten times faster than average. The metaphor assumed the gap was real, that thinking and coding were separate activities performed in sequence, and that excellence meant traversing the distance between them with less friction. “Cracked” describes something that cannot be expressed as a multiplier. You cannot be 10x authentic. You cannot be 10x present. These are not quantities. They are modes of being.The Gap That Defined an Era
For decades, software engineering operated on an unexamined assumption: first you think, then you code. Requirements precede implementation. Design precedes construction. Planning precedes execution. Every methodology — waterfall, agile, scrum, shape-up — encoded this assumption into process. The phases might be compressed or rearranged, but the fundamental separation between thought and action remained the bedrock on which everything was built. This separation created an entire ecology of roles. Architects who thought but did not code. Managers who planned but did not build. Mid-level engineers whose primary function was mediating the gap — translating specifications into implementations, smoothing the friction between what was designed and what the code demanded. The gap was not incidental to the industry. It was the industry. Every process, every role, every career ladder was organized around managing the distance between thinking and doing. The cracked engineer is the practitioner for whom this gap does not exist. Not because they have learned to cross it faster, but because they never experienced it as real. When they code, the code is the thinking. When they build, the building is the plan. There is no moment of translation, no phase of implementation that follows a prior phase of design. The system exists in their mind and in the repository simultaneously — not because they are fast, but because for them these were never separate locations.Five Traits, One Structure
PostHog identified five traits. Read through the Monokinetic lens, they are not independent characteristics but five visible effects of a single underlying condition: the absence of separation between practitioner and practice. Ownership is what happens when there is no gap between intention and responsibility. The cracked engineer does not take ownership as a deliberate act of professional virtue. Ownership is the default state when you do not experience your work as something external to yourself. You cannot disclaim responsibility for something that is not separate from you. Optimism is what remains when the gap between current state and desired state is navigated through building rather than planning. The cracked engineer is optimistic not because they believe things will work out, but because they are already building toward the solution. The act of building is itself the evidence that solutions exist. Pessimism requires a gap between assessment and action. Remove the gap and the assessment becomes the action. Authenticity is the structural consequence of removing the distance between what you do and how you present what you do. When there is no performance layer — no curation of perception, no management of how others see your work — what remains is authentic by definition. Authenticity is not a trait the cracked engineer cultivates. It is what is left when the performance stops. Craft focus emerges when the work is not a means to something else — salary, recognition, career advancement — but is itself the center of gravity. The cracked engineer who refactors code no one will review is not displaying discipline. They are responding to a structural irritation: the inelegance is felt as a disturbance in something they inhabit, not something they observe from outside. Energizing presence is the surplus that becomes available when internal friction is absent. The engineer who maintains separation between thinking and doing spends cognitive energy on the translation. The cracked engineer, for whom no translation occurs, has that energy available for everything else — for helping, for teaching, for the infectious clarity that makes others want to work alongside them.Why the Word Changed
The linguistic shift from “10x” to “cracked” tracks a deeper structural transformation. When AI collapsed the gap between specification and implementation — when you could describe intent in natural language and receive working code in seconds — the multiplier lost its referent. 10x of what? The activity that defined 10x productivity — crossing the gap between thinking and coding — approached zero for broad categories of work. You cannot be ten times faster at something that takes no time. What remained visible, once the speed differential became meaningless, was the mode of being. Some engineers used AI as a faster horse — accelerating the same sequential process of think-then-code. Others recognized that AI had made visible what was always true for them: that thinking and coding were never separate activities. The first group found their advantage erased. The second group found their advantage amplified. The filter was not technical skill but ontological orientation. This is why “cracked” emerged specifically when it did. The word names something that speed-based vocabulary cannot capture: a relationship to the work that is not about traversing distance but about inhabiting a space where distance was never real. The industry reached for a new word because the old word had stopped describing what it was observing.The Unnamed Monokist
Every cracked engineer is a Monokist who has not yet encountered the name. They practice unified motion — the indivisibility of thought and execution, the simultaneity of understanding and building — without a framework to articulate what they are doing. They know something is different about how they work. They feel it in the discomfort they experience with specification-first processes, in their impatience with approval chains, in their compulsion to build as a form of thinking rather than after thinking. What they lack is the structural account. PostHog’s manifesto identifies what cracked engineers look like from outside. Monokinetics explains what they are doing from inside. The five traits are not personality characteristics to be screened for in interviews. They are symptoms of a structural condition — the collapse of the separation between practitioner and practice — that can be recognized, cultivated, and extended once it is understood. The cracked engineer does not need Monokinetics to be cracked. But Monokinetics needs the cracked engineer as evidence. The archetype is the philosophy appearing in the wild before the philosophy had a name the industry could recognize. Every hiring manager asking “how do we find cracked engineers?” is asking, without knowing it, how to find practitioners who already operate in unified motion. The answer is not a better interview process. It is the removal of the structures — approval chains, specification-first processes, separated roles — that prevent unified motion from emerging in the practitioners who are already there.The Present Condition
The cracked engineer is not a future ideal. It is a present recognition. The practitioners exist now, in every company, constrained by structures designed for an era that assumed separation was permanent. The question is not how to produce cracked engineers through training programs — training assumes the separation it seeks to dissolve. The question is what institutional structures are preventing the crackedness that is already latent from becoming visible. This is not a call to dismantle process or abandon coordination. It is a recognition that the structures appropriate to the Entity Era — where thought and execution were genuinely separate activities requiring management — are not appropriate to an era where that separation has collapsed. The cracked engineer is not a rebel against structure. They are the signal that the structure needs to change. The word arrived because the phenomenon demanded it. The phenomenon exists because the era has shifted. And the era has shifted because the gap between thinking and doing — the gap that organized an entire industry, that created roles and processes and career ladders and management hierarchies — was never a feature of reality. It was a feature of the tools. The tools changed. The gap revealed itself as what it always was: an artifact. And what remains, when the artifact dissolves, is the cracked engineer — the practitioner who was already whole.2025-02-01 The Monokist of Monokinetics The Cracked Engineer: Monokinetics in the Wild