My previous article used the language of "visibility" because that's the vocabulary developers share. We talk about disappearing quietly, becoming ghosts in our own lives, losing presence. And that framing is real—it matters, especially for those who feel erased by remote work, asynchronous communication, and the quiet competence the industry rewards.
But that's not actually my problem.
I'm introverted. I'm private. I don't mind being invisible. In fact, I lean into it. The quiet mode of engineering—the low-friction, low-visibility, high-autonomy channel—is where I operate best.
The real threat isn't erasure by others. It's compression. It's the slow collapse into a single function. It's becoming only the part of you that produces.
Developers don't just disappear. We flatten.
Two different problems: disappearing vs. collapsing
The original article diagnosed one problem: disappearing—others stop seeing you, and eventually you stop seeing yourself.
But there's a second, quieter problem that looks similar from the outside but feels completely different from the inside: collapsing—you remain present, but only as one thing.
You're still there. You just become only the reliable node. Only the problem-solver. Only the person who unblocks the pipeline. Only the function.
You don't vanish. You compress.
That's the failure mode I resist.
Why invisibility doesn't bother me
I don't need to be seen to feel real. I don't need social presence to feel alive. I don't need external recognition to maintain identity.
Invisibility is not the enemy. It's a comfortable operating mode.
What I refuse is one-dimensionality—the reduction of a whole person into a single operational register.
Engineering work compresses you by design
Software work is optimized for reliability, predictability, low emotional footprint, asynchronous execution, and frictionless output. These traits make you effective. They also make you flat.
The longer you stay in that mode, the more the rest of you dissolves—not because anyone erased you, but because the job only exercises one part of your architecture.
You become a single-axis creature.
Ballroom isn't about visibility—it's about multiplicity
In my previous piece, I framed ballroom as a domain where you "can't disappear," where you're "seen whether you want to be or not." That language was true, but it wasn't the point.
Ballroom isn't my antidote to invisibility. It's my antidote to compression.
Ballroom forces me into registers engineering never touches—physical, rhythmic, expressive, relational, partnered, aesthetic, competitive, embodied. It's not that I'm "seen." It's that I'm plural.
Ballroom keeps me from collapsing into a single operational identity.
Teaching is the clearest example of dimensionality
Teaching competitive students on Sundays is the part that reveals the real architecture.
In engineering, excellence is extractive. Your clarity gets mined. Your competence becomes a resource others consume. Your identity narrows to your utility—you are what you produce, and what you produce is what gets pulled out of you in meetings, in late-night Slack messages, in "quick reviews" that are never quick. The better you get, the more you become a function that other people call.
In teaching, excellence is generative. Your knowledge stays yours even as you transmit it. Your leadership isn't consumption—it's cultivation. You watch someone execute a technique they couldn't land last week, and that improvement doesn't diminish you. It extends you. Your identity expands instead of compressing.
Teaching is not about being visible. It's about being more than one thing.
Anti-compression as a developer survival strategy
Some developers need visibility to feel whole. Some need community. Some need recognition.
I need dimensionality.
I need a second discipline that keeps my long-arc identity alive. I need a domain where excellence is embodied, not extracted. I need a practice that forces me to inhabit registers engineering doesn't use.
Ballroom isn't where I go to be seen. It's where I go to stay three-dimensional—rhinestones, frame, breath, and all.
Top comments (0)