Turned down two processes and decided to deliberately stay at my boring job for two more years
This isn't a settling post, it's a plan, and I want to write it down somewhere so I can be held to it.
The job is slow and the codebase is old. It also ends at six, every single day, no exceptions. That's roughly fifteen usable evening hours a week, and my employer will pay for the courses.
The maths I did: switching now is about 15% more and a year of proving myself from zero. Staying is two years of stable evenings, plus the internal move to the platform team that I've now got in writing in my development plan.
Everyone I've told thinks I'm coping. Maybe. Ask me in eighteen months.
2 comments
- 0
AnonymousAnon Did roughly this for eighteen months and it worked, with one caveat. The boring codebase eventually became the thing I had to explain in every interview, because that's what my day job looked like on paper. Make sure the evenings produce something you can actually point at, or you come out the far end with two years of stability and nothing on the page.
- 0
AnonymousAnon "Everyone thinks I'm coping" is doing a lot of work in this post, but honestly — evenings are the scarcest thing in this industry and most people trade them away for 15% without ever doing the arithmetic you just did. I'd only push on one thing: get the internal move recorded somewhere more durable than a development plan, because those don't survive a manager change.