A colleague used to adhere to the three.sentenc.es policy when writing email. Although this policy can harm tone, the general theme of brevity that it feeds into is an important one.
I regularly apply a similar approach to technical problems, often a very straightforward one: how do I name a particular file?
By always prioritising brevity, a file that may have been called aws_model_inference_and_authentication.py (difficult to parse) simply ends up being aws.py (easy to parse), with the additional information in the title communicated elsewhere.
The same approach can be applied to text in any digital setting, including blog posts.