How a Software Engineer Rebuilt His Brain in 30 Days Offline

Daniel's vacation experiment showed he could finish two books in a week—something he hadn't done in eight years.

AI is making your brain slower, not faster. That's the provocative diagnosis Daniel, a software engineer, arrived at after noticing his own thinking had become hazier, lazier, less profound—despite being more productive than ever. Watch the full video or listen to the podcast version for his complete story.

The Productivity Trap

When Daniel started programming, everything was genuinely hard. Problems felt alien. He'd come home mentally wrecked. That's what real cognitive effort looks like. Fast forward years later: nothing's novel anymore. Solving problems is just about time investment. Add AI into the mix, and sure, output increases. But productivity and sharpness are not the same thing.

The second half of the problem is dopamine infrastructure. Shorts, video games, manga, TV—an endless buffet of low-friction content. He literally cannot get bored anymore. And if you never get bored, you never get the itch to do anything hard.

Measuring the Damage

Daniel picked one metric to track his cognitive decline: books read. Before university, he devoured books every night. During his History undergrad, he was consuming over 1,200 pages per week. When he picked up programming, he stacked coding books and documentation on top. He was a reading machine.

Then came the first software engineering job. The reading stopped. Eight years ago. He was too tired. Whatever reading happened during the day was just documentation—not the same thing. Over the past year, he tried to fix it: handwriting, side projects, blogging. Small wins. But nowhere close to where his brain had been.

The Vacation Experiment

So he tried something radical: actual vacation. No optimization hacks. He and his wife went to the countryside to visit family—slow time, nature, his dog, board games, watching rural life unfold. No doomscrolling. Just slowness.

He packed two books as an experiment: Mary Beard's SPQR and a physics text called De Newton a Einstein y algo más. He finished both in his first week.

One week. Two complete books.

So he bought more. F. Scott Fitzgerald short stories and Atomic Habits—faster reads, done by early week two. But the mathematical proofs in the physics book left him wanting more. He started working through Stewart's Calculus. Realized his algebra was rusty, so he worked through the appendix. Found the laptop-and-phone reading experience lacking, hunted down better tools—Paul's Notes, Active Calculus. For physics, he moved through University Physics. No web version found yet; he just ground through it directly.

He spent the rest of his vacation doing precalculus and physics exercises. On vacation. By choice.

The Real Twist

Here's what makes this story sharp: Daniel says this feels exactly like when he first learned to code—learning purely for the sake of learning, having fun in the process. Except back then, a small voice whispered maybe this becomes a job someday. This time, there's no safety net. He admits he's not sure how a math-and-physics hobby could ever affect his career. With AI reshaping software and data engineering right now, everything career-related is fuzzier than it was eight years ago. He can't plan ahead the way he used to. And he's doing it anyway.

His only goal: someday understand advanced physics concepts, maybe read new research papers in whatever field he stumbles into. No job requirement. No monetization plan. Just curiosity, reactivated.

What Worked

Did the vacation fix his brain? Daniel's blunt: he doesn't know. There's no test score proving he's back to baseline. But he is less intellectually lazy in his day-to-day life. Not because he deleted an app or installed productivity software. Because he got bored enough, slow enough, and offline enough to pick up two books in a week and fall into calculus for fun.

AI didn't do that. Vacation did.