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

If you walk into a job and cut their cost by 25 percent are you a hero or a snitch.

Candidly everyone in your leadership between you and the CFO/CEO is going to think you just made them look bad.

And you did.

It is easier to keep a bad decision hidden than it is to admit you fucked up, or worse that you burned a pile of money.



That is if they let you cut that cost. They may only let a top 5 firm consultant do that after paying their firm a few million.


You don't even have to be a big 5...

I have been consulting over a decade now.

I used to wonder if I was going to get pushed out based on age... I suspect that I could work in tech till the day I die.


Yeah, this is why tech debt is a $1.52T problem. A few points.

* Reducing the number of pods used by a micro service doesn't reduce cost by 25%. For most micro services data storage, data transfer, and other required dependencies will be a very large chunk of the total bill.

* In the organizations I've been in the director is always looking for ways to reduce the cloud bill. This is always a huge line item for them, and the modern microservice architecture is only making the cloud bill higher.

* How is this anything but objectively good for the company?

* Avoiding stirring the pot won't make you any enemies in the workplace, but it won't make you any friends either. Deliver value where you can and the workplace politics will be what they are.

* I've be a part of, and have seen, cloud bills cut by as much as 80%. When things get that bad you won't lose reputation by fixing it because people in many departments are feeling the negative impact of the microservice.


Plan ahea

d

Planing seems to be a lost art. The word "capacity" is something on one uses in an agile/cloud based workflow.




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

Search: