3 ms·
The reason you can use these tools so effectively across native, mobile, Go, React etc is that you can apply most of what you learned about software development
by simonw 1y ago
The reason you can use these tools so effectively across native, mobile, Go, React etc is that you can apply most of what you learned about software development as a Python engineer in these new areas.
The thing LLMs replace is the need for understanding all of the trivia required for each platform.
I don't know how to write a for loop in Go (without looking it up), but I can write useful Go code now without spinning back up on Go first.
I still need to conceptually understand for loops, and what Go is, and structured programming, and compilers, and build and test scripts, and all kinds of other base level skills that people without an existing background in programming are completely missing.
I see LLMs as an amplifier and accelerant. I've accumulated a huge amount of fuzzy knowledge across my career - with an LLM I can now apply that fuzzy knowledge to concrete problems in a huge array of languages and platforms.
Previously I would stay in my lane: I was fluent in Python, JavaScript and SQL so I used those to solve every problem because I didn't want to take the time to spin up on the trivia for a new language or platform.
Now? I'll happily use things like Go and Bash and AppleScript and jq and ffmpeg and I'm considering picking up a Swift project.
- anon7000 1y agoCompletely agree. And along the way, my personal knowledge of bash has increased a lot, for example, just because I’m using it a lot more
- giancarlostoro 1y agoLLMs are search engines not robots you can automate things with search engine results but you can also accidentally automate NSFW being delivered to customers. Use the right tools correctly.
- deleted 1y ago[deleted]
- snoman 1y agoThis is difficult to express because I too have enjoyed using an LLM lately and have felt a productivity increase, but I think there is a false sense of security being expressed in your writing and it underlies one of the primary risks I see with LLMs for programming. With minor exceptions, moving from one language to another isn’t a matter of simple syntax, trivia, or swapping standard libraries. Certainly, expert beginners do espouse that all the time, but languages often have fundamental concepts that they’re built that and need to be understood in order to be effective with them. For example: have you ever seen a team move from Java to Scala, js to Java, or C# to Python - all of which I’ve seen - where the developers didn’t try to understand language they were moving to? Non-fail, they tried to force the concepts that were important to their prior language, onto the new one, to abysmal results. If you’re writing trivial scripts, or one-off utils, it probably doesn’t build up enough to matter, and feels great, but you don’t know what you don’t know, and you don’t know what to look for. Offloading the understanding of the concepts that are important for a language to an LLM is a recipe for a bad time.
- nojito 1y agoHow about converting a rust library into Haskell? https://ghuntley.com/oh-fuck/ https://ghuntley.com/oh-fuck/ That's from 6 months ago and the tooling today is almost night and day in terms of improvements.
- fleebee 1y agoWhere can I see the code? Also: > This wasn't something that existed; it wasn't regurgitating knowledge from Stackoverflow. It was inventing/creating something new. Didn't he expressly ask the LLM to copy an established, documented library?
- simonw 1y agoYes, but in another language. It wasn't regurgitating Haskell code it had seen before.
- snzixjxjxjsn 1y ago
- AstroBen 1y ago100%. LLMs aren't good engineers. They're mediocre, overengineering, genius, dumb, too simplistic, clean coding, overthinking, underthinking, great but terrible engineers rolled into one. You can get them to fight for any viewpoint you want with the right prompt. They're literally everything at once To get good code out of them, you have to understand what good code is in the first place and lead them to it My experience is iterating through 5 potential options being like "nope, that wont work, do it this way.. nope adjust that.. nope add more of this.. oh yeah that's great!" The "that's great!" made me nervous that an LLM was capable of producing code as good as me until I realized that I threw out most of what it gave.. and someone less experienced would've taken the first suggestion without realizing its drawbacks
- simonw 1y ago> To get good code out of them, you have to understand what good code is in the first place and lead them to it That's a great way of putting it. Completely agree.
- qsort 1y agoThis is 100% the rational response I'd give to OP, but I can't deny I feel a bit of the same unease. It's mostly that this technology is really... weird, I think. I struggle to put that into words if I'm being honest.
- pglevy 1y agoThis way of putting it resonates with me: unlocking the value of fuzzy knowledge.
- kiitos 1y ago> Previously .. I didn't want to take the time to spin up on the trivia for a new language or platform ... Now? I'll happily use things like Go and Bash and AppleScript and jq and ffmpeg It's pretty wild that you're characterizing the understanding of a language and its details as "trivia" that you don't need to "take the time to spin up on" before you write programs in that language. I mean, I get this perspective, but it's the position of a product manager, not a software engineer...
- simonw 1y agoI stand by what I said. Knowing how to eg loop through every file in the current directory in Bash is trivia. That's not to say it's trivial, or to disparage that knowledge. But it's not at the same level as understanding how eg Unix processes can be piped together. If I'm interviewing a candidate and they can't remember the syntax for a Bash loop, I don't care. If they can't explain what happens when you pipe output from one process to another (at least at a high level), that's a problem.