3 ms·
you're being silly. there are definitely cases in life where "verifying an answer" is much less effort than "producing an answer" (public key cryptography is b
by bananapub 1y ago
you're being silly. there are definitely cases in life where "verifying an answer" is much less effort than "producing an answer" (public key cryptography is built on this!). an obvious example is "writing boring code". I can much more quickly review the code to a simple little custom web app than I can sit down and write it. that's great! as a bonus, no one dies if my little dashboard crashes on invalid input or whatever. another thing might be marketing copy - no one really cares if it's good or not and 500 "OK" words on a topic might take an hour to write but five minutes to read and correct the grammar of.
an example of things that are the opposite is "public policy development", which is why it's simply malicious that various corrupt oligarchs are pushing for it to be used for such things.
so, a simple model for you to understand why other people might find these tools useful for some things:
- low stakes - doesn't matter that much if the output isn't Top Quality, either because it's easy to fix or it just doesn't matter
- enormous gap in cost between generation and review - e.g. coding
- review systems exist and are used - I don't care very much if my coworkers use an LLM to write code or not, since all the code gets reviewed by someone else, and if the proposer of the change doesn't even bother to check it themselves then they pay the social cost for it
- imiric 1y agoThe intentional disregard for software quality in your comment is honestly disturbing. If your quality threshold is so low that you can tolerate crashes on invalid input, you will certainly cut corners when building software for others. I wouldn't want to use a piece of software you wrote, let alone have you on my team. > I don't care very much if my coworkers use an LLM to write code or not, since all the code gets reviewed by someone else Ah, yes, let's kick the can down the road. > if the proposer of the change doesn't even bother to check it themselves then they pay the social cost for it ... The side effects of shoddy code are not redeemed by "paying a social cost". They negatively impact your users, and thus the bottom line of your company.
- bananapub 1y ago> The intentional disregard for software quality in your comment is honestly disturbing. why? my shitty sales dashboard at work doesn't control a rocket or a pacemaker. the crappy my-weird-org-mode-table-to-re-arranged-CSV convertor isn't either. not all software is safety critical, and in any case, I'm the human who ran the code generator and then the code and I'm responsible for my dashboard crashing or my convertor deleting the photos of my cat. should an LLM replace human code review? no. can I use an LLM for my own dumb projects? of course.