I mean it will be the employers of those programmers and at $5000/dev/month I expect a businesses will start demanding very tangible returns from this spend. And as much as I love the tools I don't think it's generating that much direct business value. It's very obviously not turning $140k devs into $200k devs.

Gotta be honest, when I go to an encyclopedia the last thing I want is what the mathematically average chronically online person knows and thinks about a topic. Because common misconceptions and the "facts" you see parroted on online forums on all sorts of niche topics look just like consensus but ya know… wrong.

I would rather have an actual audio engineer's take than than the opinion of an amalgamation of hifi forums' talking pseudoscience and the latter is way more numerous in the training.

> what the mathematically average chronically online person knows and thinks about a topic

Yes you do, often. Understanding ideas and consensus is part of understanding "topics". To choose a Godwinized existence proof: an LLM that didn't understand public opinion in, say, 1920's Germany is one that can't answer the question of how the war started.

You're making two mistakes here: one is that you're assuming that "facts" exist as a separate idea from "discourse". And the second is that you appear to think LLMs merely "average" the stuff they read instead of absorbing controversies and discourse on their own terms. The first I can't really help you with, but the second you can disabuse yourself of on your own just by pulling up a GPT chat and talking to it.

That's actually pretty smart to address reports in batches to find the intersection of sites users routinely encounter and sites that are AI slop instead of trying to address reports individually as they come in.

Yeah but it's february.

Meanwhile I'm considered a high performer at my company and I've been pushing for years to get our company to adopt flat percentage raises and flat dollar amount bonuses very literally against my own financial interest.

My company not only gives percentage based bonuses but gives a higher percentage to higher salary earners. It pisses me off every year that the people who would be most positively affected by the extra money get less. But worse with the "performance" based raises where they have a fixed number of annual raise percentages means the unlucky sods who have shitty managers get less than inflation every year while I get higher every year.

The lesson here is to write code that's easy to throw away. The main problem here is commitment where it becomes too hard to change some fundamental aspects of your system. This time it leads to building an ad-hoc database, but another time it will be committing to a huge over engineered architecture because we might need it later. Both cases are caused by unnecessary coupling making it impossible to untangle.

Take your best guess at what you will need later, but know you're guaranteed to be wrong because different products have different needs at different times and code for the future version of you that has to rewrite your persistence later.

There is a balance to be struck to avoid a completely ineffectual congress but I'm not sure a legislative body biased towards action is one you would actually want. Making it easier to kill bills than pass them has a natural stabilizing effect which I think is a net good for the country.

Sure but the original rules largely accommodate that. Anything that can get 60 Votes in the senate should pass.

When everything is magic I think we need a new definition of magic or maybe a new term to encapsulate what's being described here.

The key feature of magic is that it breaks the normal rules of the universe as you're meant to understand it. Encapsulation or abstraction therefore isn't, on its own, magical. Magic variables are magic because they break the rules of how variables normally work. Functional components/hooks are magic because they're a freaky DSL written in JS syntax where your code makes absolutely no sense taken as regular JS. Type hint and doctype based programming in Python is super magical because type hints aren't supposed to affect behavior.

Does the existence of did:web make it decentralized? You don't have to use the centralized identity provider at all. And if you own a domain why would you?

In theory, yes. In practice, not really, since the vast majority of users won't care to do it.

Most people don't own a domain to do it with, but I think the custodial/management of that is the one place Bluesky has had some revenues.

I don't understand why this is grey, this is exactly correct. Depreciation is good actually ignores the realities of why a car's value is tanking in the first place. The only time high depreciation is good for you as a buyer is if you think the market is mispricing cars and they're actually far more valuable than the cost they're being sold for. But best keep that secret because the market will be quick to correct once it's discovered.

I mean there is some wisdom to that, most teams separate dev and qa and writers aren't their own editors precisely because it's hard for the author of a thing to spot their own mistakes.

When you merge them into one it's usually a cost saving measure accepting that quality control will take a hit.