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
-
Automation is king. It's inevitable.
If you don't automate something, someone else will.
Honestly, I wouldn't feel bad, but I'm not very empathetic. Besides, if their jobs can be automated pretty easily, it's likely relatively unskilled labor, so it should be easy enough for them to find work elsewhere. I wouldn't feel too bad. -
One can suggest to the boss that those people whose jobs are being replaced are known quantities with knowledge of the company. They may have some great workers that would feel crazy loyal if not laid off, and not have to waste money on another new hire that doesn't work out.
Basically remind them that people are capable of more than one job, and just because you don't need them to do job A, doesn't mean the business can't make more money (for the same expense as currently) for having them do job B. -
@skprog heard about it, will give it a go soon.
-
@Silvus i did something similar to that. He then began asking me about ways of going around it. It made me feel uncomfortable really.
-
@bkwilliams how did that made you feel?
-
@georgelynch oh man I don't think I have a good enough poker face for that. Btw, is that really your name? Completely unrelated but that is the name of my favorite rock guitarrist!
-
@AleCx04 yes @georgelynch is the name of my favorite guitarist too.
-
@AleCx04 they would get replaced by either "cheaper, younger people", outsource firm, or when the bank was bought. It's the nature of business. I guess I didn't care because they would be replaced eventually anyway.
-
@AleCx04 understandable, but at least you tried. And some people fail to remember they can make more money with the same people. Rather than how much they save by firing them. When doing the work, look for stuff that you can't automate that they might start working on instead.
-
@georgelynch oh man did we just both mentioned the same Mr Scary???!!
-
@Silvus thanks man, I'll try.
Found this in our codebase, apparently one of my co-workers had written this
!rant
More like a genersl question I guess. But how do you guys react to writing software that might make someone else get laid off? At work I developed an application that manages a lot of the inventories and yard management that had to be done by hand. While I was developing it, the manager that was giving me the details mentioned (jokingly) many times that if the software works as it was expected that they will not require certain people anymore. I shrugged it off as a joke since I could not imagine it being serious. Turns out, it was serious and some talks about company restructuring have taken place since I released the app into our servers. How the fuck am I supposed to feel? If someone loses their job because of something like this, how would someone go about NOT feeling guilty af?
undefined
not a rant
wtf
wtfisthis