I’ve been there. It’s helpful to know WHY the other platform was chosen, and it’s reasonable to ask.
This is my main response to the OP's situation. It sounds like OP's solution uses modern practices but (a) is unproven and (b) still needs to be built out. Both (a) and (b) represent risk for the business whereas the Java solution, as ugly as it may seem to some, (a) has been used before and (b) exists and has support (training even). Businesses can't always afford to take a chance on newish tech, if a tool already exists which meets customer requirements then there is no need to reinvent the wheel.
Thanks @evanoman
, these are good points and you can understand why the business would want to go with tried and tested over the other options.
I've spent today familiarising myself with the system using postman to explore the API and not making a great deal of progress.
I have spent the majority of my time learning JavaScript and associated frameworks, I made this abundantly clear in my interview.
So the learning curve involved is steep as I'm not familiar with it at all making barrier to entry quite high.
I'm trying to embrace it and get familiar with it, it's going to be a tough ol' slug. And for what? To be the company expert in the CMS, no thanks.
It appears that the people making the decisions have been wowed by the marketing and I'm the person that has to make it a reality for them.
I was describing what it was I needed to do with the system today to one of the senior devs today and he was laughing his head off at how clunky it all was. He was laughing as he was relieved it wasn't him doing the work 🤷♀️
I absolutely understand where you are coming from. My current task is post-hoc unit testing a legacy C++ system w/ 5k line functions and no docs. Obviously I don't want to be doing that. However I am slogging through because I know there is a lot of potential at my company (assuming I survive my current tasking). Additionally this task, as orthogonal to my interests as it may be, is still providing me with valuable experience in problem solving, test writing, and refactoring. I can't imagine what I am learning now won't be useful someday.
So if you don't see any potential in your position after you survive this first task, and you have other options, then I wouldn't blame you for leaving. However if you believe in this company and can see yourself enjoying future tasking then I would bite the bullet, face the task head-on, and try to learn as much as possible.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is my main response to the OP's situation. It sounds like OP's solution uses modern practices but (a) is unproven and (b) still needs to be built out. Both (a) and (b) represent risk for the business whereas the Java solution, as ugly as it may seem to some, (a) has been used before and (b) exists and has support (training even). Businesses can't always afford to take a chance on newish tech, if a tool already exists which meets customer requirements then there is no need to reinvent the wheel.
Thanks @evanoman , these are good points and you can understand why the business would want to go with tried and tested over the other options.
I've spent today familiarising myself with the system using postman to explore the API and not making a great deal of progress.
I have spent the majority of my time learning JavaScript and associated frameworks, I made this abundantly clear in my interview.
So the learning curve involved is steep as I'm not familiar with it at all making barrier to entry quite high.
I'm trying to embrace it and get familiar with it, it's going to be a tough ol' slug. And for what? To be the company expert in the CMS, no thanks.
It appears that the people making the decisions have been wowed by the marketing and I'm the person that has to make it a reality for them.
I was describing what it was I needed to do with the system today to one of the senior devs today and he was laughing his head off at how clunky it all was. He was laughing as he was relieved it wasn't him doing the work 🤷♀️
I absolutely understand where you are coming from. My current task is post-hoc unit testing a legacy C++ system w/ 5k line functions and no docs. Obviously I don't want to be doing that. However I am slogging through because I know there is a lot of potential at my company (assuming I survive my current tasking). Additionally this task, as orthogonal to my interests as it may be, is still providing me with valuable experience in problem solving, test writing, and refactoring. I can't imagine what I am learning now won't be useful someday.
So if you don't see any potential in your position after you survive this first task, and you have other options, then I wouldn't blame you for leaving. However if you believe in this company and can see yourself enjoying future tasking then I would bite the bullet, face the task head-on, and try to learn as much as possible.