Some people will make an incoherent mess out of anything.<p>A garbled knot of interdependent microservices with timing issues, bad extensibility, and unpredictable flow.<p>An ornate matroyshka set of wrapper functions calling each other spreading over multiple directories making any modification a large error prone effort.<p>Event systems, probably multiple, without any real difference between just a function call other than your debugger getting very confused by it.<p>Database schemas with table names that exude the narcissism of small differences with nitpicky rules that make it explode if any flexibility is demanded<p>Aws bill that's 10x more than any reasonable expectation given the problem set.<p>An object oriented design that looks like some kind of fetishized exercise of every feature possible, where defects cascade to action at a distance and unintended consequences with tight coupling that can't be extricated leading to a rewrite, just like it did last time<p>They are the people who create the waterfall of dozens of levels of div tags for no functional reason other than to accommodate their incompetency<p>They are the ones that want to pollute your entire day with needless meetings over irrelevant things that will not be acted upon.<p>Of course there's no useful comments or tests or documentation. The git comment messages are single words like "fix" and "rewrite".
There's no versions in the deploy or a reasonable approach to logging that allows a successful audit and the thing is too state dependent to reproduce bugs.<p>Then there's dependencies, loads of them just picked seemingly at random, written by people who think like them with the same disregard for documentation, compatibility or testing. But they have very pretty websites which says they're painless, simple and easy, so I guess it's all ok right?<p>The problem with microservices is the same problem with anything else and changing paradigms won't fix it. The approach needs to change, not the technique. It's a different kind of budo.