upvote
The paradox of LLM usage: the best way to use an LLM well in a domain is to know the domain, but if you spend all your time using LLMs, your domain knowledge may atrophy.
reply
The thing is you pick up different domain knowledge. I was using AI to experiment with computer vision stuff last week, and I learned so much about hardware sensors, about accelerometers, magnetometers. I learned about the relationships between pixels and millimeters when you're talking about cameras in some reference frame. I learned about how the speed of light relates to the time it takes for wifi and bluetooth to send a message through household objects. I learned about how sound reflects in spaces and how different frequencies are picked up by microphones in different kinds of hardware I have.

There's so much to learn in the world. The domain knowledge I used to carry about software, I hope I forget most of it. I hope I learn things that let me do things I never could've conceived of before.

reply
The knowledge you gain by reading someone else's solutions is real but not as sticky as what you pick up by working out a solution yourself. I fear we are well on our way to the second type being a thing of the past.
reply
I wasn't just "reading solutions" I was wandering around my house with different devices, repositioning them, taking video, thinking about how to figure out what was going on. The code is never the point, it's the means to an end, the problems I'm trying to solve, the code is only one piece among many.
reply
Understanding "beneath" is a good idea. I used the free version of Grok to generate some Ansible scripts. I don't use Ansible often enough to be really adept, and I appreciated some help.

It was pretty good, understood what I wanted to do, and broke it up in playbooks/roles/etc. quite well. But then it did things like continuously overwrite the LetsEncrypt cert for each domain with the next one in a loop. It understood "this needs to be a loop" and how to optimize that loop, but not that it was going to overwrite each domain's key with the next.

I'm a pretty good sysadmin, so I recognized this and could take what it did and fix it, but it required a deeper understanding of the underside of nginx/LetsEncrypt and the filesystem to even see what it was doing.

Of course, once you run the playbook, test a domain and see its SSL cert is all jacked up you'll go looking for WTF happened, but just blindly taking the output as given meant it was horribly broken.

It may be that Ansible, by its nature, is a bit sui generis because it touches so many unconnected domains, and therefore is harder than outputting Python. I don't know. But one needs more than a surface level understanding of those domains if you want to catch the LLM being stupid.

reply