惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Martin Fowler
Martin Fowler
Jina AI
Jina AI
J
Java Code Geeks
Microsoft Security Blog
Microsoft Security Blog
Recent Announcements
Recent Announcements
I
InfoQ
L
LangChain Blog
The Cloudflare Blog
IT之家
IT之家
博客园 - 叶小钗
Apple Machine Learning Research
Apple Machine Learning Research
B
Blog
A
About on SuperTechFans
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Last Week in AI
Last Week in AI
Blog — PlanetScale
Blog — PlanetScale
罗磊的独立博客
云风的 BLOG
云风的 BLOG
Microsoft Azure Blog
Microsoft Azure Blog
Engineering at Meta
Engineering at Meta
F
Fortinet All Blogs
博客园 - 聂微东
美团技术团队
博客园_首页

Lobsters

CIFSwitch: a non-universal Linux local root vulnerability RIPE NCC session fixation: poaching logins with an Atlas probe GNOME 2.20 but its Web Components Agentic Search for Context Engineering – Leonie Monigatti Garnix is shutting down [not OC] akashina.tngl.sh/jjc Concerning Emacs (and Jazz) Nitpicking the shell history scene in ‘Tron: Legacy’ What's cooking on SourceHut? Q2 2026 The tenth OpenPGP email summit Package managers that package package managers Clojure on Fennel part three: parsing WordPress at 23 Finding Miscompiles for Fun, Not Profit GitHub - creusot-rs/creusot: Creusot helps you prove your Rust code is correct. Announcing Rust 1.96.0 | Rust Blog A Love Letter to Neovim sqlite AGENTS.md Am I a Bad Friend? CSS vs. JavaScript • Josh W. Comeau Erlang Ecosystem Foundation - Supporting the BEAM community A brief note about slot access cost in Common Lisp Keyboard latency probe Rethinking the GNOME clipboard issues Back to the Building Blocks’ Building Blocks Tech Notes: Theseus: translating win32 to wasm Fast is better than slow Content-addressed Rust builds (or, what kache actually caches) Intent to Prototype: Embedding API Canada’s Bill C-22 and the security cost of collecting more data
The Exhaustion of Talking to a Tool
2026-06-26 · via Lobsters

LLMs are exhausting because they require spending precious social energy to operate them. Energy that might be better spent on people.

When you use a good tool, your brain pretends that the tool is a part of your body: when you drive a car, when you type on a keyboard or when you hit that key chord to do that thing in Vim or VSCode. In contrast, when you talk to somebody, you are participating in a social ritual: share a fire, tell a story, help me close this ticket so we don’t have to drag it to the next quarter because my manager will chew me out. Obviously, the social brainwork is harder and requires much more of you.

When you use an LLM, you don’t get the tool magic: (almost) nobody will claim that Claude or Cursor feel like an extension of their body - they are not consistent or fast enough to trick the brain like a keyboard or a car can. Instead, you get to pay the social tax: you converse and negotiate and convince and sometimes even get angry1 at the so-called tool.

But the social tax is only worth paying because people give you so much more in return: they teach you something new, or challenge you, or inspire you, or tell you to GTFO if you are trying to BS them - or you might teach someone something, challenge them, or even inspire them! On days when I have these interactions I might be tired at the end of the day, but it was worth it.

With LLMs, you mostly just get more of the same: more code, more tests, more excuses. Sometimes you get more bug reports which I do appreciate.

Is it worth the social brainwork? IDK, for some tasks maybe - there are things a single person can do now that would have been impossible a year ago. But for all tasks? And wouldn’t that social brainwork do more good if it was directed at the real people you are working with?

LLMs ask us to talk to them, but rarely reward that effort in kind.

Discuss on lobste.rs.

Carpentry tools recovered from the wreck of the Mary Rose, a 16th-century sailing ship

Carpentry tools recovered from the wreck of the Mary Rose, a 16th-century sailing ship By the Mary Rose Trust, CC BY-SA 3.0