3 ms·

Honestly, the first article I've seen where the actual usage is explained clearly and matches my own experience. Maybe because I tend to write software the sam

Honestly, the first article I've seen where the actual usage is explained clearly and matches my own experience. Maybe because I tend to write software the same way. The thing I've heard the most from other developers, particular those new to the profession, is that you "have to know most of what you're asking already to know if what you get from the LLM is right." You can use the LLM to learn, but for the actual programming they struggle because they don't have the background to understand the responses well enough to continue the implementation. Also, for the record, C# and .NET, huge enterprise/ecommerce software, so not quite as malleable as bash scripts and what not.

simonw 2y ago
Having a depth of experience helps a lot, because it means you can tell the thing exactly what to do. Effectively you get to treat it as a super-productive intern, very good at taking instructions, occasionally prone to getting stuck in an error loop or falling for weird conspiracy theories.
- throwup238 2y ago
  > falling for weird conspiracy theories So that's why ChatGPT keeps interrupting me with "Have you heard the truth about Y2.038K?!"
franze 2y ago
domain experience in coding helps, but honestly I can now write clojure code without ever touching anything lisp-y before as long as you know how to ask the right questions, formulate the next steps of what you want and what context the AI might need, you are good to go
- redleggedfrog 2y ago
  "I can now write clojure code without ever touching anything lisp-y before" I have trouble with doing that myself. When I personally don't understand the code completely I worry I'm about to step in it. Maybe it's a flaw in my work ethic, but when stuff slips past code reviews and makes it even to QA because I didn't comprehend it well enough I feel bad about it. Maybe a bit too personally attached to the results.

simonw 2y ago

Having a depth of experience helps a lot, because it means you can tell the thing exactly what to do. Effectively you get to treat it as a super-productive intern, very good at taking instructions, occasionally prone to getting stuck in an error loop or falling for weird conspiracy theories.

throwup238 2y ago
> falling for weird conspiracy theories So that's why ChatGPT keeps interrupting me with "Have you heard the truth about Y2.038K?!"

franze 2y ago

domain experience in coding helps, but honestly I can now write clojure code without ever touching anything lisp-y before as long as you know how to ask the right questions, formulate the next steps of what you want and what context the AI might need, you are good to go

redleggedfrog 2y ago
"I can now write clojure code without ever touching anything lisp-y before" I have trouble with doing that myself. When I personally don't understand the code completely I worry I'm about to step in it. Maybe it's a flaw in my work ethic, but when stuff slips past code reviews and makes it even to QA because I didn't comprehend it well enough I feel bad about it. Maybe a bit too personally attached to the results.