I’ve been writing on this blog for a long time. And in this time I covered lots of different topics.
Going back in time, I started with some random Web Dev topics, then I focused on Go, React, Node.js, CSS, HTML, Browser APIs, Next.js, Vue.js, Svelte, databases, Python, Swift and even electronics and C.
Sometimes when I have the desire to write about different topics than the ones I usually do, which is Web Development in general, I think about it.
It’s my blog, it’s not a publication named “Web Development” or anything like that.
Despite that, when you write for a long time about a topic, even in broad terms like I do, you start to feel like you have a “contract” with the people that read it.
What will happen if I decide to write about X and people are not interested? Will they stop reading or checking out the blog? Will they unsubscribe from the email newsletter?
It almost never does, except you go very far, into a completely different thing.
Did you read the list of topics above? There’s very little correlation between them, except they all relate to programming. But a React developer has no interest in C or CSS.
So the broad niche is programming, and under this umbrella I can write about anything.
It’d be different if I started writing about gardening, dogs, or hiking.
Sometimes I talk about the business side of things, or the content production, but it’s all related.
I thought about doing some “travel blog” kind of posts when I travel, just to do something different. I might do one day, although I don’t want to confuse readers. And Google ahah.
The rule for me is to write what I want. It’s key to write one post every day. Otherwise I’d have stopped long ago. If one day I’ll want to write about travelling, or cooking or anything else, I will.
Sometimes I write a post about how I set up my van for digital nomading across Europe and truth to be told I get much more replies about those topics. Maybe just because it’s a little unusual in their day.
One thing I will do in the near future is to start writing about SwiftUI and iOS development. I have debated doing this for months now. Actually, I think years.
But now I think it’s the right time.
In the past I decided to write about topics I wasn’t super passionate about. Like databases. How much passion about database do I have? I started and after some days I stopped.
But I think I could write about some of the iOS app ideas I have, the planning phase, the development, the release on the App Store, and all that, and it might be something that a fraction of my readers could find very interesting.
Maybe they have an iOS app idea, and this might be the trigger they need to just start.
Am I tired of Web Development? Not at all. And any iOS app needs a Web or API counterpart anyway, so it’s not like I’ll stop writing about it.
I just love programming in general. Creating things with code. Be it a Web app, or an iOS app, or a Desktop app, it does not matter.
For me a little switch in what I write about is more a way to diversify and keep my energy levels high.
It’s always been like that for me. I’d work on a web app, then on an iOS app, then I’d switch to macOS development and back to web apps.
It’s just how I do.
I admire how some people can spend years and years work on the same thing.
I’ve since long accepted that my personality leads me to hop from one thing to another, and that’s one reason why I’m a generalist and not a specialist in a specific technology.