On Slowing Down
It’s Monday morning; you are sitting at your desk in the office and trying to make progress on your work. Let’s say you are building a website, and you need to decide how the whole thing is going to work, so you spin up a Claude Code session and start asking it to do stuff for you - build stuff, test, etc. You don’t want to be seen sitting idle staring at your screen, so you start another session in the background to finish off another task from your to-do list, and so the day goes with you multitasking multiple sessions and finishing a lot of work.
I am going to say something radical - you should start blocking time where you don’t code(or use AI to write code), reason why I think its effective is because AI can only amplify what you know about a topic if you have half baked knowledge about something you can do more with ai sure but if you are an expert then you can do way better than the average AI user so for example - if I want to build a website I will first think hard about
- Who’s going to use this website?
- How many people might log on at a time?
- What kind of content do they want to see?
- How have other people built performant websites with similar use cases?
Answering these questions means I am not building stuff; I am reading, I am thinking in solitude, writing stuff down, and this might feel unproductive, but it is actually what I think will improve your productivity with AI: the amount of time spent not coding