stillicidious
Higher rates -> reduced accessibility of personal credit -> lower spending -> lower corporate revenue -> higher cost of borrowing -> higher cost of debt service -> lower profits -> stock price
Rates act as a global parameter that impacts performance of companies differently, with the consensus understanding that it impacts debt-fuelled (or what we now usually call growth) companies the most.
The reason the author is trapped long enough in meat grinder hiring to notice this "problem" is likely precisely because of some indistinguishable cookie cutter bullet point soup getting them nowhere. If you can capture it in a data structure, it's not a resume!
See also: why isn't there a universal UI for web sites?
There is currently a widespread fear that quantitative tightening could arrive very rapidly, with disastrous effects on high multiplier tech stocks and other debt-fuelled businesses. They've all been getting hammered in uniform since at least December.
Meanwhile, can't complain all that much if zero-cost features can be added to Rust to make it easier to market it to scripting folk. I think that can only be a good thing, even if the feature design is far from ideal.
The belief in the right to a predictably long life is a new idea barely a few centuries old at most. Not that I'm personally complaining, but the statement did make me think, the value of living longer for everyone is not self-evident (at least from where I am standing), and the presumption that it is seems in itself dogmatic.
Actually, I could suggest a few non-faith approaches to rationalize the benefit of early death
At least btrees perform much worse with random insertions. I don't know how much impact it has on LSM
Original author could send a DMCA, or they could simply enjoy Christmas and assume a ticket will undo this sometime in January.
Finally with local statistics, you still have political dramatics like https://twitter.com/dancohen3000/status/1473480933579923456
As for the extremely disappointing asshole comment, coming from a moderator is quite frankly astounding. "Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith".
Reminds me of a younger self going to interview for the technical team at a bank. I arrived full of youthful zest, thoroughly aced the interview. One of the interviewers, who already looked rather zombie-like, accompanied me to the exit. As I walked off he lit a cigarette and shouted after me, "don't accept the offer, this is not a place for someone like you!"
Made a variety of friends over the years who have shared stories of that bank. It's notorious, the interviewer was absolutely right.
From that perspective, I think it might be ok to say that most eng folk complaining about AWS billing need a safer language (higher level abstraction) where they are protected from causing harm or being harmed.
I'm saying this is my bread and butter, and I've seen the same pattern in every company I've crossed the doors of. It's no made up scenario when a team of contractors have spent 12 months building out some service, not a single person will have given a damn about costs, so cost optimization is purchased separately. The contractors aren't wrong nor is the business wrong, nor is this pattern unique to cloud spend.
> I happen to work in the security industry
Then surely you will understand how an entire subindustry can exist to mop up after engineers who could otherwise 'simply' avoid most mistakes if they just spent more time Googling.
If you haven't experienced Google translating insistently German responses from one of their DC techs you probably haven't been using them for long enough ;)
As for networking, would encourage installing something like Smokeping
I don't think I've seen a latency spike on AWS in 10 years. Hetzner, it's often possible to observe latency and drops over 10 minutes (and the situation hasn't changed much in about 10 years)
Limited IO bandwidth in middle and upper management alongside difficult schedules (we covered that one already). Take 2 steps above engineer on an org chart and detail becomes invisible, the vast majority of tasks begin to resemble a teenager at a mall with their dad's credit card. Meaningful technical validation phases are almost unheard of in many organizations, and largely antithetical to agile.
> Why do outfits like Digital Ocean advertise on the notion of clear billing as a positive differentiator compared to AWS?
Because they market to folk who never take the time to model comparative costs. In any project I considered them for (3 I think, <$15k/year each), Digital Ocean was significantly more expensive than AWS. I follow my spreadsheets, the industry follows marketing.
> Nobody thinks of AWS as a security company
They're the only vendor I deal with who are on first name terms with the NSA and sell in tremendous quantities to the US government. CloudFlare on the other hand, to this day, default to MITMing SSL connections for new accounts and downgrading them to cleartext en route to the back end. It seems our perceptions differ wildly.
Corey's business exists because prevailing engineering culture encourages pretty much the entire industry to consider optimization as an afterthought, not because engineers can't understand AWS pricing, or interpret a few bar charts in Cost Explorer, and in the face of a deadline, if it's not on the agile board everyone knows it doesn't exist.
Many of Corey's technical posts are around finding sweet technical substitutes for niche use cases, but as I'm sure he'll tell you, 80% of what he does is easily discovered a few clicks away from the AWS home page.
> as they build out their pivot towards targeting the enterprise market
Cloudflare have a solid sales pipeline, but they're a sitting duck if any of the big clouds ever decide to replicate the business model like-for-like. One of the reasons this may not have happened yet is because Cloudflare's whole presentation is consumer oriented, starting with domain configuration management that is hell to version correctly when 20 people have access to the account. Outside some sweet Javascript cold start hacks they basically have no moat, and there are far more situations that could send the company into desperate measures than otherwise.