Longer or shorter blogs?

Hi Milos,

I like it when a blog's context is fully understandable on its own, for example with a photo showing what it's about, or (say) a 2-sentence introduction, so that anyone who has not read the other blogs on the topic, can still understand what it's about. And titles with some explanation in them. Some things just feel natural to have in a single blog, others may be better split up, especially if a project is modular. Sometimes I've regretted combining too much content into a blog post, because then in future blog posts I might want to only refer to a specific part that would have been better written in a more general way applicable to more than the specific project I was working on at the time.

But having said that, if I'm in the flow, I'd rather just organize into a single post, and make use of the table of contents feature. I'm learning to make each section standalone for readers, sometimes I can do that easily, sometimes I cannot. Also as Rod and Michael say, pictures/screenshots make blogs a lot easier to follow : ) Recently I've tried to annotate images more often, mainly because I'm not good at bringing the thing of interest to attention through better photo composition. So annotating/arrows works around that!

Incidentally, the best feature I've found in years is 'grammarly', you can download a plugin for Chrome browser, and for free it performs a quite reasonable spell- and grammar-check : )

I just updated an old blog post with some new content, and while I was at it, fixed my typo's and grammar. It was quick because it automatically makes the right suggestions in real-time, I can just click-and-correct with the mouse, no need to type anything.

Hi Milos,

I like it when a blog's context is fully understandable on its own, for example with a photo showing what it's about, or (say) a 2-sentence introduction, so that anyone who has not read the other blogs on the topic, can still understand what it's about. And titles with some explanation in them. Some things just feel natural to have in a single blog, others may be better split up, especially if a project is modular. Sometimes I've regretted combining too much content into a blog post, because then in future blog posts I might want to only refer to a specific part that would have been better written in a more general way applicable to more than the specific project I was working on at the time.

But having said that, if I'm in the flow, I'd rather just organize into a single post, and make use of the table of contents feature. I'm learning to make each section standalone for readers, sometimes I can do that easily, sometimes I cannot. Also as Rod and Michael say, pictures/screenshots make blogs a lot easier to follow : ) Recently I've tried to annotate images more often, mainly because I'm not good at bringing the thing of interest to attention through better photo composition. So annotating/arrows works around that!

Incidentally, the best feature I've found in years is 'grammarly', you can download a plugin for Chrome browser, and for free it performs a quite reasonable spell- and grammar-check : )

I just updated an old blog post with some new content, and while I was at it, fixed my typo's and grammar. It was quick because it automatically makes the right suggestions in real-time, I can just click-and-correct with the mouse, no need to type anything.