I feel the opposite. Interacting with humans, I definitely pay a social tax - I have to negotiate the feelings of the people involved. With LLMs there is no social tax, I can be as blunt as I like. But there are other taxes to pay with LLMs; they don't learn, they BS relentlessly, there is less fun and camaraderie.<p>But "social tax"? No, there is not a social tax.
Agreed, I haven't yet internalized them not remembering feedback from a couple days ago, which humans typically would. The process of remembering to update the context isn't entirely natural to me to this day.
There are ways to put a superficial personality on the LLM which can break up some of the mannerisms that get old. Give it a new accent, allow it to keep a memory of things that nudge it into one personality or another, make it behave differently on weekdays vs weekends. Its still superficial, but if you work with it any reasonable amount of time, I think having the ability to change some of the characteristics can make it more..."fun" I guess.
I agree. I’m a social person but I also like my purely functional conversations with LLMs, and I have a lot of them going at once!<p>Doesn’t replace conversations with other people but at the same time I feel no tax talking to the LLMs.
The first-order social consequences aren't truly there but i think the format in which you interface with the tool can trick you into behaving as if they were, which is taxing it itself.
One giant issue with say Claude Code is the speed, say you ask it to do something and you want to review the response, then I want to ask questions , I want to chat about the changes , but the slow speed of responses it just breaks the flow.<p>Unfortunetly now vibe coding is demanded to be used, to produce 10x more code or else some other developer will take your place.
> With LLMs there is no social tax, I can be as blunt as I like. But there are other taxes to pay with LLMs; they don't learn, they BS relentlessly, there is less fun and camaraderie.<p>My experience is the opposite. They bullshit a lot, derail the conversation/coding session, get defensive, and gaslight. It is not “social tax”, but they mirror sometimes the worst human behaviour.
Man, I don't know. LLMs (with the good and bad) feel like the first time a tool has genuinely been an extension of me. And quite the opposite. I'm a quite introverted person. Spending time in a meeting or talking with other humans I find quite exhausting. I don't really get that at all with talking with LLMs.
Most of my workflows have slowly moved away from the chat interface with llms. Instead they look more like traditional Unix pipelines that just happen to call Unix tools that interact with llms.<p>This allows me to make more repeatable processes, not be tied down to vendor implementations of workflows and mix and match models for cost and efficacy.<p>There is nothing that ties you to talking with the text generator black box, and for most of my use cases it’s a negative.
> 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.<p>These all seem the same to me? None of them are an "extension of my body"; they're tools I use.<p>> With LLMs, you mostly just get more of the same: more code, more tests, more excuses.<p>You get more specs, more plans, more code, more tests. If you're getting excuses, something's wrong.<p>> Is it worth the social brainwork?<p>There isn't any social brainwork. I'm using natural language to build things, not engaging in social discourse.<p>> LLMs ask us to talk to them, but rarely reward that effort in kind.<p>Nor should they! They're not people, but they're designed to reach goals. If you set a goal (explicitly or implicitly) that you want a social conversation, they'll try to satisfy (and do poorly).
I feel on the other side of this. Just yesterday I was reviewing some code output from Claude and I realized a change that I had asked for in a previous review step wasn't what I wanted. I had a moment of social anxiety, like I didn't want to bother a coworker with my indecision. But I have to remember, the LLM doesn't care. It doesn't have an ego. It doesn't get annoyed at being asked to redo work.<p>I still say "please" and "thank you" frequently, but I'm starting to embrace the fact that the LLM doesn't care about grunt work, doesn't care about rework, doesn't care about nitpicking, doesn't have a preference in general. It needs very little more than for me to be completely clear in my instructions.
Sorry to hear about the moment of social anxiety (I assume it happens with humans occasionally). But can't wonder don't you have also moments of joy because of job well done, an appreciative colleague or something similar?<p>I don't like either the "negative" part, but I find it necessary to have both negatives and positives in life to create bonds, meaning and more simply, not to get bored. I would be worried that if I just talk with a machine (no feelings involved) I will get depressed and demotivated.
It can't be bargained with. It can't be reasoned with. It doesn't feel pity, or remorse, or fear! And it absolutely will not stop, ever, until … the project is complete?
I talk almost exclusively with AI these days. There's no one around me who knows programming, I get tired of reading code for projects I'm not interested in, and the projects I am interested in are too difficult, so I just talk with AI, organize my thoughts, and read books.<p>There's no one around me who does programming. There are hardly any programmers in my town.<p>The upside is that most programming-related tasks in my town end up going through me. The downside is that there's not much work to begin with, and I can't talk about the things I'm actually interested in.<p>I'd like to stay in touch with friends who are interested in programming or academia, but since I didn't go to a good university, it seems like I haven't had much of a connection with them
Could you imagine how destroyed people like this would be if they faced actual adversity in life? Like if they had to live through the Spanish Flu, or the Great Depression, or hell even lose a loved one to something as now trivial to treat as tetanus?<p>Oh, the horror, having to type to a system that will do your job for you while you sit in an air conditioned office in a comfortable chair listening to a podcast while you work.
I’ve been experiencing similar feelings. Working with LLMs often takes almost as much mental energy as working with people, but the payoff does not always scale in the same way.<p>I think we are still on the early days of LLMs. Right now, using them productively requires deliberate thought and an acute knowledge of their limitations. As the author says, it’s easy to get angry at a model, or to foolishly let it nudge you towards more code and more tests — even when that is suboptimal.<p>To a certain extent, models keep getting better and better at discerning our intentions and providing value. Yet I am not sure whether we will reach a point where using them successfully no longer causes the kind of fatigue that it does today.
Not my experience, but I'm still new at this.<p>The way I have worked so far is to look for ways I can influence the model's "thinking" and then add that to my main AGENTS.md. I try to steer it towards a thought process that mirrors or exceeds my own. I find it a fun challenge. I think this stuff becomes less necessary in a year or so as these sorts of tweaks become part of the shipped product from the model makers.
I just use it as Google, like 'ts Omit example' or something.<p>so I don't get exhausted. If you write complete sentences and say please to the clankers, you're definitely gonna waste energy.<p>I agree they are too slow though, especially when they "Think" for so long and then say "something went wrong" after 30s.
I think it depends. If talking to a tool solves a bigger exhaustion (a bug that has been bugging you for a while) then the exhaustion from talking to the tool becomes normalized. I guess this is true for any tool really. Using a hammer causes a bit of strain in your muscles but if it solves a bigger issue of nailing something in the wall then that strain in the muscle is fine. It will take some time to develop that muscle working with AI too.
My exhaustion comes from how long winded LLMs are. I ask simple questions and get an essay with bullet points.
The productivity gains are well worth any nits I have about responding to the LLM.<p>LLM: "I've just refactored your code base. Would you like me to also fully document it?"<p>op: "you're so needy!!!"
> When you use an LLM, [...] you get to pay the social tax: you converse and negotiate and convince and sometimes even get angry1 at the so-called tool.<p>Might be a subjective opinion, but this is how writing code always felt to me, even pre-LLMs. An ongoing inner conversation where I try to convince the text on the screen to match the text in my head. It never really felt like tool use in the sense of manual labor.
Looks like the author submitted it themselves to lobste.rs. Some nice discussion there, as well.<p><a href="https://lobste.rs/s/csgzki/exhaustion_talking_tool" rel="nofollow">https://lobste.rs/s/csgzki/exhaustion_talking_tool</a><p>As an aside, it's nice to see that Lobsters has remained a quiet success. As much as I love HN and the work Dan's done to keep it how it is, I welcome to variety. There are vanishingly few places for polite and earnest discussion online these days.
i read this post while AI was busy managing jira tickets for me. Otherwise I wouldn't have had the time to be browsing HN right now
AI is the new dope for developers.<p>Introverts are first line of serious addicts.<p>ADHD developers are next.<p>Procrastinators are after that.
I feel this. These tools are viscerally unpleasant. Meetings used to be the thing I didn't look forward to but chatting with an AI is the new low point. Reading AI generated text is the written word equivalent of nails on a chalkboard.
I talk to my AI all day. Sometimes my voice goes hoarse
>> 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?<p>It's the opposite. Many people find it exhausting to interact with humans, and do so only because they are required to.<p>Humans often don't understand what you are saying or asking, and they may not know exactly what steps they need to take to find the answer. They get tired. They might get their pride hurt. They might get angry or frustrated. They might judge you because your question is silly or just wrong.<p>LLMs, for all their faults, have none of these issues. I'm not saying I'd rather talk to LLMs all day every day, but when trying to get shit done, they really can be the superior coworker, especially if you're an introvert and suffer from social-battery-drainage issues.
Fooling yourself into thinking the LLMs are "understanding" what you are saying or asking is a trap. The output you get may be useful, but it is not due to any sort of understanding.<p>The elements of human work you mentioned are why it can be both rewarding and painful to interact with humans, but at the end of the day it is important to keep trying to do that work/keep trying to interact with each other. I don't know if we want to go back to cubicles where we just talk to robots all day. Of course some work environments are just awful, and there is not much remedy for that.
>> Fooling yourself into thinking the LLMs are "understanding" what you are saying or asking is a trap. The output you get may be useful, but it is not due to any sort of understanding.<p>I hear this a lot but I think it's a matter of semantics and ultimately not very useful. I don't care whether the LLM <i>understands</i> me the way a human would. I use the LLM to get useful output. I want it to do something and it does that thing.
[flagged]
[flagged]
[flagged]