An architect drives past a building they designed and says, "I made that." A surgeon watches a patient walk out of the hospital. A carpenter runs a hand along the grain of a table they built from raw timber. A painter stands in front of a canvas. A chef watches someone close their eyes after the first bite.
A software developer closes their laptop and goes home.
The work is somewhere. It runs on servers in Virginia or São Paulo. It processes millions of requests. It handles payments, routes ambulances, connects people across continents. It might be the most consequential work on the list. But the developer cannot point to it. They cannot touch it. They cannot hang it on a wall or walk past it on the street.
Software, for all its power, produces nothing you can hold.
The Intangibility Problem
In 2017, researchers Ozgun Atasoy and Carey Morewedge at Boston University published a study across five experiments showing that people consistently valued physical goods more than identical digital versions. Tourists paid 48% more for a physical souvenir photograph than a digital one. Students paid more to buy a physical textbook than a digital copy. Participants paid more for physical books and films than their digital equivalents.
The mechanism, the researchers found, was psychological ownership. Physical objects create a stronger association with the self. You can touch them. You can place them somewhere. You can control them in space. Digital goods feel transient - fast, spontaneous, ephemeral. Physical goods feel permanent and stable.
The study was about consumer goods, but the implications reach further. If physical objects create stronger psychological ownership, what happens to a person whose entire professional output is digital? What happens to someone who builds things for a living but never produces anything they can hold?
The answer, I think, is a low-grade, persistent sense of unreality about the value of their own work. Developers know intellectually that the software they built matters. They can see the metrics, the user counts, the revenue dashboards. But knowing and feeling are different operations, and the physical world has a monopoly on the second one.
The Absence of Proof
Most professions accumulate artifacts. A lawyer has binders of case files. A doctor has a white coat with their name embroidered on it. An academic has shelves of published papers. Even a plumber has the satisfaction of watching water flow where it did not flow before.
Software developers accumulate almost nothing physical. The code lives in repositories. The products live on servers. The work is experienced by users who will never know the developer's name. The best code is the kind nobody notices - infrastructure so reliable it becomes invisible, interfaces so intuitive they feel obvious in retrospect.
There is a particular cruelty in this for senior developers. A decade of career progression looks, from the outside, like a series of identical days at the same desk. The desk might get nicer. The screens might multiply. But there is no shelf of trophies, no portfolio of tangible work, no accumulating physical evidence of mastery.
Remote work made this worse. At least in an office, there were whiteboards covered in architecture diagrams, sticky notes from sprint planning, a team you could see and touch. Working from home, the developer's entire professional existence collapses into a rectangle of light. Close the laptop and the evidence vanishes.
Why the Shelf Matters
Research on physical awards in the workplace - even in our era of remote teams and digital badges - consistently shows that tangible recognition objects outperform digital ones in emotional impact and memory formation. A trophy on a shelf stays visible long after the initial achievement. It triggers what psychologists call emotional memory - the association of an accomplishment with a specific moment in time that can be revisited physically.
A digital badge in a Slack channel does the opposite. It scrolls away. It gets buried under other messages. Within a week, nobody remembers it was there.
The human brain evolved in a world of objects. We think with our hands. We understand through touch. We remember what we can see in our peripheral vision as we walk through a room. The physical environment is not a backdrop to our cognitive life - it is woven into it.
Developers are asked to produce their most important work entirely outside this system. Everything they build exists in a medium the brain did not evolve to grasp. The screen shows them text. The terminal shows them output. But the body receives nothing.
The Torres Strait Islanders Had It Right
There is a wonderful entry in the academic catalogue of physical data visualisations about the Torres Strait Islanders. In the 19th century, these Pacific islanders did not have a numeral system, so they used sticks to keep counts. Each stick represented an accomplishment - a turtle caught, a fish speared. The sticks were tied to a string, forming a bundle called a kupe.
Kupes were used as social displays. Big kupes were greatly prized. When you wanted to show what you had achieved, you unrolled your bundle.
Every culture, across all of human history, has found ways to make accomplishment physical. The impulse is universal. Medals, trophies, certificates, diplomas, notches on a belt, merit badges, championship rings. Humans need proof they can hold.
Software developers are among the first professionals in history to produce work of enormous value while generating zero physical artifacts. No kupes. No notches. No bundle to unroll.
What a Print Does
A Codex Stellarum atlas is, at its core, a physical artifact of digital work.
The data is public - it is right there on the developer's GitHub profile. The information is the same whether you view it as a grid of green squares on a screen or as a constellation of stars on a print. The content has not changed.
But something else has. When that data becomes a 70-centimetre Giclée print on 200gsm archival paper, it crosses a threshold. It enters the physical world. It gains weight and texture. It can be framed, hung, touched. It occupies space in a room and in the peripheral vision of the person who made it.
The developer who hangs their atlas on the wall is doing something that sounds simple but is actually radical for their profession: they are making their work visible to themselves.
Not visible as a dashboard or a metric or a green square. Visible as an object. A thing with presence. A thing that says, quietly and continuously, from the wall above their desk: you built something. Here is the proof.
The Wharton researchers found that physical objects create psychological ownership - a felt sense that something is yours, connected to your identity. A digital contribution graph does not produce this feeling. A print does. The same data, in a different medium, creates a different relationship with the self.
That is what a print does. It gives a software developer something they have almost never had in their career.
Something to hold.
See what your work looks like when it leaves the screen. Enter your GitHub username at codexstellarum.com and preview your atlas - free to try, prints from £25.