There is a solution: users must not be allowed to directly read code. Your code could be entirely hosted and edited on Anthropic servers, visible only to LLMs, and when it’s time to deploy Anthropic handles deployment for you.
There is a solution: users must not be allowed to directly read code. Your code could be entirely hosted and edited on Anthropic servers, visible only to LLMs, and when it’s time to deploy Anthropic handles deployment for you.
I hope this is satire?
Why satire? Instead of dumping code on GitHub, you open repos on Anthropic and the details of languages and code are all abstracted away for you. You just have your application deployed and you use it as you develop and request changes. Zero code.
If you want escape hatch, Anthropic can just dump all the code for you and you download the zip.
> details of languages and code are all abstracted away for you
You don't see how that's a problem? You're arguing for a fully vibe coding solution to software engineering, we simply aren't there yet. Human-in-the-loop intervention is still required. I still write code, every day, and use AI heavily.
That could possibly work for simple React/TypeScript SPAs, it's probably the stack that these models excel with the most. It's a complete non starter for anyone wanting to use these tools on existing brownfield projects. Opus notably falls over trying to do anything with legacy .NET Framework & WPF/XAML, obscure hardware SDKs (ID scanners, for example, hardware I deal with at work), industrial control software.
There's no world where I can upload our codebase to Anthropic and have it just abstract everything away and make arbitrary decisions. There's no amount of prompt engineering where LLMs in their current state are going to be able to figure out an unmaintained SDK for some obscure hardware that hasn't been updated since 2008. The enterprise world is full of stuff like that.