I do this without even publishing the posts. As mentioned in one of the other comments, I am vary of making these accessible for the public due to lack of "oversight". I feel like there's a responsibility when sharing information, and if I'm not 100% sure what I've written is correct, I don't want to mislead people. And even if correct, one should really ask themselves if it actually adds something to the topic which is otherwise not easily accessible. I think this is especially important to ask today when there is so much information already available.
Hence I actually think writing blog posts as means of understanding is a really goof approach; whether or not the piece should be made public is something that should then be judged case-by-case.
goof -> good
:)
- Knowing what I think
- Sharing knowledge
- Venting
- To learn (when I get comments on my views)
- To remember better, e.g. for books I've read
- To have an archive to refer people to
- For the thrill of having people read what I write
- For self promotion
I wrote about it in more detail here: https://henrikwarne.com/2017/11/26/6-years-of-thoughts-on-pr...
> - For self promotion
I use my blog for venting as well. And love the experience, knowing that it's not a social network and no-one will rush at me screaming angrily. I just worry sometimes that some of my rants go against the dogmas of the mainstream liberal orthodoxy, and if someone did chance upon my blog, they might get upset — and oh, I don't know, fire/not hire me.
It's easier than ever to get started (as easy as forking a Github project and uploading your markdown), and as a bonus it might also look good on a CV.
Not because I'm a selfish dickwad, but most of my posts ends up being drawn from real world development experience, and to further improve my ability as a developer, I write about the experience openly.
It seems like a win win situation. I get a better understanding of what I'm doing and it becomes a searchable reference for myself and anyone else who happens to stumble on one of my posts.
I couldn’t even begin to confidently tell anyone to read what I write. Statistically, 90% of my blog posts sink without a trace. My last post was about a novel but highly pessimum solution to a programming puzzle.
Who ought to read that? And why? It was a pleasant diversion to write, and if someone finds it a pleasant diversion to read, great! But how could I tell anyone that they ought to read it?
As it happens, I have been blogging for fourteen years, and if you throw enough spaghetti at the wall, some of it sticks. Thus, I have a small but durable reputation as an author.
In that time, I have resisted the urge to closely track metrics and adjust my writing to improve its popularity. I’ve tried to get better at being me, without becoming a copy of any of the bloggers that are really popular.
It’s my hobby, it’s supposed to be for me and for those who have their own reasons in finding it delightful.
Structuring a post to be easier to digest isn’t just about writing for others, it is also a forcing function for structuring my own thoughts. In what order should I present this idea? What is essential, what is inessential, and what actually detracts from the essential idea?
Questions like these work their way back to improving my own thinking about an idea, and that is part of why I write and what I gain from it. This is why I unapologetically revise my posts dozens of times when they hit HN or go viral on Twitter: The feedback offers a clue as to how well I’ve structured my thinking, and restructuring it helps me understand the subject better.
Writing is rewriting. Without agreeing or disagreeing with any specific piece of advice in TFA, the general idea of applying some structure to writing to make it digestible nad to communicate your ideas clearly is valuable not just for the writing itself, but for your own thinking.
Mostly I think I get an enjoyable sense of accomplishment from getting down "properly" the stuff I find myself contemplating and discussing with people. It's almost like flushing a write buffer: get it from working-memory to blog, and it's done!
There's definitely a learning process and I feel I'm noticing improvements to my output and approach, which is also a satsifying outcome.
A blog is a communication device, so it doesn't make a lot of sense to do it solely for yourself. I think to myself a lot (sometimes out loud) and I write for myself a lot, but I wouldn't talk into a phone with a dial tone to myself :)
So perhaps this piece is also useful for people who write primarily for themselves, but also would like to remove any barriers to others finding and enjoying the fruits of their efforts.
Remember the diaries (I wonder when they gained popularity? in the 18th century? in the 19th? surely they've been with us longer than that). They could be read by others, and indeed there was a tradition for young lovers to give each other their diaries to read, but they were (or were supposed to be) written primarily for those who wrote them.
Same for laboratory logs (or other professional logs; I am not sure who kept them besides sea captains). They could be read by others, and might be informative to others, but were written primarily for the writer himself.
As for publishing, web publishing is so easy and makes the writing so accessible it's arguably easier to "publish" your writings on your web site than to keep them in a notebook in a drawer.
For many developers who have harnessed static site generators that turn local markdown (or orgmode, etc.) files into htmls, it is essentially one and the same thing.
Fo myself, as the topic and exposition are intrinsically motivated. For others, as that goads me to bidging chasms and leaps of reason otherwise obscured, and for which Future Me often thanks Past Me.