"I work on OpenBSD fulltime, as the project leader. I set some directions, increase communication between the developers, and try to be involved in nearly every aspect of the base system"
About this Quote
There is a quiet provocation in the plainness of Theo de Raadt's self-description: leadership as sheer, persistent attention. No grand rhetoric about innovation, no visionary buzzwords, just a matter-of-fact inventory of responsibilities that reads like a job ticket. That restraint is the point. In a tech culture that routinely mythologizes founders as idea-machines, de Raadt frames authority as custodianship: setting direction, tightening communication, and staying close to the code.
The phrase "increase communication between the developers" signals a hard-earned lesson from open-source reality: the main enemy of correctness is often not ignorance but drift. Distributed projects don’t fail only from bad code; they fail from mismatched assumptions, undocumented decisions, and unspoken disagreements. His intent is managerial, but the subtext is governance. OpenBSD's reputation for security and correctness depends on coherence, and coherence is a social achievement as much as a technical one.
Most revealing is "try to be involved in nearly every aspect of the base system". For some readers, that reads like control. For OpenBSD, it reads like a quality model: the base system is treated as an integrated whole, not a pile of loosely aligned components. The "try" softens the absolutism, acknowledging scale and limits, but it also telegraphs a standard: fragmentation is a risk, and vigilance is policy.
Context matters: OpenBSD grew up in an era when "move fast" became a credo. De Raadt's ethos answers with an unfashionable counter-claim: the leader’s job is not to accelerate change, but to prevent the wrong change from shipping.
The phrase "increase communication between the developers" signals a hard-earned lesson from open-source reality: the main enemy of correctness is often not ignorance but drift. Distributed projects don’t fail only from bad code; they fail from mismatched assumptions, undocumented decisions, and unspoken disagreements. His intent is managerial, but the subtext is governance. OpenBSD's reputation for security and correctness depends on coherence, and coherence is a social achievement as much as a technical one.
Most revealing is "try to be involved in nearly every aspect of the base system". For some readers, that reads like control. For OpenBSD, it reads like a quality model: the base system is treated as an integrated whole, not a pile of loosely aligned components. The "try" softens the absolutism, acknowledging scale and limits, but it also telegraphs a standard: fragmentation is a risk, and vigilance is policy.
Context matters: OpenBSD grew up in an era when "move fast" became a credo. De Raadt's ethos answers with an unfashionable counter-claim: the leader’s job is not to accelerate change, but to prevent the wrong change from shipping.
Quote Details
| Topic | Leadership |
|---|
More Quotes by Theo
Add to List







