This probably is the reason why it works in some settings. Anecdotally, as someone with more domain/functional knowledge and operations knowledge than knowledge of frameworks, I found microservices architecture with good functional test coverage a better way to deal with a team of programmers like me (basically, a typical team in an offshore IT consultancy building enterprise applications using SpringBoot and Node.JS). Ship the service as early as possible with available talent and then get someone really good with that programming language or framework to deal with performance bottlenecks within the microservice. I see it basically as a way to limit the blast radius of the applications. Of course, as you said, get the boundaries wrong and you have a bigger problem.
I did the same. I finished and pushed out a small static site that I still use occasionally. Haven’t participated since then, though I continue to push code and notes publicly.
If it is a good name, I think it is only a matter of time before someone gets it. You might as well, if you like the name.
Of course, I have absolutely no idea if that is a good business move. On the other hand, you'd be doing a service to anyone who bookmarked that website by adding a note about the transition somewhere on the new site. I like Hard_Space's suggestion too. This is coming from seeing what happened with Ian Murdock's website. Thankfully, a copy of it is also hosted at https://ianmurdock.debian.net
