For me personally, programming lost most of it's fun many years ago, but with claude code I'm having fun again. It's not the same, but for me personally, at this stage in my life, it's more enjoyable.
I think we much too often forget that the domain of software development has expanded its reach into literally everything and that we share a guild hall with all kinds: those who write deeply safety critical correct code, those who are hacking a blender, those who are just making their clerical task less repetitive, etc.
Every time you chill out and come back to work, you will have to invest that extra bit of start-up energy. Which can be draining.
(* probably has to do with reloading your working memory)
(In all seriousness though, it's probably not good for your health.)
I'm wholly unwilling to relinquish my health and my morals to "AI" so I can "ship faster." What a pathetic existence that would be.
I do not smoke myself, but it made me realize how little I know regarding THC and CBD
Long-term use causes the psychedelic part of THC effects to diminish over time. At some point, only a mild depressant effect remains - somewhat similar to chamomile. It does have some effect on intelligence and short-term memory, but if the alternative is to be too stressed to think at all, it might be better to just smoke.
Obviously, if possible, psychotherapy or a prescription from a psychiatrist (or better yet, a change of environment) would be better (in the latter case, it depends on the prescribed drug, of course), but THC is not that bad an alternative where it's legal.
Engineer teams are nothing but an annoying expense on the balance sheet and the goal is to cram as many features, as quickly as possible to get the sale.
That's exactly why I'm happy to use every tool available to get the work done efficiently. To this end, LLMs have been great for me, especially when dealing with large amounts of boilerplate code.
Long gone the days of crafting artisan code.
Of course, I know the next layoff will come. So I simply want to use the next time of stability to make sure I can be that artisan the next time industry kicks me out. But baby steps for now.
Every bit of coding that did anything other than give me meaningful progress on features on the thing I was actually trying to build, which at times was 80%+ of it, was always terrible.
There are plenty of articles on review fatigue including https://www.exploravention.com/blogs/soft_arch_agentic_ai/ which I published recently. The focus there is less about the impact on the developer and more about the impact on the organization as letting bugs go to production will trigger the returning to high ceremony releases and release anxiety.
The OP article talks about AI fatigue of which review fatigue is a part. I guess that I would sum up the other parts like this. The agentic AI workflow is so focused on optimizing for productivity that it burns the human out.
The remedy is also not new for office work, take frequent breaks. I would also argue that the human developer should still write some code every now and then, not because the AI cannot do it but because it would slow the process down and allow for the human to recover while still feeling invested.
Never used headphones - if the environment is too loud, make it quieter. I once moved into a new office area that had a dot-matrix printer that "logged", in the worst sense of the word (how could you find any access on such a giant printout), every door open/close in the block. It was beyond annoying (ever heard a DM printer? only thing worse is a daisy wheel) so I simply unplugged it, took out the ink ribbon and twisted off the print head. It was never replaced, because as is very often the case nobody ever used the "reports" it produced.
>if the environment is too loud, make it quieter.
we shifted to open office setups over the decades. There may not even be anyway to make things "quieter" externally.
That said I don't dispute the value of agents but I haven't really figured out what the right workflow is. I think the AI either needs to be really fast if it's going to help me with my main task, so that it doesn't mess up my state of flow/concentration, or it needs to be something I set and forget for long periods of time. For the latter maybe the "AIs submitting PRs" approach will ultimately be the right way to go but I have yet to come across an agent whose output doesn't require quite a lot of planning, back and forth, and code review. I'm still thinking in the long run the main enduring value may be that these LLMs are a "conversational UI" to something, not that they're going to be like little mini-employees.
But LLM prompting requires you to constantly engage with language processing to summarize and review the problem.
It helps that I don't outsource huge tasks to the LLM, because then I lose track of what's happening and what needs to be done. I just code the fun part, then ask the LLM to do the parts that I find boring (like updating all 2000 usages of a certain function I just changed).
To me, flow is a mental analogue to the physical experience of peak athletic output. E.g. when you are are at or near your maximum cardiovascular throughput and everything is going to training and plan. It's not a perfect dichotomy. After all, athletics also involve a lot of mental effort, and they have more metabolic side-effects. I've never heard of anybody hitting their lactate threshold from intense thinking...
My point is that the peak mental output could be applied to many different modes of thought, just as your cardiovascular capacity can be applied to many different sports activities. A lot of analogies I hear seem too narrow, like they only accept one thinking task as flow state.
I also don't think it is easy to describe flow in terms of attention or focus. I think one can be in a flow state with a task that involves breadth or depth of attention. But, I do suspect there is some kind of fixed sum aspect to it. Being at peak flow is a kind of prioritization and tradeoff, where irrelevant cognitive tasks get excluded to devote more resources to the main task.
A person flowing on a deep task may seem to have a blindness to things outside their narrow focus. But I think others can flow in a way that lets them juggle many things, but instead having a blindness to the depth of some issues. Sometimes, I think many contemporary tech debates, including experience of AI tech, are due to different dispositions on this spectrum...
My inner dialogue is always chatty; that doesn't stop when I enter a flow state. It just becomes far more laser focused and far less distracted. LLMs help to maintain the flow because I'm able to use it to automate anything I don't care about (e.g. config files) and troubleshoot with me quickly to keep the flow going.
Standing desk, while it's working I do a couple squats or pushups or just wander around the house to stretch my legs. Much more enjoyable than sitting at my desk, hands on keyboard, all day long. And taking my eyes off the screen also makes it easier to think about the next thing.
Moving around does help, but even so, the mental fatigue is real!
I suffered from the problems you describe, grabbing a browser window or my phone which would usually take my attention much longer than the task and it left me burned out at the end of the day.
There are some helper tools, like blocking "interesting" pages (like HN, reddit) on the browser, putting the phone in the bag at the end of the room or using a pomodoro timer so sequence proper breaks. But at the end the only thing that really helped is getting into meditation: I try to use these little interruptions of flow as a opportunity to bore myself. Try to reframe boredom from being an annoyance that needs to be fought to a chance to relax your brain for a couple of seconds and refocus.
The want to grab the phone is hard at the start, but it gets better very soon when you manage to push through the discomfort in the first days.
EDIT: I wanted to add that I think it's a great time to get back to it because this mental fatigue has been leading me to migrate to more analog tools, like pen and paper for journaling and ditching my smartwatch for analog ones.
LLMs force me to context switch all the time.
Today Anthropic started offering 3x(?) Opus speed at 5x cost as well.
What will have to change are workflows. Why are you ever waiting for the prompt to return? When you send an email, do you stare at your screen until you get a reply?
Probably more stress if I’m on battery and don’t want the laptop to sleep or WiFi to get interrupted.
I try to fix it by having multiple opencode instances running on multiple issues from different projects at the same time, but it feels like I'm just herding robots.
Maybe I'm ready for gastown..
Edit: Looks like plenty of people have observed this: https://www.reddit.com/r/xkcd/comments/12dpnlk/compiling_upd...
(Also, this only applies if what you're working on happens to be easily parallelizable _and_ you're part of the extremely privileged subset of SV software engineers. Try getting two Android Studios/XCodes/Clang builds in parallel without 128GB of RAM, see what happens).
But yeah improving build speed & parallel running I think are one of the biggest advances devs can do to speed up development time in the AI age. With native apps that can be a challenge. I restructured a react native project to make it faster to iterate, but I have a feeling you might not be fond of rn.
With all due respect, the commment does carry the vibes of "it's okay I can totally multitask" that's nearly a cliche in programming. It just feels a bit insensitive to respond to an article talking about context switching being a big problem with LLMs and then suggest the biggest possible context switch of managing multiple workstations.
And yes, your hardware expenditure will vary per industry. I can barely run one instance of Unreal Engine as is.
Going back from writing an email to working, versus going back from email to reviewing someone else's work feels harder.
e.g. managing systems, initiating backups, thinking about how I'll automate my backups, etc.
The list of things I haven't automated is getting shorter, and having LLMs generate something I'm happy to hand the work to has been a big part of it.
I don’t just give somebody a bit’s ticket a let the go. I give them a ticket but have to hover over their shoulder and nitpick their design choices.
Tell them “you should use a different name for that new class”, “that function should actually be a method on this other thing”, etc
The output is still small and I can review it. I can switch tasks, however if it's my primary effort for the day I don't like stepping away for an hour to do something else.
But the cycle is longer. When you help a person they don’t come back to you 4 minutes later.
I also only review PRs at specific times a day, because that’s more cognitively intensive and switching in and out pretty much ensures you’ll do it badly.
Either way, I’m really starting to think agentic as designed is a deeply flawed workflow. The future could be small, fast models that finish pseudo code and look stuff up to aide focus. Anthropic’s own research seems to support this.
The waits are unpredictable length, so you never know if you should wait or switch to a new task. So you just do something to kill a little time while the machine thinks.
You never get into a flow state and you feel worn down from this constant vigilance of waiting for background jobs to finish.
I dont feel more productive, I feel like a lazy babysitter that’s just doing enough to keep the kids from hurting themselves