The Radiating Programmer
Source: https://dev.37signals.com/the-radiating-programmer/ ↗
Manrubia describes a type of engineer who works in the open — sharing context as they go, not in reports but in the texture of how they think aloud.
The essay is short and deceptively simple: it names a behaviour that small teams depend on and that most organisations accidentally train out of people.
In 37signals terms it is a cousin of writing over meetings; in product direction terms it is a description of what distributed autonomy actually looks like when it works.
If your team is full of radiating programmers, you will know from the logs, not from the standups.
Central argument
Manrubia argues that the most valuable engineers are those who radiate context as a natural by-product of how they work — sharing progress, blockers, and reasoning in public channels without being asked. This is not about status updates or transparency theatre, but about a working style where thinking aloud is habitual and informational residue accumulates for others to use. The essay implicitly frames this behaviour as an organisational asset that reduces coordination overhead and enables genuine autonomy, contrasting it with the default pattern where work is invisible until it surfaces in a meeting.
Critique
The essay risks romanticising a behaviour that is structurally easier for some people than others — engineers who are confident, senior, or working in psychologically safe environments radiate more naturally, while those who are junior, neurodivergent, or operating in high-stakes cultures may self-censor precisely because visibility feels risky. Manrubia locates the behaviour in individual disposition rather than in the organisational conditions that produce or suppress it, which means the essay is more useful as a hiring heuristic than as a lever for culture change.
Why it matters for product
For a CPO, the radiating programmer is a diagnostic signal about organisational health: if product decisions routinely depend on standups or escalations to surface engineering context, the team structure is generating information debt that slows discovery and complicates prioritisation. Manrubia's framing also sharpens the design of async-first team rituals — the question is not how to get engineers to report more, but how to create environments where thinking in the open is the path of least resistance rather than an extra act of will.