Hacker News new | past | comments | ask | show | jobs | submit login

I disagree with this advice. I write articles when there is a need for them. Sometimes they are 2 months apart, and sometimes 2 days. I can't plan the problems I'll face and solve in advance.

I also spend a lot of time updating old articles with new information, and that new information trickles in at random intervals.

Most of your readers will find you through Google, when they're trying to solve a specific problem. They won't subscribe to your content or return without a specific goal in mind, so consistency is not that important.




Could say that is still consistent. If your articles arise out of a need then that is the formula. What you could do is delay the publication if there is no urgency.

I found a really cool blog one time where the author was writing a book spread out over 4 blog posts (or so) that he kept updating. His daily new posts briefly described the updates he made. It was a cool rss subscription for me. I certainly didn't visit his book every day but his updates gave a sense of involvement and I ended up reading the "same" articles multiple times both for the content and to see the progress. Had he just updated the postings I would never have returned.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: