SBTI
The Refactoring Addict (REFUSE)

REFUSE

The Refactoring Addict

You see bad code, your hands itch. After refactoring, you realize you made it worse.

Dimension Pattern

M
HC1 Overtime WillingnessHustle/Chill Model

It's not that you won't work overtime — it depends on the situation, mainly whether there's free dinner.

M
HC2 Work PaceHustle/Chill Model

Normal hours, occasional crunch, not quite death-march territory.

M
HC3 Career AmbitionHustle/Chill Model

A little ambition, but not much — enough to cover the mortgage.

H
CA1 Code QualityCode Attitude Model

A single misaligned space keeps you up at night.

M
CA2 Bug HandlingCode Attitude Model

If it's fixable, fix it. If not, mark it Won't Fix.

H
CA3 Tech Debt AttitudeCode Attitude Model

Seeing tech debt feels like seeing a credit card bill — must pay it off immediately.

M
PD1 Boss RelationshipPeople Dynamics Model

On the surface it's "got it," internally it's maximum roasting.

M
PD2 Team CollaborationPeople Dynamics Model

Collaborate when needed, solo when needed — introvert-extrovert switch on demand.

M
PD3 AuthenticityPeople Dynamics Model

Wearing the mask most of the time, occasionally letting a genuine curse slip.

M
MH1 Anxiety LevelMental Health Model

Occasional anxiety, but nothing a bubble tea can't fix.

M
MH2 Self-AssessmentMental Health Model

You know your strengths and limits — no ego trips, no self-pity.

L
MH3 Escape ImpulseMental Health Model

Content with the status quo — why switch jobs? It's all the same grind everywhere.

M
TC1 AI AttitudeTech/Career Model

AI? Let's wait and see — let others be the guinea pigs first.

H
TC2 Learning DriveTech/Career Model

Proactively learning new tech — chasing GitHub stars harder than chasing TV shows.

M
TC3 Career PlanningTech/Career Model

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 Refactoring Addict]. See bad code, hands start itching — you must refactor. Then you discover the refactored version is even worse, plus a dozen new bugs. Your life motto is "old code must die," but reality keeps delivering "new code is even worse." You're not a neat freak — you're late-stage OCD. Every refactor is like digging your own grave, then jumping in. Colleagues say you have standards; really you just can't stand looking at that pile of garbage. Advice: before refactoring, ask yourself three questions: 1. Do I have time? 2. Does the boss approve? 3. Will it be even worse after? The answer is usually NO.

Find Your Developer Type

Answer 31 questions to discover your developer personality type

Start Test

Explore Other Personality Types