I run into this every where I go.
"Simple" is rarely defined. Building layers consistently is never on their mind. They never had to maintain a codebase thats over 20 years old, while adding new functionality that doesn't break existing functionality.
They never fully understand the value of the single responsibility principle, they never had to maintain gnarly test suites for large & bloated classes. They never question how to structure their code to avoid changing 10 files for a simple change.
They generally find a couple of paper tiger points and anchor to them.
Its OK if a developer has never come across these circumstances, but it is dangerous for niave hubris devs guiding juniors into over simplified points of views, because they haven't gone the next step in their knowledge.
