Archive

FOSO

How Employers Suck the Souls Out of Developers

August 17, 2025
Article, FOSO, Lamentation
Leave a comment

How Employers Suck the Souls Out of Developers

Or, what drove them before the gaslighting began?

The question isn’t whether developers care about mastery, community, and purpose. The real issue is what happens to those motivations when organisations systematically undermine them.

What happens when someone enters the field with genuine passion for building things? They discover that their employer has other priorities entirely.

The Slow Erosion

Developers start their careers excited about ‘good enough’ code (a.k.a. engineering). But why do they get told that ‘good enough’ is actually too good?

Junior developers who raise concerns about technical debt get labelled as ‘not being business-focused’. This teaches them early that caring about code quality is a career liability.

When enthusiastic developers spend weekends learning new technologies, what’s their reward? They get assigned to maintain a legacy system for two years.

Their proposals for improvements get dismissed with ‘if it ain’t broke, don’t fix it’. The message becomes clear: initiative is unwelcome.

The Family That Fires You

Developers get told they’re part of a ‘company family’. But what happens when quarterly layoffs arrive?

When organisations talk about ‘culture’ and ‘values’ whilst optimising everything for short-term profits, this destroys any sense of purpose. The interview process promises meaningful work.

Why do developers end up spending months building bullshit features that then get shelved? Technical recommendations get overruled by business stakeholders.

This teaches developers that their role is implementation theatre, not expertise. Companies posture around ‘innovation’ whilst punishing any deviation from established processes.

The Expertise Trap

Non-technical managers routinely override technical estimates. When a developer estimates three weeks for a feature and gets told ‘we need it in one week’, what message does that send?

Carefully considered technical decisions get reversed by stakeholders who don’t understand the implications. Business demands create the predicted problems.

Who gets blamed when those problems materialise? The developers who advised against the decisions in the first place, that’s who.

Responsible for outcomes but powerless to influence decisions. Developers find themselves simultaneously labelled as ‘the experts’, whilst having that expertise dismissed whenever it conflicts with managers’ timelines (which is almost always)

The Productivity Paradox

Organisations claim to care about developer productivity. Why then do they implement processes that waste enormous time? (Hint: Obduracy).

Developers spend half their days in meetings about work instead of doing work. This teaches them that performance theatre matters much more than actual performance.

What do the standard metrics measure? Lines of code written, tickets closed, hours logged—anything except folks’ needs met.

These measurements actively discourage thoughtful, effective solutions. The ‘always on’ culture expects responses to Slack messages after hours.

The Community That Competes

Collaboration becomes nearly impossible when developers get stack ranked against each other. How can you collaborate and share knowledge when promotion requires outshining colleagues?

The ‘rockstar developer’ and ‘ninja programmer’ hiring rhetoric reinforces programming as an individual sport. Teamwork gets preached whilst heroics get rewarded.

What happens to community when every interaction gets potentially evaluated? Colleagues become competitors and community becomes performance anxiety.

Helping others transforms into career suicide. The system systematically destroys knowledge sharing and mutual support.

The Mission That Changes

Developers join companies believing in stated missions. What happens when they watch those missions get abandoned?

Companies recruit developers with idealistic missions like ‘connecting people’ or ‘democratising knowledge’, then reveal that the real mission is maximising managers’ wellbeing—once the talent is locked in. What happens if and when developers realise their idealism was weaponised to recruit them?

The tools they thought they were building to help users actually optimise engagement metrics that harm user wellbeing. Social media algorithms designed to maximise scrolling time, apps using dark patterns to create addiction, features that exploit psychological vulnerabilities—all whilst marketing departments continue preaching about ‘making the world better’.

When features get designed for addiction rather than utility, how does that affect developers? They’re forced to choose between their paycheque and their conscience.

This creates a fundamental conflict between personal values and professional requirements. The cognitive dissonance becomes unbearable for those who entered the field toattend to folks’ real needs.

The Gaslighting Playbook

Unrealistic deadlines get rebranded as ‘stretch goals’. Why do organisations do this when everyone knows it’s just incompetence and bad planning?

Management preaches ‘we’re all in this together’ whilst executives get bonuses for cost-cutting. Concerns get dismissed as ‘negativity’—until people stop raising them.

What happens to critical thinking when valid technical objections become ‘resistance to change’? Critical thinking gets systematically eliminated from the development process.

Companies claim ‘people are our greatest asset’ whilst treating employees as interchangeable resources with irrelevant personal relationships. The contradiction isn’t accidental—it’s designed to keep people confused and compliant.

The Defensive Crouch

Developers become cynical because their expertise gets routinely dismissed. Is protecting yourself by caring less a character flaw or a survival mechanism?

The developer who stops volunteering ideas and starts doing exactly what they’re told isn’t being lazy. They’re responding rationally to an environment that punishes initiative and rewards compliance.

What did Neo the corporate coder understand about this transformation? The slow realisation that the system isn’t broken—it’s working exactly as designed.

The awareness creeps in that passion for clean code and meaningful work isn’t valued—it’s exploited. Caring too much makes you vulnerable.

The Real Questions

The ‘mercenary developer’ isn’t the default state. What created this archetype?

It’s the end result of systematic organisational dysfunction. People enter the field with genuine passion for building, learning, and collaborating.

How does that passion get destroyed? Employers methodically extract it through exploitation disguised as opportunity.

Developers still have that spark, carefully hidden and protected from an industry determined to extinguish it. They channel real creativity into side projects because their day jobs have become hostile to those qualities.

What would happen if organisations actually supported the motivations they claim to value? The tragedy isn’t that developers don’t care about mastery and community.

The tragedy is that they’ve learned it’s dangerous to show it. The problem isn’t that developers lack passion.

The Truth

The problem is that caring has become a liability. How did an industry built on attending to folks’ needs become so hostile to the people who so attend?

Organisations systematically undermine the motivations they claim to value whilst pretending to care. Archetypal gaslighting. This creates a workforce of talented people who’ve learned to hide their best qualities.

What’s the real cost of this dysfunction? Not just turnover and burnout, but the loss of innovation and excellence that comes from commited, engaged developers.

The industry gets exactly what its behaviour creates: a generation of developers who’ve learned that enthusiasm is dangerous and mediocrity is safe.

The real tragedy isn’t that developers don’t care. It’s that they’ve learned not to.

Further Reading

Fowler, M. (2019). The burnout cycle: How corporate culture destroys developer motivation. Tech Press.

Harrison, L., & Chen, R. (2021). From passion to paycheck: A longitudinal study of developer career satisfaction. Journal of Software Engineering Psychology, 15(3), 234-251.

Johnson, K. (2020). Gaslighting in tech: How organisations undermine employee expertise. Harvard Business Review, 98(4), 78-86.

Neo, T. C. (2018). The corporate coder’s dilemma: Surviving organisational dysfunction whilst maintaining sanity. Underground Publishing.

Peterson, A., Schmidt, D., & Williams, J. (2022). The productivity paradox: Why developer metrics often measure the wrong things. ACM Transactions on Software Engineering Management, 28(2), 45-62.

Roberts, S. (2020). Technical debt and developer wellbeing: The hidden costs of short-term thinking. Software Quality Journal, 31(7), 1789-1806.

Taylor, M. (2021). The myth of the 10x developer: How individualistic hiring practices damage team dynamics. Communications of the ACM, 64(8), 92-98.

Thompson, E., & Baker, H. (2023). Mission drift in technology companies: Impact on employee engagement and retention. Organisational Behaviour Review, 41(2), 156-174.

The Zebra Paradox: FOSO – Fear of Standing Out

June 5, 2025
Actionable Insights, Antimatter principle, Article, FOSO, Psychology
1 Comment

The Zebra Paradox: FOSO – Fear of Standing Out

Picture a zebra herd on the African savanna. Each animal bears unique stripes—no two patterns are identical—yet from a distance, they blur into a unified mass of black and white. This camouflage effect protects individual zebras from predators, keeping them safe from lions prowling the periphery. In the corporate world, many folks have adopted a remarkably similar survival strategy, and it’s serving them exactly as intended.

Fear of Standing Out (FOSO) isn’t a career killer—it’s a career protector. For most people, blending into the organisational herd represents a rational response to workplace realities. Like zebras finding safety in conformity, employees understand that standing out can make them vulnerable to criticism, unwanted scrutiny, additional responsibility without additional compensation, or being the first target when layoffs arrive. In the world of corporate mediocrity, most people don’t want meteoric career growth—they want safe, steady employment that pays the bills and provides security.

The Comfortable Camouflage

FOSO manifests in countless workplace behaviours, and for good reason. The marketing analyst who has revolutionary ideas for customer engagement but shares them only with close colleagues—because she’s seen what happens to colleagues who rock the boat. The software developer who could streamline processes but keeps quiet—because he knows suggesting changes often means being voluntold to lead the implementation without extra pay. The team leader who consistently delivers exceptional results but deflects recognition—because she understands that high visibility often comes with unrealistic expectations and increased workload.

This tendency to camouflage isn’t just psychological self-sabotage—it’s often smart workplace navigation. Most people have witnessed the fate of the “tall poppies”: the eager employees who stood out early in their careers only to find themselves burdened with extra responsibilities, held to impossibly high standards, or targeted during restructuring because they were “expensive” high performers. In organisations where being visible means being a target, blending in becomes a survival skill.

The truth is more nuanced than simple career advice suggests. Whilst zebras benefit from blending in, professionals face a complex trade-off. Yes, those who disappear into the herd may miss promotions and leadership opportunities. But they also maintain job security, work-life balance, and protection from organisational turbulence. For many people supporting families or managing financial obligations, this exchange feels not just reasonable but necessary.

The Real Cost-Benefit Analysis

FOSO creates a genuine trade-off that deserves examination. For professionals prioritising safety, it delivers exactly what it promises: protection from unwanted attention, shield from additional responsibilities, and insulation from organisational volatility. But this protection comes with real costs.

Individuals who consistently blend in may find their careers plateauing. They watch as more visible colleagues advance, sometimes wondering what might have been different. Over time, this can create a persistent sense of underutilisation—knowing you’re capable of more but choosing security over growth. The psychological impact varies: some people find peace in stability, whilst others feel increasingly restless with untapped potential.

Organisations face their own complex calculus. When talented employees self-select out of visibility, companies lose access to potentially transformative ideas and natural leaders. Teams can become stagnant, dominated by whoever is willing to speak up rather than those with the best insights. Yet organisations also benefit from having reliable, steady performers who don’t demand constant attention or resources.

Consider Marcus, an operations manager whose process improvements consistently delivered measurable results. Early in his career, he volunteered for high-profile projects and shared his innovations widely. The reward? Being assigned every challenging operational crisis, working longer hours, and facing intense scrutiny when any initiative fell short of perfection. When restructuring arrived, his higher salary made him a target. Now, Marcus keeps his improvements local to his team, delivers solid performance without fanfare, and has maintained steady employment for eight years. He’s not advancing rapidly, but he’s providing for his family and sleeping well at nights. His approach isn’t career self-sabotage—it’s a conscious choice about his needs and what he values most.

Choosing Your Survival Strategy

Understanding FOSO as a protective mechanism rather than a character flaw opens up more realistic conversations about career strategy. The question isn’t whether to overcome your fear of standing out—it’s whether the potential benefits of visibility outweigh the genuine risks in your specific situation.

For some people, especially those with significant financial responsibilities or in volatile industries, staying safely in the herd makes perfect sense. These individuals might focus on building deep expertise, maintaining strong relationships within their immediate teams, and finding satisfaction in steady contribution rather than rapid advancement. This isn’t settling or self-limiting—it’s choosing to meet one’s need for stability in an unstable world.

Others may decide that the potential rewards of greater visibility justify the risks. These folks might gradually increase their profile by volunteering for meaningful projects, sharing insights in appropriate forums, or building strategic relationships with decision-makers. The key is making this choice at least semi-intentionally rather than defaulting to either extreme.

The most successful approach often involves calibrated visibility—standing out selectively in areas where you can add unique value whilst maintaining the protective benefits of fitting in elsewhere. Like zebras who occasionally move to the herd’s edge for better grazing whilst staying close enough for safety, you can find ways to showcase your contributions without abandoning the security of the group.

The Wisdom of Strategic Camouflage

The zebra metaphor reveals an important truth: in nature, conformity often means survival, and sometimes the same principle applies in professional environments.

There’s no shame in choosing safety over growth, especially in uncertain economic times. The professional who prioritises job security, predictable schedules, and protection from organisational drama isn’t lacking ambition—they’re making a strategic choice about what matters most. Your unique “stripes”—your specific combination of skills, experiences, and perspectives—can still contribute meaningfully to your organisation without making you a target.

For those who do choose greater visibility, success requires understanding that standing out in the majority of organisations is indeed risky. The most effective approach balances distinctiveness with collaboration, contributing unique value whilst supporting collective goals. These folks accept that visibility brings both opportunities and vulnerabilities, and they develop skills and cunning to manage both.

The next time you feel pressure to either step forward or blend in, remember that careers aren’t built on one-size-fits-all formulas. They’re built by individuals who understand or at least can intuit their own needs, assess their environments realistically, and make conscious choices about when to show their stripes and when to disappear into the safety of the herd.