151–160 of 194 posts
Earlier quoted context omitted.
“Engineering is the art of modelling materials we do not wholly understand, into shapes we cannot precisely analyse so as to withstand forces we cannot properly assess, in such a way that the public has no reason to suspect the extent of our ignorance.” - Dr. AR Dykes
Ah the eloquence of Dr. AR Dykes, perfectly said. Thank you.
"A cpu is literally a rock that we tricked into thinking."
Couple of years ago I saved about 14 mn of revenue per year for my company. I got a 250$ bonus for it.
This is why you should start the conversation with "I have drawn up a plan to save the company $14M per year. I will execute this plan in exchange for $7M upon completion." If they say no then just go back to your regular duties.
Shit... I reduced our spend on one AWS account from $270K a month to $75K a month.
Great! Shareholders will be happy. Did you receive any bonus?
> The best optimization is simply shutting things off This is the way. A similar idea has been bouncing around in my mind for a while now. An ideal, turnkey system would do the following: - Execute via Lambda (serverless). - Support automated startup and shutdown of various AWS resources on a schedule influenced by specially formatted tags. - Enable resources to be brought back up out of schedule when demand dictates…
Earlier quoted context omitted.
If your company has a spending commitment with AWS in order to get a few percent savings, and it's just barely hitting the contracted amount, it may not be worth the effort to pursue any cost savings. Suppose your company has committed to hit 5M in spend, and they're just barely inching over the line at 5.01M. You might spend a bunch of time and labor expense knocking it down to 4M of usage and not really move the bo…
Spending commitment on AWS? Are you referring to ec2 reserved instances? Even if you have one year reservations on your instances, starting service migrations/deprecations now would pay off quickly enough. Your commitment expires in 6 months, on an average basis.
Earlier quoted context omitted.
I think "engineer" isn't really the correct word to use for the artisans who build much of the tooling used by most companies. An engineer either wears a striped hat and drives a train, or, went to a credentialed school and passed a bunch of test and is allowed to sign documents that state "this thing, if built this way, won't collapse and kill people." It is expected that an engineer can predict with reasonable accu…
> An engineer [] went to a credentialed school and passed a bunch of test and is allowed to sign documents that state "this thing, if built this way, won't collapse and kill people." Ahhh - that old craptacular definition. You completely ignore mechanical engineers, chemical engineers, electrical & electronics engineers. Not all engineers make bridges. Secondly, the implied cause and effect even within civil engineer…
I suppose you've got an engineering degree in pedantic engineering? Engineers manage cost and risk. The skunk-works stuff is marginally "science" not "engineering" given the relatively large budgets and relative lack of "we know this works." Cern is similarly an enormous engineering enterprise in that it's a huge stack of "we know this works" in service of "we're not sure what this will do"
A discussion of how "software engineers" deliver projects with neither cost or risk as part of the process implies, to me, that they're not engineers.
Earlier quoted context omitted.
Unfortunately it seems like businesses only wake up and asks for cost reduction on the infrastructure spend side once the problem is out of control. At that point, the level of operations effort to get it under control feels more like a "big rewrite" than a collection of small tweaks.
It's opportunity cost. If it's not a problem then you can just make more money with your time.
Earlier quoted context omitted.
It's truly fascinating how companies won't bat at an eye at spending ungodly amounts of money on things they don't need, but will sweat profusely at the thought of a tiny fraction of that going towards additional compensation.
Something something snakes, something something unintended consequences.
Earlier quoted context omitted.
I’m very aware of that tool but it’s far from perfect. I’ve spec’d things out on that then seen very different prices when I actually create things in AWS. In part because the tool doesn’t take some things into account or because sometimes it’s impossible to guess your usage for a new feature. I don’t believe the VPC was factored in when I used that calculator, even after selecting RDS Proxy.
VPCs are free. Are you talking about data transfer? I know it has options to enter values like amount of data transfer you are planning to do.