I do suspect it was built with some form of AI though because the handful of links I've tried to dig into have all linked to the wrong place/are invalid :/

Which is also how we've gone about working out how to improve the CLI. It's usually one or more of:

* rethinking the subcommands and hierarchy to something more obvious and aligned to the task

* providing clear documentation upfront (i.e, in the skills file)

* keeping help text concise, but not too concise. You can't assume the reader is already a power user and it's simply looking for a reminder/reference. So include usage examples for common use cases

* where possible on errors, suggest the likely commands the person meant.

* In general offer affordances on what likely next steps will be. This goes for help output, success, and errors.

> cli help text is usually massive

That doesn't have to be true.

> could eat a lot of the savings on retries

This doesn't have to be true either. You don't need to give the same full help output on every single error, once they've got it once they've got it. Also the size of the entire help output for most CLIs is generally insignificant compared to even just a couple of source files in most repos.

I don't know if we'll keep dissecting every incremental improvement we make as (so far) the general approach is the same as documented in the existing blog post: document common use cases -> benchmark them -> identify bottlenecks/expensive hot spots -> fix them -> repeat

The main thing changing right now is observing new more frequent use cases (either because we're adding new capabilities, or users are doing things we didn't entirely predict) and adding them to the test cases.

What can definitely happen though is you get one that is inappropriate in a given context. An example here might be a recommendation from an m5.2xlarge to an m6g.2xlarge instance. Same vCPUs and memory, lower cost, but... also a switch from Intel -> ARM architectures. For a lot of companies their build pipelines make it easy enough to make that change. For others there may be some specific dependency on Intel for that workload which means changing the architecture isn't viable. In that case you can simply dismiss the recommendation and we'll stop suggesting it.

We've found even more improvements since that post so those will be shipping soon too.

"the kind of movies that I loved and the kind of movies that were my bread and butter (are no longer affordable if I was to do a cinema release)"

So maybe Behind the Candelabra was direct to HBO precisely because of the economics he was pointing out?

I'd posit the main difference between the two was Terraform's declarative approach provided more consistency and predictability in how infrastructure was defined and provisioned. The constraints it imposed were the benefit vs a sprawling estate with a hundred different bespoke ways to provision a given service in your preferred language.

This is absolutely not a car that screams "Ferrari" though.

Locally there's a bridge that is regularly hit by human drivers. A bridge! Not a rare weather pattern, not some temporary and surprising change in conditions. A physical structure that has literally been there for over 100 years. The approach has numerous warnings, flashing lights, and swinging poles that will hit your vehicle and alert you that you're too high to clear the underpass if you continue. And yet... it's so common that there's websites and instagram tags and all manner of things to track and laugh at the people that continue to do it anyway.

FYI, 59 days since the last incident apparently: https://howmanydayssincemontaguestreetbridgehasbeenhit.com

He was having great success with small and mid-tier companies, then he'd run a pilot with a massive global brand and the results would be even more stark than what he'd see with his existing users. But basically could not close a deal.

Because of exactly what you've shared here: "they measured on how much the spend, not on how much they bring in. Because they've never been able to do that. Their job is so much easier if nobody can ever see that latter figure they just go year to year asking for more budget and the more they spend the more everyone thinks they're doing a great job". I was naive enough at the time to think he was wrong and that couldn't possibly be true. But I've seen enough in the years since to realise he was right.

And yes, one of the outcomes of this was also ditching the human output for something more dense and LLM friendly.

Comments URL: https://news.ycombinator.com/item?id=48193230

Points: 12

# Comments: 5

Turns out the price I saw in the booking portal isn’t actually what Amazon paid. It’s kinda more like a rack rate listing. But then there’s all kinds of discounting/cash back that happens on the backend based on the amount of travel booked each month.

I used to love his stuff. Until he just wouldn’t stop beating this drum so breathlessly. Now I wonder how much I’d suffered Gell-Man amnesia with the other content of his I’d previously enjoyed.

[1] https://lumenate.co/lumenate-nova/