I Like Coding but Don't Like Engineering Cultures

You find yourself at 2 a.m., deep in a refactor, and you’re grinning. The architecture finally makes sense; the outside world is silent. Yet on Monday morning, that joy evaporates during standup, buried under velocity metrics, roadmap politics, and “growing the team.”

This is the paradox: you love building software, but you can’t stomach the engineering culture that surrounds it. You’re not broken — you’ve just seen the gap between craft and the machine.

The Pull of Code

Coding taps into something primal: the desire to make, to solve, to shape logic into something tangible. Mihaly Csikszentmihalyi’s classic research on *flow* found that the state of deep immersion is one of the most rewarding human experiences. When you’re refactoring a gnarly algorithm or wiring up a test harness, the world melts away. It’s intellectual play, and it doesn’t require a company to exist.

Many of us fell in love with computing because of this alone — not because of “Agile certifications” or promotion ladders. The craft is inherently joyful.

The Push of Culture

Engineering cultures often reward everything but craft. They celebrate velocity over clarity, overtime over sustainability, and process over outcome. In a 2023 Gallup survey, only 23% of employees worldwide reported being engaged at work; in tech, burnout is the unspoken tax. Teams chase KPIs that measure lines of code or ticket throughput, ignoring whether the work actually matters.

Here’s how that toxic edge typically manifests:

**Hero culture**: The 10x engineer myth erodes collaboration and normalizes overwork.

**Process theater**: Standups become status battles; retrospectives turn into blame games.

**Metric obsession**: DORA metrics, cycle time, and burndown charts become the goal instead of indicators.

The real sting? None of this has anything to do with the act of programming. Yet it's the water we swim in, and it slowly poisons the craft you love.

Designing Your Own Environment

You can’t single-handedly fix a broken culture, but you can build your own fortress of craft.

1. Find the Quiet Spaces

Many of the best engineers I know thrive in smaller, focus-first environments: remote-first startups, open-source communities, or even solo consulting. Places where async communication is the default and meetings are a deliberate exception, not a reflexive calendar invite.

2. Switch to Craft-as-Code

Treat your immediate workflow as an engineering problem. Automate away the toil that steals your energy: CI/CD pipelines, staging environments, test infrastructure. When you reduce the draining “ops” overhead, you reclaim time for actual building. Tools like **Sapior** help: by providing on-demand cloud browser infrastructure, you can run integration tests and browser automation without babysitting a machine, shrinking context switches.

3. Set Boundaries Around Deep Work

Block out maker time. Paul Graham’s “maker vs. manager schedule” remains one of the most cited essays because it’s true: a single meeting in the morning can destroy an afternoon of coding flow. Guard that time like a craftsman protects their workshop.

Culture Is Code

DORA’s research consistently shows that high psychological safety and a generative culture lead to better software delivery outcomes. A healthy culture isn’t a soft skill — it’s a performance multiplier. The teams that build the most reliably are the ones where blameless post-mortems and work-life balance aren’t just slogans.

If you’re in a toxic environment, you’re not just unhappy — you’re also writing worse code. Stress shrinks the brain’s capacity for creative reasoning. So choosing a culture that respects your craft is as pragmatic as using the right database.

Stay in Love with the Thing

You didn’t fall in love with sprint ceremonies or performance-review cycles. You fell in love with that moment when a machine finally does what you asked. That love is still there. Protect it by finding or building an environment that treats coding as a craft, not a factory. Whether that’s through tools that handle the boring bits, teams that value deep work, or simply your own side projects at midnight — the code itself is still worth it.