Badabinski

Nah, it’s really not necessary. I’m senior dev at a large software company you’ve absolutely heard of and I’m just as productive as my colleagues who use LLMs. My tasks usually take fewer PRs as well, since there are fewer bugs that need to be fixed.

I still don’t understand why people are foaming at the mouth about LLMs. They’re fucking awful at writing software.

Metro 2033 is so good, you’re gonna love it. He wrote such a fever dream of a novel.

Security Council.

The segmented caching request thing is… weird. I worked for a company that developed a caching proxy and it very much did not work that way. Like, random access in a caching system is usually kinda bad and you should try to avoid it. Like, our proxy manually controlled the disk (it wasn’t a mounted filesystem) so it could constantly sweep the head across the disk and cue up reads and writes optimally. This gets much harder when things are fragmented as fuck.

If the concern was about what would happen with multiple connections for the same cache miss, then the caching proxy should just combine the client-side connections into a single upstream one. You can still cache the first part of the response if your upstream connection gets terminated and then restart it from that point.

I don’t know why, but 🫩 has been bugging the shit out of me recently. There’s something about the way it’s used that really irritates me.

Where’s the CVE? Was there an attempt at responsible disclosure? Was confidentiality breached? Did they coordinate this release with the devs like the dirtyfrag people did? This “announcement” doesn’t answer any of these questions and I am frustrated by it.

EDIT: Ok, there IS a CVE: https://security-tracker.debian.org/tracker/CVE-2026-46300

yeah, like, supposedly it can be hard to use GPL with some rust dependencies, but the MPL is right there as a decent compromise.