|
|
|
|
|
|
by ericyd
811 days ago
|
|
|
This is all sage advice except #7 "avoid monorepos" doesn't resonate with me. I worked at a seed level startup for 2 years and we used a monorepo for everything. I felt like it saved me a bunch of time vs my current employer with 400+ repos. I could potentially* get behind a logic of splitting unique web services into their own repo, but for libraries I find separate repos to be a huge unnecessary overhead. *potentially, as in I still prefer a monorepo for everything but I can see valid arguments for this one case |
|
|