Engineers are not entirely cost-oblivious entities.
replyThey're not but if they don't talk to the pricing team, and most devs don't want to talk to business people, they'd never coordinate on where it makes sense to show pricing to customers.
replyYou didn’t read the comment I replied to, did you? The premise was :
reply> the UI flow is geared towards the idea that engineers don't really see the costs, they just build stuff and then management pays at the end of the month.
So this is about the engineers consuming AWS, not the ones who designed and implemented AWS
A core part of an engineers job is including thinking about cost in what they do.
replyRight - nobody who’s had a formal education in engineering would think that way, because cost considerations are part of the curriculum from the start.
replyI don't think a lot of formal education places teach AWS's resource pricing structure, which can be incredibly confusing, but can be boiled down to: if you want to be as cheap as possible, just use EC2 for everything and maybe S3 for storage.
replyI'm very surprised you expect any formal education to teach any specific pricing structure. You teach how to evaluate solutions for their price impact. No one was claiming any curriculum includes AWS's resource pricing structure.
replyI can't recall cost ever coming up as a consideration during my years of formal computer science studies in school. Big-O efficiency, sure, but the cost of compute, storage, bandwidth, nope, not once.
replyIt was absolutely hammered into me in the years of working for startups that followed, though.
Just noticed you did say computer science, not computer engineering. Two very different things.
reply