Simply put: You're shopping, not creating. I went through a phase like this, too. It also had some relation to being stressed, or not socializing enough, in my case.
The healthy thing you want to be doing is practicing. Ground the big idea within the question, "what part of this can I start implementing now?" It doesn't matter how tiny or trivial that part is, as long as it has a clear link to the big project - the more direct, the better. Allocate time to implement that, instead of shopping for best practices. Allow your implementation to be a little bit cruder than you think it should be.
If you're doing anything worthwhile, you'll soon land in a zone where tools and tutorials don't really help you anymore. There's just the project you have, and your will to work on it. You can still fall back into the shopping cycle at this phase by rewriting things with a different tool or technique, but that's where you should reassert the part where it's "a little bit crude." Focus on concrete, measurable metrics, and you will get away from the spell of "best practice."
It's very hard to stop shopping, and if you don't stop, you lose. There's a fantastic SF story that is the perfect allegory (Arthur C. Clarke, Superiority):
EDIT: It angers me that this comment was down-voted. That story was difficult to find, and it really is the perfect allegory to the OP's problem, and the more general "worse is better" notion. What is this, some sort of prejudice against Golden Age SF as a cultural touchstone? Would I be similarly penalized if I mentioned "Sisyphus" or a "Gordian Knot"?
I have loved that story ever since I read it as a teenager. Incidentally, it is an almost perfect metaphor for the F-35 Joint Strike Fighter, the "jet that ate the Pentagon".
Thanks for this comparison. I went through this very same thing, and spent a lot of time and ammunition firing at the wrong solutions before I landed on this very same thinking. Best practices are fine, but it's way more important to get some code written for that feature. Forging ahead without tutorials and Stack Overflow (using only what you know as a software developer in general) is going to make you a better, more productive developer a lot faster than anything else. The shopping metaphor is excellent.
The healthy thing you want to be doing is practicing. Ground the big idea within the question, "what part of this can I start implementing now?" It doesn't matter how tiny or trivial that part is, as long as it has a clear link to the big project - the more direct, the better. Allocate time to implement that, instead of shopping for best practices. Allow your implementation to be a little bit cruder than you think it should be.
If you're doing anything worthwhile, you'll soon land in a zone where tools and tutorials don't really help you anymore. There's just the project you have, and your will to work on it. You can still fall back into the shopping cycle at this phase by rewriting things with a different tool or technique, but that's where you should reassert the part where it's "a little bit crude." Focus on concrete, measurable metrics, and you will get away from the spell of "best practice."