3 ms·
Maybe we interpreted the article differently, but I understood this point as favouring a few "big" classes/interfaces/functions, as opposed to a lot of "small"
by yen223 3y ago
Maybe we interpreted the article differently, but I understood this point as favouring a few "big" classes/interfaces/functions, as opposed to a lot of "small" classes.
- akasakahakada 3y agoNot at all. > if you have a class that solves a difficult problem with, say, only 2 methods with no more than 3 arguments each, you’re in good shape
- Swizec 3y agoYes. The only way to solve a difficult problem with just 2 methods that take 3 arguments each is if those two methods are huge. Keep your APIs small, but poweful. This is the opposite of short function people which keep their APIs huge, but weak.