When programming, you may struggle to find coherent meaningful names and types, given conflicting alternatives, metaphors and styles suggested by many previous APIs in many languages or by scientific literature. Or you may just pick the first thing that comes to mind.
Google-style monorepo does allow "gloobal" refactoring. But it won't scale to thousands of loosely coupled teams publishing or using free software.
I have pushed minor API changes to ASDF by sending patches to all packages broken in @Quicklisp… tough. Yet the next "easy" case.
-
-
I’m not convinced that it won’t scale. Just requires rethinking tooling (and GitHub could do this once and for all).
-
For example, I’m using `mbt` rather successfully in our organization and it isn’t hard to imagine how that could scale to 1000s of modules on GitHub across disparate teams.
- 3 more replies
New conversation -
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.
Read my blog!