Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@YouAllSuck how? That doesn’t make a lot of sense this isn’t something about job security.
-
@HolyTeabags whether it’s unconscious or not adding more work to the project when you’ve already put a lot of effort in
The way you presented it is extending funding and writing off the loss
You see the project better than I do but that’s the first thought -
@YouAllSuck yeah this isn’t anything to do with funding and things like that. I work for a pretty big company and the app I’m working on is legacy (20+ years) and in desperate need of some TLC as you’ll see by my previous posts it has plenty of money and investment behind it.
The upgrade path I got told to take was to do it all in one go. Not ideal of course but I did what I was told to do.
The issue I have here is how I was kept in the dark while I was working on the upgrade, a new path was just decided and no one had the decency to tell me haha -
-
@YouAllSuck job wise I’m pretty safe, my manager is currently looking at promoting me to senior some point this year so we’ll see what happens.
Found this in our codebase, apparently one of my co-workers had written this
In the ever-growing saga of the upgrade, here is another one.
In the daily scrum meeting, I chat about the upgrade, standard stuff.
The other dev pipes up - "Oh we had a meeting about that this morning and were going with a different approach"
Me - "wait, we're doing what now? You do know I've spent a month so far just on this upgrade?*
*silence*
Anyways I continue working on the upgrade, few meetings while I try to find out what's going on.
Spoken to BA, my line manager and the other dev didn't get much basically saying yeah this is how we're handing it now.
Well it turns out after writing a big long message to the other dev, he decided *yesterday* in a manager meeting (he's kind of a manager but not really) to propose a new approach and they all just leapt at the chance even though it's going to take way longer (2 years estimate) to patch up the system version by version until we get to the latest release.
So at some point today he sends me a message to stop what I'm doing and go and help with a product release and that we *are* doing this new approach and that he made the decision yesterday. I'm sorry but since when did he become my manager micromanaging me haha
So as the only one doing the upgrade, I only got told of this change in passing, the other dev said that he decided yesterday and didn't bother to tell me as he had other stuff to work on and neither did my line manager.
Seriously what the hell.
So hopefully the things I've worked on and done might get used in a year or two haha
rant
legacy
wtf
ruby
rails