3 ms·
> First of all, its a reset on context. You'll start at 0, and you'll have to learn, wind up, and prove yourself again. And its a reset on your team, you'll get
by moduspol 4y ago
> First of all, its a reset on context. You'll start at 0, and you'll have to learn, wind up, and prove yourself again. And its a reset on your team, you'll get a completely new set of people you'll have to learn to work and communicate with.
I just went through this starting earlier this year, and it didn't go well. It was a smaller company and even though I knew all the parts of the tech stack ahead of time, there were just a ton of undocumented internal-isms and an overall culture of "just stay in your lane and iterate on JIRA tickets. None of us really understand how to build the software, can deploy the software, or can trace inputs and outputs throughout the system." Among other tedium.
I only lasted four months before moving on, but the new job is working out a lot better and pays more, too. So I agree it's not risk-free, but at the end of the day, I was getting paid the whole time and ended up somewhere better, so it worked out anyway.