Title: Reading this page (https:&#x2F;&#x2F;hackerdaily.io&#x2F;29237308&#x2F;comments) and I&#x27;ve found a few blogs I like, but I&#x27;m struggling to build a rubric for what makes a good engineering blog.<p>I&#x27;m working with some awesome engineers who have day jobs but still find time to write some posts. How do we make sure we make best use of their time?<p>Do &quot;How we did X to improve Y&quot; posts work? Do you want backgrounders to our key area or should we assume knowledge and give a bucketload of detail? I&#x27;m assuming nobody wants promotional content, but if we say how awesome we think something is because we solved our biggest pain point, does that count?
Upvote: