The folder structure didn't make sense. Not unfamiliar — I mean it genuinely didn't make sense. I sat there on my first morning, scrolling through the new codebase, waiting for a pattern to click. It didn't.
Seven years at my previous company had given me a very specific kind of confidence. I knew every quirk of the system. I knew which warnings to ignore and which ones actually meant something. I knew, without thinking, where to find things. That knowing had become invisible — background noise I'd mistaken for competence.
On that first morning, the background went silent. The silence was loud.
The decision I couldn't stop second-guessing
When the offer came in, I spent two weeks analyzing it. Salary differentials, tax implications, benefits breakdowns, contract clauses. I built a spreadsheet. I built a second one to sanity-check the first.
I told myself this was due diligence. It was also fear wearing the costume of thoroughness. The real questions — can I still do this somewhere else? will I lose everything I built here? — weren't things a spreadsheet could answer. So I kept adding rows.
Eventually I accepted. Not because the analysis was complete, but because I ran out of things to add.
The first morning
I'd prepared. Read through their public repos. Watched architecture talks they'd shared during the interview process. Felt reasonably ready.
Then I opened the codebase.
The patterns were different. Not wrong — different. Every naming convention, every folder structure, every way of organizing state was a choice I hadn't made and didn't yet understand. I kept reaching for muscle memory and finding nothing there.
I asked a question in Slack. Got a kind, thorough answer. Didn't fully understand it. Asked a follow-up. They answered that too. I wrote notes I wasn't sure I'd be able to interpret later.
This is fine, I told myself. This is just the first day.
The dizziness
Around midday, I stood up to get water. My legs felt strange. Not painful — just distant, like they belonged to someone who hadn't slept properly in a week.
I sat back down.
I've since read that the body sometimes does this when it's processing something the mind hasn't caught up to yet. At the time, I thought I was getting sick. But I wasn't sick. I was grieving.
Seven years is long enough to build a life inside a job. Not just skills — reflexes. The particular way a certain colleague phrases questions when they're worried about something. The exact tone of a codebase shaped by the same architectural decisions for years. The rhythm of a team that knows each other well enough to disagree fast and move on.
None of that transferred. I'd left it at the door.
Imposter in the building
The afternoon got better, in the way that "better" means I stopped expecting myself to already know things.
I asked more questions. Drank more water. Took notes I knew I'd have to revisit. Stopped trying to map the new codebase onto the old one and started trying to read it on its own terms.
It didn't click that day. Or the next. But around the end of the second week, something shifted. Not mastery — more like the first time you drive a new car and stop consciously noticing the position of the mirrors.
What I know now
Leaving a long job isn't a job change. It's a small loss.
You lose the colleagues who knew your work well enough to give feedback in shorthand. You lose the codebase you could navigate half-asleep. You lose the accumulated context — a hundred small decisions that shaped how things work and why — that lived in your head without you ever cataloguing it.
That takes time to rebuild. Not days. Weeks.
If I could say something to myself from that first morning: the dizziness is real, but it passes. Ask the questions. Drink the water. Give it two to four weeks to start feeling like you belong.
You already do. You just haven't had time to learn the accent yet.
It's a strange thing, grief for a place you chose to leave.