Most of us have felt it: after a few solid hours of coding, your brain starts shutting down.
Work for only 3 hours a day, but everyday | plumshell
I am an indie iPhone developer, and I've been working for 3 hours everyday for almost 2 years now. It may not work for everybody, but I started this habit in early 2014, and I have continued to do it since have I found that this is the most productive way to work for me.
Matt Pocock on Twitter / X
There's an AI coding approach that lets you run seriously long-running AI agents (hours, days) that ship code while you sleep. I've tried it, and I'm not going back.It's the Ralph Wiggum approach. Here it is in a nutshell:Run a coding agent with a clean slate, again and again…— Matt Pocock (@mattpocockuk) January 4, 2026
Is full-time work bad for our brains?
If you’re over 40, working more than 25 hours a week could be affecting your intelligence, new research suggests
What AI coding costs you | Tom Wojcik
What's the effect of the prolonged AI usage among coders and is it tracked correctly, if it all?
Why developers using AI are working longer hours
Studies find AI helps developers release more software—while logging longer hours and fixing problems after the code goes live
AI research speeds up. Monitoring gets harder. - Sensemaker
OpenAI says coding agents now run 3.1 days for every human research day, while its chief scientist warns the lab’s main monitoring method is weakening.
How AI coding is reshaping theoretical neuroscience
Agentic coding makes it possible to specify a neuroscience model in hours instead of months. Neuroscientists weigh in on that tectonic change.
Less stress, more productivity: why working fewer hours is better for you and your employer
There’s always too much work to be done on software projects, too many features to implement, too many bugs to fix. Some days you’re just not going through the backlog fast enough, you’re not producing enough code, and it’s taking too long to fix a seemingly-impossible bug. And to make things worse you’re wasting time in pointless meetings instead of getting work done. Once it gets bad enough you can find yourself always scrambling, working overtime just to keep up. Pretty soon it’s just expected, and you need to be available to answer emails at all hours even when there are no emergencies. You’re tired and burnt out and there’s still just as much work as before. The real solution is not working even harder or even longer, but rather the complete opposite: working fewer hours.
What Is Code? If You Don't Know, You Need to Read This
The world belongs to people who code. Those who don’t understand will be left behind.
What Is Code? If You Don't Know, You Need to Read This
The world belongs to people who code. Those who don’t understand will be left behind.
People don't work as much as you think
There is a persistent idea that people work 40 hours a week. They don't, and if you try to do this it will break you. Here are some more reasonable guidelines.
AI #190: Scion of the Times
The amount of code being written at Anthropic continues to rise exponentially.
Doing nothing at work
Many engineers should be doing less work. I don’t necessarily mean producing less code or fewer changes, but literally working fewer hours in the day. When they do work, they should be working at a slower pace. I like to aim to be running at 80% utilization by default: unless I have a high-pressure project going on, I spend 20% of my workday away from the computer.
