Why we named a studio after the third bit.
One bit is a switch. Two is a choice. Three is where a system starts being able to mean something.
Three bits is where counting turns into meaning.
A single bit holds one of two states. Add a second and you have four — still a table you can hold in your head. Add a third and you get eight, and somewhere in that jump a system stops being a switch and starts being something that can represent things.
- 01 — One bit
A switch. On or off, nothing in between.
012 distinct states
- 02 — Two bits
A choice you can still hold in your head.
000110114 distinct states
- 03 — Three bits
Enough room to mean something. This is the interesting one.
0000010100111001011101118 distinct states — four times the first rung
It's a small technical fact and we have read more into it than a computer scientist would. But it describes the moment we care about in almost every project: the point where scattered information turns into something you can actually reason about.
The pattern isn't ours. It's everywhere.
Three is the point where a sequence stops being a sequence and becomes a structure. Same move, five different languages.
- GeometryLine → Plane → VolumeOnly the third has an inside
- NarrativeAct I → Act II → Act IIIOnly the third resolves
- RhythmBeat → Beat → BeatOnly the third makes it music
- Computation1 bit → 2 bits → 3 bitsOnly the third can represent
- CraftIdea → Iteration → Version 3Only the third is any good
Most bad software decisions are a forced choice between two things.
Binary thinking is efficient and often wrong. True or false, cheap or good, ship it or scrap it. Real decisions in a project usually live in the space those pairs leave out.
- The brief
- Build exactly what was askedObvious
- Turn it downObvious
- Ask what it's actually forতৃতীয় — the third
The dashed line is the cheap one. It costs a conversation and it is the single highest-return thing we do — which is why it's in the name rather than in a values section nobody reads.
তৃতীয় doesn't only mean third.
It carries the sense of the other path — the one outside the two you were offered.
That reading matters to us more than the arithmetic does. The word already contains the argument: a third position isn't a compromise between two others, it's a different question.
It also made for a slightly stubborn company name, which we decided we could live with.
What any of this looks like on a Tuesday.
None of it shows up in a commit message. It shows up in the first two weeks of a project, roughly like this.
- 01
A brief arrives
Usually written as a solution: “we need an app”, “we need a dashboard”.
- 02
We restate it
In one sentence, as a problem, and read it back to you. Half the time it changes here.
- 03
Two options appear
They always do, and they're always the expensive one and the disappointing one.
- 04
We look for the third
Smaller, or differently shaped, or something you can stop doing instead.
- 05
Then we build
Scope written down, price fixed, weekly builds you can click on.
A name is a promise you make to yourself. Ours is that we go one step past the obvious answer before we start building.
Bring us the problem you haven't solved yet.
The ones with an obvious answer rarely need us. Tell us where the two easy options both feel wrong.