1. Monorepo Benefits for AI Tools and Unified Context
Users praise monorepos for simplifying AI workflows like Claude by providing full context in one place, enabling atomic changes across frontend/backend/marketing.
"I used to be against monorepos... Then I got really into claude code, and monorepo makes sense for the first time in my life" - giancarlostoro
"Claude Code can actually work on multiple directories, so this is not strictly necessary!" - esafak (noting alternatives but acknowledging appeal)
2. Deployment Atomicity and Backwards Compatibility Concerns
Skeptics argue monorepos don't enable truly atomic rollouts, especially with clients, DBs, or multi-node setups, requiring compatibility regardless.
"Rollout should be within a minute... Aka it's broken 0.02% of the time" - ChadNauseam
"Atomic changes are mostly a lie when talking about cross API functions" - eddd-ddde
3. Git Workflow Debates: Squash vs. Rebase/Atomic Commits
Intense discussion on squashing PRs for clean history vs. preserving granular commits for review/debugging, with preferences for rebase or stacked diffs.
"squash results in a cleaner commit history" - sallveburrpi
"Squashing only results in a cleaner commit history if you're making a mess... throws information away" - Denvercoder9