Yeah, punk was a bit of a rejection of the polish of the big bands of the time. In a sense, the "horrible" was sort of the point. And for the shock value. But did that really mean they were horrible? Probably everyone kind of sucks at first. But it's hard not to improve your skills once you have got to a point where you have done a certain number of shows because you created a sustainable cash flow to support it.
And you could say similar for the transition between painting and photography.
ETA: It's interesting how the bottleneck may reveal the real skill in the thing. Architecting the code. Having a eye for interestingness in creating an image / painting of something, etc.
Is that what they're wagering on though? Everytime I open X, it's all about the first to some hand-wavy definition of AGI is going to win everything, and it's the only thing that can get us through the painful transition period from massive job loss to abundance.
One of my favorite movies as a kid was Explorers (1985) where kids built a spaceship from a Tilt-A-Whirl and other parts. It was an inspiration. Like you, I enjoy programming, but I haven't built a spaceship yet. Hehe
That movie was really incredible, right up until the part where they ran out of money making it and it took a right hand turn into being absolutely terrible.
When I was young I only saw the first half. Decades later I got to finish it ... what a letdown after all this time.
Didn't read the articles, but at least the planners know and understand a map.
SO... a map is static reference. A calculator is deterministic computation. An LLM is probabilistic generation
In high-stakes environments like military planning, tools that generate new claims rather than reference known data introduce a different class of risk.
Yes, everyone is responsible for their own decisions. But then circle back to risk. How can the planners be sure they aren't dealing with hallucinations, questionable data, differing outputs based on prompts, and a long list of other things...
> How can the planners be sure they aren't dealing with hallucinations, questionable data, differing outputs based on prompts, and a long list of other things...
I'm not sure they care nor do I know who holds stealth bombers accountable. We're back in the might makes right world.
That should be fine, because it's still using their tooling. And this seems like the better way to go. I have a couple of tools that work like this. I think the issue is mostly 3rd party harnesses that seek to do the same as Claude Code. And it seems reasonable that Anthropic decides how you can use the subscription, because it's heavily subsidized. Get a Claude $200 sub and max out the usage limits, then compare that usage to the cost of using their API. The difference is significant, which is why people are getting multiple $200 subs rather than paying for API usage (and I have seen reports where they are cracking down on this as well.)
Okay, I was mistaken. The tooling I was speaking of uses Claude Code rather than the SDK. One uses the Zed ACP protocol. I'm not sure about the other. I should have said Claude Code rather than the SDK. For example, I can run a session through one of the tools, and then access that session directly in Claude Code. It's still Claude though. It seems the important element is that you're not using OAuth tokens from a sub to use in a different tool. If you go through Claude Code, then Claude Code is handling everything and giving your tool the output. Thanks for the correction.
I would argue the chips don't even matter (important, but not as a reason for defending Taiwan.) It's a strategically important location that is a stone's throw from Japanese islands. If Japan feels the need, then nukes may be on the table. If that were to happen, S. Korea may not be far behind. And the cycle spirals.
Yes that is correct. However, I think embedding bubblewrap in the binary is risky design for the end user.
They are giving users a convenience function for restricting the Claude instance’s access rights from within a session.
Thats helpful if you trust the client, but what if there is a bug in how the client invokes the bubblewrap container? You wouldn’t have this risk if they drove you to invoke Claude with bubblewrap.
Additionally, the pattern using bubblewrap in front of Claude can be exactly duplicated and applied to other coding agents- so you get consistency in access controls for all agents.
I hope the desirability of this having consistent access controls across all agents is shared by others. You don’t get that property if you use Claude’s embedded control. There will always be an asterisk about whether your opinion and theirs will be similar with respect to implementation of controls.
reply