I buy rice from an online store that carries speciality Japanese varieties. The rice is very good.
But this year they replaced their previously obviously-English-as-second-language-but-informative descriptions with just total slop that say absolutely nothing at all about the rice you’re buying. Every description is just platitudes about how good the rice is.
So as in TFA we get people who seemingly can’t resist “pressing the button” and getting nice shiny results even if they aren’t, like, good. It’s nuts. FWIW I emailed the rice shop and politely asked them to revert to the old descriptions but received no reply.
That auditors are responsible for catching the lies of an audited company on penalty of being suspended is a position that the big audit firms would not agree with. They might agree that they are responsible for ensuring the material accuracy of accounts if fraud occurs, but even here EY has disclaimed responsibility if the fraud were sufficiently complex [0]. Indeed auditors lobbied very hard against being mandated with a broader anti-fraud role [1].
Admittedly this is on the "real" audit side and not the advisory/consulting side, which would be the ones to handle SOC I imagine, but nonetheless a position I find a bit absurd.
The page appears to be dark themed even without dark mode enabled; if I use Noir to force-add dark mode, then the diagrams indeed become difficult to read but this seems like a Noir issue more than a site issue
Atkinson Hyperlegible is an incredible font family! I read much faster and strain much less when I use it. The Braille Institute licenses it under SIL and includes the Glyphs 3 source files used to build it with the download too which is very cool.
I do not think that it is as well-reasoned as that. Far more likely IMO that teams are being evaluated on upsell uptake and so push these requirements to make the number on the dashboard go up.
Anyway, I’d be more sympathetic to this way of thinking if windows wasn’t getting worse over time. But it seems like investment in the OS is being disfavored for investment in AI-in-things-no-one-wants-AI-in, which is inverse of the subsidy direction you propose
I don’t think I have ever seen ∋ used to mean “such that” so I was very confused until I got to the explanation (as it were; why CONTAINS AS MEMBER is being used to mean “such that” is never explained).
I have a TS3+ that broke about 18 months in. I talked to support, set up a repair, and before I could send it the dock unbroke and had worked since. Truly mysterious and left me with a sense of unease with that thing given the cost.
> Not a product launch. Not a keynote. Not a revenue metric. The thing he was most proud of in four years at one of the biggest companies on …
What’s tiresome about this is that people don’t even bother to edit it. I use LLMs to draft long-form text all the time because I think the hardest part is getting something on the page to refine. But I would be embarrassed to leave LLM tells like this in the final result, if only because I want people to know that I actually cared about what I’m asking them to read and that I value their time.
It’s especially ironic here because this is about lauding a person who cut through the impersonal behavior of a large organization. Evidently this person was not worth even an editorial pass over the article though.
It’s your last point that keeps me up at night. I opt out of letting my data be used for training (and don’t use tools like Gemini that make this very difficult or impossible).
But I have very little reason to trust that they actually don’t use my data. The incentives to violate the data controls are so great with the billions sloshing around AI companies. The worst that would happen if they are found to be abusing my data would be civil penalties (i.e. fines) that I’m sure executives would see as the cost of doing business.
Ideally there would be an attested zero data retention option, but I’m sure that’s not available.
Really love this article. Opens with the problem statement and jumps straight into the investigation. Thanks for a very enjoyable read (and an rss feed!)
This is the kind of assertion without evidence that just muddies the waters. “All kinds” of people is so vague as to be an almost entirely vacuous category and “routine” means almost nothing without an actual quantification of how prevalent and frequent the problem is.
It’s undeniable that the proverbial guns for hire make it easy (if not cheap) to target basically anyone — but just because the vibes are bad doesn’t mean we can just say “it’s common knowledge that …”
The fact is mitigations are costly in terms of convenience and ease of use. Helping people make informed choices about whether to enable mitigations and bear that cost requires more than platitudes imo
Mac prices on eBay are sort of bizarre. Back when I was looking (when you could still purchase a new one in a reasonable timeframe) many of the higher end listings cost as much or more (!) then just getting them from Apple. I ended up buying an Apple certified refurbished Mac Studio for less than the comparable eBay listing.
Not sure who’s buying these or if it’s just people dreaming about finding a rube.
I'm beating a dead horse here but the challenge is a11y. Chromium wrappers get a11y for free; bespoke UI frameworks must implement accesskit (or something) which is a lot of work and something that (imo sadly) many small teams decide is not worth the investment.
I took a look at gpui-component a while ago when assessing GPUI for a project I was working on. IANAL but was dissuaded because it's almost certainly not compliant with the Zed license--gpui-component "borrows" gpui code patterns lifted straight from the main zed repo, which therefore must be AGPL/GPL (unlike the gpui-only which is Apache IIRC). Caveat emptor (caveat user?).
The existence of a soundness bug in the typechecker doesn’t refute the value of soundness as a language design contract.
If anything it’s the opposite: issues demonstrated by cve-rs are _language bugs_ and are _fixable_ in principle. “Safe Rust should be memory-safe” is a well-defined, falsifiable contract that the compiler can be measured against. Meanwhile memory unsafety is a feature of the semantics of C++ and so it would be absurd to file a bug against gcc complaining that it compiled your faulty code.
But this year they replaced their previously obviously-English-as-second-language-but-informative descriptions with just total slop that say absolutely nothing at all about the rice you’re buying. Every description is just platitudes about how good the rice is.
So as in TFA we get people who seemingly can’t resist “pressing the button” and getting nice shiny results even if they aren’t, like, good. It’s nuts. FWIW I emailed the rice shop and politely asked them to revert to the old descriptions but received no reply.