Moving North
This is my final week in Denver. On Monday, I’m hitting the road solo, bound for northern Wisconsin — my wife joins me in December. Leaving behind a job I’ve genuinely liked, even with the occasional disagreements, is bittersweet. That’s just how it goes: you work for a company, you don’t always see eye to eye on everything. Kind of like relationships — never smooth sailing all the time.
I’m going to miss my coworkers and the environment at the hospital. Three years is long enough to care about the work and the people doing it with you. The banter, the brainstorming sessions, the team dynamic — that’s not easy to walk away from, and pretending otherwise would be dishonest.
What Drew Me to the New Role
The new opportunity came with a chance to go deeper on the technical side — more autonomy, a different stack, and problems I haven’t solved before. I’ve been in a comfort zone for a while, and comfortable is fine right up until it isn’t. This felt like the right time to push.
This week feels more like a consulting engagement than my last week — answering questions, documenting things, handing off context. I’m already thinking about how to approach the new role, though I know better than to show up on day one with all the answers. Step one is to listen.
Key Takeaways
- Leaving a good job for a better opportunity is still hard — the people make it that way.
- Three years is enough time to build real relationships and care about the outcomes. That’s a good sign, not a reason to stay.
- Job transitions are a good forcing function for documentation — you realize quickly how much knowledge lives only in your head.
- A new chapter kicks off next week — bring on the adventure.