The aluminum can is sweating, a ring of condensation forming on the mahogany laminate of the conference table. I am tapping my pen against the rim-click, click, click-trying to ignore the way the air conditioning hums at a frequency that feels like it is drilling directly into my prefrontal cortex. I just missed the bus by exactly ten seconds. I watched the taillights disappear around the corner, a red smear against the grey morning, and now I am sitting here, listening to Rick explain why we cannot use a modern library for the new data pipeline. Rick has been here for 22 years. He is the human equivalent of a legacy system that no one dares to reboot because nobody knows where the original documentation is hidden.

Sam, a junior dev who still has that terrifying glimmer of hope in his eyes, had just suggested we look at a specific rust-based framework to handle the concurrency issues. It was a good suggestion. It was a 102 percent improvement over our current messy workaround. But Rick leaned back, his chair creaking with the agonizing sound of a dying animal, and waved a hand as if swatting away a particularly persistent fly. ‘We tried something like that back in 2002,’ Rick said, his voice thick with the unearned authority of someone who hasn’t read a technical blog post since the Blackberry was king. ‘It didn’t work then. It won’t work now. We do it this way here because this way is stable.’

He doesn’t know that the library Sam suggested solved those 2002 problems before Sam was even out of elementary school. Rick doesn’t care. He has mastered the internal politics of this 122-person department so thoroughly that his ignorance is now protected by a layer of bureaucratic armor that no logic can pierce.

I look over at Jordan S.K., our emoji localization specialist. Jordan is currently staring at a 52-page document regarding the subtle cultural nuances of the ‘folded hands’ emoji in different regional markets. Jordan is someone who actually understands that the world changes. They once spent 72 hours arguing that a specific shade of yellow in a grinning face was technically offensive in three different sub-regions of the Pacific Northwest because of a very specific historical context involving a defunct local soda brand. Jordan gets the details. Rick, on the other hand, thinks that localization means ‘making sure the text fits in the box.’

“

The seniority of a person is often inversely proportional to their willingness to admit they are wrong.

– Observation, 2024

The Paradox of Rewarding Survival

This is the paradox of the modern corporate structure. We reward tenure because we mistake it for expertise. We assume that because someone survived the 102-day crunch of a product launch in the late nineties, they must have some secret wisdom that the rest of us lack. But the truth is more depressing. In many cases, long tenure just means someone has become very good at navigating the political system while their actual skills have atrophied into nothingness. They are the living embodiment of the company’s resistance to change. They are the cultural anchors, and they are dragging the entire ship to the bottom of the ocean.

I remember a time when I thought Rick was a genius. That was about 52 weeks into my first year here. He seemed to have an answer for everything. But then I realized his answers were always the same: ‘It’s too risky,’ ‘We don’t do that here,’ or ‘You’re overcomplicating it.’ It took me another 12 months to realize that ‘you’re overcomplicating it’ was actually Rick’s code for ‘I don’t understand the words you are using and I am terrified of looking stupid.’ It is a defense mechanism. If he can keep the technology stack firmly planted in the year 2002, he remains the expert. If we move to something modern, he becomes a student again. And for an Expert Beginner, being a student is a fate worse than death.

This poisoning of the well is systemic. When a new, talented developer joins the team, they are immediately met with Rick’s wall of ‘no.’ Within 62 days, that new developer has usually stopped suggesting ideas. Within 122 days, they are looking for a new job. The only people who stay are the ones who are okay with mediocrity, or the ones who have their own reasons for wanting to hide in the tall grass of a stagnant company. The result is a self-selecting group of people who are committed to doing things the wrong way because the right way requires effort they are no longer capable of giving.

The Exhaustion of Explaining the Peach

Jordan S.K. once tried to explain to Rick why the localization of a specific set of icons was failing in the latest build. Jordan had data-actual, hard numbers showing a 32 percent drop-off in user engagement in the targeted regions. Rick just looked at the spreadsheet and said, ‘The users will get used to it. They always do.’ I watched Jordan’s face in that moment. It wasn’t anger. It was a profound, quiet exhaustion. It’s the exhaustion of trying to explain the flavor of a peach to someone who has only ever eaten sawdust and insisted it was steak.

While some are content to sit in the same chair for 22 years, those who actually want to build the future usually find their way to programs like

iStart Valley where the focus is on the actual mechanics of innovation. You cannot build an AI-driven future with a 2002 mindset, no matter how many ‘senior’ titles you stack on top of it.

I find myself wondering if I am becoming a Rick. I caught myself the other day almost telling a new intern that we don’t use a certain CSS methodology because ‘it’s too messy.’ I stopped. I realized I hadn’t actually looked at that methodology in 12 months. I was just repeating a sentiment I had heard someone else say. It’s a virus. The Expert Beginner is patient zero, and if you aren’t careful, you’ll find yourself coughing up those same tired excuses before you even realize you’re sick. It is a constant battle to remain a beginner in the true sense of the word-to remain open, curious, and willing to be the dumbest person in the room.

“

True expertise is the ability to unlearn what you think you know the moment the evidence changes.

– Insight on Adaptability

The Cost of Operational Integrity

Rick is currently talking about ‘operational integrity,’ which is his favorite way of saying ‘I don’t want to change the server configuration.’ He has been talking for 12 minutes now. Sam is looking at his phone. Jordan is subtly adjusting the kerning on a digital mock-up, probably just to feel a sense of control over something in this room. The meeting is scheduled to last for another 42 minutes, but we all know it ended the moment Rick opened his mouth. We are just going through the motions now, a pantomime of productivity designed to keep the status quo safely in place.

I think about the bus I missed. If I had been ten seconds faster, I wouldn’t be in this meeting right now. I’d be at my desk, probably arguing with a different Rick about a different 2002-era problem. There is no escaping it entirely, not in this industry. But we can choose how we respond. We can choose to be the person who listens to the junior dev. We can choose to be the person who admits that the world has moved on and that our ‘tried and true’ methods are just ‘old and tired.’ We can choose to value the 32 percent of ideas that sound crazy today but will be standard tomorrow.

As the meeting finally winds down, Rick stands up and claps a hand on Sam’s shoulder. ‘Good hustle, kid,’ he says with a patronizing grin that makes my teeth ache. ‘Keep those ideas coming. We need that energy, even if we can’t always use it.’ Sam smiles back, but it’s a brittle, 2-dimensional smile. He knows. We all know. And as I pack up my laptop and head back to my desk to fix a bug that has been in the codebase since 2012, I realize that the only way to avoid becoming an Expert Beginner is to never stop being terrified that you already are one.