An unofficial home for the advent of code community on programming.dev!
Advent of Code is an annual Advent calendar of small programming puzzles for a variety of skill sets and skill levels that can be solved in any programming language you like.
Solution Threads
| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | 3 | 4 | 5 | 6 | 7 | 8 |
| 9 | 10 | 11 | 12 | 13 | 14 | 15 |
| 16 | 17 | 18 | 19 | 20 | 21 | 22 |
| 23 | 24 | 25 |
Icon base by Lorc under CC BY 3.0 with modifications to add a gradient
console.log('Hello World')
Well, that was a month. Congrats everyone who has reached the end, and thanks to everyone who has contributed solutions and advice.
Sometime in January I will create a megathread for visualizations. If anyone has any other ideas, happy to hear them, otherwise, take a well earned 11 month rest until next year :D
Congrats to everyone! Not first year, though first year of at least trying every problem. Burnout definitely got me by day 20 though, ha ha ha... There was a lot of ugly (readability a backseat to "code writing speed"), a lot of bad (don't ask how long the test suite has to run for), but an occasional gem of good (my day 19 solution is some of the most dopamine from just writing code I've gotten. I'm only used to getting that much when it actually gets merged). I learned a little through the problems themselves, but I did learn a lot about writing
macro_rulesmacros by creating a test suite generator and a benchmark generator. I also picked up some useful Git knowledge like--allow-unrelated-histories, interactive rebasing,--name-only, and using the reflog to help recover data (don't ask what happened on day 23). This year was a personal success. Till next year!I liked 19 as well. Adding memoization and seeing the runtime drop to near zero was so satisfying.
My main learning takeaway was that I am not fully aware of all the various inbuilt iterators in rust, so exploring those was quite valuable.