When I needed to get my newborn daughter's social security card I went to the local SS office, only to be turned away because I did not have an appointment. So I went home, finally got an appointment after an hour on the phone, trying to explain why I didn't have her SS card (apparently "it never arrived" did not compute), went back the next day with my passport card to provide as proof of identity. Only for them to say "we don't accept passport cards as ID. We can use your license though!"
> the US government is too corrupt and intentionally ossified to react
The trump administration is not too ossified to react, it's in full support of. It dropped two investigations into polymarket mid-2025, and polymarket is crypto-adjacent, a field which the trump family takes full advantage of.
> Obviously this is a horrible use case, and I'm not sure if such websites actually exist or are just rumors.
polymarket has an @died tag, which I assume is for betting on people's deaths (I never used the site, and it's currently inaccessible) given apparently someone recently made half a mil betting on Khamenei's death, and a cool billion was traded on bets on the timing of the bombing of iran https://www.npr.org/2026/03/01/nx-s1-5731568/polymarket-trad...
It's also fundamentally something you can't really do properly in crypto. You need a central authority to decide if "thing has happened". There's no way to properly incentivize accuracy in cases where the majority of stake benefits from an inaccuracy.
> Facebook's coding AIs to the rescue, maybe? I wonder how good all these "agentic" AIs are at dreaded refactoring jobs like these.
No.
This is something you shouldn't allow coding agents anywhere near, unless you have expert-level understanding required to maintain the project like the previous authors have done without an AI for years.
I've done some work in this sort of area before, though not literally on a malloc. Yes you very much want to be careful, but ultimately it's the tests that give you confidence. Pound the heck out of it in multithreaded contexts and test for consistency.
AI is more than happy to declare the test wrong and “fix it” if you’re not careful. And the cherry on top is that sometimes the test could be wrong or need updating due to changed behavior. So…
> ...but ultimately it's the tests that give you confidence. Pound the heck out of it in multithreaded contexts and test for consistency.
I don't think so.
Even on LLM generated code, it is still not enough and you cannot trust it. They can pass the tests and still cause a regression and the code will look seemingly correct, for example in this case study [0].
Years ago I made harissa out of peppers for sauce for baked chicken wings. To my surprise it tasted tomato-ey.
After doing some Google searches I realized the plants were related and eventually it sort of made sense. Peppers are almost like a very dry, very firm tomato.
In hindsight it's obvious but at the time it was very surprising.
but for some reason my fealty to potato does not extend to tomatoes and eggplant quite the same way. i feel toward potatoes sort of how gary Larson feels about cows
Grifting is about as American as apple pie honestly. Melville is of course know for Moby Dick where he delves into the psyche of the Great American Man but he also wrote The Confidence Man. Mark Twain’s work is full of con men and grifters. Ponzi laid the groundwork for more complex schemes in the 20s. Pyramid schemes were all the rage in the 40/50s, Tupperware parties as an example, and of course still are huge today.
It seems like whenever American society is changing very rapidly or has changed very rapidly con men become the powerful ones of the time. Maybe this is true everywhere but as an American I don’t know the history of cons in other countries.
I personally don’t care for rebasing in magit (I actually find it confusing when hitting conflicts).
My primary reason for using it is reviewing and staging commits. The non-linear staging with line granularity (which also lets you revert changes at the same time) is so, so very good when you care about crafting commits.
> I remember these Macbooks did tend to break apart at the corners of the palmrests.
Not the corners for me, but the "feet" of the topcase digging into the palmrest, which would splinter the plastic, then you'd have holes in the case and jagged plastic splinters digging into your wrist as you typed, not enjoyable.
Shame because it was the last macbook that was really easy to upgrade: the battery was removable (with a simple lock), and behind it were the RAM and 2.5" drive slots.
The next generation was not that hard but you had to unscrew the entire bottom shell, and the battery was glued.
Unscrewing the bottom on the generations after this gave you access to nearly everything. Which was vastly superior for most repairs. Getting to the logic board or AirPort card on the polycarbonate MacBook took significantly longer. For the Bluetooth motherboard you had to remove the display cable, optical drive and HDD.
Mine had been upgraded from 4GB of RAM to 8GB, and I replaced the HDD with an SSD, and replaced the DVD drive with the original HDD for more storage. Was a nice machine for uni, I really loved it.
You can experience something like that by using plugins which simulate CVD / color blindnesses.
reply