/rīt thiŋ/
noun — “the supposedly obvious solution that somehow still starts arguments.”
Right Thing refers to the solution, behavior, design choice, or action considered compellingly correct, elegant, or appropriate within a given technical or conceptual context. The phrase is often spoken with heavy emphasis—as if capitalized verbally—even when the “correct” answer is far from universally agreed upon. In hacker culture and programming discussions, invoking the Right Thing usually implies confidence bordering on philosophy.
The term became especially associated with early LISP and hacker communities, where debates about language behavior, software design, and system architecture could spiral into long, deeply opinionated arguments. Developers would argue not merely about what works, but what should work… the cleaner abstraction, the more elegant behavior, the more philosophically pure implementation. The amusing part is that two equally intelligent programmers could each insist they were defending the Right Thing, while arriving at completely opposite conclusions.
In technical culture, the Right Thing often contrasts with pragmatism. A solution may be theoretically beautiful yet impractical in production, or efficient yet aesthetically offensive to language purists. This tension appears everywhere: API design, operating systems, naming conventions, error handling, parser behavior, indentation styles… yes, even tabs versus spaces somehow becomes existential after enough caffeine.
Historically, the phrase gained traction through hacker jargon and communities surrounding LISP, UNIX, and academic computing culture. It became shorthand for a style of reasoning where elegance and conceptual purity mattered deeply. Unlike a simple “best practice,” the Right Thing carries a subtle implication of inevitability—as though the universe itself secretly prefers one implementation over another.
In practice, Right Thing might include:
// Example 1: divide-by-zero debate
What's the right thing for LISP to do when it sees:
(mod a 0)
Should it:
- return a
- throw an error
- return NIL
- halt execution entirely?
// Example 2: API behavior discussion
Should an API silently ignore invalid input,
or should it fail loudly and immediately?
// Example 3: filesystem philosophy
Should file paths always use forward slashes internally,
even on systems that historically used backslashes?Conceptually, the Right Thing is less about certainty and more about conviction. It’s the idea that software design can possess elegance beyond mere functionality—that certain solutions feel internally consistent, harmonious, or intellectually satisfying. Of course, the moment someone confidently declares they’ve found the Right Thing, somebody else usually appears five minutes later with a completely different interpretation… equally convinced.
Oppose Wrong Thing.
See LISP, Hacker Culture, UNIX, API, Software Design