Just reviewing the code

I was warming up to this. It certainly is better than vibe coding, but I’ve started to see libraries [with this ai policy] push out bigger releases faster with bad ergonomics and unnecessary, undocumented breaking changes, because the ai quietly migrated the internal tests/examples.

Clearly, they’re reviewing large amounts with an eye on new features and they’re not thinking through ergonomics: spending time with it, writing it themselves, and seeing where the sticking points are.

Maybe if you’re using ai for the migration, then-- problem avoided, for now. As time goes on I could see it compounding and becoming a tangled mess that’s not only inaccessible to humans, but requires more and more compute to navigate than thoughtful, handcrafted code.

Dang. Their online filter bubble must be strong. Likely the kind of person who also doesn’t care about surveillance capitalism because “it’ll recommend good things to buy.”

You’d be surprised. Data centers seem like a big issue. My boomer parents hate data centers, as do a lot of rural voters who have them nearby or proposals nearby. But to your point, I also see a lot of people who are aware of problems around ai/data centers/billionaires still using ai.

For those not in NJ trying to avoid this, pay in cash and punch in a random phone number at the register.

You may need to try a few numbers at self-checkout to find a working one, but it’s surprisingly easy. Rotate the numbers to dirty up the data of these parasites.