|go ahead... be a heretic|
Re: Refactoring complex module into set of specialized sub modules?by BrowserUk (Patriarch)
|on Apr 06, 2019 at 05:12 UTC||Need Help??|
The reason you are finding what you are trying to do, hard, is because it is a purely intellectual exercise, not driven by either need or urgency.
You'll probably take that as a criticism, but it isn't intended that way, we all have our back-burner projects. I've dozens.
IMO there are exactly two reasons to 'create a module':
Any and all other reasons are 'costs'. To you and your life, and your company or institution. Investment, maybe; but only iff ....
And whether the ...s ever happen, whatever they may be, is unknown and unknowable. Like an old man putting money under the mattress for a rainy day that may never come.
That doesn't mean you don't do them -- if (for example) OSS is a hobby of yours, then 'somebody might find it useful' can be enough of a reason.
If you are young enough, and work (or aspire to) in a field where OSS contributions can be considered a part of your CV, better still.
But structuring and restructuring code to satisfy the intellectual need (your own, or that of others) to 'get it right' has been the ruination of vast numbers of commercial projects.
And if this is a purely personal project, the knowledge that you 'did it right' will be of scant comfort when you look back at all the things you didn't do to achieve it.
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority". The enemy of (IT) success is complexity.
In the absence of evidence, opinion is indistinguishable from prejudice. Suck that fhit