Comment Re: AI break down (Score 3, Insightful) 138
Comment Re: Big AI's business scheme (Score 1) 38
Comment Re: idk if this makes me impressed with the agent (Score 2) 81
Comment Re: No Free Speech in France (Score 3, Insightful) 19
Comment Re: Disingenuous (Score 1) 70
Comment Re: No this is not possible (Score 4, Interesting) 50
Comment Re: Leave Meta alone or face embargoes on all trad (Score 2) 111
Comment Re: Bull Hockey (Score 1) 81
They're changing their tune because AI is not showing productivity gains. I've seen this first-hand. Every major tech company dove headfirst into AI, and the work being produced went up. But it's the wrong kind of work. It's not revenue producing work.
The reason is simple: The time it takes for humans to review *new* work is often similar to the time it takes to create new work in the first place. So every engineer eventually comes to the conclusion that they'll send agents to do code-cleanup type tasks in parallel with the actual work, because it's easier to review and validate that. The result is they're now splitting their time on the real work and the tasks they added to keep the agents busy to increase productivity. So on aggregate people are "more productive", but moving slower on real work, only now with high token costs.
The answer of course is "more AI", which means AI code reviews, but nobody is comfortable with the inmates running the prison yet, or the increasing token costs that are being paid to frenemies. So effectively there needs to be a generational leap in capability and an overall reduction in token cost before AI coding productivity gains are realized, but right now capability has plateaued and costs are going up.
Comment Re: OK, lets bet on how long till it is unsafe! (Score 1) 85
Comment Re: Anthropics "safe" model refused debugging (Score 1) 85
Comment Re: Sell it for $350... (Score 1) 89
Comment Re: Just Add Security (Score 2) 24
Security isn't something you bolt on after the fact, but a new tool could significantly upend what it is you need to secure against. I suspect that's the real issue here.
My experience of Opus is that it's shockingly capable of tearing apart software binaries. I drop a path to a binary in Claude Code and ask it to tell me how a feature works, and it will usually give me a complete breakdown of classes and functions and how they work together. The binary loader information, symbol data, assembly, etc. are all just another language to Claude, so it really doesn't care. It's not hard to imagine a model trained on and geared toward binary data could seriously undermine how "secrets" are hidden in software.. "Hey Claude, could give me the API keys and explain how transactions are signed for this app?"
Comment Re: Betteridge's Law of Headlines (Score 1) 79
Comment Re: 25,000 lines of code (Score 1) 78
As far as I've seen, the AI fanatic's answer is "don't care about the code".
I'm not an AI fanatic, I work for a major tech company and have been forced into being "AI Native" to keep my job. I *like* writing the code, and often disagree with how CC does it, but "don't care about the code" is pretty much right and not a fanatic's point of view.
All of these arguments already happened when "high-level" languages like C first appeared. "How can I trust the assembly produced by the compiler?" "I can do register optimization better!" "If I don't practice managing operands on the fpu stack I'll lose that skill!"
English is just the next high-level programming language. If you don't like the code being produced, write a skill or update your personal context.md to explain why. Ask CC to do code reviews that catch and fix the bad patterns.
Maybe not today, but ultimately saying "I need to always read every line" is going to turn out like trying to verify the assembly produced by compilers.