{"id":526,"date":"2025-11-07T06:51:00","date_gmt":"2025-11-07T06:51:00","guid":{"rendered":"https:\/\/viker.info\/?p=526"},"modified":"2026-04-28T08:28:18","modified_gmt":"2026-04-28T08:28:18","slug":"what-are-you-even-doing-when-claude-is-clauding","status":"publish","type":"post","link":"https:\/\/viker.info\/?p=526","title":{"rendered":"What are YOU even doing when Claude is Clauding?"},"content":{"rendered":"\n

There\u2019s a question I\u2019ve been asking every developer I meet, and the answers are depressing.<\/p>\n\n\n\n

\u201cWhat do you do while your AI is generating code?\u201d<\/p>\n\n\n\n

The most common answer, by far, is nothing. Or rather: the modern nothing. Check Slack. Scroll Twitter. Open a new tab, forget why, close it, open it again. Stare at the bouncing Claude logo like it\u2019s a slot machine that owes you money. Maybe get up for coffee. Sit back down. Refresh. Still generating. Check phone. Put phone down. Pick phone up again.<\/p>\n\n\n\n

If this is you, I need you to hear something: you have been given the most radical gift in the history of knowledge work, and you are spending it on your phone\u2019s lock screen.<\/p>\n\n\n\n

Let me say it differently.<\/p>\n\n\n\n

Before AI coding tools, you wrote every line yourself. Your brain was the bottleneck at every stage: architecture, implementation, debugging, testing, documentation. There was no gap between thinking and doing because you were doing all of it, all the time, with your hands on the keyboard.<\/p>\n\n\n\n

Now there are gaps. Beautiful, precious, recurrent gaps. You prompt, and then the machine works for thirty seconds. A minute. Sometimes five minutes. These gaps add up to hours every single day. Hours that did not exist before. Hours that appeared out of thin air because a machine took over the mechanical part of your job.<\/p>\n\n\n\n

And the collective response of our industry has been to fill those hours with Twitter<\/em>.<\/p>\n\n\n\n

Here\u2019s what I think most people get wrong about AI productivity. The conversation is always framed as a multiplier. \u201c10x developer.\u201d \u201cShip in a weekend what used to take a month.\u201d \u201cBuild faster, ship more, do everything at 5x speed.\u201d And sure, you can do that. You can use every second of AI-generated free time to prompt more, ship more, grind more. You can turn yourself into a coding factory that never stops feeding the machine.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Or. And hear me out. You could do something else with that time.<\/p>\n\n\n\n

Not nothing. Something.<\/p>\n\n\n\n

When Claude is Clauding, I\u2019m walking. Literally. I\u2019m on a trail, moving my legs, breathing air that doesn\u2019t come from an HVAC system. But the walking isn\u2019t the point. The point is what happens in my head when I stop typing and start moving.<\/p>\n\n\n\n

I think about the next<\/em> thing. Not the current function, not the bug I just described to Claude, but the layer above. Where is this product going? What does the user actually need? Is this feature even worth building, or am I solving a problem nobody has? Is the architecture going to hold when we scale, or am I building a house of cards that looks fine at demo day and collapses under real traffic?<\/p>\n\n\n\n

This is the kind of thinking that never happens at a desk. Not because desks are evil, but because desks are where you do<\/em>. And doing crowds out thinking every single time. Your IDE is right there. Slack is right there. The next ticket is right there. The bias toward action is so strong that the moment you have a free minute, you fill it with another task instead of asking whether the task even matters.<\/p>\n\n\n\n

The gap that AI creates is the feature, not the bug.<\/p>\n\n\n\n

It\u2019s the first time in the history of programming that the machine says \u201chold on, let me work on this for a minute\u201d and you get to step back and be the architect instead of the bricklayer. You get to be the person who decides what<\/em> to build instead of the person who builds it. That\u2019s not a downgrade. That\u2019s the promotion you\u2019ve been waiting for.<\/p>\n\n\n\n

But you have to actually take it. You have to physically, deliberately step away from the screen when the spinner starts spinning. Because if you stay in the chair, you will check Slack. You will. It\u2019s not a willpower problem, it\u2019s an environment problem. The chair is surrounded by distractions. The trail is not (except if you\u2019re into nightingales and wild foxes).<\/p>\n\n\n\n

I\u2019m not saying you need to go Viking (I mean, you should. But that\u2019s a different article). I\u2019m saying you need to have an answer to the question. A real answer. Not \u201cI wait.\u201d Not \u201cI check my phone.\u201d Something intentional.<\/p>\n\n\n\n

Some options, ranked by how much they\u2019ll change your life:<\/p>\n\n\n\n