Linus Torvalds on Project Management: Why Users Matter More Than Code

Common Misconceptions in Software Development

Linus Torvalds identifies two pervasive misunderstandings that affect both solo developers and large teams:

Ownership of work – Developers often assume they can hand off tasks and rely on others to complete them. Torvalds stresses that the initiator must treat the work as entirely their responsibility, seeking advice only on *what* to do, not on *who* should do it. Expecting automatic collaboration leads to stalled progress.

Code versus users – Many believe the code they write is the most valuable artifact. Torvalds argues that code only has value when it is actually used. Prioritising code quality at the expense of user experience is a fundamental error.

Importance and Limits of Development Tools

Torvalds distinguishes between the tool itself and the workflow it enables:

For small projects with a few hundred patches per release, manual management (e.g., tar‑balls and plain patches) can be sufficient; a sophisticated SCM is not mandatory.

The Linux kernel, with thousands of patches per three‑month release, requires a robust SCM such as git. The tool supports a fast, distributed workflow, but the underlying process—clear responsibilities, review, and integration—is what delivers value.

Historical tools shape practices: CVS introduced the notion of “committers,” influencing how projects organise authority. Torvalds prefers tar‑balls and patches because they treat all contributors equally, avoiding privileged‑vs‑non‑privileged hierarchies.

Keeping Contributors on Track with the Linux Kernel Mailing List (LKML)

The LKML functions as a public, searchable archive that connects a small core group with the wider developer community:

Developers typically skim subject lines; only a subset reads full threads.

Messages are automatically archived, indexed, and searchable (e.g., via Google), allowing later retrieval of bug discussions and design decisions.

The list is not a mechanism for enforcing discipline; instead, it provides transparency and a shared knowledge base that enables developers to work independently while staying informed.

Trust, Delegation, and Managing Oversight

Torvalds advises leaders to:

Learn to let go and avoid micromanagement. Trusting contributors reduces the need for constant monitoring.

Accept occasional oversight for minor issues (e.g., trivial bugs or workflow annoyances) but recognise that the majority of delegated work is reliable.

Focus on high‑level direction rather than inspecting every line of code; intervene only when a problem threatens the overall stability or user experience.