> When everyone is committing to the same repo certain types of encapsulation and abstraction aren't always as critical as they're made out to be.

Until you want to refactor or reuse. We develop a lot of in-house tools for our rather esoteric systems and systems analysis. We start by writing specific solutions, then refactor as we find common elements across tools. Now we have several libraries that can be used by anyone to develop custom solutions to problems because we've factored out common elements into those libraries.

Treating encapsulation and abstraction like they're unimportant would've resulted in a lot of extra work over the years.