Is "release early, release often" as good a policy for personal blog posts as it is for software?
Certainly writing helps clarify your thinking, but what about the publication step? Is publishing a post and responding to feedback an essential step in finding out what you have to say on a subject?
@underlap Yes please! I like reading raw ideas and to discuss them. It makes me look stupid, or dead wrong often, so probably not great for personal branding if one is, like me, not super smart/precise/disciplined. That's less of a problem for you, I guess. Either way, overall, the learning from imperfections is precious, so please share.
@iwein That's an interesting position. I certainly like getting an insight into others' thinking, so it makes sense to be open with my thinking including any gaps and rough edges.
I guess for major revisions of a post, it would be helpful to note these in some way in case anyone re-reads the post.
@underlap I'm sure it is correct from a learning perspective. It probably applies to any "knowledge product". On the flip side, I blog primarily for personal reasons, so I will blog in a way which gives me the most enjoyment. I often get enough of the "do just enough to make it work" kind of tasks at work, so it gives me more satisfaction to allow myself to spend enough time on each post to pass my personal quality standards.
Add comment