Devlog techniques for busy coders

I spend all my time working on my software, and without a marketing team I need to find ways to build an audience without taking too much time away from working on the product.
I started doing devlogs because they’re a good way of showing progress and new features without it turning into a huge production.
How technical should a devlog be?
Technical explanations can help to build trust when done right.
We see a lot of marketing that tries to make things seem more “sciencey”
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.