I think this puzzle was about as frustrating as actually untangling a mess of wires, so that’s fun!

Now that I’m caught up, I want to try to provide some more details on how I came to my solution.

Day 2 was pretty interesting! Design a small interpreter to run the int-code program, and find the result.

Puzzle 1

A couple interesting twists in Puzzle 1 that I liked here are that the program is allowed to modify itself, and that I have to modify the program ahead of time. First, the (small) computer:

Day 1 ended up being a nice, gentle introduction to the year, with a bit of flexing of some fun programmatic skills. The macro from Day 0 came in handy to really keep things small and simplified.

Puzzle 1

Puzzle 1 was pretty straightforward. Given the masses of a number of modules, calculate all the fuel required.

I’m three days behind, so this will be kept pretty short! This post details the set-up for the rest of the exercise. I make no guarantees that I’ll solve all of them, as I only made it to day 8 last year.

The Project

Advent of Code is a fun coding challenge that poses 2 new puzzles from Dec. 1 to Dec. 25. I enjoy [elixir] and don’t get to use it at work, so I will be solving the puzzles with elixir. A quick mix new advent_of_code will get us up and running!

At GitLab, the front-end department has dealt with too many CSS issues. To take a stand against these issues, we’ve declared to not write as little CSS as possible. We’ve focused on writing utility classes to reduce these CSS conflicts.

As part of this, the talk of using tailwindcss came up. Unfortunately, we are on bootstrap and stuck in the bootstrap world, and I personally assume that there would be a lot of collision, either through class naming or specificity, or something else. It made me take a long hard look at my dependency on Jekyll themes, and wondered why I never bothered writing this up myself.