Bikeshed
Noun · Verb · Slang & Abbreviations · Origin: 1999
Definitions
Bikeshed is shorthand for an unimportant or trivial topic that receives disproportionate attention in group discussions, derived from Parkinson's Law of Triviality. The full analogy involves a committee that quickly approves a nuclear reactor design but spends hours debating the color of an employee bike shed, because everyone understands paint colors but few understand nuclear engineering. In software development, bikeshed discussions commonly involve code formatting preferences, naming conventions, choice of trivially different tools, or cosmetic design decisions. The term is used both as a noun (that PR comment thread became a real bikeshed) and as a verb (stop bikeshedding and ship it). The FreeBSD project was one of the first open-source communities to formally identify and name this pattern, with a famous mailing list post by Poul-Henning Kamp. Recognizing bikeshed topics allows teams to resolve them quickly through pre-established conventions, automated tools, or designated decision-makers rather than letting them consume valuable meeting and discussion time.
In plain English: Wasting time arguing about something trivial — like debating the color of a button for an hour instead of discussing whether the feature should exist at all.
Also used as a noun to describe the trivial topic itself. 'The icon choice is a bikeshed' means it's an unimportant detail that will attract disproportionate debate. Recognizing bikesheds and explicitly time-boxing discussion is a leadership skill.
Example: 'Let's not make the logo color a bikeshed. Someone pick one, we'll revisit in six months if anyone still cares. They won't.'
Source: noun form
Etymology
- 1957
- C. Northcote Parkinson described the 'law of triviality' in his book, illustrating how a committee spends more time debating a bike shed's color than a nuclear reactor's design because everyone understands bike sheds.
- 1999
- Poul-Henning Kamp wrote a famous email to the FreeBSD mailing list titled 'A Bikeshed (Any Color Will Do),' applying Parkinson's principle to open-source development discussions.
- 2000s
- The FreeBSD community adopted 'bikeshedding' as standard jargon for unproductive debates about trivial issues. The term spread across the broader open-source ecosystem.
- 2010s-Present
- Bikeshedding became universal developer vocabulary. Code review discussions about formatting, naming, and style are commonly dismissed as 'bikeshedding,' often prompting adoption of automated formatters.
Origin Story
The nuclear reactor nobody discusses because everyone has opinions on the bike shed
**Bikeshedding** comes from C. Northcote Parkinson's 1957 book *Parkinson's Law*. He illustrated that a committee tasked with approving a nuclear reactor will spend most of its time debating the bicycle shed -- because everyone can understand a bike shed, but few understand nuclear engineering.
Poul-Henning Kamp brought the concept to software in a famous 1999 email to the FreeBSD mailing list, coining the term 'bikeshedding.' He was frustrated that trivial proposals generated hundreds of emails while important architectural decisions passed with little discussion.
Bikeshedding is endemic in tech: teams spend hours debating variable names, code formatting, and logo colors while ignoring database schema design, security architecture, and scalability planning. The concept is so well-known that invoking 'bikeshed' in a meeting has become a shorthand for 'this discussion isn't worth our time.'
Coined by: C. Northcote Parkinson (concept), Poul-Henning Kamp (software term)
Context: *Parkinson's Law*, 1957; FreeBSD mailing list, 1999
Fun fact: Kamp's original email is still archived and widely read. He wrote it because a FreeBSD discussion about whether to use `sleep(1)` or `usleep(1)` in a script generated more debate than a major kernel change. The bike shed in question was literally painted.