- Me
- [Rants for a while about a desired mechanism for solving a technical project-management issue at work]
- Better-half
- But there's no way to do that?
- Me
- Oh, no! It's worse than that! There are at least six ways!
Seriously, I'm spending too much time reading about `git-subwhatever`, build-system support for external dependencies, and even dependency management systems (though this really shouldn't require going to those lengths). And I'm really thinking about suggesting we do this the old fashioned way.1
1 Take the bits we want to factor out and share between projects, make each it's own project that builds a library, and link the libraries in the overlying projects. Done and dusted. Except for the hassle of getting a new hire up and running; and versioning issues; and remembering where each bit actually exists when you need to work on it; and deciding on, setting up, and enforcing commit privileges for each library; and extra deployment complexity for software we ship. But at least those are all known problems.
