DOC-DEAD
The Documentation Corpse
Comments are always TODO, README is always empty.
Dimension Pattern
It's not that you won't work overtime — it depends on the situation, mainly whether there's free dinner.
Normal hours, occasional crunch, not quite death-march territory.
A little ambition, but not much — enough to cover the mortgage.
Good enough is good enough — we're not launching rockets here.
If it's fixable, fix it. If not, mark it Won't Fix.
Tech debt? Let it pile up — it's not like it affects your credit score.
On the surface it's "got it," internally it's maximum roasting.
Collaborate when needed, solo when needed — introvert-extrovert switch on demand.
Wearing the mask most of the time, occasionally letting a genuine curse slip.
Occasional anxiety, but nothing a bubble tea can't fix.
You know your strengths and limits — no ego trips, no self-pity.
Content with the status quo — why switch jobs? It's all the same grind everywhere.
AI? Let's wait and see — let others be the guinea pigs first.
Learning? Work is exhausting enough — after hours I just want to lie down.
Got ideas but no action — plans stuck in the notes app forever.
Personality Profile
The following is a stylized description of this personality type, written in the original author's uniquely humorous voice.
Congrats, you've tested as [The Documentation Corpse]. "Docs? I barely have time to write code!" Comments are always TODO, README is always empty. Someone asks how to use it, you reply "read the code." You don't not know how to write docs — writing docs would literally kill you. You'd rather work overtime fixing bugs than spend ten minutes writing API specs. Result: every new hire has to come ask you, making you the living documentation. Advice: next time you write code, toss in a couple of comment lines. Don't let future-you become a documentation corpse too.
Find Your Developer Type
Answer 31 questions to discover your developer personality type
Start TestExplore Other Personality Types
