Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That's normal nowadays, even in the most ridiculous of situations.

I once found that a system was getting a little expensive. As, AWS was billing us a million a month expensive. I figured this out, and came up with a plan that would cut it down to 80 thousand by spending 4 days: You know, a mild, 11 million a year of savings. Management insisted that the work had to go through scheduling, and intake, a process that would involve zero developers looking at anything, but would delay doing the task a month and a half.

And no, nothing the team was working on came even remotely close to that ROI. Following the process just cost an extra 1.5 million dollars.



The manager probably can't take the credit for saving 10 million dollars if they don't put it through the system.


What was the opportunity cost of potentially deprioritizing other work?


^ nothing the team was working on came even remotely close to that ROI.

I read it as that the opportunity cost would be lower.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: