That is a misinterpretation of what was said. I did not say all complexity is needless nor did I claim to have the one panacea.
I presented my story of how we've actively kept our architecture simple, and noted we've had very few issues. I did not say our architecture is the architecture for everyone.
Then I said
> People really love adding needless complexity in my experience
If the complexity is legally mandated, as in healthcare, it's by no means "needless". Legal compliance is a need.
If the complexity is justified, has merit or value, it's not "needless".
However, I've known a fair number of people who work on complicated kubernetes driven architectures that give them non-stop grief, and whose user base max out at ten-twenty active users.
My point is just don't make things more complex than they need to be.
Sounds pretty absolute to me. I mean, when asked "Does your startup need complex cloud infra" (which is a loaded question) and you say "No. YAGNI" that seems pretty unequivocal and not really fair to say I misinterpreted it.
> My point is just don't make things more complex than they need to be.
I agree. I just don't care for the absolute language (that I and others use sometimes). It made learning when I was just getting into this field really tough. My answer to that exact same question would be "It depends".
No, people love thinking their experience is the same as everyone else's.
Have you ever worked in healthcare? Do you have any idea what sort of requirements there are for storing sensitive information?
>n my 12+ years I've only had to work off hours twice.
Well that settles it. Then no one on the planet should need cloud infra if yuo didnt.
And please, please don't tell me you've spent the last 12 years at the same place and have the gall to extend that to all software development.