3 ms·
Good article. A very relevant paper worth reading is Programming as Theory Building: https://pages.cs.wisc.edu/~remzi/Naur.pdf https://pages.cs.wisc.edu/~remzi/
by lexandstuff 2y ago
Good article. A very relevant paper worth reading is Programming as Theory Building: https://pages.cs.wisc.edu/~remzi/Naur.pdf https://pages.cs.wisc.edu/~remzi/Naur.pdf.
Programming is not just about producing a program, it's about developing a mental model of the problem domain and how all the components interact. You don't get that when Claude is writing all your code, so unless the LLM is flawless (which it likely never be on novel problems), you won't understand the problem enough to know how to fix things when they go wrong.
- danielbln 2y agoFeels like a bit of a broad statement. I tend to request chunks of work/code that I place into my codebase. I still know what it's for and where it goes, I just care a lot less about the specific implementation details of the chunk, as long as it's typed and passed the smell test. To me it's just one higher rung on the abstraction latter. But it goes to show how difficult it is to discuss this stuff, because depending on model, IDE, workflow, experience/seniority, intuition etc. LLM assisted developmental might look very different in each instance.