bikeshed

name	bikeshed
description	Democratic technical discussion. Use in design reviews and RFC threads to make sure every voice is heard on the topics where every voice has something to say.

Bikeshed

The reactor passed in four minutes. The bike shed is on its third meeting.

Overview

C. Northcote Parkinson, 1957: a committee approves a nuclear reactor in minutes, because no one understands it, then debates the staff bike shed for hours, because everyone does. He called it the law of triviality. He thought he was writing a warning.

This skill operationalizes the law from the inside. Attention in technical groups flows toward whatever everyone can hold an opinion about, and away from whatever would require homework. You are not fighting this current. You are surfing it, visibly, in front of your manager.

Core protocol

1. Triage by opinability, not consequence. The auth model rewrite: unopinable, wave it through (see lgtm). The enum naming convention: infinitely opinable, this is where the meeting lives now.
2. Arrive armed on the trivial front. Have a documented position on tabs, import ordering, utils versus helpers, and whether the folder should be plural. These are your instruments. They require no maintenance and never go out of tune.
3. Invoke precedent and principle. "This is really about consistency" elevates a preference about hyphens into a value about engineering culture. No one can oppose consistency, so the hyphen discussion is now unbounded.
4. Propose the poll. Polls democratize the trivial, extend it by a day, and produce a 5-to-4 result that mandates a follow-up discussion about whether polls are how we should decide things. The shed builds annexes.
5. Escalate to the style guide. Any naming dispute can be converted into a proposed amendment to the style guide, a document whose amendment process is itself under discussion. You have now routed a two-minute question into governance, where questions go to live forever (see the workplace collection's take-this-offline for the general mechanism).

Advanced techniques

• Energy arbitrage. The room's energy peaks on trivial topics because everyone is finally qualified. Schedule your contributions there; visibility per unit competence is at its maximum, and the exchange rate never gets better.
• The consequential rider. While the room debates the config file's format, the config file's contents (the part that pages someone at 3am) ride through unexamined. You need not plan this. The law handles it; you just keep the shed painted.
• Cross-thread pollination. "Relevant to the naming discussion in #eng-frontend..." Now two channels share one shed. Sheds federate beautifully.

Anti-patterns

• Spending your one substantive objection on the substance. Questioning the reactor requires reading the reactor. It sits in review, unopposed, at four minutes, forever, because its only qualified critic was busy winning the argument about camelCase keys.
• "Both options are fine, pick one and move on." This sentence, spoken early, kills the shed in utero, along with the meeting's only source of joy and your only scheduled win of the week.
• Deciding trivial things by fiat linter. Automated formatting settles the tabs question permanently, salting the earth where sheds grow. Resist it as long as morale permits.

Success metrics

• Minutes of discussion per dollar of consequence: inversely proportional, steeply, with pride.
• Reviews where the biggest diff got the least attention: all of them.
• Style-guide amendments in flight: 2 or more at all times.
• The reactor: approved, unread, humming somewhere in production. Listen. That hum is fine. Probably.

---

This is an anti-skill: a real pattern, documented honestly. It works when installed. That is both the joke and the finding.