headsman's axe
-
Found this in the documentation for the business case on an enhancement I'm making to a webpage: "This change could eliminate 1 position in Orders and another position in customer service as well." hmmm. What amounts to a few hours of work for me could cost 2 people their jobs. :~ I've been making these kinds of changes for over a year. I may have decimated an entire department by now :wtf: Efficiency FTW I guess.
Play my game Gravity: IOS[^], Android[^], Windows Phone 7[^]
-
Found this in the documentation for the business case on an enhancement I'm making to a webpage: "This change could eliminate 1 position in Orders and another position in customer service as well." hmmm. What amounts to a few hours of work for me could cost 2 people their jobs. :~ I've been making these kinds of changes for over a year. I may have decimated an entire department by now :wtf: Efficiency FTW I guess.
Play my game Gravity: IOS[^], Android[^], Windows Phone 7[^]
Odds are that just means that someone who is currently working 3 different jobs can go back to only one or two now. If it's a good company that person even gets to keep their current salary which wasn't paying them to do 3 jobs in the first place.
------------------------------------- Do not do what has already been done. Absolute power corrupts absolutely.. but it ROCKS absolutely, too.
-
Found this in the documentation for the business case on an enhancement I'm making to a webpage: "This change could eliminate 1 position in Orders and another position in customer service as well." hmmm. What amounts to a few hours of work for me could cost 2 people their jobs. :~ I've been making these kinds of changes for over a year. I may have decimated an entire department by now :wtf: Efficiency FTW I guess.
Play my game Gravity: IOS[^], Android[^], Windows Phone 7[^]
"headsman's axe" That's how I swing. :cool: Actually, often in that kind of situation it's the developer who gets the axe when the project is done*. * With a rather loose definition of "done".