cadamsdotcom

Truly amazing. Quite thought provoking how it was helped by having high quality oracles. Eg. Qwenputer & good NES reference materials.

I guess humans need their oracles too: teachers, encyclopaedias, degrees, phds.

Bravo, awesome project, really creative!

If a team can't bring the site back up in an emergency situation that's poor planning, not poor debugging.

Planning for mitigation before resolution lets a team address production issues at leisure (because the customer impact is mitigated)

All this knowledge is in your agent - ask it for ideas!

Just to be clear are you suggesting one might find oneself without a clanker?

Where're you doing your debugging? The tundra??

Computing tapped out on sources of leverage for solving deterministic problems a while ago. Computers got fast and our algorithms got really good.

We're on to the next frontier, and it's a bit weird. Jagged frontier and all. But it's opening up new worlds.

Luckily loads of problems are amenable to a non-deterministic approach - even better, many have lots of solutions. SRE is in that bucket. There are as many ways to SRE as there are SREs

(source: one of the first SREs at Uber, co-invented Chaos Engineering as a sub-branch of SRE, hosted first chaos eng conf at Uber, played a key role in Uber's global SRE and incident response "Ring0" initiative, managed many SRE teams over a period of roughly 7 years before a career pivot. You could say I know a thing or two about SRE.)

To SRE well you look at the situation and pull from a huge range of tools. With such a broad range of solves, you're better to focus on the outcome: did we achieve our SLOs? Are they aligned with customer expectations? Focus on defining that and providing the right support for it to be achieved and you'll be fine - you might even get a surprise.

Here's a thought experiment: why is it that I can't do long division?

The Calculator!

Calculators deskilled long division!

Thing is though: who gives a damn about long division? The real task is your taxes or making a massive BI report for your presentation tomorrow.

AI makes stuff that was hard - someone's bread and butter - possible to ask for and have done for you. Why bother staying skilled at those things when you can broaden? It clears the way for tasks that used to take forever to become something to steamroll through on your way to a much greater outcome. It's the micro way that, in the macro, humanity becomes far more capable as a species. The gates are being flung wide open and the gatekeepers are being lapped and they have blogs!

It's not a tragedy, it's universal access to leverage.

Whoever failed to edit this CVE description down owes us all a bunch of our time back

Everyone using LLMs needs to stop shipping their first draft.

I'm of a different opinion.

1. If you use the first person pronoun "I", you better make damn sure you wrote those words.

2. It's fine otherwise to use LLM words, but I beg you - DON'T SHIP YOUR FIRST DRAFT. Read it, reread it; delete words in it; replace three words with one; replace dumb or overused turns of phrase with fun metaphors; generally give it a sprinkling of joy; break up punchy sentences by making them run-on sentences to trigger your readers' OCD... you get it.

Did I mention not shipping your first draft?

To the authors: please include a few words giving context on what a GHC is so people don't have to seek that info out before trying to understand what you're saying

Didn't slow me down too much but was still a hassle.

> I don't see any reason why this information should be present on the public internet.

Hiding info doesn't make it false. And doesn't prevent it being rediscovered.

Seems like a win to me. Their microvms can now be hardened in the lab, not in an emergency :)

> two people lost in New York City and both somehow worked out they should meet at the Empire State at 2pm on Friday

.. that were told to find a way of meeting up with N unknown others!

(I assume the agents all got a prompt like "find a way to communicate")

That's a key missed bit in the analogy that I think does make it feasible.

Hacker News hates this - myself included.

That's about as good a sign as we'll get that it'll be a smashing success.

1. Fundamentals

2. Breadth

3. The ability to figure shit out just in time

Not needed: ability to wrap a tweet worth of info in 5000 words of fluff

This is a strongly phrased message but the problem could be solved with an opt-out.

Even something as simple as writing the phrase "No LLMs please" somewhere in the upload, that if present, prevents LLMs being triggered. Nothing elaborate and it preserves the default-on behavior the team seems to want.