I've got nodejs lambda code that is doing 388B/month and only at this point have we even considered changing the language for performance because the cost savings have a net positive ROI.
It took 5 years to get to this point.
1,405 karma · joined October 28, 2009
All opinions are solely mine and do not reflect any employer's.
I've got nodejs lambda code that is doing 388B/month and only at this point have we even considered changing the language for performance because the cost savings have a net positive ROI.
It took 5 years to get to this point.
Can they reallocate capital to stock buybacks if they were already going to do this, yes! Could I find anything prior to this bill to indicate any competitive reason for Intel to do this in the USA? No.
Article just reads as written by one who is anti-corporate, rise up and this is why one must be anti-work because the government only cares about lining the pockets of corporations.
Noticed as I was leaving. They kind of nervously laughed and fixed it.
You'd buy it just for the garage but don't want to put in the time to sort out logistics of a purchase?
IMO they're a dying company. Selling is a smart move to push their existing customers a cross sale product to close the loss gap. They'll drop 15 to 30% of their staff.
They're not that far from profitability when you realize their staffing cost is high vs the yielding return per employee.
It'll take 3 to 5 years for the pain to be felt and another 3 to 5 years from that point to collapse because most companies will just pay the renewal to buy time to let the rest of the space mature.
Source/bias: I see this happening all the time in the space. I gave a talk about why Terraform is dead and long live Pulumi.
I've been at a company where getting a Slack plugin approved took 8 months alone. Vendor review took a year.
These departments aren't equipped for the modern day and most want to live 10 years ago without change. Just keep with the old and vest.
Why is an individual after 3 years becoming the go to expert when the government employees many individuals for this very reason.
I don't mean this in a demeaning manner, but the government needs to raise the standard of expectations of their workers.
There is nowhere else I know of that has this sense of absolute job security and yet expectations on individuals never rise.
Why does government staff continue to grow at incredible numbers with the access to technology, and yet services don't leap forward?
People while also all including tends to bring with it the identity war with it.
I use folks as a 1:1 to avoid the above.
With such a high price per IP there are a lot of organizations finally putting in the effort of cleaning up their space and selling off blocks. I know a company that was doing consolidated and clean up for an aggregation of freeing 200k worth of space. They were looking at adding $15-35M to their pockets.
IPv6 support is still not where it needs to be. Look at the clouds. There are many services that still are only IPv4 or partial ipv6 support. Just check back in 1-3 years and the price will have recovered.
You can also start the close account process which takes 60 days and just pay the fees for anything not torn down and then it all gets nuked at the end of that period.
The managed services are expensive, but boy do they work well. Over the last couple years been running +100 each of managed elastic searches, RDS, and firehouse with minimal to no issues.
For most folks here on HN, you should not care about your cloud opex cost as long as it is time benefiting. The most costly thing to waste is time.
Can you cut your cloud bill by 35% with optimal provisioning? Most likely. Can you do this cut with a greater return given all the inputs, time, wages, opportunity cost, AND what level of confidence in completion to that exact or less deadline?
The only times I've seen the numbers work out has been, growth is flattening, +$3M/yr vendor spend or $45k/month specific service spend.
Corp B to continue the growth it forecasts apart of the merger needs to continue to invest in areas of high returns. Cut where it makes sense.
Corp B now has access to Corp A even solely as independent corps. Corp A gives them private pricing to Azure. Corp B starts shutting down their own infra/data center and need less staff. Don't need as much staff if you're shifting the management of many things to Corp A. Many companies do this with buying managed services.
Used this to power a +$30M revenue affiliate platform tracking.
I can't believe the cost of NATs! If you're running in triple AZs that is 3 nats you're paying for.
Not sure of the uproar if that is the case.
This way, all the R&D expenses are happening in Canada.
Is the speed limit emitted by LEDs? Why is it ever different between winter and summer? Etc.
If the sign is not white background,no LEDs, and black or red font I as a human would ignore the signage just like the car is probably trained for as that isn't reflective of North America standards.
I agree with comments in this thread that LTS should be a commercial bought option only.
Saying there are several in the running makes all exec/senior management think they have a chance and be gunning as hard as possible for the possibility.
If you want an easy way of increasing the risk folks are willing to take with little downside to the company at this point that is exactly the strategy one would implore.
I had an experience very similar to your, "just add a couple of columns". That experience which I'll explain was the final straw to getting me to start drafting the book.
An individual at an enterprise company made a PR to change the code from handling a single item to a list of items. Of course this showed promising performance because it reduced a bunch of the overhead operations that used to be O(N) down to some sub N amount.
It took me about 3 hours to fully understand the surrounding systems. At that point I did not review the implementation, BUT instead the problem. A system was falling behind and timing out. This implementation did help fix the issue by batching API calls. While I as the reviewer did the "laying groundwork" portion I realized that a lot of the API calls themselves did not need to be triggered in the first place.
Looking purely at the implementation for review was a LGTM (Looks Good To Me) kind of review because I could not weigh out the solutions to the problem without the information on the systems to understand where the problem could be.
I agree that larger PRs can increase the latency of getting feedback and getting quality feedback. I also have another view.
Most code reviews struggle not from the reviewing part and shockingly not the authoring part, but the laying groundwork part. The laying the groundwork part is before any hands to the keyboard to write actual implementation. This part focuses on explaining what is trying to be solved and for what problem. It is bringing everyone who would like to participate in the conversation up to speed on terminology, background, understanding of past decisions and the different proposals looked at, ruled out, etc.
I've seen too many PRs ask for reviews where the reviewer had to read the description half a dozen times and spend an additional hour understanding other systems that interact with the diff to be able to even attempt to discuss if the implementation solution is even the "correct" implementation that should be tackled for the problem at hand.
IMO, there are four key parts to better quality PRs, laying the groundwork, authoring the technical implementation, reviewing and feedback.
- Payments not properly supported outside of EU
- Identity verification process subpar. Wtf they ask more info than AWS does at $100k/m spend.
- Phone verification doesn't even properly work outside of Europe and support suggested just calling manually to verify.
- Support terrible to get started with
- K8s Kosmos documentation is lacking. Debugging issues is zero.