Watch me code in Haskell for 25 days straight
| Day | Part 1 | Part 2 | Day | Part 1 | Part 2 | Day | Part 1 | Part 2 |
|---|---|---|---|---|---|---|---|---|
| Day 01 | ✅ | ✅ | Day 10 | ✅ | ✅ | Day 19 | ✅ | ✅ |
| Day 02 | ✅ | ✅ | Day 11 | ✅ | ✅ | Day 20 | ✅ | ✅ |
| Day 03 | ✅ | ✅ | Day 12 | ✅ | ✅ | Day 21 | ✅ | ✅ |
| Day 04 | ✅ | ✅ | Day 13 | ✅ | ✅ | Day 22 | ✅ | ✅ |
| Day 05 | ✅ | ✅ | Day 14 | ✅ | ✅ | Day 23 | ✅ | ✅ |
| Day 06 | ✅ | ✅ | Day 15 | ✅ | ✅ | Day 24 | ✅ | ✅ |
| Day 07 | ✅ | ✅ | Day 16 | ✅ | ✅ | Day 25 | ✅ | ✅ |
| Day 08 | ✅ | ✅ | Day 17 | ✅ | ✅ | |||
| Day 09 | ✅ | ✅ | Day 18 | ✅ | ✅ |
As usual, day 1 is pretty simple, so I took some time to just write some script to autogenerate everything I need to start working.
I do have a small complain about that day: part 2 is a bit unclear on the "oneight" problem (basically: this is "18" and not "1ight")
Simple day, the hardest part was parsing the input.
Well the actual hardest part was importing and learning how to use the regex module but whatever <:)
Repeat after me: manipulating 2D grids in Haskell is not fun.
I spent like 40 minutes on parsing the input... 😿
Was fun 😸
Challenging enough to make me take out a pen and paper, simple enough to make me solve it
I am now convinced that odd days are hard and even days are easy.
This is just simple maths!
Not too hard, so I decided to have fun with Instances!
I hated that I took a wild guess for part 2
This was probably the easiest one so far
I overcomplicated things once again
Well that was easy :)
What do you do when your bruteforce solution is too inefficient? YOU DO MEMOIZATION! :D
Easy peasy lemon squeezie
Not a hard day, but I'm a bit ill and I ended up going from an awful solution first before reworking everything.
THAT'S IT???
Spent 20 minutes debugging. Didn't notice I swapped north and south somewhere.
Please lord have mercy on my sould and stop giving me puzzles involving 2D grids.
Also, I was definitely not recoding an A* or a Dijkstra on the stop. No can do.
This is simply computing an area. Nothing more!
It took me a while to understand part 2 (thank you Adam for your explanation)
I am once again asking you to analyse the input and make random assumptions.
Stop making me analyse the input :)
Problems in 3 dimensions usually scare me. But it turns out this one barely makes use of its third dimension, so all is well :D
Now this is the AoC I like, where analysing the input gives me hint at what a more optimised solution could be, without making my solution input-specific!
My first time using a SAT solver!
Didn't really solve it with code lol