I’ve worked on code that’s both ways. That is, either: (1) spaghetti code that relies on the author having a great deal of it memorized. It uses opaque types t

I’ve worked on code that’s both ways. That is, either: (1) spaghetti code that relies on the author having a great deal of it memorized. It uses opaque types that get passed through multiple modules. There is no hard separation of modules. Consequently it’s easy for someone who knows the system to reach into any part from one part and immediately get something done. However it’s a nightmare to make changes on otherwise. Unless you have an near-eidetic memory, it will likely negate any coding skills. (2) Strongly typed and modularized code that takes advantage of advanced language features. In this case, it requires somebody of a certain proficiency in the language, but they only need to focus on one module at a time, and the compiler will stop them from violating architectural assumptions. And these aren’t mutually exclusive, nor are they binary.