The designer in the room was always you
Nobody hired you to design anything. And yet: you picked the defaults, named the buttons, wrote the error messages, and decided what happens when the network drops. Somebody is designing the layer between your code and the people who use it. It's you. It was always you.
The Interface Layer is a field book for engineers who ship without a designer in the room. No color theory, no tools, no lectures — twelve chapters of hard-won judgment, each opening inside a real situation where a reasonable engineering decision produced an unreasonable human outcome, and each closing with a move you can run on your own product this week.
You won't finish it as a designer. You'll finish it as something rarer: an engineer who no longer ships accidental design.
What makes it worth two evenings
UX written for engineers, not designers
The classic usability books assume a design practice exists. This one assumes the opposite — because in most of the software actually running in the world, the engineer is the designer, knowingly or not.
Every chapter ends with a move
Not principles to admire — exercises to run on your own product the same week: the defaults audit, the ten-minute silent user test, the dead-network screenshot gallery, the mouse-unplug pass, the commute test.
Learned from support queues, not studios
The pre-ticked checkbox that buried support for a month. The error message behind a third of the ticket queue. The release that felt twice as fast while changing zero milliseconds. Real incidents, anonymized so they can be told honestly.
The unglamorous chapters included
Forms, empty states, accessibility, offline — the parts of the interface nobody demos and every user meets. Each gets a full chapter, because that's where products actually win or lose.
Short on purpose
Twelve tight chapters, a two-evening read, no padding. Companion to The Manager Layer — same series, same rule: field notes, not frameworks.
Four parts, twelve chapters
Part I — The decisions you didn't know you were making
Defaults as decisions, the user in your head, and why the unhappy paths are the product.
Part II — The craft
Words as the interface, the shape of a screen, and speed as a feature.
Part III — The system
Consistency over cleverness, forms as the everyday battlefield, and the interface everyone forgot.
Part IV — The judgment
Research without a lab, the physics of thumbs, and taste — when to break the rules.
Full chapter list
- Every default is a decision
- The user in your head
- The unhappy paths are the product
- Words are the interface
- The shape of a screen
- Speed is a feature
- Consistency beats cleverness
- Forms, the everyday battlefield
- The interface everyone forgot
- Research without a lab
- The physics of thumbs
- Taste, and when to break the rules
Who it's for
- Engineers shipping product with no designer on the team
- Tech leads and EMs who review UI work and need shared standards
- Backend engineers who own APIs, CLIs, error messages and docs — all interfaces
- Founders building the first version of the product themselves