I've worked with (and been a) staff engineers who have fallen into the same trap. Over engineering is something that we need to constantly be cognizant of because it's often dependant on scope.

E.g. are microservices over engineering? If you have 1 user now, and only expect 100 total users over the next 2 years, probably. If you're running AWS, definitely not. Everything in between becomes a grey area that requires thoughtful architecture to decide on the right approach, and even very experienced people will make the wrong calls

Well, sure. I wasn't saying it never happens to non-junior engineers.

Respectfully, that seems to be what your parent comment says :).

> I think for junior developers that might be true.

That strongly implies, if not outright says, "this only inflicts junior engineers".

I meant "if this can be generalized onto anyone at all, then at most junior developers". Was probably not the best way to express that, haha.

no I'm not junior