The correct question is: from whom?

When I was in finance there was a question whether US debt would crowd out other debt instruments. The answer, obviously, is "no." There seems to be an unlimited appetite for zero-risk debt, which makes no sense.

It can. Not sure what AI you're using, but Gemini outputs great bash. Of course you need to test it.

You do have to make sure to tell it what platform you're using, because things like MacOS have different CLIs than Linux.

This actually is easy to do with terraform and shared infrastructure; you don't need an AI in the loop.

Who hasn't accidentally deleted a resource because that property triggers a resource delete/create instead of an update?

It would help if it was obvious what the key fields were. But for some reason docs usually don't tell you.

Does information weigh anything?

There's no expectation of privacy in public areas. That's been the law of the land now for a long time.

>The right of the people to be secure in their persons, houses, papers, and effects,[a] against unreasonable searches and seizures, shall not be violated, and no Warrants shall issue, but upon probable cause, supported by Oath or affirmation, and particularly describing the place to be searched, and the persons or things to be seized.

Also:

>No person shall ... be deprived of life, liberty, or property, without due process of law.

Have been the law for a long time too and yet…

There’s a difference between happening to be captured on camera if there’s a camera in a public place and having a government agency identify and track you and your vehicle across hundreds of miles of travel.

It's actually no different from how real software is made. Requirements come from the business side, and through an odd game of telephone get down to developers.

The team that has developers closest to the customer usually makes the better product...or has the better product/market fit.

Then it's iteration.

I worked at a company where the VPs etc spewed the word "ontology" all the time. We were never sure if they knew they were spewing bullshit or they really believed what they were saying was real.

Ontology is one of those fancy words that sounds important but is basically, as another poster pointed out, a standardized vocabulary.

If you know what you're doing you don't need AWS support.

We add support when we want to do something new, like MediaTailor + SSAI. At that point we're exploring and trying to get our heads around how things work. Once it works there's no real point in support.

That said, you need to ask your account manager about (1) discounts in exchange for spend commitments, and (2) technical assistance. In general we have a talk with our AM when we're doing something new, and they rope in SMEs from the various products for us.

We're not that big, and I haven't worked for large companies, and it's always been a mystery to me why people have problems dealing with AWS. I've always found them to be super responsive and easy to get ahold of. OTOH we actually know what we're doing technically.

Google Cloud, OTOH, is super fucked up. I mean seriously, I doubt anyone there has any idea WTF is happening or how anything works anymore. There's no real cohesion, or at least there wasn't the last time I was abused by GCP.

> That said, you need to ask your account manager about (1) discounts in exchange for spend commitments, and (2) technical assistance.

Depending what precisely you mean by the second one, you may not even need an AM/support for that.

They won't help me use the platform, but they will still address issues with the platform. If you run into bugs, things not behaving how they're documented, or something that simply isn't exposed/available to customers they seem to be pretty good about getting it resolved regardless of your spend or support level.

(On my personal account with minimal spend, no AM, and no support... I've had engineers from the relevant teams email me directly after submitting a ticket for issues.)

So yeah, "if you know what you're doing" you probably don't even need the paid-for support.

> If you know what you're doing you don't need AWS support.

Hard disagree. I have to engage with AWS support almost once every 6 months. A lot of them end up being bugs identified in their services. Premium support is extremely valuable when your production services are down and you need to get them back up asap.

Mine is a M1 ultra with 128gb of ram. It's fast enough for me.

Thanks for the perspective!

Note that they were running Postgres on a 32 CPU box with 256GB of ram.

I'm actually surprised that it handled that many connections. The data implies that they have 4000 new connections/sec...but is it 4000 connections handled/sec?

32 vCPU, meaning an undetermined slice of a CPU that varies depending on what else is running on the box (and the provider has an incentive to run as many VMs on the box as possible).

It’s likely an actual CPU would’ve handled this load just fine.