4 ms·
Almost every time someone says "but most of my code nowadays is LLM generated" it's usually one of three things: 1. Very greenfield work where the LLM doesn't
by alfalfasprout 2y ago
Almost every time someone says "but most of my code nowadays is LLM generated" it's usually one of three things:
1. Very greenfield work where the LLM doesn't really have a lot of constraints to deal with and can fully control the setup + doesn't have to ingest a lot of existing context
2. Very small projects that largely follow established patterns (CRUD, frontends, etc.)
3. Well established implementation work (the kind of feature that's a simple JIRA ticket).
In my experience they're painfully bad at:
- Novel/niche work where there aren't really answers online to what you're trying to do
- Complex refactoring
- Architecting within existing constraints (other systems, etc.)
- cyanydeez 2y agoI assume it's the commoditized work that made India a success at outsourced activities.
- alfalfasprout 2y agoI suspect it's a lot of that too. Essentially pattern matching.
- darioush 2y agoI think they are counting the autocomplete as well. Yeah when I write golang, and write: result, err := foo(thing) it's gonna autocomplete: if err != nil { return fmt.Errorf("%w: could not foo: %v", err, thing) }