absurditation
A family of paradoxical emotions arising from the realization that your work is meaningless or impossible.
absurd + -ation
see also
Developer burnout is highly prevalent, with up to 80% of programmers reporting feelings of exhaustion and cynicism. While developers enjoy higher salaries and better flexibility than many jobs, the cognitive intensity, constant need to upskill, and unclear project requirements make them particularly vulnerable compared to less technically demanding or non-digital professions.
We believe part of the problem is that developers have no language for what they go through, so we created this lexicon of coined words for the emotions unique to developers — to help us name, share, and ultimately better understand our experiences.
Take what you need.
A family of paradoxical emotions arising from the realization that your work is meaningless or impossible.
absurd + -ation
see also
The moment you think “what idiot wrote this code?” — only to discover it was you.
auto- + ridicule
see also
A strain of absurditation brought on by an imposed, impossible timeline.
chrono- + absurditation
see also
The bond formed between like-minded developers working in the same codebase.
code + camaraderie
see also
The trauma bond that forms between developers surviving a nightmare codebase together.
code + commiseration
see also
The realization that the brand-new component you just wrote already exists elsewhere in the codebase.
déjà vu + view
see also
The clarity and elation of being deep in flow, producing high-quality code rapidly and effortlessly.
euphoria + flow
see also
The confusion when an error message points to a line number that is empty or otherwise useless.
error + enigma
see also
The helplessness of working in a codebase so fragile that fixing one bug spawns three more.
fix + fragile + -ation
see also
The uneasy realization, mid-refactor of “dumb code,” that it wasn't dumb at all — and now you're in over your head.
hubris + refactor
see also
The dread of making architectural decisions you aren't qualified to make, because time or budget won't let you reach the real expert.
impostor + factor
see also
The respectful frustration of taking over someone's code, knowing it was written under the same crunch you're in now.
inherit + irritation
see also
The urge to refactor code that already works fine, simply because it feels too complex for you to fully grasp.
inept + factor
see also
The rush of joy when code works on the first try — and you're sure it's because you did everything right.
initial + elation
see also
The unnerving skepticism when code works on the first try, making you suspect something is lurking beneath the surface.
initial + paranoia
see also
The state of trying to “lock in” and focus, only to be thwarted by exhaustion or burnout.
lock in + -osis
see also
The nagging certainty that the file, method, or variable you need already exists — if only you could recall its name.
-onym + amnesia
see also
The paralysis of being unable to decide what to name a file, method, or variable.
-onym + -lysis
see also
The point at which lockinosis becomes so severe that the entire dev team breaks down.
pop-and-lock + lockinosis
see also
The hollow relief of a build finally compiling, after which you feel too worn down by repeated failures to truly celebrate.
Pyrrhic + compilation
see also
The eerie experience of reading your own code with no recollection of having written it.
scribe + amnesia
see also
The mounting tension and anticipation built up across repeated attempts to get a build to succeed.
Sisyphus + -ation
see also
A strain of absurditation caused by a stark lack of team resources.
strato- + absurditation
see also
The unease of venturing into the undocumented parts of a library or framework.
undocumented + -osis
see also
The condition of code growing ever more verbose and overengineered, yet too entangled to simplify without risking a break.
verbose + atrocity
see also
Nothing blooms here yet — try another word.