Tip: identify PRs with this problem by looking for discrepancies between the metadata (files/lines affected) for PRs via GitHub API and associated commits in the time window.
The 8% and 50% numbers are pretty concerning, but I’d add that was for the “computer use environment” which still seems to be an emerging use case. The coding environment is at a much more reassuring 0.0% (with extended thinking).
Edit: whoops, somehow missed the first half of your comment, yes you are explicitly talking about computer use
> Most (probably >99.9%) players can't do that at the first attempt
Eh, both myself and my partner did this. To be fair, we weren’t going in completely blind, and my partner hit a Legendary joker, but I think you might be slightly overstating the difficulty. I’m still impressed that Gemini did it.
After being acquired by ServiceNow in 2021 for $510M and being rebranded to ServiceNow Cloud Observability, Lightstep is now being sunsetted with minimal fanfare.
I can, I’ve written a billing system before (unfortunately). There’s a lot of annoying math/edge cases and systems to sync between.
While I never implemented a restriction like this, it would have prevented a lot of weird bugs/customer support issues and kept the underlying code much simpler.
(Annoying math = time zones, prorations, discounts, billing cycle anchors, etc. see the “falsehoods programmers believe about X” series)
(Systems to sync between = internal DBs, billing APIs, payment processors, etc.)
I mean sure, I get it, but companies like Uber leave edge cases like that out when it hurts them (customers cancelling) but move heaven & earth to remove them when it helps them (I bet its easy to re-join within 24 hours of cancelling?).
My experience from working in the security space is that all the tech is pretty un-sexy (with very good sales pitches), and none of it will save you from a nation-state attacker.
I've seen this exact UI style a dozen times now and it's always accompanied with tell-tale overly verbose, overly dramatic text.