I have a test I run before wasting time talking about ideas: have I spent at least as much time trying to implement this idea as I've spent talking about it? If not, and if the idea's any good, then it's time to shut the fuck up and sit down and start coding. That gives me much more time to talk about ideas I've already implemented.

I'm not saying you shouldn't talk or write about ideas, but that you should try to strike a balance, like tacking a sailboat against the wind. You learn some things from talking with other people and writing to organize your thoughts, then you learn other things from shutting the fuck up, writing code, and using what you built.

33 years ago I was lucky enough to come up with a good enough idea to shut the fuck up and implement, which proved it was good enough to talk and write more about, which led to many more rounds of implementation, changes, talking and writing. Now I'm learning how to program Blender in Python, to do yet another round, by learning from and building on top of other people's work!

https://medium.com/@donhopkins/pie-menu-timeline-21bec9b2162...