this post was submitted on 14 May 2024
118 points (96.8% liked)

Programming

17303 readers
75 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] prowling4973 9 points 5 months ago (2 children)

I believe that the trick is not to show the developers the bill.

I haven't had access to the AWS bill in 4 of 5 companies that I've worked at. Why? Fuck if I knew, but I got vague answers like security and compliance when I asked.

I wonder how many thousands could have been saved if all devs could see what they're actually paying for but not using.

[–] UFODivebomb 8 points 5 months ago

I think it's a combination of things. My experience definitely parallels yours: when developers have access to the bill they tend to realize the cost of the services they are using. Sometimes even resulting in optimizations to those costs.

At the same time AWS can get fucked with how horrible their bills are to understand. They don't exactly go out of their way or even slightly on a good path to deliver a clear bill.

So even if the developers have access to the bills they might just end up with an impenetrable list of bullshit from AWS

[–] [email protected] 0 points 5 months ago

They will don't care, not their money, not their job. Can't blame them