u/Positive-Theory-4851

Been going in circles on this at work for weeks. Our monorepo started clean but builds are crawling now and one bad commit takes down four devs. Multi-repo isn't better, we've got version drift everywhere and nobody can agree which shared lib is the source of truth.

What keeps annoying me is that the whole debate assumes dependencies have to live inside a repo. If shared code was just a reference the system resolved and pulled in on its own, the mono vs multi question kind of dissolves. You'd get isolation without the drift, sharing without the coupling.

Anyone actually working this way in production?

Our product has been tested only by our own team for 24 months. We need to see it under live conditions. But the bottleneck I didn't see coming is that most potential users push back because they don't have time. They have the problem. They want the solution. Evaluating a new tool just doesn't fit anywhere in their daily grind.

I've considered offering paid pilots or guaranteed integration support, but the time problem is upstream of the money problem. The people we want to talk to don't have a free hour in their week, let alone a free week to vet a new tool. Cold outreach is brutal because nobody can read a 4-paragraph email.

What's worked for you when your buyers are time-poor?