3 ms·
When it comes to technical blog, I've read interesting idea that you should blog about things you weren't able to find (e.g. "how to change print width in ngspi
by dvh 5y ago
When it comes to technical blog, I've read interesting idea that you should blog about things you weren't able to find (e.g. "how to change print width in ngspice"). Once you solve the issue yourself, blog about it and your blog entry will be the only one Google can find thus you'll receive all the traffic which you can then utilize for ads or for propagation of your other projects.
- TrueGeek 5y agoThis is why I do it. If I can figure it out quickly or via a Stack overflow search, great. If I get stuck for 2 days before solving it then I’ll blog about it. Maybe one person will read it and my 5 minutes of writing a blog post will save that person 2 days of headache. I have seen visit logs where people visit my articles from Google years after I write them so it seems to be working. And more then once I’ve been stuck, googled the problem, and found my own article because I forgot I’ve solved this exact problem before.