3 ms·
I've eased this multi-project burn out in those steps: - move all projects to a monorepo. This is great because all projects are in one place, they become inte
by epolanski 4y ago
I've eased this multi-project burn out in those steps:
- move all projects to a monorepo. This is great because all projects are in one place, they become interconnected as some code will end up being a library for multiple ones. This ensures that even when I'm doing side-project "foo" some of the code or stuff will also end up improving "foo" or "bar".
- move the monorepo to github codespaces. The very last thing I want to do when I want to work on my side projects after some time is to remember how I had to setup everything, from ide, to the os, etc.
- keep todos, documentation, notes, all in the monorepo. What did I have to do? `apps/foo/todo.md` or search in the project for "TODO:". No point into having docs on different services, they stay close to the project.
- write E2E and integration tests first, never unit test anything that doesn't really need to, implement in the end.
And that's it. Lowering a lot the entry barrier to contributing and getting back on projects was a huge step (I literally need codespaces to load). Then came creating an ecosystem around my projects thanks to the monorepo. I can now forget a project for months and come back to it with a small effort or checking back where I was.
I admit I will never write git in two days like Linus, I won't be releasing a hit game on Steam at any time, but I have fun with my projects, I learn a lot, and even though they move slowly they do move consistently in time.
Not saying you will release a banger OSS project this way or some killer application that will make you rich, that requires discipline and focus more than organizing a git repo and few tools, but you will build yourself a nice playground which at every iteration will make further experimentation or production have lower friction.
- zaptheimpaler 4y agomonorepo is a good idea. how do you manage multiple languages and build toolchains?
- epolanski 4y agoIt's monolanguage by design and intention, I don't think I would be able to handle this added complexity which is far from trivial to tame. Potential benefits from having access to more tools would take too much of my limited time and energy from moving the applications further. That being said, I use @microsoft/rush for my monorepos and I think that with a bit of tinkering it could easily support building external tools.
- yodsanklai 4y ago> move all projects to a monorepo. I wonder if it's a good idea. Some projects have nothing to do with each other. The toy compiler in Haskell isn't going to benefit from the experimental OS in C. On the other hand, the git history and branches will be harder to manage.
- mathgladiator 4y agoAuthor here, the one project that has been causing me stress are the ones outside my current mono repo. The core project is giant, but the other two repos (the IDE and runtime) are separate... The tool chain I'm using is easy to install fortunately, and I can bootstrap it quickly. I've automated most of it to a single command line, and I can deploy in two commands (for sanity sake).