A lot of very knowledgeable tech people would like to blog but the thought of how to sustain it keeps them from starting. I feel like when it comes from the unfair comparison of themselves with other amazing content creators, some even compare themselves to CNN!. There was something Sean Kernan wrote a long time ago about how SEALs are able to survive the gruesome training with reference to his dad. His post literally addressed how to build consistency and survive uncomfortable yet long-term situations.
FOCUSING ON THE BIG PICTURE CAN BE OVERWHELMING AT TIMES
While we're encouraged to think long-term, it can sometimes discourage us when we're about to make some difficult discussions that we need to sustain over a period of time. a lot of people quit early or don't start because of the fear of not being able to keep up or the basic thought process of "if it's this hard on day one how will I go two weeks?". Taking things one day at a time helps with starting out long-term activities, yes you have a big perspective in mind, however, break it down into bits and don't think about tomorrow. Every day show up and write and don't think about what you will write tomorrow, when tomorrow comes you'll figure it out.
SOFTWARE ENGINEERS NEED TO UNDERSTAND CONCEPTS AS MUCH THEY NEED TO CODE
I also feel that a lot of software engineers believing that code blogs should be all about writing code and teaching people new coding trick, while coding tricks and content about code is really helpful, there's more that software engineers need to know when they visit tech blogs. There are more inexperienced software engineers than experienced software engineers because there are different ways people transition into tech, either through boot camps, schools or self-study, you find that some people can code but don't understand why the code is working.
UNDERSTANDING WHY YOU WRITE IS KEY
Explaining concepts that you think everyone should know is helpful to not just software engineers but the average person who looks it up. In job interviews, a lot of software engineers are unable to land these jobs because they're unable to properly explain basic concepts in a way that gives the interviewer the impression the engineer truly gets it. Personally, I write because I like storing my knowledge somewhere in a way that helps me remind myself when I forget things I used to know, over time, I realized that I faced a lot of frustrations when I started learning how to code and I would like to take the pressure off other new entrants in the industry. If you take the pressure off the process of writing it gets easier with time.