nostr:npub1nq52crat03tppdmz5xnczxzuyx9qv3xjtrj5af2r5ug5r0tp3teqnvlyhk nostr:npub1pfe56vzppw077dd04ycr8mx72dqdk0m95ccdfu2j9ak3n7m89nrsf9e2dm it's a balancing act, but they can save a lot of time for simple tasks where lightly editing stackoverlow posts is the right answer. Lots of stuff is like that: bash commands with sed/xargs/etc, graphing data with matplotlib... Unless you specialize and do it all the time, it's faster to have the computer make up the code and manually touch it up if needed than to reread the flags section of the sed man page for the 50th time and forget it before the next time you use it.
nostr:npub1pfe56vzppw077dd04ycr8mx72dqdk0m95ccdfu2j9ak3n7m89nrsf9e2dm
It's amazing how many programmers and colleagues tell me they're using it to write software (even bigger programs) because every bit of code I've gotten out of them, if it isn't just buggy and wrong, is clearly mashed together from stack overflow and blog posts.
Which, tbf, these are the kinds of people that would just mash together SO answers themselves. But by getting the LLM to do it, you also gets little hallucinated bugs and extras! And you still learn less than nothing!
Discussion
nostr:npub1ve7g5q4lsth9z6n39mt9sctj8708sxcn465ucm8m9fancgg02l3ql8ydyh nostr:npub1nq52crat03tppdmz5xnczxzuyx9qv3xjtrj5af2r5ug5r0tp3teqnvlyhk this is an unrelated use of the technology, but my personal experience is that they don’t function very well for this. When senior engineers use it we discover that the output is riddled with errors and it’d be faster to configure our editors to just generate any boilerplate that we need frequently. When junior engineers use it they produce code riddled with errors they’re not catching. If we’re lucky they’re just bugs and not vulnerabilities. https://gist.github.com/0xabad1dea/be18e11beb2e12433d93475d72016902