I Am a Cross-Cutting Concern: On Having a Personal Monorepo

scottlawsonbc.com

5 points·lioeters··3 comments

This is an article about the advantages of keeping your code projects in a monorepo. I was surprised to see it because I'd started doing the same a while ago, as it naturally evolved, and found similar benefits to the ones in the article, such as discovering unexpected connections between my many projects. I even have my own CLI for managing it, like described in the article.

It's a good organizational pattern, not perfect but cuts out a lot of bureaucratic cruft in modern code management and lets you jump in and get to work. Hope it was OK to add an explanatory subtitle in the submission, since the title by itself was not clear what it was about.

Thanks for posting this. I'm glad I'm not alone in the monorepo club! I really believe in the benefits. Especially for a personal monorepo where the amount of code is not usually enough to run into the limits of git.

I'm curious about your CLI tool, what do you use it for?

Ah I was hoping to get a discussion started but no one bit the bait, haha. But I'm glad you saw it so I can personally thank you for a thoughtful article! I like the "Dot a Day" idea too, and enjoyed seeing a glimpse of the workspace.

As for the CLI, it's a primitive script (was Bash, now TypeScript with Bun) that does a few common actions like scaffolding a new project with minimal base, some shortcuts for Git, SSH, taking notes. I really liked this part of the article too, aside from the monorepo idea, seeing how other people are making their own personalized CLI tools to manage projects. Like that ASCII art, the feeling I got was a mix of nostalgia and camaraderie.

Reply on news.ycombinator.com