I actually think that is actionable advice. Like, stop thinking about, stop planning to do it, just, right now, fucking do it. It doesn't matter if it's sub-optimal or whatever, that can be fixed later.
This works for most things, but not all things. If you're trying to solve a difficult math problem for example, you can't just put your head down and grind through it. But for other things that you do know how to do, but not necessarily the right way (writing an essay, writing some code, etc), you can start immediately. Like if you have a problem and can only think of a O(n^2) solution, well, just write the O(n^2) solution, even if you know it won't be good enough in the end. Implementing the code for the O(n^2) solution will often give you insight into how you can turn it into O(n) or O(n log n). By writing a loop to sum number for example, you might realize you're summing mostly the same number over and over and can save time by instead calculating a cumulative sum.
You could very well have this insight without writing any code, but actually typing something and reading it gives you a different and deeper perspective into the problem.
I know you're being cheeky but for me when I've procrastinated on things the fix has been to "just get started." Often in the past I've gotten caught up on how to do something "right" or "well" and this leads to avoidance procrastination. Instead finding somewhere to start and just getting started and continuously improving has been the way for me to break out of the hurdles of avoidance procrastination (overthinking).
This works for most things, but not all things. If you're trying to solve a difficult math problem for example, you can't just put your head down and grind through it. But for other things that you do know how to do, but not necessarily the right way (writing an essay, writing some code, etc), you can start immediately. Like if you have a problem and can only think of a O(n^2) solution, well, just write the O(n^2) solution, even if you know it won't be good enough in the end. Implementing the code for the O(n^2) solution will often give you insight into how you can turn it into O(n) or O(n log n). By writing a loop to sum number for example, you might realize you're summing mostly the same number over and over and can save time by instead calculating a cumulative sum.
You could very well have this insight without writing any code, but actually typing something and reading it gives you a different and deeper perspective into the problem.