Remix.run Logo
daemin 17 hours ago

Using a LLM to fix a spelling mistake is retardedly lazy.

Presumably they used a free version of the LLM, therefore it is completely understandable that it inserted a snippet of text advertising its use into the output. I mean using a free email provider also adds a line of text to the end of every email advertising the service by default - "Sent from iPhone" etc.

hrmtst93837 14 hours ago | parent | next [-]

sed fixes typos faster. The absurd part is watching devs burn prod tokens on glorifed autocorrect, wait through LLM lag for a spelling fix, and then act shocked when the output comes back as word salad with a coupon code glued to the end.

LeoPanthera 16 hours ago | parent | prev | next [-]

This comment is shockingly ableist.

16 hours ago | parent [-]
[deleted]
onion2k 16 hours ago | parent | prev [-]

Using a LLM to fix a spelling mistake is retardedly lazy.

If you do it manually, sure.

If you have an agent watching for code changes and automatically opening PRs for small fixes that don't need a human-in-the-loop except for approving the change, it's the opposite of lazy. It eliminately all those tedious 1 point stories and let's the team focus on higher value work that actually needs a person to think about it.

Given time all small changes will be done this way, and eventually there won't be a person reviewing them.

pabrams 16 hours ago | parent | next [-]

That scenario doesn't require any explicit "summoning", and if there's a human in the loop approving the change, certainly they can fix the typo themself.

ex-aws-dude 16 hours ago | parent | prev | next [-]

Sounds like a great use of energy and tokens, not overkill at all

In fact I don't even use Ctrl + F anymore and instead just use Claude for all my searches

onion2k 15 hours ago | parent [-]

Sounds like a great use of energy and tokens, not overkill at all

As much as AI uses a lot of energy, having something that fixes issues in the background is very likely to be a net saving if you consider the number of users who fail to complete a task due to the bug and have to either wait in a broken state or retry later.

It's probably using less energy than a person fixing the issue too. That's a guess though.

16 hours ago | parent | prev [-]
[deleted]