There was a time when my calendar felt like a container around the work. Now it feels like the work itself.
I can finish a full day and realize I built nothing except alignment.
This wasn’t a workload issue — it was a slow replacement of creation with coordination.
I still write code, technically. But it’s no longer the center of the day.
The day is shaped by conversations about what might be built, why, and when.
Why Meetings Expanded Until They Became the Job
Every decision needed a room full of people to exist.
As teams grew, so did the need to synchronize. That made sense at first.
But the synchronization never stopped growing. It multiplied into rituals.
Standups, planning, refinement, grooming, check-ins, syncs, retros. The work became a series of confirmations that work was happening.
Coordination is necessary — but it can quietly swallow the craft.
When Communication Replaced Momentum
I started performing clarity more than creating outcomes.
I got better at explaining work than doing it. Better at writing updates than writing code.
My value began to show up in how well I could translate ambiguity into something others could approve.
Some days, my most “productive” output is a document that makes people feel comfortable, not a change that makes something better.
It’s possible to feel busy while being far from the thing you actually do.
How Building Became a Small Part of a Very Large Process
The code was the smallest part of everything we called engineering.
Before a line of code exists, there are requirements, stakeholders, edge cases, sizing, roadmaps, dependencies.
By the time I reach implementation, the decisions already feel distant.
The building happens at the end, almost like an administrative step — and it rarely carries the excitement it used to.
When creation comes last, it starts feeling like compliance.
What This Shift Does to the Way the Work Feels
I miss the quiet concentration more than I expected.
Meetings fragment attention. They turn the day into pieces that never fully connect.
The deeper thinking — the kind that used to make me feel capable — becomes harder to access.
I started noticing this after the work stopped feeling creative , and it amplified once burnout stopped looking like burnout .
Fragmented days can make even meaningful work feel thin.
Why It’s Hard to Push Back Against Meeting Culture
Declining a meeting can feel like declining responsibility.
The meetings are framed as collaboration, alignment, ownership.
And sometimes they are. But they’re also a kind of proof that you’re engaged.
To want fewer meetings can sound like wanting less involvement, even when what I really want is more building.
The desire to create can get misread as the desire to disengage.
Is it normal for senior engineers to spend most of their time in meetings?
Yes. As responsibility increases, time often shifts toward coordination, decision-making, and communication.
Why does this feel draining even if the meetings aren’t stressful?
Because they fragment attention and reduce time spent in deep, satisfying work.
Does this mean I’m not suited for engineering anymore?
Not necessarily. It may mean the role has drifted away from the part of engineering that felt most alive.
This didn’t mean I stopped caring — it meant the work stopped letting me build enough to feel connected.
