The Career Ceiling No One Talks About: Senior Dev, Stuck Forever

“Congrats, You’ve Made It” You made it. You’re a Senior Developer now. You’ve got the title, the responsibility, the trust. You’re the person they call when things go sideways and production is on fire, or a junior is stuck, or no ones reading the error logs. You don’t even need a manager anymore. You’re “self-managing,” which is shorthand for doing two people’s jobs while politely declining meetings. You’re experienced, stable, and invaluable. And this… is as far as it goes. There’s no ceremony. No next step. No map. Just a long, slow plateau. ...

August 7, 2025 · 4 min · The Cynical Developer

The Death of 'Senior'

A few years ago, “Senior Developer” meant something. Not just a pay grade, not just an internal leveling band, but a signal that you’d seen some things. Broken prod on Christmas Eve. Legacy codebases with more comments than code. Real consequences, real complexity, real context. Now? I’m seeing resumes from people three years out of university with “Senior” in their title. Not senior in years, not senior in depth—just the most experienced person on a three-person dev team at a startup that launched last quarter. ...

June 4, 2025 · 3 min · The Cynical Developer

OKRs: Objectives, Key Results, and Corporate Cosplay

There’s a special kind of sigh that comes out when someone says, “We’re rolling out OKRs.” It’s not quite despair. Not quite sarcasm. It’s the sigh of someone who’s seen this play before—probably in Q1 of last year, and Q3 of the year before that. The costumes are different, but the script is the same. Let’s get this out of the way: OKRs—Objectives and Key Results—can be useful. They’re not inherently evil. But like many good ideas, they tend to die in the wild. Not because the framework is flawed, but because the way most companies implement them is. ...

May 22, 2025 · 5 min · The Cynical Developer

As the pendulum swings

Originally published on August 26, 2022 In my last post, I described the arc most software companies follow—from chaotic startup to process-heavy bureaucracy. If you missed it, check it out here: An Evolution of a Software Company. Spoiler: there’s a pendulum, and it swings hard. Today, we’re talking about what happens next—and how to stop the pendulum from turning your team into a JIRA-powered approval queue. From Chaos to Control By the time the dust settles, you’ve landed in a company that’s seen one too many outages and decided that the cure is process. Lots of it. ...

May 16, 2025 · 3 min · The Cynical Developer

An Evolution of a Software Company

Originally published on August 15, 2022 Let’s start with a story. It’s one you’ve probably lived through in some form, if you’ve spent more than ten minutes in the software industry. The Origin Story (and Its Inevitable Sequel) A company forms. There’s an idea, a goal, a dream. Usually it involves building the next great thing—a widget, a platform, a barely differentiated SaaS for onboarding PDFs. The founding team is small and experienced. They might be well-compensated, but more often they’re paid in the warm, fuzzy promise of equity. ...

May 15, 2025 · 3 min · The Cynical Developer