Replies: 1 comment
-
|
If 300+ modules isn’t a problem today, don’t try to solve it now. As long as your abstractions are clean and consistent, scaling won’t hurt. Evolutionary design is about getting the fundamentals right and refactoring when real pain shows up, not anticipating every possible issue. Further reading recommendation: https://martinfowler.com/bliki/Yagni.html |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I have a question.
I analyzed subfinder before and really liked the way it uses interface-based modules (like Source). I used a similar design in my own project.
But I’m wondering — if I have 300 or even 1000 modules like this, will the codebase become too large or hard to manage?
Also, If imitating the nucleus, will it expose too much information?
Beta Was this translation helpful? Give feedback.
All reactions