i noticed that more and more people write like this. no capital letters, no period at the end of a line. it saves typing, and it removes noise when eyes parse the text, so i gave it a name: leancase then i made the rules exact. links, mentions, hashtags, and code keep their case, because changing them can break them. an ellipsis stays... converting leancase text again changes nothing, so leancase is a normal form. evolu now has a function that converts text to it and a type that validates it. property tests found a bug the examples missed, and a proof in lean would make it certain is this a joke? half a joke, half serious the rules, the edge cases, and a converter you can try: evolu.dev/blog/leancase

the real reason maintainers are disabling PR from external contributors is that they don't need them anymore also because they're totally overwhelmed with their own bug reports and feature requests contributors are just the first thing devs won't need anymore

writing code is dead, long live reading tests, er, learning formal verification then formalizing all the things

AI is nerd-sniping the world. Some say "AI is eating software," a nod to "software is eating the world," but that's too shallow. AI is software too, and while it's eating software, it's also producing new software in unprecedented quantity and quality. That has a nice side effect: it separates the wheat from the chaff. That's why, as someone wrote, everything is fake now, yet genuine things are growing more than ever. For developers, this means they have to learn completely new skills or they'll lose their jobs. But it definitely doesn't mean there will be less work, because humanity now has an invention that can make the whole world vastly better, and there's a hell of a lot to improve. And it's not just about developers, it's about everyone, which brings me back to the title. So for me, it's absolutely great.

What I really don't understand is why most runtime validation libraries don't have typed errors. Zod 4 returns a ZodError (an Error instance) whose issues are one generic union for all schemas, each with a pre-built message string. Effect Schema 4 fails with SchemaError (also an Error) wrapping issue objects that hold schema AST nodes. Valibot comes closest: its issues are plain objects typed per schema, but each one still carries a pre-built message. In Evolu Type, an error is just data: { type: "Int", value: 37.5 }. You can switch on it, store it, send it across a worker, and format it later, in any language. A missing translation is a compile error.