What you want is to both learn valuable, interesting skills and have a job that both utilizes them and leads to more of the same.
The first sentence - they 'took a chance on you' suggests that you don't yet have the technical resume you want to help you get a different job.
Based on that, it sounds like the path to getting the job you want is just to do the one you have for now. My suggestion is to commit to your current job with the intent of sticking it out for a year unless something perfect falls in your lap. In other words, you're not really committing to this job long-term, but you don't want to be affected by an "I don't care" attitude while you're there.
Some places accept new developers but aren't actually a good place for new developers. I'd talk to the manager and express goals but not concerns. The response to that will tell you what you need to know. If they see your enthusiasm and ability to learn but don't seem decisive about helping you toward those goals, or promise but don't deliver, then it's likely not a good long-term job. You can waste years waiting for change that never comes. It's a cultural problem that will survive multiple management turnovers.
Learn as much as you can on your own time during that year. When you start applying for new jobs
You'll have something technical-sounding on your resume, even though it's not the kind of experience you want yet.
They'll see that you stuck it out for a year. That's reasonable.
When you describe your previous work and goals to an interviewer, don't be negative about your current work. A smart interviewer will read between the lines because your concern is a common one.
Look at the picture you're painting. I didn't like this, but I stuck with it. I'm capable of performing my current tasks (because I'm still employed there.) I took the initiative to learn more on my own. I'm so enthusiastic about applying what I've learned and learning more that I want a job that helps me to do that.
It sounds to me like you could leverage your current situation to move you toward where you want to be.
I really appreciate the reply and do agree with you on all the points really, that's the sanest/logical thing to do.
but
I can feel any motivation I've got for this role evaporating fast I haven't wanted to get up in the morning and code (I have been getting up at 05:00 for the last 18 months to code before going to work) I haven't wanted to hack on anything on the weekends.
So, stay and be the passionless developer resigned to working on antiquated/proprietary tech for the rest of my career.
Or, get out before that happens and try gloss over the last couple of months.
Sticking around for a year or so might help you get your next job. But if you can get the next job without doing that, go for it. It's not like you're doing it every three months. My answer was just focused on the long-term solution to being where you want to be down the road. There's nothing wrong with a shortcut if you find one.
I feel for you. Writing software takes some mental energy which is hard to give if you're not enjoying it. When a company puts a developer in that situation I can see their point of view, but it reflects a lack of understanding which is very common and hard to change. It's like raising pigs in tiny cages, not because you're cruel, but because you don't know that pigs in tiny cages aren't happy, and that they can do amazing things if they're not in tiny cages.
What you want is to both learn valuable, interesting skills and have a job that both utilizes them and leads to more of the same.
The first sentence - they 'took a chance on you' suggests that you don't yet have the technical resume you want to help you get a different job.
Based on that, it sounds like the path to getting the job you want is just to do the one you have for now. My suggestion is to commit to your current job with the intent of sticking it out for a year unless something perfect falls in your lap. In other words, you're not really committing to this job long-term, but you don't want to be affected by an "I don't care" attitude while you're there.
Some places accept new developers but aren't actually a good place for new developers. I'd talk to the manager and express goals but not concerns. The response to that will tell you what you need to know. If they see your enthusiasm and ability to learn but don't seem decisive about helping you toward those goals, or promise but don't deliver, then it's likely not a good long-term job. You can waste years waiting for change that never comes. It's a cultural problem that will survive multiple management turnovers.
Learn as much as you can on your own time during that year. When you start applying for new jobs
It sounds to me like you could leverage your current situation to move you toward where you want to be.
Wow, thanks @scotthannen 🙏
I really appreciate the reply and do agree with you on all the points really, that's the sanest/logical thing to do.
but
I can feel any motivation I've got for this role evaporating fast I haven't wanted to get up in the morning and code (I have been getting up at 05:00 for the last 18 months to code before going to work) I haven't wanted to hack on anything on the weekends.
So, stay and be the passionless developer resigned to working on antiquated/proprietary tech for the rest of my career.
Or, get out before that happens and try gloss over the last couple of months.
Sticking around for a year or so might help you get your next job. But if you can get the next job without doing that, go for it. It's not like you're doing it every three months. My answer was just focused on the long-term solution to being where you want to be down the road. There's nothing wrong with a shortcut if you find one.
I feel for you. Writing software takes some mental energy which is hard to give if you're not enjoying it. When a company puts a developer in that situation I can see their point of view, but it reflects a lack of understanding which is very common and hard to change. It's like raising pigs in tiny cages, not because you're cruel, but because you don't know that pigs in tiny cages aren't happy, and that they can do amazing things if they're not in tiny cages.
Wow! What is life?
We're all just pigs in little cages 🙃
Yeah, I know where you're coming from Scott, thanks again 🙏