Hey, OP here. This blew up a little. Thanks everyone for replying. Don't want to repeat myself in replying to everyone individually, so I'll add a comment. Ma

Hey, OP here. This blew up a little. Thanks everyone for replying. Don't want to repeat myself in replying to everyone individually, so I'll add a comment. Many people suggest keeping them separate for the sake of lower signal:noise ratio. I get it, but I also feel like comparison to YouTube is unfair. YouTube is a different platform, and you generally don't watch individual content pieces of a creator, but rather subscribe to a creator as a whole. I agree that in the case of YouTube, it's harder to keep a broad channel. I have subscribed to people who provided content on Software Engineering, tolerated when they pivoted towards indie-hacking, and unsubscribed when their content turned into anti-government/establishment rants or personal story of how they overcame adversity over and over again. But in the case of blogs, you can subscribe to a particular category. Say, you are interested in software engineering content, then just subscribe to it via RSS and get relevant content. I tried to look at other blogs, one of them is Patrick McKenzie (patio11)[0], and I can't say that his blog is super niched down. Some content is very valuable for me, while other is not interesting. Another thing is that I think most people misunderstood the "general life" thing. I don't intend, and never planned to, post about the food I ate or how I prepared lasagna on Saturday. I was aiming more towards self-improvement content, for example tips on time management. Where would you put that kind of content? In a software engineering blog? In entrepreneurial blog? It is relevant for both disciplines, yet it does not fit any niche if you plan to niche down. One suggestion that I liked from the comments, is to treat the content as a DB. So essentially, I can keep 4 blogs: the one under my name domain will be the master, and the one I'll update. I can design the URL scheme is such a way that I can point individual blog domains to a particular category, so my software engineering blog will https://xyz.com https://xyz.com, but the domain is pointing to http://me.com/blog/category/software-engineering http://me.com/blog/category/software-engineering. This might simplify things, while still keeping them separate. Thanks everyone for the comments, I appreciate it. Edit: after giving it some more though, I came to the conclusion that my problem is unnecessary complications in the way I manage my blogs. And as a good software engineer, I will probably redo my statically generated blog, unify everything to one big repo that will use common building blocks, but each piece of content will be segmented to one blog, under its own domain, and they all will be built from the same repo. This will ensure that I can reuse common building blocks like OG image generators, JSONLD tags, and reuse parts of theme, while minimizing the maintenance to just a single repo. [0] https://www.kalzumeus.com/archive/ https://www.kalzumeus.com/archive/