recentpopularlog in

monorepo

« earlier   
System boundaries: the focus of design
Efforts must be focused on where the system cannot evolve gracefully.
systems  design  api  monorepo 
5 days ago by vipom
Monorepo: please do! – Adam Jacob – Medium
You should choose a monorepo because the default behavior it encourages in your teams is visibility and shared responsibility, especially as teams scale. You will have to invest in tooling no matter…
monorepo 
12 days ago by pks
Monorepo: please do! – Adam Jacob – Medium
It's new year's day and I'm arguing about how ridiculous monorepos are. 2019 is off to an inauspicious start. In spirit of this, I bring you a poll. Who are the bigger zealots? Supporters of:
monorepo  critique 
13 days ago by bobzoller
Monorepos: Please don’t! – Matt Klein – Medium
It's new year's day and I'm arguing about how ridiculous monorepos are. 2019 is off to an inauspicious start. In spirit of this, I bring you a poll. Who are the bigger zealots? Supporters of:
monorepo  critique  development 
13 days ago by bobzoller
Monorepos: Please don’t! – Matt Klein – Medium
Here we are at the beginning of 2019 and I’m engaged in yet another discussion on the merits (or lack thereof) of keeping all of an organization’s code in a “monorepo.” For those of you not familiar…
monorepo 
14 days ago by pks
Monorepos: Please don’t! – Matt Klein – Medium
I think the author is dismissive of some of the benefits, I agree with his main point. That most people cargo cult practices of Google and Facebook without understanding the enormous engineering effort those companies invest in their source control systems and related tooling.
scm  vcs  programming  monorepo  build 
15 days ago by jefframnani
Monorepos: Please don’t! – Matt Klein – Medium
He writes with an assumption of "scale" that's a silly one to make.

If I were starting a company today I would absolutely start with a monorepo, reap all of those benefits he tried to shoot down, and take it all the way to the bank for _years_ until I got lucky enough to get big enough to experience those problems. Then I'd choose whether to let people make more repos or go the Google route. Hell, by then, Git or Mercurial might Just Work™.
monorepo 
16 days ago by rcrowley
We’ll Never Know Whether Monorepos Are Better
This makes sense to me where the monorepo-vs-polyrepo argument is concerned -- it's another religious war:
About six months after the project was declared “done” (but there was always more to do, more improvements to make to our homegrown dependency management solution), we had a retrospective meeting. The same engineers who had taken sides, for and against the project, were again assembled to discuss how it went.
One of the main opponents went first.

“Thank goodness we’re finally having this retrospective,” he said. “I think we can all see that this experiment has been a colossal failure and that it’s time for us to change course and roll back to monorepo.”
“What do you mean?” one of the main multirepo advocates replied. “This was one of the best decisions we’ve ever made!”

This really shocked me. We had access to all of the data you could possibly want to evaluate the decision. The same engineers working with the same codebase had seen what it was like in the monorepo model and the multirepo model. We knew exactly how much it had actually cost to switch. We had lived with the advantages and disadvantages of both models. But still we couldn’t come to an agreement.

That retrospective taught me to be humble in my ambitions to “improve” engineering productivity. There’s no way to measure productivity in software, so there’s no way to know whether controversial, expensive “productivity enhancing” projects actually deliver on their promise, even in hindsight.
monorepo  productivity  dev  engineering  coding  polyrepo 
16 days ago by jm

Copy this bookmark:





to read