• 3 Posts
  • 1.35K Comments
Joined 3 years ago
cake
Cake day: April 10th, 2022

help-circle













  • Because the idea of a European alliance is nonsense. NATO IS the European alliance. And NATO’s strategy for defending against Russia is a nuclear killchain with one critical position in Ukraine. What would a European alliance do? Not defend against Russia? Or defend against Russia in a different way? Would they do that while still in NATO or would they have to dismantle NATO first and then build this alliance?

    It’s nonsense. You can’t just make a new transnational military that is capable of defending against Russia by just saying “European Alliance”.





  • This is delusional. It’s not a personal vendetta against the USA. Nuclear Europe fielding military in Ukraine is a red line for Russian national security. Until people understand the reality of security, you’re all going to be blathering idiots.

    There are two positions on security - it’s either I am secure while you are not or it’s we’re both secure. Mutual security is the only way that peers can engage sustainably. Assymetrical security cannot be sustained by peers.

    Ukraine being a non-militarized buffer between Europe and Russia is critical to Russian national security. Any arrangement where Ukraine is militarily aligned with the rest of Europe is an asymetrical security situation where Europe has security at the expense of Russia losing security.

    It will never be sustainable.

    Russia will either establish Ukraine as fully demilitarized with its constant oversight for the next several decades, as a result of the violation of trust that the US and EU committed, or Russia will occupy Ukraine. These are the only two options that establish mutual security and thus are the only sustainable options. Anything else is an escalation by Europe.



  • I am so tired of these sorts of shallow analyses from people that think their screw-ups are actually caused by EDAs or micro services or whatever. They’re even totally transparent about the fact that they did because they heard cool things but never say “so we sat down to learn about best practices, what the current state of the art is, and considered how our use cases matched the architecture”

    They just say “we thought it would be cool so we just started doing it and it sucked - here’s why that’s an inherent problem of the architecture and not in any way related to our behavior”.

    Yes. If you take a team of people who build n-tier and hexagonal MVC monolithic apps, and then tell them to build micro services, they’re going to build a bunch of n-tier or hexagonal MVC monolith candidates and eventually end up with a single service that does too much and ultimately becomes the monolith.

    Yes. If you take a team that does 100% synchronous HTTP interfaces, SOAP or ReST, and then tell them to build microservices, they’re going to daisy chain those microservices via synchronous HTTP interfaces, and if you tell them to build an EDA they are going to build an EDA that attempt to replicate all of the aspects of their synchronous HTTP interfaces with busy polling loops.

    So stop doing that and actually do the hard thing of learning fundamentally different architecture, techniques, technologies, trade offs, best practices, operational patterns, design patterns, and heuristics and principles for managing software. Learning is difficult and humbling. But it sure beats writing ignorant articles like this.