| ▲ | bryanrasmussen 3 hours ago |
| >Why must there be a dichotomy: "use AI/don't think for yourself", vs "don't use AI/think for yourself"? because studies show that use of AI in subject areas of which one has expertise consistently decreases that expertise? As these subject areas are generally ones with intellectual requirements "use AI" = "Don't Think for Yourself", which underlines well known common sense aphorisms such as "use it or lose it", where the it is the expertise that one stops to use in favor of AI. You lose your ability to think for yourself in your field of expertise, but you gain the AI. |
|
| ▲ | tegling 3 hours ago | parent | next [-] |
| That's kind of the whole question. You're correct, and we're likely heading towards a complete brain-drain if we don't adjust something. But those studies are descriptive. It's what it looks like now. I'm wondering what we can do in order to both have our cake and eat it. How to keep skill and knowledge mastery in humans AND use AI. And it's not helping that education/internships/junior positions are all pivoting for AI use rather than providing a proper learning environment with relevant friction, a curated corpus and time to mold our minds until we truly grok stuff ourselves. |
|
| ▲ | audience_mem 3 hours ago | parent | prev [-] |
| do you think it's not possible for a person to be doing the thinking but AI to be doing the gruntwork? (eg coding) |
| |
| ▲ | bryanrasmussen an hour ago | parent | next [-] | | if I thought that then it would be up to me to explain why the studies that show this is not the case are wrong, if you think that it is then it is up to you do to so and not to try to put the task on to me. In other words, the data shows it is maybe not possible, you think it is, describe why the data is wrong and you are correct. | |
| ▲ | galactus 2 hours ago | parent | prev [-] | | coding = thinking | | |
| ▲ | zahlman an hour ago | parent [-] | | I don't think this is actually true, or rather it's hiding something. We used to not be able to separate the gruntwork from thinking, because even at the level of typing out an individual line of code there's an instinctive review process. But this kind of "thought" is on a different level from the "thought" which led to starting the typing. Not even all the way up at the architecture level, but more the idea of just extracting the essential complexity of the task from the incidental complexity. When I write code by hand and I feel confident about what I'm doing, the confidence comes from knowing that the extraction is generally already done. But I'll still find myself pausing and hesitating, checking for typos, making sure things correspond to their surrounding context… even after decades. It feels like "thinking" in the moment, but not so much when I reflect back on the nature of the task. AI seemingly is not limited by psychology, so it doesn't have these hangups (and of course it also just "types" far faster). It doesn't get an ego boost from being right the first time, and its "confidence" in the compiler, tools and tests is just not relevant. |
|
|