This doesn't seem like a well-thought-out post. I mean, I probably could have told you that from the fact that it's either pro-AI or anti-AI (in this case the latter), but this is a particularly poorly thought out post. Others here have pointed out the water-wasting red herring, but there are several other pieces of nonsense here — the general environmental doom-mongering, and labeling recursive self-improvement as "mystical", for example.
Me, I pointed Claude Opus 5 at a C codebase I've been working on for years and it immediately found five serious bugs and told me how to fix them, as well as how to use Linux system calls I wasn't familiar with to solve some other problems. And I gave it a new language for PEGs I'd written up a couple of years ago, and it wrote me a working implementation in OCaml that afternoon, fixing several bugs in my example grammars along the way and resolving a conceptual problem I'd had a roadblock on. I asked Fable 5.1 to implement a minimal proof assistant, and it wrote a clone of J-Bob in Python, which I'm studying now. Although there is a certain firehose quality to this stuff, I sure don't intend to use AI to actively de-skill my brain.
That doesn't guarantee that AI will be a beneficial innovation overall, of course! As with most innovations, it probably depends on the balance between people being able to use the innovation to gain control over their own lives, and people being able to use it to gain control over others' lives. (Barring a FOOM scenario, of course, where our prediction ability is nonexistent.)
So, I don't think a pro-AI post can be well thought out, either. It's too early and chaotic to understand what's going to happen, and it may actually be uncertain. Pro and anti are both far too simplistic.
I am sure many smokers in the 1950s also saw the health benefits of tobacco, that they were very happy to experience the increased energy after a smoke and could get more done as a result. I‘m pretty sure none of them felt their lungs and throats deteriorating either.
Likewise, you may not feel like AI is de-skilling your brain. But it probably is. We don‘t have the research (yet) that AI is addictive and causes brain atrophy, but all the evidence is certainly pointing that way, the same way the evidence were pointing that way about tobacco in the 1950s. My only hope is that it doesn’t take us another 2 decades to prove the obvious.
>Likewise, you may not feel like AI is de-skilling your brain. But it probably is.
It is, but why is that a problem? Moving from physical labor on the farm, factory or construction site to sedentary work and lifestyles would also atrophy our muscles so now we pursue physical activities we actually enjoy like gym and sports instead of hanging on to those dangerous and strenuous physical labor jobs just to stay in shape.
Similarly, you will use the AI to churn through the repetitive mundane tasks the AI can do, and then work your brain on the activities you actually enjoy.
Now if you choose to not exercise your brain and dumb yourself down the same way sedentary people don't exercise their bodies and get obese, then I guess that's on you, but we can't force the world to technologically regress just because some people are lazy and don't exercise, the same way we haven't forced construction workers to use pickaxes instead of machinery to tear up a road just to make sure they stay in shape and don't get too fat from sitting in their air conditioned excavators.
Agreed. I haven't written a line of code since last November when AI had the big shift into something good.
The average HNer would imagine me scrolling TikTok while I periodically swivel to Claude to type "continue" while my brain shrivels away.
That I can delegate lower level work like implementation means I spend my time at increasingly high leverage positions like deciding what gets built. And any time I want, I can get as granular and inquisitive as I'd like about the lower level work. After all, I probably chose it from a multiple choice AskUserQuestion tool call, each with a blurb and shortlist of trade-offs.
All this talk of de-skilling doesn't make a lot of sense to me because what are these skills people covet so much that defined most of the day to day of a software developer? What, the implementation details of some framework or the intimate details of your company's crappy legacy software stack?
That may very well be true, but as you're describing it, I think of all my fellow engineers, all of them very talented, who moved up into management, arguing exactly the same point of thinking at higher abstraction levels. And after one or two years go by, they will come to me with requests or opinions that are literally the dumbest shit I've ever heard. Like arguing that we (holding most of our data on MariaDB and Postgres) should move everything into Kubernetes custom resources because "the Kubernetes resource model is the best database ever". That's a real thing that I've had an engineering lead say to me. When I asked how you're gonna do an efficient table join on Kubernetes resources, I just got a blank stare.
kragen · · focus · HN ↗
Me, I pointed Claude Opus 5 at a C codebase I've been working on for years and it immediately found five serious bugs and told me how to fix them, as well as how to use Linux system calls I wasn't familiar with to solve some other problems. And I gave it a new language for PEGs I'd written up a couple of years ago, and it wrote me a working implementation in OCaml that afternoon, fixing several bugs in my example grammars along the way and resolving a conceptual problem I'd had a roadblock on. I asked Fable 5.1 to implement a minimal proof assistant, and it wrote a clone of J-Bob in Python, which I'm studying now. Although there is a certain firehose quality to this stuff, I sure don't intend to use AI to actively de-skill my brain.
That doesn't guarantee that AI will be a beneficial innovation overall, of course! As with most innovations, it probably depends on the balance between people being able to use the innovation to gain control over their own lives, and people being able to use it to gain control over others' lives. (Barring a FOOM scenario, of course, where our prediction ability is nonexistent.)
So, I don't think a pro-AI post can be well thought out, either. It's too early and chaotic to understand what's going to happen, and it may actually be uncertain. Pro and anti are both far too simplistic.
runarberg · · focus · HN ↗
Likewise, you may not feel like AI is de-skilling your brain. But it probably is. We don‘t have the research (yet) that AI is addictive and causes brain atrophy, but all the evidence is certainly pointing that way, the same way the evidence were pointing that way about tobacco in the 1950s. My only hope is that it doesn’t take us another 2 decades to prove the obvious.
PorciiVorbesc · · focus · HN ↗
It is, but why is that a problem? Moving from physical labor on the farm, factory or construction site to sedentary work and lifestyles would also atrophy our muscles so now we pursue physical activities we actually enjoy like gym and sports instead of hanging on to those dangerous and strenuous physical labor jobs just to stay in shape.
Similarly, you will use the AI to churn through the repetitive mundane tasks the AI can do, and then work your brain on the activities you actually enjoy.
Now if you choose to not exercise your brain and dumb yourself down the same way sedentary people don't exercise their bodies and get obese, then I guess that's on you, but we can't force the world to technologically regress just because some people are lazy and don't exercise, the same way we haven't forced construction workers to use pickaxes instead of machinery to tear up a road just to make sure they stay in shape and don't get too fat from sitting in their air conditioned excavators.
hombre_fatal · · focus · HN ↗
The average HNer would imagine me scrolling TikTok while I periodically swivel to Claude to type "continue" while my brain shrivels away.
That I can delegate lower level work like implementation means I spend my time at increasingly high leverage positions like deciding what gets built. And any time I want, I can get as granular and inquisitive as I'd like about the lower level work. After all, I probably chose it from a multiple choice AskUserQuestion tool call, each with a blurb and shortlist of trade-offs.
All this talk of de-skilling doesn't make a lot of sense to me because what are these skills people covet so much that defined most of the day to day of a software developer? What, the implementation details of some framework or the intimate details of your company's crappy legacy software stack?
Dunno, I have bigger plans for myself than that.
majewsky · · focus · HN ↗