My main technique for actually doing, as opposed to thinking and exploring, is guiding that curiosity into different levels of detail.
As long as I remember to wonder how this behavior is happening at the code level, and I remind myself that I don’t really get it fully until I see it working in the debugger , I can use that curiosity to drive the detail work of actually delivering well-understood working code.
I’ve also found this to work well in my work as a programmer, but it’s generally something I have to remind myself to do in a reactionary way and therefore doesn’t seem to help me “get my butt in the chair”. So, this is a good reminder to try and guide my curiosity in the way you described, thanks!
I’ve also found this to work well in my work as a programmer, but it’s generally something I have to remind myself to do in a reactionary way and therefore doesn’t seem to help me “get my butt in the chair”. So, this is a good reminder to try and guide my curiosity in the way you described, thanks!