|
|
|
|
|
by stephc_int13
386 days ago
|
|
If you want to reach the full potential of your brain to solve a specific problem, you'll need both hard focus during intense sessions and "background" work, and yes taking a step back (during a walk, shower, coffee break or bathroom visit) is a way to trigger the switch. The key is to care deeply about solving the problem, not simply looking to get rid of it for a quick win, if you are immediately thinking about something else as soon as you can, you'll never get the best results. When using code assistants I found that a nice way to take a step back is to use the Socratic method, chatting with it about the design instead of trying to force it doing it for you. It is like chatting with a well informed but not too clever normie colleague, it can help taking a step back. |
|