I've worked at a company that probably hit every single one of these. Don't even get me started on microservices. If your company name isn't Amazon or Google,

I've worked at a company that probably hit every single one of these. Don't even get me started on microservices. If your company name isn't Amazon or Google, then what are you even doing? Just don't. One company I worked at did microservices. They never had enough headcount to actually do things properly. Every single service was this half-assed API that followed the current trend-of-the-day. Looking at the microservices was like looking at the rings of a tree. You could tell when certain people joined or left a company or when they decided to experiment with Clojure or Elixir or GraphQL, etc. Each service required a different header incantation to get it to work properly. You couldn't just curl a URL because that would be way too sensible. I wrote my own curl wrapper just to deal with this bullshit. And of course the biggest problem with microservices is that documentation is horrid. There is no incentive to maintain good documentation because the APIs are internal. I've spent many nights staring at the internals of various microservices to decipher what they are doing. It's not even my code or my department. But I'm stuck sifting through other people's messes. Oh, and it's really really cute that developers still believe in the mechanical documentation fairy that extracts documentation from the code with some geewhiz tool. No, GraphiQL is not documentation. Stop lying to yourself and each other. > Please don't use gRPC gRPC is another bandwagon. The gRPC proxies must be made out of paper mache with how quickly they crumble under the slightest load.