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.