The show
Studio · School · Show
Piss Pour Software
Specify the ideal. Pour it so it stays. A house for software that can be specified once and poured again — without folklore, blessed laptops, or Friday ghosts.
Two names, one standard
We named it after the software we refuse to ship.
Piss-poor software is almost never a talent problem. It is a specification problem nobody wanted to look at — then a system nobody can replay.
PISS
Platonically Ideal Software Specification
The form, not last Tuesday’s screenshot. Complete enough that a stranger could implement it without calling you.
POUR
Predictable Observable Universal Replayable
Same inputs, same universe. A story you can read. A recipe that travels. A moment you can pour again.
Latest from the show
Episode 01 · 34 min
The Platonic Spec
Most specs describe a vibe. We want the form — the thing a stranger could build without calling you at 11pm.
Read the essayP
Predictable
Same inputs, same universe, same outputs. Hidden clocks, hidden I/O, and “it depends on the machine” are bugs in the design, not facts of life.
O
Observable
If you cannot see it, it did not happen. State changes leave a trace a person can read. Logs are not a garnish; they are the story of the system.
U
Universal
It behaves the same on a laptop, in CI, and in production. No blessed laptops, no snowflake environments, no “works on my cluster.”
R
Replayable
Any moment can be poured again. Events, not vibes. If you cannot replay a failure, you do not understand it — you only survived it.