YAGNI is one of the easiest to misunderstood ideas behind eXtreme Programming. That's why I think it's a good thing it stays under active discussion. Often people understand it too literally which can create issues. That's why people talking about "PAGNI" (probably are gonna need it) are right. After all, people who also conceptualized YAGNI wrote back then: "This doesn't mean you should avoid building flexibility into your code".

Interesting strategy, shows a fascinating blind spot in the typical AIs used for Go nowadays. It kind of hints to the fact that the neural networks abstract knowledge much less than advertised.

Interesting explanations of the main drawbacks of microservices. Nothing is magical so you need to know what you loose, in this case this is mostly about increased coordination efforts and latency in feature availability.

This is a sound advice, it's better if it's a conversation. Some companies push for that some don't. If they don't the proposed plan is a good one.

It is indeed getting easier every days to self host a website. Some other services or email are a different story though.