Tangental, but my LSP config breaks every few months. I don't bother to fix it anymore, I open an LLM in ~/dotfiles and complain until it works again, usually in a few minutes. What's interesting is observing how much work this takes. (it gives me much more empathy toward my past self; how was a clumsy human supposed to know and reason about these things!?, especially when I hadn't touched the configs since a few mon…
I have the exact same anecdote; it makes me wonder if this is a common enough use case that a small language model could be trained and run locally for these kinds of “configuration bullshit problems”. I feel like a very large percentage of my Claude usage ends up having it automate configuration shit, because historically that has been the part of software engineering I have always hated.
Grep beats LSP? Why coding agents ignore your fancier tools
61–70 of 80 posts
Re: Grep beats LSP? Why coding agents ignore your fancier tools
#62It is astonishing how easy it is to see the AI hand at work in the writing. Really, it is almost impossible not to see. I don’t get how these people feel it is appropriate to pass off slop like this and not even bother to edit it. Just painful to read.
The author is not a native speaker. The research topic and methodology are manual, along with the first draft of the article, but he eventually did use AI to make the writing "better". It is either this or grammatical slips here and there, which may annoy the same group of people even more. Hope this clarifies things.
Re: Grep beats LSP? Why coding agents ignore your fancier tools
#63Re: Grep beats LSP? Why coding agents ignore your fancier tools
#64It is astonishing how easy it is to see the AI hand at work in the writing. Really, it is almost impossible not to see. I don’t get how these people feel it is appropriate to pass off slop like this and not even bother to edit it. Just painful to read.
The author is not a native speaker. The research topic and methodology are manual, along with the first draft of the article, but he eventually did use AI to make the writing "better". It is either this or grammatical slips here and there, which may annoy the same group of people even more. Hope this clarifies things.
As a non-native speaker, I really hate how people use this as an excuse. LLMs are good at fixing grammatical errors, so I use them daily as spell checkers. Using LLMs for rewriting is just lazy.
Try: I'm learning English as a second language. I will provide you with a text, and you have to print the corrected text in a code block so that I can copy it. Under it, there should be two lists: one containing the errors and brief descriptions of them, and another containing tips for improving the text. Do not give your opinion about the text. Focus on grammar.
Format: [TEXT] C: [CONTEXT]
Re: Grep beats LSP? Why coding agents ignore your fancier tools
#65Re: Grep beats LSP? Why coding agents ignore your fancier tools
#66Earlier quoted context omitted.
The author is not a native speaker. The research topic and methodology are manual, along with the first draft of the article, but he eventually did use AI to make the writing "better". It is either this or grammatical slips here and there, which may annoy the same group of people even more. Hope this clarifies things.
I think it's extremely unlikely that people who are bothered by LLMisms in writing would be more bothered by human grammar slips.
Re: Grep beats LSP? Why coding agents ignore your fancier tools
#67Re: Grep beats LSP? Why coding agents ignore your fancier tools
#68Re: Grep beats LSP? Why coding agents ignore your fancier tools
#69Tangental, but my LSP config breaks every few months. I don't bother to fix it anymore, I open an LLM in ~/dotfiles and complain until it works again, usually in a few minutes. What's interesting is observing how much work this takes. (it gives me much more empathy toward my past self; how was a clumsy human supposed to know and reason about these things!?, especially when I hadn't touched the configs since a few mon…