Sure, we're all more productive now, but how much of that is because we leverage AI on top of the intelligence we gained from all of that manual work? Who is to say that in 36 months you're not a worse developer over all because that systems knowledge starts to atrophy too?
This isn't me saying you shouldn't use AI. I use it all of the time to do useful side tasks like to setup GitHub Workflows while I write a feature, or with my agent on a VPS to do internet tasks for me. It's nice to have a little synthesized intelligence.
What isn't nice is to supplement your own intelligence. I think the gains are in the work there--similar to how you can be absolutely ripped from taking steroids while destroying your body. Often it's the shortcuts that are the most treacherous path.
Does handing off that sort of work to people also ruin your skills in the same way? Or are AIs fundamentally different, and if so, why? Because we have no moral or social pressure to not delegate everything?
It is quite extraordinary and breath-taking at times to see the agents in action; the flipside is that very power renders us both vulnerable to its seduction and enfeeblement on an equal scope - its almost hard-drug like in its potential long-term psychological effects.
So, yes, I do feel like I've lost some of that very low-level skill. But maybe I've also been able to spend more time on a higher level skill? Maybe the doctors got worse with the images but had more cognitive resources to think about the patient's context?
Not sure.
But yes, I can't physically get myself to write code without an AI anymore. It feels so much slower, almost painful.
Instead, they act more like highly technical product managers. They help VPs plan and write high-level product requirements sprinkled with technical terms. They draw boxes on whiteboards and create pretty slides. They write polished documents that keep their leadership happy, and they are either in meetings or on their way to the next one. When they have a technical idea, they dispatch a team to test it out.
Naturally, they still feel deeply technical, until the day they have to resolve a production issue, pass a technical interview, or write extensive code. That is when they realize their skills have grown rusty.
I point this out not to criticize, but to highlight a genuine career challenge. As an engineer, I would rather hone my technical skills. Yet, if you want to climb the corporate ladder, you have to take on more organizational work. The only solution I can think of is to become more like a researcher or a professor. Over the years, good professors spend less time writing papers or deriving formulas. However, their insights are so deep that they still produce amazing results by advising PhD students. But that path is much easier said than done.
What we gain though is for people don’t possess that knowledge in the first place, now have this superpower. I know several individuals who have vast experience in specific disciplines and they are now able to solve real problems where there were previously struggling and having to make existing solutions work.
In the context of software engineering it allows people that have great institutional knowledge bypass the software market and construct stuff on their own - or at least prototype something and turn it over to an SE if the situation dictates.
I’ve been using CC for several months now and have noticed an increasing quality of output - Fable 5 I think was 85% there. At 95% SE’s are going to be increasingly looking for work to do.
To the title though, I’ve noticed while my desire to actually write code is decreasing CC is forcing me to improve my high level thought processes in the context of overarching goals in a project through discussion with CC. The software often introduces things that had escaped me or just think more outside the box.
My concerns are that this technology will be restricted at some point and the people making the restrictions will have a lot of control - and we know how that works out. But I believe they are inevitable, first obvious example being Fable 5. Are guardrails needed - yeah sure. Common sense says that I don’t want someone able to concoct an easily transmittable Ebola virus that has a 90 day incubation period in their kitchen but I do want an entrepreneur to be able to build a competitor to MS Office, or a cure for Ebola, for example.
I am using LLMs quite a lot, but the amount of time I spend sitting on some slopped out code is I think on average much longer than a lot of my peers. What I've found is that while the original thing "works", it usually winds up being another 2-3 cycles of iterating on the original idea after I've let it settle in my head before I actually feel confident about merging.
As a result, when I add it all up, for actual "this is important" design-level concerns, I do not feel significantly more productive.
100 years from now people will wonder at how anybody did anything manually writing all their code, but at the same time will have their mind boggled that a game like Roller Coaster Tycoon is possible without 1024 CPU cores running a few terabytes of memory in order to control every single person walking around the park.
I'm not sure if we'll become less intelligent. I think our sacks of neurons are gonna keep on making associations, just across a different set of topics.
I'm probably losing some coding skills, but replacing them with different ones, and honing some others.
I used to manage dev teams of 20+ people inside high pressure, high stakes projects.
I've been coding all my adult life, on big things and small.
To me, agentic engineering is a deja vue of managing teams, except in real time.
One example is I got it to setup a new terminal (wezterm) and configure it quickly to my liking. This would have been a lot of googling and reading before, generally too much time for me to invest.
I don't think it's valuable knowledge for me to have apart from a high level to evaluate the possibilities.
Autocomplete of entire functions and methods. Nice, but also really boring. Takes the fun out it. It's all about fixing sup-par code now, a line here or there.
It's just boring. I tried writing some code by hand today after a few months hardly thinking about things and it was really hard to do even the simplest stuff.
However, I cannot build a good mental model of a software component that I didn't write myself, and that can affect future maintenance if that component is not properly decoupled from the rest of the system.
Losing a specific skill to automation isn't necessarily a bad thing. Losing the ability to learn things would be however, and that would be my fear with AI, but I'm not sure it's well-founded. Humans learn naturally by interacting with the world.
> To investigate whether skills are being lost in the field of computer science, researchers at the AI firm Anthropic in San Francisco, California, designed a randomized controlled trial in which 52 software engineers were asked to perform a basic coding task
That's this study here: https://arxiv.org/abs/2601.20245 - also written about on the Anthropic research site here: https://www.anthropic.com/research/AI-assistance-coding-skil...
There's no way this isn't happening with other skills. No goddamned way. Anyone who tells you otherwise is grifting.
> Afterwards, all of the software engineers were asked to complete a quiz about what they had learnt from the task. The participants who had used an AI assistant did significantly worse on the quiz than those who hadn’t: the average score was 50% in the AI group versus 67% in the non-AI group.
This doesn't strike me as a great test? Most engineers aren't going to learn anything from a basic coding task anyway, so I do wonder exactly what they were testing there. If it was just recall about what the issue was, then it doesn't really strike me as a problem - using AI to handle simple problems that it's clearly capable of dealing with is the right way to use it, and of course you're not going to spend time poring over the details because then you haven't saved any time by using AI.
There are other examples that don't strike me as particularly problematic, like GPS eroding people's sense of direction. It's totally reasonable to let a skill atrophy that you no longer really need because you have an ever-present tool to handle it. I'm a lot worse at doing long division than I was when I was <whatever grade one learns long division in>.
The whole skill atrophy thing seems like much less of a problem than it's made out to be. We've been letting skills atrophy for good reason long before the advent of AI. If you start at McDonald's as a fry cook and work your way up to regional manager, if you suddenly have to work a shift on the fry station you're going to be worse than you were when you were doing it all the time. MDs at investment banks almost certainly can't put together a pitch deck as well as the junior bankers who are doing that task regularly. These things are fine - part of moving up in the world and having a broader impact is being able to successfully delegate tasks, and when you delegate tasks your skill at those tasks will atrophy. No real difference whether you're delegating them to AI or not.
To be clear, there are of course cases where skill atrophy is bad. iLoveOncall posted about senior engineers in their org who have lost all of those skills and their judgment along with them. That's definitely bad! If you delegate so much that you lose the ability to even judge good work, now you can't even delegate effectively any more.
I think the real lesson with AI is that you need to be self-aware about what skills you should practice and retain vs. what skills you can let atrophy, since it's easier than ever to hand things off. I've lost most of my ability to write a SQL query, but that's fine because it was only a skill I used intermittently and AI can always do the job fine at the level of complexity I need. I have not let my skill of writing product specs atrophy (I am a PM, in case you haven't read my username), because that's critical to using AI correctly in the first place.
If social media is consuming first, or primarily consuming, anyone can scroll their way to a negative rabbit hole that never ends.
If creation is the use it's something else entirely.
AI in the form of interactive chats, can be a novel kind of consumption.
You can have passive conversations in terms of asking a magic genie, or more active ones.
I’ve been trying to ask people a different question: sure, we’re more productive now but to me, the AI era is only serving to plunge us deeper than ever into producing more, more, more, faster, faster, faster. And for what? What’s it all for? I became a software engineer because I have a lot of fun writing code, thinking through and solving complicated problems, and experiencing the reward of seeing what I’ve built by hand working for the first time.
Do people really have fun managing a fleet of agents that generate the code instead? Or is it just the rush of producing something extremely quickly, much more quickly than you might be able to alone, regardless of how well (or poorly) it might work? For me, being able to move quickly was never the fun part.
It’s one thing to utilize AI to lessen the drudgework, the boilerplate, but I look at people who have gone all in on agentic development and it just really makes me wonder.
I feel like I am learning a whole new branch of the programming skill tree. LLMs and their harnesses are like a mew set of constraints to work around when designing systems, but if you get them right you can build bigger, better things than ever before.
I say all of this as someone who spent the last two days rebuilding RBAC for my application after Claude royally messed it up.
Needless to say I have been looking for a way out of this job (and likely career) ever since.
What's going to happen is people who give a shit are going to get filtered and self-select out of the job, and then the entire field is going to be dominated by dunning kruger AI maximalists. The "AI will replace engineers" is true, but for an entirely different reason and entirely different way than most people making that argument think.
- they require specific roads being paved for them. for example, if your tooling is proprietary and not accessible from the CLI, your agent is pretty much fucked. if your tool is not represented in training data (think, `jj` VCS or your proprietary/tailor-made tooling), you require duct tapes such as "skills" and "memories". a bicycle (that is, your own mind + computer) handles such off-roads much better.
- they get you from A to B faster, sure, but along the way you may encounter something curious - a different road to take, an interesting vista. not to mention, bicycles are actually good for your health, and professional drivers suffer from all the sedentary job diseases we programmers do, unless they actively counter it. with LLMs, we get a "sedentary job disease" of skill atrophy, on top of all the other atrophies us coders should counter with a proper exercise set at least three times a week.
- finally, when you crash in a car (Opus/Sonnet, GPT-5.5) or, worse, on a motorcycle (smaller Qwens, DeepSeek, Haiku/GPT-5.4-nano), you crash very loudly and with a high chance of irrecoverable casualties.
Social media and content algorithms come to mind as an early wave that changed the landscape here that defines the horrible status quo leading into the AI era.
These days it's trivial to slide into an echo chamber and very hard to break out of the silo.
There might be a double-edged sword here where AI, trusted by most people as an omniscient oracle, can offer the only pushback we encounter on positions we picked up passively by scrolling social media, Youtube, TikTok.
For example, ask Claude, ChatGPT, and even Grok about the "space lasers" that started wildfires in Hawaii in 2018, something people like Marjorie Taylor Greene floated on social media. It quickly debunks it as bullshit.
Now, maybe it will pan out such that everyone will have their own AI that tells them what they want to hear. But so far I've watched people abandon arguments on Twitter because Grok rejected their claim. So it feels like there's a glimmer of hope.
You should possibly spend some time reading what people used to say about the invention of Radio and Television.
> It is quite extraordinary and breath-taking at times to see the agents in action;
So is any magic trick. The unsettling notion that it may all just be an illusion that you've failed to correctly understand doesn't seem to weigh on people.
> its almost hard-drug like in its potential long-term psychological effects.
That might have more to do with how the owners of these products choose to market and deploy them. Perhaps if they peeled back the covers just slightly your euphoria would change to dread. There's an Upton Sinclair moment coming.
https://pubmed.ncbi.nlm.nih.gov/39216648/
https://www.cancer.gov/news-events/cancer-currents-blog/2023...
https://www.nejm.org/doi/full/10.1056/NEJMoa1309086
https://info.asge.org/083024-colon-asge/acg-quality-task-for...
New tool that does task better than worker leads to workers being less good at task. Net outcome for patient is positive. Next?
Programming: "for a given task, if you take a shortcut then you will not have the familiarity and expertise that someone who took the veritable and righteous path would have".
The question is then, what did you do with the extra time. If it's fuck all, then yes, that's a liability.
Like any technology, it comes down to the disposition of any given person in how they plan on applying it.
Not trying to say it's all going to be awesome. Definitely maybe the opposite. These arguments are weak tho.
"Currency" in all fields relates to the recency and frequency with which you dealt with a particular issue. Whether flying on auto-pilot or coding with AI, automated reduces some currency. But is that a reduction in capability?
Measuring concrete tasks makes currency the operative skill; that's why it works to cram for standardized and mid-level tests.
(Indeed, the 2010's interviewing "wisdom" about people being quick to answer simple questions veered into measuring currency, not skill.)
I think this effect is strongest in time-impacted professionals. Doctors doing dozens of endoscopies a week and developers churning out code will use what tool leverage they can, and forget as much as possible to focus on what they need to. I suspect the effect is weaker in personal or research projects.
People riding bikes won't be able to run long distances - because they won't have to, and will be able to outdo any runners. That's only a problem if the supply of bikes is someone constrained. So the risk is not skill loss, but losing control of the means of production.
"Just being aware that this phenomenon exists hopefully provokes some self-reflection about which skills people want to maintain and which they’re willing to outsource” to AI tools. Right. Obviously.
So we need to be teaching that core lesson to children -- they don't retain skills that they don't practice. And we need to be careful to decide what skills and verify they are learning them. We also should absolutely be using AI to provide personalized instruction to every single student.
Blaming the tools for things that humans do is incredibly stupid and dangerously misguided. Because it shirks responsibility onto the technology, when technology is the best lever humans and society have to improve things! It just happens to also be the best lever available to make things worse.
This negative view of improving technology starts from a warped and very unrealistic concept of the state of the world, where it has been, and the role technology has played.
1. Technologies, starting with fire, the printing press, etc. have been critical in raising life expectancy, standard of living, etc.
2. The world is still a profoundly unequal and exploitive place.
3. AI and robotics have the potential to provide everyone on earth who wants it with extremely inexpensive labor to help them with anything they need or can imagine. This will be a dramatic shift in quality of living.
Human society is the source of our problems, not technology. Part of this is that I think deep down people believe that any tools or developments that arise will just be used to exploit and suppress them more, and there is no alternative. In this case, I guess people think the best outcome is to go back to feudalism or some nonsense because technology just makes things worse.
But why stop there? Why not go back to, I don't know.. fire? Or maybe no one should ever eat any red fruit?
In concrete terms, AI isn’t all that useful for writing a personal blog, because no one wants to read obvious AI slop. But it is useful for creating boilerplate product pages, FAQs, and other types of writing that weren’t very interesting pre-AI.
So it’s not really a huge deal to me that my skill for writing descriptive product page text or FAQs is atrophying, assuming that it is.
And suddenly I was stuck! It was like thoughts weren't forming properly. My instinct was to use Claude to help brainstorm, but I resisted. 5 minutes later, I finally broke free and instantly came up with the plan.
What the hell?
I realized I'd offloaded my planning onto AI. I would ask it for plans and then choose the best one, but that's a different skill than coming up with the plans in the first place. My skills were rotting.
I pity those who need to contend with that as ICs, though.
A very similar topic was discussed here: https://news.ycombinator.com/item?id=48392004 and I make the exact same conclusion:
All of this makes me selfishly excited for my own future. It's glaringly obvious that anyone who's a heavy user of LLMs is atrophying their skills in real-time. I have yet to meet a single person for whom it's not the case. But I essentially completely stopped using them for software engineering (why isn't really relevant, but it's not because od this skill atrophy). So as the skills of everyone else is diminishing, mine is proportionally raising.
It has never been easier to get better than others. You don't need to put in more effort, just the same effort as you always have, and others will do the job of losing their skills for your own benefit.
So I totally disagree with this premise that human skills are being ruined by the use of AI technology. No, many human skills are being made obsolete. That's a good thing for economic productivity as a whole, but for those who only have skills that are being automated, their labor value decreases (which is usually bad for them as individuals).
Nurses, doctors and family members know damn well how life trajectory nosedives for somebody ie suddenly bound to bed, when stimulus and doable challenges are reduced to minimum.
llms remove challenges, or minimize them. I can't image any added value for any engineer apart from cost cutting for employer. Sure, next come folks who are doing 10x compared to before, and some actually do. Even there, I have my doubts. For rest of us, its not good and won't get better unless they price it out of most markets.
If you are doing your job as a manager it’s the scariest career possible. There is no realistic fallback to lower paid IC work after a certain amount of years. Your job is to enable others, not do things yourself.
There are shades of grey and you try to keep skills at least honed a little here and there doing R&D and side projects - but it’s just not the same as day to day production line work.
And of course some people start at a much higher baseline of skill than others. The impact is largely the same though over time.
This is by far the single largest caution I give to skilled engineers who talk to me about moving into a management track. It’s a decision not to be taken lightly.
Programming normally highlights this difference. LLM programming makes it much less apparent but its still there, LLM are not thinking the way humans do and therefore struggle to solve many problems humans easily solve. So letting all human programming skills rot and just use LLM will halt our progress unless we reach AGI before our programmings skills are mostly gone.
I do think there's more than enough room to claim that LLMs are probably significantly worse than that kind of human delegation though, in part because you have such a rapid cycle time that not-incredibly-rich people can't afford from humans.
That's not the way the economics behind this work.
Supposing the AI priests are right (they aren't) and using AI creates a thought surplus on the user, freeing cognitive capacity to think of higher things. What do you think will said user's boss want to do with that surplus? Let the user develop higher-level cognitive abilities? I don't think so.
The doctors in the article performed worse post-AI: suppose AI saved them so much time that they did 100 exams in the time they used to take doing 10 exams. What will their employers do with that freed up labour time? They'll of course have the doctors do more exams and perhaps fire some now-redundant doctors that are no longer needed. The surviving doctors are left deskilled, doing the same or more work, and society gets worse quality medical care. But hey, its not all bad - the employer gets to save on labour, and shareholders will be happy.
LLM output is unreliable, so we still need to judge it. If I want to be able to judge code, I must have worked with it to a certain extent. So the unreliable tool does not help me much if I don't want to accept the unreliability.
Indeed. The great innovation of AI is giving people with wealth access to vast amounts of knowledge, while limiting the amount of wealth that people with knowledge can access.
It's completely bass-ackwards.
Avoiding tool use because you're afraid you won't be able to use the tool responsibly is not likely to be a winning strategy in the end. Learning to use the tool well is much more effective.
People who use coding as a means to an end, producing a product
People who enjoy process over product and coding is the enjoyable part, not the end product
Company executives fall into bucket 1. Even if you love your cushy air-conditioned job, doesn’t mean the people above you don’t see you as a means to an end, a better product.
Solo founders and small startups are in bucket 1 as well but that doesn’t mean that don’t enjoy coding, just the product being made is much more satisfying.
Many devs here have stated that the fun part for them is seeing the end product, not the act of creating it. Using AI is an act of need satisfaction.
Unfortunately, cloning a GitHub repository or downloading a Squarespace template doesn't hit the spot, because you can see exactly where the code came from, so your brain knows you were not the one responsible. AI's greatest feature is that it obfuscates provenance. You can now happily clone that repository or download that template without the feeling that you're cloning someone else's repository or downloading someone else's template.
This is why I think even the fuss about Noam Shazeer joining OpenAI needs to be seen within a context; as good as this hire is, there is no inherent reason to believe he still brings some secret undiscovered magic that others do not have in a more current form.
it's definitely easier to catch up after some time away than it would be if you'd never developed the skills in the first place or didn't have a natural talent, but you'll definitely atrophy without exercise. every leader i've ever worked for who graduated to a purely managerial/'strategic' position and didn't keep up their IC skills eventually got pretty slow on the uptake.
i appreciate that this study was done (AI and its inverse relationship to human wellbeing is one of the biggest challenges of our time IMO) but this also seems obvious
You aren't learning anything. Learning involves doing.
We've known this for ages: simply reading a maths book without drilling on the problems will not get a student to pass.
Best case scenario, you're reading stuff. For users of coding agents, they're not even doing that.
LLMs are sycophants, and in long conversations, their sycophancy produces a positive feedback loop: the context window contains affirmations of incorrect interpretations / analogies, so the chatbot continues down that path because, well, that's the most likely completion of previous text. And before you know it, you're discovering the hidden fabric of the universe, which is always some Minkowski fractal spacetime tensor lattice manifold with subharmonic DNA nanotubes.
That is to say, unless you have a robust way to evaluate what you're learning, and to confirm that you're actually learning, I'd tread carefully.
I've wildly increased my breadth of learning. If I'm ever curious about anything, even a passing thought, I can scratch that itch in a way I never could before.
But am I going deep? Acquiring new skills? Eh... I usually go far enough to unblock myself and/or settle a curiosity. I don't think that's good or bad, but it does present a certain set of tradeoffs that are different than going deep.
When I was in design school, as much of our work was in physical media — graphite, cut paper, paint, vine charcoal — as was practicing great kerning and getting experience with the digital tools. Even though you still had to make the individual strokes and choose appropriate tools in the digital realm, there was still a perception of the process that was obviously lacking among those that came from strictly digital backgrounds. It’s similar to seeing someone who’s only worked with photo references try life drawing — there’s an entire part of the cognitive process not being used when you’re drawing something that’s already 2D. Sure, they can learn, but unless they’re forced to, they’ll probably just keep taking a picture and drawing that. But image generating, even with extremely granular inpainting and such, is so different it’s not even comparable. I’d hesitate to say that someone with a lot of experience doing very advanced image generation would be dramatically further along than a complete beginner if they learned to draw which is not true of the photo reference artist, and even less true of a purely digital artist that did life drawing on a tablet.
Kind of like how millennials, many of whom always had access to technology, but also experienced dial-up-era computer use, are generally more technically savvy than the your stereotypical “iPad kid” that can’t even traverse a directory structure.
I am not convinced that there are tasks, like project management or architecture, that the Ai is inherently worse at.
You will have to write code to understand deeply what goes on at the low level. Without a solid understanding of the low level, you won’t truly know what optimal solutions look like on a high level. You will be flying by the seat of your pants, churning out code that works but has bad low level quirks sprinkled through the code base. The AI will say it’s fine, but you’re just building up shitty software. Feels like shit, run likes shit.
Once someone new comes along who has worked with the language manually and can get AI to produce effective high quality code, you’ve lost competitive advantage. They can build way better versions of whatever you do. You’re finished. You’re a low quality engineer.
For LLMs, we can see this sentence but replace "arithmetic" with a variable X
I'm sure people got worse at X after the invention of LLMs"
The problem isn't that X skills atrophy necessarily
The problem is that for LLMs, X is "basically all knowledge and communication skills"
Can we really tolerate a society where "basically all knowledge and communication skills" are atrophying?
It turns out that when the use of a tool has external consequences for misusing it, it's important that there are structures in place for penalizing the misuse of that tool.
There will always be value in a human writing fiction or a memoir or even a Substack. The human perspective is inherently valuable there. Much less so with ad copy that's just going to get A/B tested ad infinitum until a winner is picked out based entirely on data.
Same with visual art. Art painters aren't going to lose their jobs to AI, but once you've got a robot that can paint a house reliably, house painters are done for.
I’m not even sure why this has to be said.
Universal fact 1) most people lack the self discipline to choose what really benefits them and takes care of their well being. We already know this - obesity rates, excessive screen time etc.
The solution is to control the actions of people. But most of you ain’t ready for that conversation.
So now imagine you're using Chineses AI/AR glasses that you've come to rely on for "knowledge" and you look at the famous picture from Tianemen square: "Doesn't look like anything to me".
The article's claim is probably true, but not really an argument against AI. Using keyboards degrades my ability to write by hand but that's not a good argument against keyboards. AI will become another tool that allows us to operate more effectively and at a higher level of abstraction. Just like keyboards and Python.
Now, we still occasionally need people who can write assembly (and do calligraphy). But mostly we don't.
We do however create new skills, skills that might be more relevant for the future, but still, it is controversial.
This year I'm building and IoT data management platform and I've already built two demos of the product and am adding a bunch of features for a third. Nothing is vaporware about it. All in about 4 months.
The big wins have been system config, debugging, and exploration. I was able to build an Arrow Flight SQL backend to use as an interface and try it out with some use cases, decide it wasn't going to work, and replace it with something else, all in about two weeks. Would have taken far longer before, if I would have been able to do it at all. I knew nothing about Flight SQL before trying it out.
maybe because people see AI not just as a clever packet manager, but also, to some degree, as a problem solving engine. Similar to humans.
I also use Ai to be more ambitious. Online evaluation for our in app flows instead of offline.
So for us the entire quality of the product has been increased a lot.
If you wanted a literal answer, it is to accelerate revenue as much as possible to make the very rich people who own most of the company even unfathomably richer. No benefit to you for making more faster. Other than the burnout, that's all for you to enjoy.
[0] https://pluralistic.net/2025/12/05/pop-that-bubble/#u-washin...
I have been drawn to coding from the first day I took a course at college learning Pascal and assembly on an IBM PC. Hell I even wrote an IEEE/488 driver for an Osborne 1.
As an experimental physicist, coding was always central to my work. I always felt guilty because I had more pleasure coding than tackling the physics itself.
This is a new age we are entering. AI changes how we do things, but I believe that the human passion to be creative and do intellectual work will always be part of it. It's in our nature.
So I'm not worried that we'll all dry up and turn into zombies.
Just one more ~~lane~~ datacenter, bro. That'll fix it; trust. Please. One more ~~lane~~ datacenter. It'll be so good.
My friend said being an engineer is not just writing code, but designing and architecting the system. I agree, but we are also moving that to AI. We are offloading the thought process to a LLM, which confirms our biases and tells us what we want to hear.
Essentially, we are also losing the software architecture and design skills because we aren't talking to other engineers/architects/designers who may approach the problen in a complete different way; we are just asking the AI to confirm our thoughts.
I’d be curious to see alternatives ownerships structures. Like an AI-coordinated collection of guilds, unions, or co-ops. If it can’t accumulate upwards, maybe the fundamental unit of ownership will stay with the workers.
I still believe the slot machine analogy holds to some extent, but I can honestly say my winning percentage is at least 90% for one shot generated code now.
I think if you know it's limitations (inlcluding your own), I don't think about hoping anymore.
I should note that when I say AI, I mean the collective models from all the major providers. The most important lesson is, you need to ask around.
> There’s definitely a skill to using AI but it just doesn’t generalize very well.
This I agree with. The only way working with AI can really be benefical outside of dealing with AI is, we are visited by extremely intelligent beings that will fuck up in the weirdest ways.
But it's not the only way to learn and not even the only way to do a lot of forced recall.
It's downright crazy to say you aren't learning anything by reading. You likely won't retain that high a % of the content without repeated drilling, but it's not like nonfiction exists for no reason!
You can have it write a program that generates drills for you.
I wanted to become better at reading sheet music so I generated a sheet music reading program. You can have it generate maths drills, then ask questions about it if you get stuck or whatever. If you genuinely want to get better at something then AI will help you learn it faster. Obviously its going to hamper more people's cognitive ability that it will enhance but that is a separate problem.
For example: AI has helped me get into restoring retro tech, specifically resoldering leaky caps on retro Macintosh logic boards. Before AI, I didn't know how to use a multimeter (I knew theoretically how it worked), I didn't know how to use flux, solder wick, heat gun. I also didn't understand how bromine radicals yellowed plastic and how to reverse it by using blue light similar to what they use for indoor aquariums.
So AI unlocked doing for me.
Without doing you may as well read some fiction. The result is mostly the same.
An LLM absolutely shortens the research part of learning. If I had a human of who had a moderate level of skill who would endlessly answer all my questions, the result would be the same.
You might have a point when it comes to software development because the AI can tell you things but it also just do them for you, at which point, you've learned a lot less. But for non-software things I have to learn things so I can then go and do them.
But even for software development, I've learned a lot of esoteric crap to get interop working on projects that I will probably quickly forget just the same as when I had to spend hours skimming through stackoverflow.
In another case I follow a bodybuilding cutting regimen and it helps me create and track recipes consistent with my diet plan and macro guidelines. It helps me also create tasty recipes that fit my criteria based on the ingredients I have on hand.
Those are just 2 examples.
I also recently built a backyard jib setup with a platform, ramp, PVC jib rail for snowboarding, and it helped me architect the design for it.
I have been very pleased with the results so far. I was able to tune the tutorial to exactly what I want to learn, and it did a very good job (at least that i have seen so far). It has made learning fun, since I get to learn exactly what I want, and I can ask the AI questions and have it make changes to the tutorial in real time as i am working through it.
Now, will I keep using this at a rate to fully offset all of the thinking i have stopped doing since i started using AI? I am not sure, I guess time will tell.
i could not get through the hurdles of installing an IDE and js/python modules before.
now i am learning basic scripting and data modeling etc.
it is phenomenal for learning languages.
i built a chicken coop and some furniture. the skills and confidence i gained are real. am i failing to learn certain skills in the process? of course. but I'm getting further then i would on my own, and that is truly meaningful.
you can keep dismissing it; but I'm genuinely using it to break down barriers, give me confidence, and highlight my ignorance in very productive ways.
i find it bizarre how unwilling some people are to recognize that.
The code they submit for review no longer represents their thinking or their skill. The feedback loop for beginners is a bit broken.
What is their skill now? How is it displayed? How and where do we provide valuable feedback? I find myself just approving large PRs because I don't have the time to read it all.
I feel like I've let down a lot of developers this year.
* There's meaning in all the little marks. Drawings are potentially layered with meaning. I was drawing a stick I found in the park, and thinking: this is the extent and the way in which the stick is straight or curved, and the specific way and form that it's knobbly, and that's all explained by how it grew; this green on it is the peculiar blue-green of lichen; it's a oak stick, I like oak; my drawing is just a stick, good, I might frame it, call it anti-art maybe. Some or all of that is expressed in the marks, though this becomes more apparent if I tell you that it is.
* So, an AI - diffusion - could undoubtedly draw a stick in an arty way. But to draw one that fits the above meanings, it has to be prompted with the meaning. The AI can't prompt itself, so there's a role for artist-as-prompt-writer. Whoopee, right, what fun. These prompts, if about graphical matters and a sort of meditation on the stick, would be essentially lies, because no such exploration of the form and significance of the stick would have really taken place without trying to draw it. It can't prompt itself or be honest.
* So to come up with the above words that might do as a prompt, I had to draw a stick. I had to learn by drawing a stick, even though I've been drawing for decades. Experience isn't the whole deal, otherwise the artist is only churning out filler material, which would be like AI art. Instead the artist has to explore all the time, while leaning on experience. The viewers are into that, they sense the excitement of exploration. They want to see an artist. Well, not exactly, most artists are unrewarding to look at (Brian Froud for instance), but they want to see creativity unfolding, over several pictures.
You can have non-graphical (non-mark-making) prompt-art, a bit like collage or photography, sure, but that's its own thing. Like you're saying, you can't just fake the craft forever, and even faking it once is less than ideal, unless you're narrowly focussed on output that meets targets, instead of meaning.
With programming, this might be different, since hitting targets and getting functionality might be all that's wanted, but I'm sure it depends.
10-20 years ago we had such high hopes for data and IoT, but it’s still just banal and mildly useful, full of walled gardens and property formats. General purpose AI may end up similar. My company has like 10 different MCPs to enterprise software we use that has context, but AI still needs lots of guidance.
I think you can also see the vague outlines that someone is going to have to be in charge of token cost.
The lack of attention does reduce the overall correctness of the system.
But, and unfortunately, in most situations the loss of correctness is more than made up for by the speed gains.
Unless you're building software that could kill someone, it's hard to reject the improved speed. The cost of delay is usually more damaging than the cost of incorrectness.
Building skills over time leads to insights that lead to innovation.
AI does many interesting things, but it doesn't innovate (yet).
The real threat isn't that we'll all lose our skills (possibly) and then lose access to AI (unlikely), it is that AI will remain at roughly currently levels and we'll dull our skills due to reliance on it and innovation will stall because we've offloaded too much of the thinking to the non-innovative machine.
I'm not saying this is what definitely will happen, but it does seem like a very possible outcome.
Every time I see an anecdote like this, A it reaffirms my belief that FAANG devs are fairly mediocre on the whole (not saying this is you, obviously there are good FAANG devs) and B it reaffirms my belief that the developers who kind of give up their thinking like this are really using the tool wrong or didn't really care about the work before AI either so its now just a quick means to an end.
I think a lot of academics and researchers who code but aren’t software engineers or CS majors are going to benefit, provided they take the time to prove what the model does and are curious about whether it’s doing something sensible!
Relative to a 1% coder hand rolling something then yes it’s AI slop etc. but it’s prob still raising the bar generally.
For example I am following Dirac's book "The Principles of quantum mechanics" to study QM. Pre-AI wouldn't have been able to do so, I am just that dumb. Even with AI its tough. but the thing is I can keep asking questions until I get that concept drilled in. Now I am doing it at a pace that's unfathomable to me.
But now that I am getting to grips with QM, I can get to things that I am really interested to learn like spin resonance and so on. This is something I am so grateful for.
Now it can be questioned that is it making me wise, intelligent or just "giving me answers" that I should strive to discover myself. I dont know the answer to that. But studying what I want, how I want and not getting judged is something i deeply enjoy. Srry the comment might have taken some tangents.
My current position is more on the operational side and AI allowed me to create a pretty significant software system for our technical ops, that the wider org liked and given me the resources to recruit flesh-made engineers to support.
A rare case of AI creating jobs.
So far I’m very happy with my decision.
I wrote about it here: https://news.ycombinator.com/item?id=48083162
> I had the same experience over the past year with early coding harness at the beginning of the year, then Claude code since its release date. But after 1+year going that direction I really don’t want to continue. The novelty is gone, dealing with AI now feels frustrating and boring, I miss engaging deeply with the actual lower level technical challenges. I do not want to manage fleets of agents. I do not want to rediscover for the hundredth time that in fact all this time an agent took shortcuts for acceptance tests I rely upon and didn’t catch. Or once again get the agent to understand why and what I want it to do after its context got bloated and it start to drift completely. While I got artifacts I can use (libraries, tools, docs), including some things that I’m pretty confident are SoA I do not feel satisfied anymore knowing that I used a model to generate them, even if I was the one designing every part of it. I do feel that I’m lying anytime I come to a colleague to share a new cool tool I have made.
> YMMV but I’m personally feeling burnt out with AI coding agents and ready to go back to the old ways for my next personal project
And also here (specifically to human communication): https://sam.elborai.me/articles/no-more-llm-comms/.
I think this highlights the difference between the “how do I make a ham sandwich?” approach of chat vs the “sudo make me a ham sandwich” of agentic coding.
One of the canonical references of Jobs’ use of “bicycle for the mind” also compared the efficiency of locomotion to the California Condor which was (I’m working from memory, here) 17X more efficient than a human walking.
A human on a bicycle, according to Jobs then, is more efficient than the most efficient animal locomotion known to humankind. The comparison included animals moving through non-terrestrial environments.
You would need similar restrictions during the learning phase to get people to learn things in an LLM world.
So writing and LLM are still a net positive, but only if you acknowledge the problem and add fixes so people still learn rather than just rely on this crutch.
How much of a nonfiction book can you recall a few months after reading it? Probably very little.
However, I haven't taken a calculus class in nearly a decade and I still know how to solve derivatives and integrals.
Point being: there's levels to this, and reading is not nearly as effective as drilling exercises.
I'd really like to know the prompt, because I did try and, this took me way too long to figure out.
> I don't think about hoping anymore.
Running the exact same prompt again that already failed doesn’t have a that high success rate, but it’s also very low effort. So IMO it’s often worth attempting.
mine def has to be the initial impl of my python to my personal fave compiler ir. i got claude chat to write it in two sentences. 4 turns helping it rmeemver where it put shit becsuse of transcript issues
I don't quite follow how AI unlocked any of that?
The best way to learn these things (well, second to a human coach who has the expertise and has time to guide you) is from youtube videos, not AI.
You're happy using AI instead of other material because it will constantly tell you how brilliant you are, or how quick you're learning.
I actually did have an LLM ingest some material and generate drills. It worked well. It's rare that happens, though.
The difference between humans and other animals on the planet had always been the ability to reason. If we, as a species, lose that ability, we're looking at an extinction-level event.
That is my point: an LLM can be great if you know the field and can spot errors. Or, to a lesser extent, if you have some automatic feedback loop that the model can't easily game ("does this code pass unit tests?"). It's a lot less great if there's a risk that you won't detect the early drift.
No, it doesn't. Because in any scenario where you are using AI in a potentially appropriate manner, you are verifying every single source it spits out and cross referencing everything it says. If you do not do this you are failing the process entirely.
You want us to believe you couldn't overcome the puddle-deep challenge of installing an IDE and using Pip or Node in the past, but now you're actually learning how to write functions?
Cool for you if true I guess but I'm pretty seriously skeptical
Diffusion models basically record, classify, and amalgamate those decisions, which is why it’s so dang difficult to get generated art to look like something distinct. Not distinct like an existing artist, but genuinely unique.
The workflow of the prompter is very similar to an existing workflow in the art world: someone commissioning art. There’s often a discussion where the customer gives the artist a textual description, back-and-forth with sketches and preliminary versions, and sometimes revisions if the proposed final product isn’t what they wanted. Commissioning a piece of art is a creative process, but it’s not the same thing as being the artist. Even an art director who has extremely granular control over what they commission would never claim to be the artist. They’d get run out of town. I believe creating a collection though juxtaposition or even curation could be art, but you’d still never be the author of the contained pieces.
I think the industry has, and we don’t get much out of individualizing it. Let’s not forget that this progression is a series of deliberate choices made by a handful of very influential people that couldn’t give a teaspoon of shit about developers beyond what their subscriptions bring in.
It’s not a super well-received opinion around here, but I think the economics of the large-scale services will mean on-device models are going to be where this all goes sooner or later. My gut says setting up a local LLM coding assistant will be more like choosing and setting up an ide. I don’t have a crystal ball though.
Welcome to the future, where we can create buggy, broken software at a higher velocity than ever before!
If that doesn’t apply, you are just writing toy apps or front ends that are of no real significance, so yes you could carry on with incorrect code in those cases, but it’s not much of a career either.
LLMs will implement what you ask them to, even if it is the wrong approach. They can be lazy and take shortcuts all the time, but they do not feel PAIN (obviously they don't feel anything and aren't lazy, I'm just personifying them but you get the point). Only when you implement by hand can you feel if the implementation of your design is painful or not, and only this signal can tell you if your design if truly good or not.
I do think LLMs are useful for design work, they are good at asking clarifications and probing questions which actually do push you to approach problems differently, but leaving implementation of designs to LLM is a recipe for disaster, and judging your own design skills when you're not implementing such designs is seriously laughable. And to be clear, it already was before LLMs, when "software architects" were just designing and then had peons implement for them.
LLMs are enabling a whole new level of bad code that is best describe by the following Jurassic Park quote: “Your scientists were so preoccupied with whether or not they could, they didn't stop to think if they should.”.
> A it reaffirms my belief that FAANG devs are fairly mediocre on the whole
Off-topic but having worked in other companies as well, I can guarantee you that this is not the case. The skill of engineers in FAANGs and other "top tier" companies is much higher than average.
I think another (partially causal?) problem is how they're managed. The whole perf circus is just ridiculous, especially the stuff recently reported about facebook. But they're all more or less like that. Steeped in that cocktail of incentives, who even knows what might happen to an otherwise excellent engineer.
But also just numerically, they can't be much above average, on average, because there are so many.
> my ability to reason over and edit code
You can't be able to do one but not the other, they're the same thing.
> I suspect that your LLM-pilled coworkers' judgment issues are related to laziness that LLMs have enabled, rather than an inherent property of LLM use.
Does it matter? The end result is the same. Maybe the studies that the article mentions are simply showcasing the exact same effect that you're suggesting here, but it doesn't change the fact that there is indeed a negative outcome.
Pre-AI slop got a pass because the creator probably worked tirelessly to make it and that process gave it value.
Post-AI slop get criticized because AI can create it so fast and easily.
But the builder has not changed. Because the builder knows that the product depends on iteration and polish. And knowing what to iterate and what to polish requires intuition and taste. And thats the thing about taste, its forever fleeting. What we think is AI slop, was actually novel and coveted at a point before AI existed.
I think this touches obliquely on a point I keep coming back to, that one of the most important things a codebase does is to communicate ideas about how a process should work. Yes, it also produces some binary that runs on a bunch of servers or whatever, but that's a really temporary, ephemeral artifact. The lasting thing is the idea. Making your ideas (expressed in code) easy to understand, easy to work with, and easy to evolve in time is the art of software engineering. I 100% agree, from my own experimentation with LLMs, glancing at something a model has produced and checking that it has some test coverage isn't enough to know whether it's well-engineered. You'll only find out later when you try to work with the code.
It matters. If LLMs are like alcohol, useful but potentially dangerous, they should be treated very differently than if they're just poison. If someone's a drunk and they can't keep their lives together, it's not the alcohol's fault, it's the person's.
Whether the demand will match the supply is still an open question. Did the apple app store need another 4,000 to do apps? I guess we'll see.
https://github.com/gitsense/gsc-cli/blob/main/internal/cli/r...
Since I don't know go, I can't say which is the best. I am also sure they would not live up to a go experts expectations. I just know that since I don't know go, I would not have been able to create the tool. I can also prove that you can easily maintain AI generated code since I have been expanding and evolving it for over 6 months with pretty much no issues.
> There isn’t a magic prompt I could have written before knowing the solution. A retrospective prompt can reproduce the 200 lines only because it embeds the invariants you discovered. The useful AI task would have been systematically finding counterexamples and iterating toward those invariants, not generating the final file in one shot.
For me the value with AI isn't the one shot, it is the fact that it can help you iterate faster. My biggest take awway so far with AI is it can help you fail fast. The faster you can fail, the faster you can iterate.
I also use AI to take in-progress pictures as I desolder to help me check for traces that need to be repaired or help identifying specific chips. I probably could try and find a video where the same chip is featured and someone explains it, and/or retrieve the schematic for the specific logic board, but that's very painful and does slow the process. Think of AI, in this specific case, as enabling skill development for me in a field I wouldn't have necessarily have gotten into, because of being short on time and AI helps me consolidate that information quickly.
Just because you can't use a tool doesn't mean the tool isnt useful.
Your bias on display here is frankly silly. Im not saying LLMs are ALWAYS the best way of learning something just like they aren't always the best at anything. They are a valuable tool though. Yes so is youtube and textbooks, and professsors, and peer review literature, and pen and paper, and block training etc.
In addition, I literally had AI build a complete list of parts to order from Amazon down to the caps for each system I wanted to rebuild -- it was close to 20 different items, I would have probably given up if I had to try and assemble this list from different YouTube videos.
However, your perspective on how LLMs are used might be too narrow. While no one is suggesting using an AI to find a one-shot cure for Alzheimer's, LLMs are incredibly effective tools when paired with textbooks to master subjects like undergraduate physics.
A lot of the most miserable parts of getting started coding have nothing to do with programming and everything to do with like, trying to apt-install the right compiler version or figure out which build headers you need or some other equally trivial bullshit that gets in the way of writing code.
It made me realize I've only had the misfortune of being employed at fake ones.
If course code craftsmen will feel the pinch of this change
I fear on-prem AI is likely to become as popular as on-prem servers without Cloudflare using self-hosted email are today: that is to say, people have heard of it but the skillset is almost popularly eviscerated, external policies make it progressively impractical, and anyone who does it is 'niche'. While basic guides will exist, obtaining top-level output will probably require many moons of concerted effort.
Basically: AI is SaaS for thinking.
I don't see what this has to do with what I posted.
Yes, AI lowers the floor on software development, and there are positive aspects of that, but that doesn't change the possibility of an innovation stall.
https://github.com/kristofferR
One of them, a Home Assistant integration for controlling adjustable beds, would be borderline impossible to do well manually - I've vibe-reverse engineered the Bluetooth protocols of more than a 100 Android apps.
Fwiw we both agree that LLMs should not design systems. I do the design, but otherwise I don't get how this is true, the success of a design is indicated by long term success in the system it built. You can measure this against success in the task it was deployed for via performance metrics for one. And then from a developer standpoint how easy it was to maintain later on. Success of a system is a measurement over time, but it's not some quality that can only be measured by those who built it.
> Off-topic but having worked in other companies as well, I can guarantee you that this is not the case. The skill of engineers in FAANGs and other "top tier" companies is much higher than average.
I have first hand knowledge of this so I agree to disagree. Being surrounded by google, aws, and meta folks my understanding is the best people leave faang when they get the itch to do something better with their time.
There are as many CS grads every 2 years in the US alone as total software engineers employed by FAANGs...
https://x.com/yaroslavvb/status/2067367657272422584 https://x.com/voratiq/status/2067667800643268928 https://arena.ai/leaderboard/agent
Concentration of power exists when the model makers are the same as (or control) the inference providers. Making a model is capital intensive, so there aren't many of them. Providing inference is not: I don't even need to own GPUs; I can rent them from those who do and then sell by the token. B300s cost less than $4 an hour currently.
Cloud can even be more effective at lowering concentration of power than on premise. Asking people to individually buy $20,000 of compute equipment plus power and cooling equipment to run a frontier model is not something they're going to do if they can just pay four-tenths of a cent per output token. If the only cloud inference providers are the big proprietary US titans, that means you're going to get far more power concentration than if open source inference providers are an alternative, because then I can just switch my API endpoint.
If we're talking about research as in actually attempting to learn and get to the heart of a matter then yes. You should be cross referencing everything.
I agree that they can be helpful for explaining things if you're stuck. But since you used the example of physics, the majority of hard won physics knowledge comes from working lots of problems yourself.
Too many people are already used to LLMs circumventing the laborious aspects of things, so it takes a certain person to withhold from just having the LLM solve the problem for you when you're stuck.
Until we can figure out to teach people to fight against their instincts, then I don't think LLMs will lead to better long term outcomes.
Students cannot grade their own answers for more complex problems, they make mistakes but say they are correct since they don't understand the material, or they are correct but since it doesn't say the exact same thing as the example answer they say they are wrong and correct it even though it was already correct. And an LLM would be even worse than that at correcting tests.
This is not a bias against you, its just a general thing that applies to all students and people. Nobody is good at correcting their own work, even the most esteemed professor gets his work checked by other people. And an LLM is not another person here, they aren't good enough to check your work.
Note its much harder to accurately grade an answer than to answer a question.
https://news.ycombinator.com/item?id=48567759
Commenters there were saying GLM 5.2 was roughly equivalent to Opus 4.8 in coding prowess, based on personal experience of the people commenting. Opus 4.8 came out on May 28 this year (so more like 3 weeks ago), GLM 5.2 came out 2 days ago.
Consider another perspective: They don't have to keep up. Once a model is good enough for a task, the model can stay. A hammer is a hammer and a hammer from 100 years ago still has most of its utility.
Similar to the hammer, it's not unreasonable to think that some classes of work will simply be solved by some model generation and whatever happens at the frontier after that does not matter all that much for work that puny humans do.
Then, of course, there will be a time where all of this is moot: Absolutely no human will want a human to diagnose their medical issues. That is not a skill deterioration issue. We simply will concede that we are not able to do it as well as a more capable system can, and without much fanfare, increasingly delegate, as we have always done.
Your understanding is wrong. The extreme majority of people who leave FAANGs don't leave willingly, and are not the best, unless it's to go to even better companies like Jane Street and the like, but those are rare.
Turns out for most people, there's not much better to do during your 9 to 5 than solving problems for half a million a year.
I started learning Monogame with C# literally yesterday after being a chiefly JavaScript dev for over a decade. I'm having a lot of fun learning it from scratch with no AI
I'll concede that before yesterday it had been a while though
> Especially something older that won't hold your hand
Python and JavaScript are two of the most "will hold your hand" languages these days aren't they?
> A lot of the most miserable parts of getting started coding have nothing to do with programming and everything to do with like, trying to apt-install the right compiler version or figure out which build headers you need or some other equally trivial bullshit that gets in the way of writing code.
I agree but absolutely not for these two languages in particular
You can open the developer tools in any major browser and start typing in JavaScript right there if you want
Python you can install it and write it right in any editor
The upfront burden for both languages is absolutely trivial imo
Even if this occurs, and I don't trust well-resourced humans to allow their existing apex-predator positions in present era capitalism to be overturned, the action - as far as either humanity or AI is concerned - will still be at the forefront of possibility: a front by definition invisible to old models. And someone has to pay for the hardware to be there. Do we (a) allow private-sector dominance, effectively depowering traditional nation states and empowering a private cabal beyond historically conceivable levels (b) nationalize thought (c) head in sand and pretend it will all go away?
Most of the world seems to be with strategy C right now, strategy A is the advancing default and has already achieved extra-terrestrial reach with a threat of extra-terrestrial persistence, and strategy B is potentially scarier than the other outcomes if it goes wrong but might be lovely, if you believe in nordic state funds, solarpunk futures and socialist utopia.
Interesting times. By the way, if anyone with AI capitalization reads this, I'm looking for investment to feed humans more efficiently and have a NASDAQ reverse merger under negotiation and effectively priced out with board buy in. Just need capital support. https://infinite-food.com/
After a while, you do start to start to skip a couple rounds of open source models until there's a notable release. That, and the resources needed to run them are increasingly bought up by the owners of frontier models
More people are coding, I wouldn't say they are closer to the code if they are vibe coding. Are any of them going to produce the next breakthrough in computer language/framework/method of development/etc?
The risk of AI is that we dull the skills of enough people at the high end of the state of the art of the nuts and bolts of software development that we slow down innovation on that end. That's the concern.
Previously-non-programmers vibe coding CRUD apps they never could have before is all well and good but really has nothing to do with this concern. They may create wonderful and successful businesses but they are irrelevant to computer science related innovation.
Lol. I don't know I was talking with a guy yesterday who left a FAANG clearing 1.4 million / yr who's now running his own successful startup. My sample is successful founders backed by top tier VCs or exited founders who have done much better than FAANG. If you can't do more you stick around the FAANG, those who can go and do it.
So did you build a house, or did you build a house?
FAANG doesn't straightforwardly retain the best technical talent, and the median task there is routine.
When you ask 'who knows' that's the point of research which was my original comment here. The same goes true for some random asshole telling you to drink bleach as it does an LLM, except people seemingly have hyped themselves into believing the LLM is more right somehow instead of being trained on every random asshole ever.
If I had to have a complete idea of what I was doing to do it, I wouldn't even have a job. Doing stuff and making mistakes is exactly how you learn.
But it's not going to do that. It's literally designed to give the best and most accurate answer that it can. It's not perfect and I don't expect it to be perfect. According to my personal experience it's definitely good enough for a lot of things like recipes, coding, hobby stuff, and home repairs.
You're expecting me not to trust my own personal learned experience using AI as if somehow all my continued successes are worth nothing because you can invent some wild hypothetical. The more I use it, the more I understand its limitations and avoid them.
This is not true. This is not how LLM's work. They have no concept of accuracy or "best".
No, no, no and no. This is the biggest mistake I see people consistently make with LLMs. It is not designed to give you the most accurate answer, it is designed to give you the most likely series of words following your prompt.
If an LLM is trained on 10 jackasses thinking bleach is a medicinal drink and 1 doctor who disagrees, it will by virtue of probability tell you to drink bleach. Companies add additional safeguards or system prompts to try and keep it 'on rails' but it's all probability based on what you prompt it. It is by the literal functionality of how it works to do so. A function depending on what said company ingests during training, many of which include the entire corpus of the internet.
If you do not understand how LLMs work under the hood then yes, you shouldn't trust your own personal learned experience because you've already demonstrated that you're wrong.
The system designers (OpenAI, Anthropic, etc.) are absolutely trying to build a system that gives the best and most accurate answers possible.
The model itself does not have goals, intentions, or an internal concept of "best" or "accurate."
That's not specifically true either; training is more complex than that. ChatGPT had to be trained, for example, to answer questions in a chat format.
> If an LLM is trained on 10 jackasses thinking bleach is a medicinal drink..
Again with the hypotheticals! You literally cannot discuss this subject without hallucinating things that don't exist. LLMs are trained on huge corpus of information from books to videos to reddit posts. Ultimately, statistically, it's going to predict the most common answer to something. Yes, that might be wrong but the vast majority of the time it's going to be right. And you know what, in the real non-hypothetical world, it works great. As much you don't want it to. You can hypothetically hallucinate as many weird unlikely scenarios as you want but that doesn't make it true.
The people least willing to understand how the system works are also the most willing to blindly believe it.
AI companies are trying to build a system that gives the best and most accurate answers possible -- that's the whole point of it all.
Reliance on artificial-intelligence tools degrades the abilities of physicians and software engineers, studies show.
By

Physicians’ own ability to spot pre-cancerous growths during colonoscopies declined after they had grown accustomed to using an artificial-intelligence tool to help with the task.Credit: Gabrielle Voinot/Look at Sciences/Science Photo Library
As more professionals begin to rely on artificial-intelligence tools in their work, could their hard-earned skills atrophy?
That possibility is a growing concern for medical specialists, computer scientists and other workers. Seventy per cent of nurses and 77% of physicians, for example, are worried about losing their skills because of over-reliance on AI systems, according to a survey of US health-care workers published earlier this month1.
Their fear might be justified. Evidence suggests that AI-driven ‘deskilling’ is starting to happen in medicine, computer science and other fields. Researchers are now discussing how to preserve important human expertise in the age of AI.
“Just being aware that this phenomenon exists hopefully provokes some self-reflection about which skills people want to maintain and which they’re willing to outsource” to AI tools, says Kevin Crowston, an information scientist at Syracuse University in New York.
A study2 of physicians in Poland who specialize in endoscopy — the use of flexible probes to examine the inside of the human body — shows how quickly AI tools can erode human abilities. The physicians, who had all performed at least 2,000 colonoscopies during their careers, were given access to an AI system that analyses colonoscopy images in real time and flags a type of precancerous intestinal lesion called an adenoma. The tool was available to the specialists on some days but not on others.
Once physicians began using it, their performance dropped significantly whenever the system was unavailable. During the three-month period before the AI tool was introduced, the specialists found at least one adenoma during 28.4% of colonoscopies. During the three-month period after the tool was introduced, the adenoma detection rate for colonoscopies performed without AI assistance decreased to 22.4%.
The findings, published last October in The Lancet Gastroenterology and Hepatology, suggest that even highly skilled professionals might get worse at tasks that their job requires as they become more dependent on AI tools, says Robert Wachter, a physician at the University of California, San Francisco, who is the author of a book on how AI tools are transforming health care. The study authors say that continuous exposure to such tools can cause clinicians to become “less motivated, less focused, and less responsible when making cognitive decisions without AI assistance”.
Co-author Yuichi Mori, a physician-researcher at the University of Oslo, says that more studies are needed to confirm the phenomenon. But people who use AI tools should be aware that they risk losing some of their skills, he adds. “There is no established solution against deskilling right now. It should be a very hot research topic in the next decade.”
To investigate whether skills are being lost in the field of computer science, researchers at the AI firm Anthropic in San Francisco, California, designed a randomized controlled trial in which 52 software engineers were asked to perform a basic coding task3. During the exercise, all 52 participants could search the web and access instructions on how to do the task. Half of the participants were prompted to use an AI assistant as well.
doi: https://doi.org/10.1038/d41586-026-01947-1
Wolters Kluwer. Patients, Doctors, and Nurses on AI: Similar Tools, Different Pathways, One Destination (Wolters Kluwer, 2026).
Budzyń, K. et al. Lancet Gastroenterol. Hepatol. 10, 896–903 (2025).
Shen, J. H. & Tamkin, A. Preprint at arXiv https://doi.org/10.48550/arXiv.2601.20245 (2026).
Rinta-Kahila, T., Penttinen, E., Salovaara, A. & Soliman, W. In Proc. 51st Hawaii Int. Conf. System Sci. (ed. Bui, T. X.) 5244–5253 (HICSS, 2018).