You work as an engineer in an org and think the code is 20% of the job, so AI automating that part leaves you safe. But that line of reasoning has one consequence: it means you were already a bureaucrat. Not pejoratively. Bureaucracy has its place. But the industrialization hollowed out the craft long before the models arrived. Which means there is less protecting you than you think.
The code and understanding the code was your real moat. You had the craft and talked yourself out of it. You started running processes and ceremonies, writing docs about systems you no longer built, telling yourself you were above the code. And honestly, you were not sad about it. The code was always the part you wanted to escape.
Everyone is quietly hoping AI plateaus right before it reaches their specific skill level. Find yourself on the spectrum below and use it as a reflection tool. This is not a manifesto. We are on the brink of a paradigm shift and nobody knows what comes next. The more honest question is not whether your role survives. It is what you want to be doing when the music stops.
The terms come from an internet meme circa 2021, loosely rooted in cognitive research: verbal reasoning versus spatial rotation as distinct cognitive modes. Slightly edgy framing, but the underlying distinction is real and useful here.
Shape rotators think in systems, code, spatial structures. Wordcels think in narrative, language, persuasion. The original thesis: tech was run by wordcels at the top and shape rotators doing the actual work below.
AI flipped it. AI is the ultimate shape rotator. It manipulates code and data structures faster than any human. Pure shape rotation is getting commoditized. The wordcel input layer is now more valuable because articulating what to build clearly is what you feed the machine.
The real winner is neither. It is the person who is both. Who sees the shapes and tells the story. That is what the left end of the slider below actually looks like in a person: not someone who codes and also has taste, but someone for whom the thinking and the making are the same motion. The insight does not precede the work. It lives inside it. You cannot hand that to a model because there is no spec to hand over. The spec is what emerges from the building.
The open question: who crosses more successfully? My take: a great designer has an easier path to building than a great engineer has to designing. The counterargument writes itself: great engineers at the Craftsman end have gestalt too, the feel for when a system is wrong before they can say why. True. But engineering gestalt is about the medium. Design gestalt is about people: taste, intuition, the sense of what feels right before you can explain why. That is gestalt. When AI handles more of the medium, people gestalt travels further. The engineer's intuition does not disappear. It just operates on a layer that is becoming more automated.
I built a radio with Claude Code and only later realized how elegant the math behind it was. Radiobananas.art is a music radio handpicked from my own taste. Everyone hears the same music at the same time without any backend sync or websocket. Just a static HTML page with files sitting on Cloudflare R2.
So how do my phone in Amsterdam and your laptop in Yerevan end up on the exact same second of the same song. It is just: (UTC seconds since midnight) % total playlist duration. Everyone runs the same calculation and gets the same answer.
The shuffle is what makes it tricky. If it is random, two people loading the site at different moments get different orders and the whole thing breaks. So it has to be a deterministic shuffle, same input, same output, everywhere. I use the date as the seed so everyone gets the same shuffle for the day.
The shuffle itself is the Fisher-Yates shuffle, which guarantees every track plays exactly once before the cycle repeats. There is also a tiny three-line PRNG in the code, a variant of xorshift from the 1990s. Without it, Math.random breaks the sync.
Here is the part that matters for this page. If you look at what is actually in that codebase: deterministic shuffles, a PRNG variant, modular arithmetic for sync. None of these are trivial. A year ago I would have been the gatekeeper for this. You needed to understand xorshift to produce xorshift. Now I curated it, understood it after the fact, and shipped. A good designer with a flexible brain and a good model could build a better version of this than I did. That is not a complaint. That is the elephant in the room this entire page is about.
Seven archetypes on a spectrum. On one end, insight and craft are fused: you discover the answer by building it. On the other, they are separated by layers of process: someone else holds the vision and you implement it.
Intelligence is executing complex rules. Judgement is knowing which rules apply, when to break them, and what to build next. AI has crossed the threshold where it can do most intelligence work autonomously. Where thinking and building are one, the work is mostly judgement. Where they are separated by layers of process, it is mostly intelligence. That is why it matters where you land.
Drag to find where you are.