One of the best types of developer content is a debugging story.
"What is X" or "How to solve Y" work in some situations, especially when you focus on SEO distribution. But a good debugging story is something that even senior devs want to read.
This is an old article from the GitLab and is such a good example of thos format:
- Set the scene: Say what happened, what results you managed to get, and introduce the problem. Skip the fluffy intro and invite devs into the story
- Go deep into the problem: show what happened and go into technical details. Address the obvious solution that unfortunately didn't solve the problem. Showing profilers, charts, UIs. Make the problem more concrete.
- The journey: explain what you tried, how it failed, and what you learned, go technical and detailed. Take people on that journey
- Close the loop: Close with a win, show the improvements/results, summarize what you learned
The downside of using this format is the same as with most good developer content. You need a real situation, explained by an actual dev in a technical language.
