I thought monorepo was an anti-pattern. Especially in the age of micro-everything. This post just swayed me: http://buff.ly/2iOnYje
-
-
Replying to @housecor
I'd bet that it encourages NIH because it is much easier to have an internal dependency than an external one.
3 replies 0 retweets 0 likes -
Replying to @darrel_miller @housecor
IME it's much easier to use external dependencies at Google (monorepo) than at MS (highly fragmented repos)
1 reply 0 retweets 0 likes -
Replying to @darrel_miller @housecor
of the 14 package managers we have, which does your team use? :P
2 replies 0 retweets 0 likes -
In my neighborhood, package management is so bad that teams sometimes copy-paste *internal* code...
1 reply 0 retweets 0 likes -
...instead of creating a re-usable internal package. External code is even worse, of course.
1 reply 0 retweets 0 likes -
the fact that our experiences are so different is part of the point. Every group has its own mechanism here,
2 replies 0 retweets 0 likes -
and many of them are so bad that people go through horrible contortions to avoid using them.
1 reply 0 retweets 0 likes
If you have one platform, the cost of good tooling can be amortized across the entire company.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.