The original article nailed the diagnosis. Here's the architecture I use to prevent the quiet disappearance it describes.
The [https://dev.to/the_nortern_dev/the-hardest-part-of-being-a-developer-isnt-coding-its-disappearing-quietly-52l) makes a point most developers recognize instantly: you don't burn out from code, you burn out from erasure. From becoming the quiet, reliable node that everyone depends on but nobody actually sees. From being the person who answers the late-night Slack messages, unblocks the pipeline, patches the brittle system—and then disappears again until the next emergency.
Developers don't quit because the work is hard. Developers quit because the work slowly dissolves the parts of them that aren't work.
That's why I insist on keeping my competitive ballroom weekends intact—Saturdays to dance, Sundays to teach. Not because it's a "hobby," but because it's the only system I've found that reliably prevents the quiet disappearance the article describes.
Why developers disappear quietly
Most engineering environments reward the same traits that make people vanish—high reliability, low emotional footprint, asynchronous communication, deep focus, quiet competence. These traits make you effective, but they also make you invisible. You become the person who "just gets things done," which is corporate shorthand for "we don't have to think about you."
Over time, that invisibility becomes internal. You stop thinking about you, too.
I'm naturally reserved and introspective, so the social silence of remote work doesn't bother me the way it bothers some people. But the disciplined side of me—the part that thinks five to twenty years down the line—insists on maintaining a channel that forces presence, even if it's strict and structured rather than social in the conventional sense. The goal isn't to become an extrovert. The goal is to maintain a practice that keeps me from dissolving into my own usefulness.
Ballroom is the counter-architecture
Competitive ballroom is the one place where the developer failure mode simply cannot operate.
In a partnered dance, your partner feels everything—your hesitation, your confidence, your frame, your breath. There is no background mode. There is no "quietly competent" role where you deliver results without being perceived. The floor demands eye contact, presence, timing, projection, and shared risk—all at once, all in real time. You are seen whether you want to be or not. And that forced visibility is precisely the point.
Software work is disembodied. You live in your head for days at a stretch—reading code, reviewing abstractions, communicating through text that flattens every nuance into a thread. Ballroom is the structural inverse—physical, rhythmic, expressive, immediate. It forces you back into your body after a week of living behind a screen.
And there's a distinction that matters more than people realize: in engineering, excellence often means being mined for answers. Someone breaks production, someone pings you at 10 PM, someone needs you to "quickly review this PR." Your expertise becomes something others extract from you. In ballroom, excellence is something you inhabit. You show up, you dance, you sweat, you improve. No one is extracting anything from you. The excellence stays yours.
Why teaching on Sundays matters even more
Teaching competitive students isn't "extra work." It's structural protection.
In tech, leadership often means being the person who absorbs ambiguity and shields everyone else—draining work disguised as authority. In ballroom, leadership means shaping technique, shaping confidence, shaping discipline. It's generative rather than extractive. You build capacity in someone else without losing your own.
Teaching also gives you something engineering rarely does—immediate, visible impact. Engineering impact is often invisible or delayed by quarters, buried in metrics dashboards no one reads. Teaching gives you instant feedback and tangible improvement. You watch someone execute a technique they couldn't do last week. That matters in a way that closing a Jira ticket never will.
Most importantly, teaching anchors your identity outside of work. Developers who disappear quietly usually have one thing in common—their entire identity is tied to being useful inside a system that doesn't see them. Teaching creates a second domain of competence, one that isn't tied to sprint velocity or on-call rotations or the quiet dread of another Sunday night deployment.
The deeper truth—developers need a domain where they cannot disappear
The hardest part of being a developer isn't coding. It's staying human in a system that rewards you for becoming a ghost.
Ballroom is my anti-ghost architecture. It's the place where I am visible—not because I demand attention, but because the discipline makes hiding physically impossible. It's the place where I am embodied rather than abstracted, where I am not extractable, where I am not "the reliable one," where I am not disappearing quietly.
Every developer needs something like that—a domain that structurally prevents the fade. It doesn't have to be dance. It has to be something where you cannot operate on autopilot, where your presence is required in a way that code reviews and async threads will never require it, where excellence is something you carry in your body rather than something that gets pulled out of you in a meeting.
Mine just happens to involve rhinestones, frame, and a competitive floor.
This is a response to @the_nortern_dev's piece on disappearing quietly. If you've found your own anti-ghost architecture, I'd like to hear what it is.
Top comments (2)
This was such an interesting read Narnaiezzsshaa! I totally get what you mean about feeling invisible as a developer, even though the coding itself isn't the hard part. It's like, you're so focused on the tasks at hand, you forget to show up to the rest of your life.
I never thought about it, but competitive ballroom dancing makes a lot of sense as a way to combat that - it's all about presence and connection with others, which is pretty refreshing.
I myself have been thinking about joining a boxing gym to enjoy another hobby, but the time just doesn't allow that right now. I need to stabilize things that are already there before I step foot in a new environment.
For me, the equivalent of your ballroom weekends has been photography and long solo walks with a camera: I’m forced back into my body, into specific places and light, instead of living purely in abstractions.