Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
the problem is that there are ALWAYS people in need of work and ready to do any kind of shit.
So old legacy survive, without even evolving.
I'd love to hear about companies destroyed because few developers left.
But I wonder if it happens so often. Considering the high turnover of our profession, my impression is that companies rarely fail because they cannot replace developers.
There is also something called "Bermuda plan": A way to finish a project is to invert Brooks' Law. This is the Bermuda plan, when 90% of the developers are removed ("send them to Bermuda") and the remaining 10% complete the software (Wikipedia)
acz09034122yI love that!
A few years ago, I was part of a 3-head team in charge of the flagship project at the company: I, a colleague (NN), and my line manager.
We had recently been bought by a giant "global technology group", and the new management was putting my line manager under pressure to deliver more and faster, and he passed all the heat on to me.
NN had been on that project for 5 years and he was good friends with the line manager, so he basically got praise just for being there, even though he spent half the day in the kitchen.
I, however, had moved to that project recently and was still in the process of understanding the most horrible code base ever (with literally zero documentation).
One day, he just fired me. He said: "Sorry, I need to deliver, and you are not helping me deliver." What he didn't know: NN had already decided to go and quit on his own only one week later. So, all of the sudden, my line manager was all alone and still had to "deliver".
He was fired a month later.
cprn11832yHonestly, use that. Make them an offer. Tell them they can re-hire you for quadruple of your old salary with half the hours. And margarita Fridays.
bols595442yI don't want to rain on your parade. But they'll hire young inexperienced devs at a much lower rate of pay. You're merely a debit resource on some oik's laptop.
Legacy doesn’t matter. Someone will figure it out. If they’re in startup mode then yeah it’ll prob fall apart but if the business is well grounded then it’ll make it. Devs are replaceable unless the product is other worldly. My last job demanded devs to obtain knowledge over 12 different micro services. I built two of them so when I left or anyone left, it would be quite a blow. They’re still doing just fine but they’ve opted for rewriting rather then trying to figure it out as they brought new lazy influencers on board
Ohhh. That's why recruiters ask for 20 years experience when requesting entry level devs
TestInProd423150243d@Fast-Nop Yeah upper management who thinks "oh they're a dev, so they should know this" is absolute fucking annoying.
At my place there are VBA Macros, WPF desktop apps, and Web apps. There are only 2 developers, we're about as productive as possible when we have to switch from different programs constantly.
But you know, we can't apparently hire 2 more devs due to "cost" to help offset the load or anything.