4 ms·

Better title would be "Monorepos don't fit with my particular use case."

WorldMaker 8y ago
I disagree. The thesis statement repeated several times throughout is "Monorepos don't scale in exactly the same ways that polyrepos don't scale, the tools to solve the scaling problems are the exact same except monorepos need more of them and encourage bad habits along the way." You may disagree with that thesis, but it definitely seems to cover more than one use case.
- thehazard 8y ago
  ...the author's title is literally "monorepos: please don't!"
forrestthewoods 8y ago
I strongly agree. I hate this style of blog post. Telling people what they should or should not do is generally absurd. Every situation is unique and you can't possibly know another project's requirements or acceptable trade-offs. A better approach, in my opinion, is "Here's what we did and why". The author clearly has experience in the area. Great! Tell me about your problems. Tell me about your attempted solutions and what did or did not work. Tell me what you wish you had done! I'd love to use knowledge of your situation to inform my own decision making. But don't be surprised if my circumstances are different and lead me to prefer different trade-offs and choose a different solution. That doesn't make me a zealot or an idiot.
- icebraining 8y ago
  Isn't your own post telling people what they should and should not do (specifically on how to give advice)?
  - deleted 8y ago
    [deleted]
  - forrestthewoods 8y ago
    The irony wasn't lost on me. It's a fine line. Let me try a slightly different approach. When I blog I've had much better luck telling people "here's what I did and why". I don't know your circumstances and can't tell you how to solve your problems. You may need to choose different trade-offs than I did. With that said, here is my problem, how I solved it, and what I learned along the way. Hopefully you can learn from my experiences and make a more informed decision for how to handle problems you may encounter.

I disagree. The thesis statement repeated several times throughout is "Monorepos don't scale in exactly the same ways that polyrepos don't scale, the tools to solve the scaling problems are the exact same except monorepos need more of them and encourage bad habits along the way." You may disagree with that thesis, but it definitely seems to cover more than one use case.

thehazard 8y ago
...the author's title is literally "monorepos: please don't!"

forrestthewoods 8y ago

I strongly agree. I hate this style of blog post. Telling people what they should or should not do is generally absurd. Every situation is unique and you can't possibly know another project's requirements or acceptable trade-offs. A better approach, in my opinion, is "Here's what we did and why". The author clearly has experience in the area. Great! Tell me about your problems. Tell me about your attempted solutions and what did or did not work. Tell me what you wish you had done! I'd love to use knowledge of your situation to inform my own decision making. But don't be surprised if my circumstances are different and lead me to prefer different trade-offs and choose a different solution. That doesn't make me a zealot or an idiot.

icebraining 8y ago
Isn't your own post telling people what they should and should not do (specifically on how to give advice)?
- deleted 8y ago
  [deleted]
- forrestthewoods 8y ago
  The irony wasn't lost on me. It's a fine line. Let me try a slightly different approach. When I blog I've had much better luck telling people "here's what I did and why". I don't know your circumstances and can't tell you how to solve your problems. You may need to choose different trade-offs than I did. With that said, here is my problem, how I solved it, and what I learned along the way. Hopefully you can learn from my experiences and make a more informed decision for how to handle problems you may encounter.