|
|
|
|
|
|
by tm-guimaraes
1006 days ago
|
|
|
Bingo. At $work i see lots of projects leaving the monorepo due to that very mess. The problem is that services outside have other CI and maintenance issues that wouldn’t happen in the monorepo. But monorepo got so messy that it got unbearable. The proper solution would be to have a dev teams dedicated to tooling for it, the org has the resources, but it’s just not investing enough in that area. |
|
|