2 ms·
What do you do if you need a higher level interface to a bunch of classes that are already fairly complex in their own right? Seems to me "plain" nouns (since
by dasil003 15y ago
What do you do if you need a higher level interface to a bunch of classes that are already fairly complex in their own right? Seems to me "plain" nouns (since really these are all nouns) are good for simple concepts and things with real world analogs, but in projects of any complexity you quickly end up with complex logic whose only succinct description is what it does.
My experience tells me the key aspect of software quality is the interfaces. The simpler and less leaky the interfaces, the more understandable, maintainable and correct the software will tend to be. Part of this is inherent to the problem itself, but a big chunk of it—especially in the middleware—is the ability of a software architect to have a sense of the whole project and figure out the best places to carve the interfaces. Doing so correctly is the difference between a maintainable million-line project and spaghetti. Truly brilliant engineers will figure out interfaces that make code 100x more reusable and elegant, maybe spawning open source extractions, etc.
If something is named well is an orthogonal concern, and highly contingent on what the actual object is. The best code in the world might be impossible to name intuitively if there is no real world analog.