Large apps will always be hard to navigate - just because they are big...
All apps will get messy over-time too. I think the key is to write your apps as simple as possible (which sometimes does require a complex strategy) and in a way that individual pieces are easy to replace.
That's why I prefer to avoid sharing code as much as possible. That way, most parts of the app are isolated and can be replaced without affecting other parts.
When you reffer to avoid sharing code, do you mean sharing code between modules in the same app, or not code shareable code in mind for future projects?
Does it means that is better to write two almost identical functions in two modules to not share between both or not to use a module for common functions?
Generally, I mean sharing code between modules or assemblies, etc.
At face value that might sound strange to many, but I've seen this hinder large projects because they are all coupled together due to these shared "common" libraries.
This is what something like microservices totally avoids - which is one of the main reasons these services are easily replaced, etc.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Large apps will always be hard to navigate - just because they are big...
All apps will get messy over-time too. I think the key is to write your apps as simple as possible (which sometimes does require a complex strategy) and in a way that individual pieces are easy to replace.
That's why I prefer to avoid sharing code as much as possible. That way, most parts of the app are isolated and can be replaced without affecting other parts.
Using something like Clean Architecture or something like a vertical slice architecture really helps.
Thank you James,
When you reffer to avoid sharing code, do you mean sharing code between modules in the same app, or not code shareable code in mind for future projects?
Does it means that is better to write two almost identical functions in two modules to not share between both or not to use a module for common functions?
I'll take a look to your link!
Thank you!!
Generally, I mean sharing code between modules or assemblies, etc.
At face value that might sound strange to many, but I've seen this hinder large projects because they are all coupled together due to these shared "common" libraries.
This is what something like microservices totally avoids - which is one of the main reasons these services are easily replaced, etc.