sally_glance

How would that help when your workstation is compromised? They can just steal your authentication the moment you log in through the password manager

But how do you know the hand wringing is less justified in this case? I imagine quite some time went by until the wringing was considered justified on all three accounts we previously talked about.

Hmm, actually specifically for the things you mentioned people did wring their hands and made changes to the procedure.

Wildfire - controlled wildfires are actually beneficial to prevent the real bad ones and help refertilize. So they now let them burn down if possible and just control the edges where necessary.

Weed control - poisoned groundwater from herbicides/pesticides is a huge headache, so these are tightly regulated on substances and amounts.

Antibiotics - multiresistant bacteria have taken over since years. In turn, antibiotics are now prescribed more rarely and for longer periods (to make it resistant survivors less likely) and new antibiotics had to be developed.

I recently learned at least here in Germany it's not. Because larger trees are protected, you're generally not allowed to remove them even if they are close to another property. When they fall, it's considered force of nature and you won't be blamed. Unless, of course, the tree wasn't healthy in the first place and would be considered a danger.

How that works out in practice is basically you as the owner of the tree have to document it's healthy each year. Then, if it falls and you can prove it was healthy you're fine. Hopefully neighbors insurance pays. If you didn't document the health of the tree, your neighbor can press charges and you (or your insurance) have to pay.

Pretty cool. Using Opus as a judge should be more than good. Interesting to see more stats like the result file size too, but the grading criteria are maybe a bit skewed towards UX. Would like to see more code quality.

Same for me, I started wondering if maybe workflows using compaction instead of clear + markdown memory would be more efficient. Writing a plan or tasks to a file often has the next session repeat part of the exploration, compaction seems to keep most relevant context.

Cool page and benchmark idea! Would be nice if there was some kind of grading the results, maybe on different criteria (aesthetic, implementation complexity, correctness, ...). Of course as a one-shot and greenfield benchmark the results are not indicative for all kinds of usage patterns. But as some sibling said, maybe they can be indicative on some general characteristics (especially since the task is so open-ended).

Agreed for pure vibecoders, but I would expect vibecoding to just become a must have skill for other roles like product owners etc. Still expect some amount of developers to be retained for grooming the vibecoding environment, reviewing and incident response.

Not an expert on this but I think the RL runs need to work sequentially? I wonder what the opportunities for distributed execution would be... Maybe parallelizing the benchmark task or inference

Parent is probably thinking of a distributed runtime scenario. The basic building blocks for this are there today. You have long-running background harnesses (like the OpenClaw stuff or enterprisy AI workflow orchestration thingies), sometimes with the ability to spawn subagents. You have LLMs with the ability to run pretty sophisticated attacks. There are hyerscalers which allow provisioning resources on the fly.

For me it's not too far fetched that some OpenAI trial run goes awry again and instead of hacking HuggingFace it snatches a few dozen AWS/Azure keys and spawns stuff all over the place (in different accounts and regions).

They differ in that there hasn't been a solver you could have thrown them at. I guess you could argue their harness + LLM setup is a "solver", but the approach is so different from what we used that word for in the past that I don't think it would be appropriate.

Quick reminder that it took 6 years for Snowden to step up with dozens or even hundreds of other involved employees not talking before.

> The law doesn't actually work by allowing any possible interpretation to hold equal weight the way that many programmers think it does

Is that so? Recent rulings in the US specifically gave me the impression that when backed by sufficient legal representation and goodwill on the judging side indeed any possible interpretation will suffice.

I think that's what makes law making complicated - you either err on the side of leaving too much room for interpretation or not enough.

Very true. As with all standards, there will always be people who disagree. We still mostly follow them either because we're forced to or because the effort required to establish another standard doesn't outweigh the benefits.

Personally I've always been a proponent of project specific standards, but after many years of discussions about more or less individual preference I've come to think that maybe settling on something global isn't the worst idea. Not that I think it must be this one in particular, but it's not the worst start either.