|
|
Hello everyone,
I’ve been working on a mid-sized open-source project and am curious how more experienced developers handle code-base structure and module organization.
How do you decide how to split your project into modules or packages?
What criteria do you use for naming modules and keeping them intuitive?
How often do you revisit and refactor the structure as the project grows?
Have you found any tools or practices particularly helpful for keeping the directory structure clean and maintainable?
I’d love to hear about your workflows, lessons learned, and any anti‐patterns to avoid.
Thanks in advance for sharing!
|
Locked
