We’re on the cusp of December again…somehow…also, we’re nearing the end of 2025. Where is time going?
Setting that existential question aside for a bit, December means it’s Advent of Code time again. I haven’t had much success in the past, but each year I dip a toe in and give the puzzles a try.
This year, due to a variety of factors, the AoC author is reducing the number of puzzles by half to 12. This is good and bad, good in the sense there are fewer, bad in the sense they’ll get difficult very quickly.
We shall see how it goes.
I will write about my approach and progress.
The major thing I’ll be trying to do differently is keep my system simple. I’m going to use my MacBook Pro exclusively and will only be using iTerm and Neovim. I don’t want Rust Analyzer as training wheels. I need to work on my visualization of what’s happening with the code I write. This is important with Rust, as it helps to cement the ownership system. I’ve not made enough effort to work without supports and develop my own internal model of what’s happening.
The other thing I plan to try this time is to solve the puzzles on paper first. This will make things much slower, but it’s a step I tend to skip, to my detriment. I need to learn to sit with the discomfort of not being able to make progress. Hopefully, with a notebook first approach, I’ll give myself some tools to think and loosen up the mind.
So, I don’t think I’m going to be very successful, as usual, but I hope to make it to at least the 3rd puzzle this year without flaming out.
Wish me luck!
Comments