migrations (e.g. replacing one service with a new one, or switching database engines, or whatever) are part and parcel of software engineering and are a skill that you should invest in and get good at, not avoid or treat as special one-offs.
Honored to be speaking at the 2026 Innovations in Psychotherapy Conference (Nov 10–13 in Anaheim & Online)! Join us for evidence-based education & practical strategies to enhance your practice. Use code SPEAK26 to save $50:
I've said like the licensable engine thing kind of was our AI transition already unfortunately and uh I regret to inform you that the news is not probably that positive.
Technologies from our community - CRDTs, sync engines, universal version control, and good old-fashioned open protocols and file formats - can give a nation more independence and control over its own critical software infrastructure.
Software is kind of unique in having the third kind of the practitioner conference where we are just meeting to get better at what we do. We also are really the only kind to really focus heavily on like open source in making our knowledge freely available.
And I believe the best product CEOs are in the minutia of the details. you know, all the stories about Steve Jobs. I was so impressed when I heard that he insisted on picking out the carpeting in the conference rooms, you know, and and I tried to have that same mentality of micromanaging the really small pixel level details that matter.
So I'm looking at this like guys the fundamentals of this isn't like everything is going to change because of MCP. What the hell? A whole conference guys? This is just API design.
Honestly, if the team doesn't sign off on it, it doesn't happen. I mean if something is really contentious contentious or really big it will probably end up being discussed at a conference for example.
Often people in industry I feel like sort of have short circuit reasoning. Like don't maybe don't quite reason something through from first principles but just like oh I heard this from a conference talk I'm just going to go with that
I gave pi a skill for using the search engine SearXNG (which aggregates many search engines together at the same time), and one for calling into a daemon that I wrote that gives it access to read my email and Signal messages, and send-to-self, and send to others only with human confirmation.
The deal was always simple: search engines had permission to crawl sites because they were going to be sending users to those sites. If they're hitting your site half a million times for every one user they send to your site, all they're giving you is higher costs.
The right way to incubate a video game is you have the smallest group possible and you try to get the idea across with whatever technology you can get your hands on, using other engines, using art from whatever. You prove out that idea, and once you know what you’re doing, then you expand the team.
And when I say that, as I have said on a number of occasions, that it had technology equivalent to ours in the 18th century, I’m referring specifically to the ability to calculate longitude. I’m not saying that they were building steam engines. I don’t see any evidence for that.
It's really a self-perpetuating board that effectively elects its own members. Once the balance tips, politically, one way or another, it can be kept that way forever. There's no kind of rebalancing system.
It just predicts what you are likely to re-Tweet and like, and linger on. That’s what all these algorithms do. It’s what Tik-Tok does, it’s what all these recommendation engines do. And it turns out that the thing that you are most likely to interact with is outrage. And that’s a quirk of the human condition.
the electric technology used for cars only has to beat energy hogs that are below 10% in efficiency, our everyday car. But to qualify for aircraft use, the technology has to equal or beat what is used today, which is at the 30% to 40% efficiency level using modern turboprop or turbofan engines.
A korrent is a belief a person has stated in their own words: one
sentence stating the claim, backed by a quote and a source, kept at
korrents.com.
Under a name here, the quoted block is what they actually said.
The korrent beneath it is the claim those words support, in
korrents' wording — tap it to see the record, its source, and who
else holds it.
Nobody here wrote their own korrents. They are compiled from public
statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they
do, this site shows a machine translation beneath the post, in
this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the
serif above is exactly what the person published, and it is what to
quote them on. A translation can be wrong in ways that matter,
especially about tone.
Only the post's own words are translated. A quoted post, a linked
article and a belief on korrents.com
are left in their original language.