linus torvalds

Bilingual

On Linus Torvalds, technical & corporate communications - Bert Hubert's writings
2 months ago
- Linus Torvalds' communication style degraded from robust to hurtful, but he is now seeking help.
- Three communication styles are contrasted: aggressive honesty, corporate HR-compliant verbosity, and concise engineer-style directness.
- The engineer-style response is recommended as it is direct yet respectful, avoiding both insults and bureaucratic padding.
- Supporters of Linus' old style mistakenly conflate swearing with honesty, fearing that avoiding insults leads to corporate drivel.
- It is possible to communicate concisely without insulting, and engineering organizations should strive for this.
<antirez>
2 months ago
- Linus Torvalds' early work on Linux was technically impressive but within reach of many skilled programmers, not just a unique genius.
- Torvalds shifted from writing most code himself to primarily leading and coordinating the Linux project, delegating implementation to maintainers.
- His role as leader involves maintaining design coherence and direction, not reviewing every patch line-by-line, unlike many other project maintainers.
- This leadership style mirrors modern AI-assisted programming, where developers act as directors guiding agents (like maintainers) rather than writing all code.
- Automatic programming, when done well, requires expertise in design and communication, not just prompting, and demands training similar to Linus' evolution.
Being Linux Torvalds
2 months ago
- Linus Torvalds initially wrote the Linux kernel, a feat achievable by many skilled programmers, not just unique geniuses.
- His true genius lay in transitioning from coding to leading, coordinating, and defining the project's direction.
- He delegated implementation to maintainers, focusing on design concepts and strategic decisions rather than line-by-line code review.
- This leadership style, described using Brooks' 'Mythical Man Month' concepts, is rare among open-source maintainers.
- In AI-assisted programming, developers should adopt Linus's role as a director, guiding agents (like maintainers) while they implement code.
- This approach is easier and faster than managing human teams, with less context switching and interpersonal issues.
- Automatic programming for experts is not 'vibe coding' but assuming a leadership role, requiring training and design intuition.
- The lesson of Linus is that programming with AI means becoming an orchestra conductor, not just a coder.
Why Linus Is Right and AI Is Wrong
2 months ago
- Linus Torvalds affirms Linux is not anti-AI, views AI as a useful tool, and tells critics they can fork or walk away.
- The author argues pragmatic engineers are natural allies of AI critics because excessive AI use is unpragmatic and wasteful.
- The author uses rhetorical analysis (Kings Council pattern) to show how Linus's words are being weaponized by AI hype to silence critics.
- Criticism of Anthropic CEO Dario Amodei for inciting panic, manipulating markets, and using alarming predictions to gain power.
- Proposes language reforms: avoid disempowerment terms (e.g., 'left behind'), call technologies by specific names, and reject anthropomorphizing AI.
- Calls for solidarity among AI critics and recognition that most developers are allies despite surface-level pro-AI rhetoric.
- The author supports right of refusal for AI use in projects, citing examples like Ghostty and Zig, and criticizes purity tests.

linus torvalds

On Linus Torvalds, technical & corporate communications - Bert Hubert's writings

<antirez>

Being Linux Torvalds

Why Linus Is Right and AI Is Wrong