If you're trying to build an audience based on pithy advice in a well-known space, there are a lot of posts like this that apply. Focus your ideas, write about one thing, make it relatable, bold a couple random words, and Bam! Traffic!
If you're writing about something technical, complex, or sophisticated, it's worth spending more time to get it write. If you're writing for developers, include code and make sure it runs. If you're writing about hard topics, find research to back up your conclusions and build a real narrative (Priceonomics does this well).
Especially as a founder, your goal should be to write the definitive piece on whatever your topic is. As somebody starting a company on that topic, you are legitimately one of the foremost experts on this topic, so people want to hear your thoughts! Keep all those other rules in mind, buy don't sell yourself short by writing half-hearted pieces that sort of rehash the same topics.
For example, where I work, we think that traffic management (routing, proxies, service mesh, all that rot) is a better way to do things if you've gone to microservices. One example is releasing software. So we wrote one article on it (in two parts). It's long, it's technical, and it has been so, so successful. We don't try to reinvent the wheel on this topic. We just point people to this post.
https://blog.turbinelabs.io/deploy-not-equal-release-part-on...