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
-
@Trinsec Oh no way...they "provide too much benefit to the company", to even be included in the employee pool...
-
@Kgd- Currently, the spec doesn't really specify, but I assume that the number of people to output will be an option...and just output X people with the lowest "profitability score"
-
So here's my two cents.
If you don't code it, they might fire you and get someone who will. Then you and others will end up unemployed. Also, they're kind of reeping what they've sown if they're unproductive with their work.
At the end of the day, I look at it like this: I've got bills to pay and need food on my table when I sit down to eat. While I may help out my co workers anyway I can, I'm more important to me than they are. And I full heartedly expect the exact same mindset from them.
I'd code it and get on with my job. Jobs come and go these days.
Also, are sick days the only days you're allowed to take off? Like I know some places allow people to convert the overtime they work into days they can take off. what asshole attributes being sick to unproductiveness? -
Same what @Stuxnet said, plus - be extra transparent on documenting how the picker works, so that you and colleagues know exactly what is worth their effort (for the profitability index or whatever you're working on).
This gives power to employees to question employer about practices used (motivation to firong because days taken off), and as well exploit the system, so that management would have to step up -
@Stuxnet Well yeah, that's basically my mindset as well. If they're good at their job they won't get fired...
And, regarding the sick days. We don't really have like "You have 20 sick days per year and thats it" system. You can come in and come out whenever you want (that for devs at least). But they track it heavily, and you will get some lashback if you start missing days too often
Algorithm strikes again! 😁
:)) finally a good answer
Always wondered how Dijkstra came up with that algorithm!
This is more of a story than a rant, but it has some rant-ey elements, so whetever...
I work for a pretty big company. Several departments, teams, many different markets...so it's a big orchestration. The programming department (aprox. 5% of all employees) is the core of the whole company, because everybody else uses software we've written...(a bit off topic, the point is there are a lot of people)
So today, I got assigned with a side-project. The project spec arrives, and as I read through it, I start realizing that upper-management whats me to build an app to fire people instead for them. The app is supposed to track salary, connect with Trello (for departments that use it) to track finished tasks, track sick days, work attendence...a lot of stuff, and at the end, if the situation requires, spit out a person that is of least benefit to the company, to be fired...
Now from coding perspective, this will be very interesting and fun to build, but from a moral standpoint, I'm a bit woried...simply because, indirectly, I'm firing those people. Because, the way I tune the the app(specifically the algorithm that weighs the value of an employee to the company) will cause certain people to get fired...
So I'm woried I'm gonna have a small breakdown when the app goes live and I see someone saying goodbye to theie colegues of something similar...heck, the app might even spit out my name some day(I should probably add a tiny if statement somewhere in there :) )
What do you guys think about this, from a moral standpoint? Would you be okay with building something like this?
(Sorry for the long post :/ )
rant
plshelp
firing people
exsitential crisis
algorithm
morality