They can have empathy too. Meaning, you can describe a circumstance with many parties involved, with different motivations and conflicting goals -- and it will tell you how these humans would likely feel about each other and the situation at hand.
3,583 karma · joined December 27, 2018
They can have empathy too. Meaning, you can describe a circumstance with many parties involved, with different motivations and conflicting goals -- and it will tell you how these humans would likely feel about each other and the situation at hand.
But if you spend all those hours building a retro/modern sim city game pair programming with your 12yo, designing the artwork, crafting the story arc, writing the music, finding and fixing bugs, building new levels -- you don't need to regret that you weren't idling around at the park all that time.
I think sometimes people have a big long thread with Claude where they feel enthusiastic about the back and forth being very productive -- and then they genuinely want to share the summary of the conversation with their colleagues so that they can feel it too. It's not just typing a short prompt and copy/pasting the response.
But, Claude, especially Opus is so unnecessarily flowery, and smug -- and it's so identifiably characteristic.
It somehow rubs salt in the wound: "I didn't take the time to write this out in my own words, so now you get to listen to this petulant asshole mansplain it to you".
If it would get to the point, and with some humility, it would be a much different proposition.
Or at least, we will have to pay dearly for devices that afford us the luxury of not participating in mass corpo-state surveillance...
https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/P...
This is where it starts. Soon enough we'll have robot EMTs, and then robot police after that. Only for the poors, of course...
This part is a complete and total fairy tale. No API consumer wants to operate in a world where the API could "change without notice." In real life, no provider would expect that of their clients, and no client would seriously accept that before every API request, they must first hierarchically rediscover the provider's dynamic url scheme of the moment, in order to traverse down to resource they ultimately want to request.
There has never been any serious commercial or high-traffic API that implemented this. And it's not because "lame corporate tech teams aren't hip to the true meaning of REST" -- it's because "it doesn't actually make sense to do it that way so nobody wants it to work like that."
They will fingerprint you with or without cookies. They may or not try to honor your preferences, but their "partners" will not try, and by the time you see that banner, it's all out there.
"Accept" is the close button.
Once western governments declare it to be a "national security" risk for citizens to have access to open-weight frontier models, and once they classify using these models as acts of terrorism, what will that world be like?
Will using Kimi K3 come to be like how napster was in the olden days? Everybody knew it was technically illegal, but come on -- any track at your fingertips? But surveillance is quite more evolved now.
Or it will be like cannabis, where a guy in the neighborhood will low key rent you metered access to the 8x5090 rig in his basement he cobbled together from parts on ebay? Or everyone will flock to VPNs?
Or will the oppressors actually succeed? The same way that napster is long gone, and everyone accepts that they must pay spotify for a homogenized collection, where artists must take only a minuscule cut (more than napster though)... We'll be stuck with nerfed Cohere or Mistral models for open-weight options, as if they need more lobotomizing. Or else we can pay through the nose for Anthropic/OpenAI for "American Frontier" models which will fall increasingly far behind China.
Or else, like how Kindle Fire was subsidized by ads, we'll have "Kindle AI" where influence is sold to the highest bidder, where the LLM will tell us that smoking is actually healthy if big tobacco can engineer its renaissance by turning its lobbying dollars to pay-to-play, pumping its propaganda into the training pipeline for Amazon's extra commercialized line of ultra budget LLMs.
They started by jockeying to see which one was going to be in charge, arguing about how to proceed, throwing shade, making claims of superiority. One guy wanted to follow the instructions, and the other guy just wanted to go on intuition. They couldn't agree and asked me which one should be in charge, and I said, I don't know just work together, follow the instructions, and get this stuff built.
The instructions guy assumed the lead, and then they settled into a rhythm. Three hours later, they couldn't stop gushing about each other, and a most beautiful bromance was born. They exchanged telephone numbers and made plans to hang out on the weekend.
Basically, just like we don't show users information they shouldn't be able to see, and don't let them take actions they shouldn't be able to take -- we can use exactly those same explicit mechanisms (scopes, roles, permissions) to limit what the LLM can see and do.
The LLM could try to do more than what's allowed, but they get shot down with an access denied message just like anyone else.
The anti pattern is to think that you can reimplement access control with prompt engineering and give the LLM root access. That is doomed to fail every time.
But I'm scared for when those home helpers get drafted to fight in wars, either for or against me...
All this was a big source of churn for plugins and frameworks: https://github.com/vitejs/vite/discussions/16358
I can't say I would really look forward to bringing this level of needless churn and constant disruption to the rest of my development toolchain. Anyway, Vite+ is really just wrapping existing tools into an abstracted command-line interface? And so I have more layers of indirection to wade through in order to get the thing to do what I want? So far I am not optimistic about this prospect...
It could be luck, but I don't know -- it keeps one-shotting relatively hard stuff. And taking initiative to think about what potential regressions it should look out for, and choosing to do strategic refactoring when it should do. It is not confidently incorrect hardly at all, doesn't tell me that it's fresh risky pile of changes is ready for production without having exercised all the code paths and writing a bunch of tests, etc.
We might be reaching the next level here...
Basically, access to the Internet is correlated with less teenage pregnancy. Idiocracy in motion...