John Underwood

balanced between getting things done and looking at the big picture.

Too far either way become problematic. If thinking takes over instead of action, people begin to think that thinking *about* the problem/plan/action is productive. Too little about the big picture and a person or team can become stuck or optimize in the small but are no longer reaching the impact.

being more direct and impatient about non-action.

One danger in being so action oriented is that I might be missing the bigger picture and the task that has gripped me might not be as productive as I think. 

One thing others can do is start at the end/goal/outcome and walk me through from the end back to where I am, checking assumptions I might have made. From there, it will likely be the case that I will know what help I can ask for.

Just stopping

It might sound weird, just writing down where I am at in projects, etc and letting it all go will relax and rejuvenate me really fast. I can pop back refreshed in as little as 10 minutes.

Preferably quick feedback loops between learn something then do something.

I want to deepen my knowledge about SQL, window functions, etc.

Currently, I think I limit features, code by what I can currently accomplish, but being able to handle some of those in SQL would expand the features I could implement and do it performantly.

I love creating with a strong tendency towards it being tangible: a product, piece of code, tiny robot, etc.

I like blocks of time for deep work, but try to make a block of time every day for meetings and such.