9 ms·
> Does this mean one per product, program, library, class? Only you can say. However, dividing stuff up later is annoying and leads to rewriting public history
by letmeinhere 5y ago
> Does this mean one per product, program, library, class? Only you can say. However, dividing stuff up later is annoying and leads to rewriting public history or duplicative or missing history. Dividing it up correctly beforehand is much better.
Got it, simply devise the correct level of modularization for an increasingly complex project at the beginning of time, to avoid annoyances. Easy peasy. /s
Git actually has tools to separate paths into their own repositories with intact histories, so I recommend the opposite.
- phone8675309 5y ago> Got it, simply devise the correct level of modularization for an increasingly complex project at the beginning of time, to avoid annoyances. Easy peasy. /s I know you're being sarcastic, but this is the "you know what every late project has in common - it should have started earlier" observation, just applied to program design. A killer thought terminating cliche.