> I find myself checking resources and other code examples often. Being in the zone does not exclude research tasks. Being in the zone is simply a state of hyp

> I find myself checking resources and other code examples often. Being in the zone does not exclude research tasks. Being in the zone is simply a state of hyper focus. It's very possible to be in the zone and constantly switching back and forth between the IDE and API reference, the point is that even though you are switching windows you aren't switching tasks. You've got this clear model or objective you're working towards and you're just referencing details plugging them in as you go along. > to get unstuck? The definition of the zone, what makes it so amazing, is that you aren't stuck--you're in constant motion towards the solution. The only way to get from stuck to the zone, is simply to stop being stuck. In other words, take the first step towards the solution do something, anything to address the problem set. That may mean, doing research, checking out code samples, etc. Just because you aren't typing characters into an IDE doesn't mean you haven't started coding. The research is helping you build a model, understand the scope and structure of the thing and eventually leads to describing it in the editor.