|
|
|
|
|
|
by derangedHorse
2212 days ago
|
|
|
I've also noticed that point in one of his talks and disagreed with it immediately. My own experiences have found small components easier to test and reason about in higher level components. I do think that navigating through a codebase with a lot of small files would make the codebase seem a lot more complex (especially without a modern code editor where you can't do things like click on an interface method and see all its implementations), but the biggest drawback of having small components, in my opinion, is that a lot of the developers I've observed are very bad at drawing coherent software boundaries |
|
|
That's a very good point. Designing small components probably requires more effort and can also cause a lot of harm if done incorrectly.