> If I could just "start" things on command, I wouldn't need any of these special techniques in the first place For me, it's the opposite. This is one of my fa

> If I could just "start" things on command, I wouldn't need any of these special techniques in the first place For me, it's the opposite. This is one of my favorite things about doing pomodoros. I hate to be the tactibro who sources inspirational quotes from special forces influencers, but I worked with a guy who introduced me to the phrase "go before you're ready," and I really took it to heart as a check against my natural tendency to leave problems alone and wait for them to get easier. I got this tendency from studying math in school, where I fell in love with the magic of getting stuck on a hard problem, putting it aside, and having the solution come to me hours later while I was thinking about something else. That approach works when my subconscious has everything it needs to work on the problem, like when writing proofs for a math class, but at my job I'm usually working in a different way, where the solution depends on concrete details that I'm in the process of learning, such as a new part of a codebase, a new library, a new API, etc. I can't delegate that kind of work to my subconscious, because my subconscious isn't going to read documentation and write exploratory code. But my brain keeps whispering, "You're stuck. Take a break." Because of this, I love the "go before you're ready" aspect of doing Pomodoros.