On Expectation of Technical Blogging
Starting a technical blog is easy but maintaining it for a long period of time is a pain in the neck
People say every developer should have a technical blog, there are many benefits of blogging, you're convinced to have one, you buy a cool domain, you setup a static blog with popular Gatsby, you publish some random posts, then you abandon it for months to come.
There are very few blogs maintained more than a year!
Blogging in general can benefit your personal and professional life in many ways like share your passion, build professional network, build online portfolio, learn out loud, make money online, or become an authority in your industry.
Technical blogging is no different, it can be your most valuable asset after many years in tech. It's tempting to have one, it's easy to start, but there's one thing that not many developers can do:
writing consistently in a long period of time.
Developer nowadays often has a blog with some random posts with very little value and left in dust for many years. Why is that? 🤔
Consistent writing is hard but the expectation is not right!
On learning out loud by writing — this is a good expectation for newbie developer who wants to build an online identity while shaping career path. Content quality is often low and inconsistent, easy to quit because reading only is far more easier than reading and writing.
On building an online portfolio — the main purpose of portfolio is to showcase your work, popular choice for every developer, writing some Random Thoughts here and there over the years will be just fine.
On making money online by writing — it's a dream to have passive income stream from technical blogging as a developer, but only a handful people can do this because it requires extreme consistent content writing for many years with reasonable quality and marketing strategy.
On becoming an authority in tech industry — this is a common choice for senior engineers who have many years in tech industry, contributing to high profile open source projects. The content they produce has very high quality and deep in thoughts (people expect so). These days it's easier to build authority on social networks and occasionally sharing some posts is enough.
On building personal brand for something bigger — popular choice for indie makers, book authors, startup founders. Your main purpose is to build a marketing channel for selling digital products or driving leads to landing pages. Consistent writing and high quality content is required, if not then just a waste of time.
On random combination of multiple purposes of writing — the most compelling and dangerous choice of all time. There will be a conflict between quantity and quality of content which will demotivate you. On temptation of doing many things - promoting to multiple social networks, running newsletter, writing daily, buffering content, noting ideas - will make you exhausted.
Picking the right purpose of technical blogging is not that hard, but keeping reasonable expectation with that purpose is very hard. It is very tempting to target multiple purposes because people told you so, but soon you'll get intimidated by low quality of writing.
Never forget that successful bloggers spending majority of time on writing content and successful developers spending majority of time on writing codes. If your purpose of life is to become a true competent software engineer then don't let writing oriented people tell you otherwise.