2 ms·
Absolutely I could have learned more from that particular project if I'd spent more time with it rather than getting the LLM to do the work... but that's why I
by simonw 3y ago
Absolutely I could have learned more from that particular project if I'd spent more time with it rather than getting the LLM to do the work... but that's why I like it as an example: since it was effectively a distraction (a "side quest") the alternative wasn't learning more, it was not doing it at all (and learning nothing).
I'm able to get really great results out of LLMs because I have 20+ years of experience helping me know what questions to ask of them.
I do feel like my rate of learning has increased though, because I'm much more likely to try out a completely new technology when I know an LLM can flatten the learning curve for me a bit.
- gtirloni 3y ago> I do feel like my rate of learning has increased It's the same for me. Lots of experience knowing what to ask for. It does a better job in summarizing knowledge and getting me a relatively coherent explanation. Much faster than using Google Search to find and connect the dots from dozens of pages. I just don't see much benefit in its reasoning and code assistance features besides basic stuff.
- yawaramin 3y ago> I have 20+ years of experience helping me know what questions to ask of them. That seems rather unlikely given that LLMs didn't exist more than seven years ago, much less 20+.
- Loocid 3y agoThey mean they have 20 years experience in programming, which helps them ask good questions.
- simonw 3y agoYeah, that's what I meant. With LLMs having deep domain knowledge in a field helps enormously in terms of prompting them as productively as possible.
- yawaramin 3y agoSo, to maximize the usefulness of LLMs, requires expert level domain knowledge in a field? Sounds like a useful tool for highly trained experts. For the average Joe Developer, perhaps not.
- skydhash 3y ago> I'm able to get really great results out of LLMs because I have 20+ years of experience helping me know what questions to ask of them. While a direct answer is nice, I like an iterative/explorative process because of all the things I pick up alongside it. An example is when I was working on an epub reader for macOS (side project). I wanted to a native layout engine instead of a webview and I decided to go with muPDF. This has lead me to know more about text layout and rendering, and embedding C inside Swift than I would if I just have direct answers for every problem (if I'd know the correct questions in the first place). I accumulate side quests like that until I can do a nice experiment to learn as much as I can for a particular domain space.
- BoorishBears 3y agoYou're talking right past them though: you were working on a side quest you had interest and bandwidth to iterate on. I agree with the parent comment, my pipeline is already saturated with side quests, I'm already iterating on a bunch of random fun work, and side-project work and work work. So often times the most "LLM-heavy" projects of mine are things I straight up would not do if I didn't have something to get the ball rolling other than more of my own free time which is already in short supply. Hopping from direct answer to direct answer isn't where I find wonder/fun in programming anyways, but sometimes you don't have bandwidth for the side quest to be fun or wonderous.