It seems to me that many well-known "best" practices need to be considered with more context. In an environment with a large, frequently changing team, heavy u

It seems to me that many well-known "best" practices need to be considered with more context. In an environment with a large, frequently changing team, heavy use of features that provide extra abstraction may result in less-skilled team members being confused. Most enterprise environments consider that normal. Most startups would fire a programmer who couldn't grasp reflection.