Usually the best time to show code - and, indeed, to publish a blog post - is when you're still at least a bit embarassed by it. I've learned over time that wh

Usually the best time to show code - and, indeed, to publish a blog post - is when you're still at least a bit embarassed by it. I've learned over time that what I consider a barely acceptable first draft of either is often even so of great interest to other people and reminding myself that my own perfectionism is in fact mostly counterproductive. Ok, for critical code that really really needs to work reliably I let myself go full pure math grad on the problem but for everything else ... shipping is a feature. A suggestion to try and help with this - I'll often show stuff to a couple of trusted friends first and if the result is mostly approving noises that helps a lot as leverage against my brain to get it to agree I should hit publish in spite of my reservations. Either way, good luck, and I hope whatever else happens you have fun working on this :D