this post was submitted on 21 Apr 2026
149 points (98.1% liked)
Technology
83966 readers
5447 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Your point is well-taken, but this is also exactly why AI reliance is dangerous. Anyone who sees this should realize the precarity of relying on products that can just be locked away from you.
Like Gmail? Google drive? Slack?
I'm not defending AI, but I can come up with >10 products that would absolutely cripple the company I work at if the provider suddenly says "Soz, terms of service violation".
Vendor reliance is dangerous. That doesn't just apply to AI. If the company in OP's message had both Claude and Gemini they'd been okay, so the problem isn't with AI explicitly - the problem is with reliance on services that are critical for workflows, and providers being able to change their mind at a moment's notice.
In any case, leaving aside where the problem is, the idea that 60 employees can't use Natural Intelligence to do their jobs means there's something really wrong with that company...
Windows 11, Onedrive, Intel Management Engine, Google accounts, ...
It's not that they can't be productive. Right now at least, what AI does is amplify how much work you can do. One of my friends codes for a big company that uses state of the art Claude models and he says that the system does 80-90% of the coding grunt work and the job is more of an editor and making sure everything is correctly annotated so that humans can understand what's happening in the code in the future. This means that work that might have taken months he can complete in a week or two.
This approach to coding is exactly what creates the problem. They will find out the hard way if they can continue to be productive when something breaks and AI is not available for whatever reason. Does anyone know how to fix it? Is the documentation sufficient to understand what the AI did?
This is how the Adeptus Mechanicus is born.
My friend said early AI iterations were really bad at being opaque and that even now if you're having it design the core architecture you're going to have the problems you mentioned. But his job has basically changed to being focused mostly on being that architect. Using the metaphor of constructing a building. He used to have to do a lot of manual labor too, not just be an architect. Now he just has to tell the AI system what to build AND how. But the majority of the actual "construction" work is done by the AI system.
To continue with the analogy though, how many architects create things that an engineer takes one look at and laughs at because it’s structurally impossible (hint: a lot). Knowing the deep parts of the code and how it works becomes even more invaluable otherwise you risk Chinese building practices (quick, looks good, falls apart quickly).
My friend is a full stack programmer with over 15 years experience with one of the largest financial institutions. So he can handle what you're talking about no problem. But what IS a huge problem is that the reason he has the requisite knowledge now is because he spent years learning best practices by doing the grunt work that's going to disappear. So in a few years they might no longer have people with the skills to do things right and then what you're describing will absolutely happen and build quality will go to hell. The assumption from big tech is by then the models will have improved enough it won't matter by then.
At least in my experience these models are pretty good now to write code based on best practices. If you ask for impractical things they will start doing ugly shortcuts or workarounds. A good eye catches these and you either rerun with a refined prompt, fix your own design or just keep telling it how you want to have it fixed.
You still gotta know how good code looks like to write it, but the models can help a lot.
This is what I'm hearing too. One thing my friend did mention was that without a nearly unlimited amount of tokens he'd run out really quickly.