Steve Smith (Ardalis) writes about .NET, software architecture, microservices, and developer practices.
HN links it for explanations of Postel's law and Conway's law, and one commenter recommends his tips alongside other engineering newsletters.
I think this was the meme before moduliths[1][2] where people conflated the operational and code change aspects of microservices. But it's just additional incidental complexity that you should resist.
IOW you can do as many deploys without microservices if you organize your monolithic app as independent modules, while keeping out the main disadvantages of the microservice (infra/cicd/etc complexity, and turning your app's function calls into a unreliable distributed system communication problem).
[1] https://www.fearofoblivion.com/build-a-modular-monolith-first
[2] https://ardalis.com/introducing-modular-monoliths-goldilocks-architecture/
which has had some backlash of late? it seems that one should not be liberal in any capacity because it results in undetected corner-cases
https://ardalis.com/postels-law-robustness-principle/
https://tools.ietf.org/id/draft-thomson-postel-was-wrong-03.html
It's called "Conway's law"
https://ardalis.com/conways-law-ddd-and-microservices/#:~:text=Conway's%20Law%20states%20that%20%22any,Domain%2DDriven%20Design%20are%20adopted.
Cargo[1]. REPL[2].
[1]: https://ardalis.com/how-to-add-a-nuget-package-using-dotnet-add
[2]: https://docs.microsoft.com/en-us/dotnet/fsharp/tutorials/fsharp-interactive/
sounds like Postel's law in play, but I agree it's annoying that there are incorrect / bad atom emitters.
https://ardalis.com/postels-law-robustness-principle/
I can recommend:
https://blog.bytebytego.com/
https://bigtechdigest.substack.com/
https://www.oreilly.com/emails/newsletters/
https://ardalis.com/tips