To add a single example here (feel free to chime in with your own):
Problem: editing code is sometimes tedious because external APIs require boilerplate.
Solutions:
- Use LLM-generated code. Downsides: energy use, code theft, potential for legal liability, makes mistakes, etc. Upsides: popular among some peers, seems easy to use.
- Pick a better library (not always possible).
- Build internal functions to centralize boilerplate code, then use those (benefits: you get a better understanding of the external API, and a more-unit-testable internal code surface; probably less amortized effort).
- Develop a non-LLM system that actually reasons about code at something like the formal semantics level and suggests boilerplate fill-ins based on rules, while foregrounding which rules it's applying so you can see the logic behind the suggestions (needs research).
Obviously LLM use in coding goes beyond this single issue, but there are similar analyses for each potential use of LLMs in coding. I'm all cases there are:
1. Existing practical solutions that require more effort (or in many cases just seem to but are less-effort when amortized).
2. Near-term researchable solutions that directly address the problem and which would be much more desirable in the long term.
Thus in addition to disastrous LLM effects on the climate, on data laborers, and on the digital commons, they tend to suck us into cheap-seeming but ultimately costly design practices while also crowding out better long-term solutions. Next time someone suggests how useful LLMs are for some task, try asking yourself (or them) what an ideal solution for that task would look like, and whether LLM use moves us closer to or father from a world in which that solution exists.
STO stream is LIVE from Linux! Get ready for some space adventures on Twitch! #STO #LinuxGaming
High-gain model-following control for trajectory tracking
Nicals Tietze, Kai Wulff, Johann Reger
https://arxiv.org/abs/2506.13463 https://
Nonlinear Joint Spectral Radius
Piero Deidda, Nicola Guglielmi, Francesco Tudisco
https://arxiv.org/abs/2507.11314 https://arxiv.org/…
Creating a beautiful Wood Style Plant Pot with the perfect soundtrack: 80s synthwave! ✨ Join the 3D printing stream on Twitch and unwind with us. #3DPrint
Die ePetition 180634 an den Bundestag aus dem Bereich Lebens- und Genussmittel mit dem Titel
Verhinderung der Lebensmittelverschwendung in Produktionsstätten
kann bis zum Donnerstag 24. Juli 2025 01:00 UTC mitgezeichnet werden und lautet
Mit der Petition wird gefordert, die Lebensmittelverschwendung in Produktionsst…
MK2 at PBIG Competition: A Prompt Generation Solution
Yuzheng Xu, Tosho Hirasawa, Seiya Kawano, Shota Kato, Tadashi Kozuno
https://arxiv.org/abs/2507.08335
Continued Rapid Radio Brightening of the Tidal Disruption Event AT2018hyz
Yvette Cendes, Edo Berger, Paz Beniamini, Ramandeep Gill, Tatsuya Matsumoto, Kate D. Alexander, Michael F. Bietenholz, Aprajita Hajela, Collin T. Christy, Ryan Chornock, Sebastian Gomez, Mark A. Gurwell, Garrett K. Keating, Tanmoy Laskar, Raffaella Margutti, Ramprasad Rao, Natalie Velez, Mark H. Wieringa
I have seen toots warning about this and wanted to comment on it.
They are impersonating the Mastodon team to require users to ‘verify their account’ and saying that until they do this their account is suspended.
Verification on mastodon is free and you can do it yourself without giving any personal information and it is TOTALLY OPTIONAL.
No server/instance is going to require verification.
I have my verification with my neocities page, on tkz.one, misskey.social and …