Inspired by Lucian’s post, I finally setup code quality for the first Practical Computer app.
This whole process was definitely borderline “do it right, or do it twice.” I wish I’d solved this a bit sooner. I knew it was necessary, but had kept pushing it back because the app isn’t even close to being live yet. But this line from Lucian’s post changed my opinion:
Side projects developed while having a full-time job have a unique characteristic worth noting. The time dedicated to working on the side project is not continuous. For instance, you may work on it for 1-2 hours on Saturday, and the next opportunity to work on it may only arise a week later.
It is then essential to make the code quality built-in and use as much automation as possible.
That’s a very strong argument, and one I hadn’t heard yet. Of course, since I delayed, it caused the past 3 work sessions to be solely about fixing up the repo. But the upside is now I have all the code ready for the next project. And speaking of that, here’s a gist of my customized set of Rubocop & CircleCI configuration. I hope it helps!
I made a few technical differences than Lucian:
- I trimmed down the Rubocops used. This gives me a balance of expressiveness & the benefits of a linter
- I chose CircleCI because it’s what I’ve been using for years and it’s Fine™️. Plus it has the distinct advantage of SSH access to debug jobs, and job reporters
- I’m using Bun, so relying on Dependabot for my JS dependencies
- I’m using Code Climate for maintainability monitoring