My experience and techniques have been remarkably similar, albeit on a smaller scale than Gergely. A few years ago I decided to start writing one post per month

My experience and techniques have been remarkably similar, albeit on a smaller scale than Gergely. A few years ago I decided to start writing one post per month on any subject within tech/software development. I've missed that goal a couple of times but my average since then has still been ~1.4 posts per month. I write about whatever is interesting to me and most often that's exploring topics in tech that were a mystery to me before like compilers, databases, etc. Like Gergely I keep an ever growing list of projects or topics that seem interesting to tackle at some point. One book I'd recommend most to folks writing in tech (whether it's technical or not) is On Writing Well, which teaches you the same kinds of things Gergely uses Hemingway Editor for. That is, to be concise and precise. I think the biggest benefit to writing consistently is that you improve as a writer and that you get to explore interesting topics. Even if you are doing coding projects to improve as a developer, it's a whole new level to start trying to explain that work in blog posts. It's easier in coding to get things right without understanding exactly how/why they worked. When you write to explain you have to actually dig into that how/why. Some people say tech blogging is great for getting jobs but in my experience, of all the things that helped me get work, my blog didn't contribute much. But I'm just one data point. I say this so that you don't get discouraged if you don't suddenly unlock emails from hiring managers because you start writing more.