Of course, but there is a difference between programing using sdk/library/api and some glue, and actually engineering some self standing solution, and everything in between that. I belive blind programer wouldn't fare well in fast churn ci/cd every minute startup, but would be amazing in embedded space with multi year release cycles.
I perhaps didn't express my point clear enough. If you're developing net framework, ios or android sdk itself, you're trying to be consistent and well structured, and you'll probably mostly work in one part of the code base. Then app dev will again use your structured expected layout as part of his structured system. The point wasn't to know the whole code base, but rather that it's made in a way that it makes sense how to use nth thing after you use first few.
I developed ios apps, and it's vastly different experience than android or flutter. And then that is not even comperable to JS and dozen build steps, standards, and libraries that are countless and all with different approaches to how they're structured and built...
And even if you make it consistent, using domain driven names, etc.
The method names are going to be different and not easily guessed. Why wouldn’t I use an IDE feature where I put a “.” at the end of the class instance and use autocomplete to tell me the methods? Why wouldn’t I use an IDE feature where when I rename a method, it automatically renames all of the references in an entire project?
Unless you are using reflection, this can be done in a provably correct way in a statically typed language?
