|
Dear HNers who engage in any form of "thinking in public" (whether that's blogging, posting notes online, or maybe even participating in HN/Twitter/forum discussions): What are some of the pros and cons of thinking in public vs thinking in private? Since it's relatively easy to find the benefits of blogging and other ways of thinking in public, I'm especially curious to hear about some of the potential cons of thinking in public / the benefits of thinking in private? And with that in mind, how does one effectively manage both to make the best out of both approaches? |
1. Intent is preserved. When you write something publicly, your output are words that you constructed from your ideas and your intent. As others read it, they will have wildly different interpretations of the text, even if you write well. Thus, your original intent does not translate perfectly. You don't have this problem with private thinking, because you own the additional context and intent.
2. No self-censorship. You don't have to cater to anybody's liking of whatever your thoughts are. You don't need to win anybody's approval, and this allows for the brewing of fresh and pure thoughts.
3. Exclusivity. Maybe one of your ideas is of high value. Could simply be a rare skill you mastered, a trick unknown to the world, a little software asset you produced. The norm in our industry is to share wide and far. Write that blog post, open that Github project, etc. Alternatively, you can also keep it to yourself and leverage its value. Quite literally as leverage.
I imagine this last point to be somewhat controversial. By sharing far and wide, you'll be doing free labor for an industry that doesn't give a fuck about its volunteers. People will simply take your free shit and run with it, and often still complain about it. In light of such hostile and unrewarding environment, I have absolutely no moral problem with refusing to do free labor and keeping some things private and exclusive.