A significant portion of developers want to dazzle with complexity. First and foremost, it's a flex and a resume builder - everyone wants to have K8S on their resume (even though it's ancient at this point). Second of all, people are simultaneously lazy - when you tell them to put the customer list in the database, suddenly it becomes a later issue. So you get "solve it in a really complicated way, but because you made it so complicated, barely make it work, and when it breaks, no one will be able to figure it out."
This is a pattern I see again and again. I constantly get downvoted here when I suggest that new devs should be able to get up and running within a couple of hours and that should be one of the priorities (at least on the "core" project that they will be working on). And yes, I "get it" - the company I work for just acquired a bunch of other companies with various stacks, on various clouds. But at the end of the day, people are way more worried about introducing a 1000 new libraries and writing ABSOLUTELY useless unit tests where everything is mocked than actually creating one source of truth for the data.
As you can see, I am a bit bitter about all of this.
This is a pattern I see again and again. I constantly get downvoted here when I suggest that new devs should be able to get up and running within a couple of hours and that should be one of the priorities (at least on the "core" project that they will be working on). And yes, I "get it" - the company I work for just acquired a bunch of other companies with various stacks, on various clouds. But at the end of the day, people are way more worried about introducing a 1000 new libraries and writing ABSOLUTELY useless unit tests where everything is mocked than actually creating one source of truth for the data.
As you can see, I am a bit bitter about all of this.