If you care more about pizza crust (especially when studded with burgers), you should instead compare the circumference:
I added a page about Leo’s astounding “iCE2Tetris” project to the London Computation Club wiki this week.
According to the git history, I have made 637 changes to the wiki since 2015, adding 8,228 lines and removing 1,911.
The write-up I remember most is “Types and Programming Languages Chapter 15: Subtyping” as I left the meeting defeated and burnt out, ready to give up on the club altogether but the act of writing it up clarified my understanding and restored my energy for returning to the club.
I recently inherited a codebase and am the sole developer working on it. This means I’m in the rare position to make whatever change I see fit to make it easier to work on and so I decided to start with dependency updates.
Having seen it used before, I decided to set up GitHub Dependabot. While finding the right documentation was tricky given that Dependabot is being integrated into GitHub itself, once I had it set up I was pleasantly surprised how well it worked: raising PRs for upgrades, automatically rebasing them and even detecting when multiple dependencies need to be updated in tandem.
I have mixed feelings about updating dependencies now being an essential part of being a web developer but if you’re going to have to do it anyway, you might as well automate it.
The other change I’d like to make is to the code style itself: the formatting, linting, etc. Running RuboCop with the project’s current configuration produces over 1,000 violations so I needed some advice on how to approach this in a manageable way.
Thankfully, Scott Matthewman’s “Calling in the cops” is an excellent talk about this exact topic: how to sensibly approach linting a legacy codebase.
This led me to discover the
Rails/FilePathcop prefers using forward slashes in paths and share in the collective disbelief that Ruby’s
File.joindoes not change separators based on platform.