Why I don't write technical posts
In the world of software, it’s common to write a blog where you share specific lessons about writing code. It’s a good way to share your knowledge, build an audience and make a name for yourself. But because technology moves so quickly, value of those posts diminishes over time. Anything that you write today might become outdated after a couple of years.
I love reading anything that Seth Godin writes—not only because his writing is exceptional, but also because things that he writes about passes the test of time. In his archive you can find posts that are 15 years old but still full of insight and actionable advice.
In more extreme example, ancient Stoics produced a number of writings, which, while are over two thousand years old, describe issues in life that people are struggling with even to this day.
I don’t expect my writings to exist two thousand years, but to retain a long term view, I want my blog to exist as long as I’m alive. It’s not necessarily important that people read it today—if someone stumbles upon something that I wrote 10 years from now and it gives them an opportunity to learn something, it makes it all worth it.