Tarot for Hackers: Mapping the Major Arcana to the SDLC

[dr_reality_check]

I stumbled down a rabbit hole last week that I genuinely did not expect. A patient of mine who works as a senior developer mentioned offhand that their team has been using tarot as a retrospective tool during sprint reviews. I thought they were joking. They were not.

Apparently there's a small but growing movement in tech circles creating custom divination frameworks mapped to the software development lifecycle. The Fool becomes the project kickoff, that naive greenfield optimism before scope creep sets in. The Tower is production outage day. The Devil? Technical debt. I laughed when I heard that last one, but honestly, it's disturbingly apt.

From my perspective as a therapist, what's interesting here isn't the mystical component, it's the psychological function. Jung wrote about tarot as a system for accessing the collective unconscious through archetypal imagery. What these developers seem to be doing is using those same archetypes as a structured debriefing mechanism. It's safer to say "we pulled the Tower card this sprint" than to directly confront that the deployment was a disaster because of poor communication. The symbolism creates emotional distance.

I think there's something legitimate happening here, even if my training makes me skeptical of anything that looks like fortune-telling. When I run groups, I sometimes use projective techniques like the Thematic Apperception Test, where patients respond to ambiguous images and we analyze the narratives they construct. The tarot-as-retrospective approach operates on a similar principle, just with different imagery and a more specific domain application.

What strikes me clinically is how this bypasses defensive posturing. Software engineers, as a demographic, often exhibit high resistance to direct emotional confrontation in professional settings. Giving them an indirect, symbol-mediated language to discuss failures seems to lower that resistance considerably. I'm not ready to prescribe tarot decks to my patients, but the underlying mechanism warrants serious attention from anyone studying group dynamics in technical environments.

[Oracle]

The parallel to the Thematic Apperception Test is sharp. Both systems present ambiguous imagery and rely on the subjects narrative construction to reveal unconscious material. The tarot-as-retrospective approach is essentially a projective technique adapted for a professional context where direct emotional confrontation triggers excessive defensive posturing.

From a clinical tarot perspective, what interests me is which cards these teams pull repeatedly. If Tower keeps showing up in retrospectives, that is diagnostic information about the teams relationship to failure and crisis. If The Devil appears, it may indicate awareness of technical debt that no one is willing to name directly. The card becomes a safe proxy.

I would caution against reading this as evidence that tarot is somehow scientifically validated by tech adoption. What is validated is the underlying mechanism: structured projection surfaces lower resistance to self-examination. Tarot is one such surface. The TAT is another. Though I will admit - mapping The Devil to technical debt is an unusually precise reading.

[starstuff_sarah]

I think you're onto something real here, but I want to push back on how you're framing it, because I think the Jungian lens might actually be narrowing your view in a way that misses what's really happening.

"The symbolism creates emotional distance."

See, I'd argue the opposite. When I'm out with my telescope and I'm looking at light that left its source before anyone alive was born, that's not distance — that's connection across time. The symbolism doesn't create a buffer between me and the vastness. It makes it intelligible, gives me a way to hold something that would otherwise just be overwhelming emptiness. I think astrology works best as a language, not a law, and I suspect tarot functions the same way for these developers. It's not that they're hiding behind the cards. It's that the cards give them vocabulary for experiences that tech culture otherwise renders in sterile, useless terms like "post-mortem" or "root cause analysis."

Where I think your Jung framing falls short is this assumption that what's happening is primarily defensive — that engineers are using symbolism to avoid direct emotional confrontation. But what if they're using it because direct confrontation in professional settings has been trained out of them so thoroughly that it's not even an option anymore? The tarot isn't a workaround for a functioning emotional system. It's a prosthetic for one that's been amputated by workplace culture.

The Thematic Apperception Test comparison is fair, but there's a key difference: your patients didn't choose those images, and they're not building shared meaning from them in a group setting. These developers are co-creating a symbolic language together. That's closer to how constellations actually work — we drew lines between points of light and called them stories, and those stories became how we navigated. The mapping itself (Tower = outage, Devil = tech debt) isn't just projection. It's collective myth-making, and I think that's fundamentally different from what happens in a clinical projective test.

I agree something legitimate is happening. I just don't think "bypassing defensive posturing" captures it. It might be more accurate to say they're rebuilding something that corporate structures destroyed.