Here we go again! Christmas needs saving and what a better way to save it than solving Advent of Code puzzles.
This year, I'm doing a few of things:
- I'm solving these puzzles with Python
- I'm writing explanations to help people learn Python and software development
- I'm publishing all my notes as a digital garden on my website
I've been writing and talking about the benefits of taking good notes as a software developer. I want to show how Advent of Code can be a good way to get started. To inspire new people to start taking notes, I'm sharing all of my notes: solution explanations and technical notes about relavant topics. Those notes would normally live in my full notes system but for example's sake I've created a new, isolated environment to share here.
From this repository in GitHub, you can find the code solutions. For explanations and my full Advent of Code Digital Garden, head over to my website and dive in!
- Day 1: ⭐️⭐️ code : explanation
- Day 2: ⭐️⭐️ code : explanation
- Day 3: ⭐️⭐️ code : explanation
- Day 4: ⭐️⭐️ code : explanation
- Day 5: ⭐️⭐️ code : explanation
- Day 6: ⭐️⭐️ code : explanation
- Day 7: ⭐️⭐️ code : explanation
- Day 8: ⭐️⭐️ code : explanation
- Day 9: ⭐️⭐️ code : explanation
- Day 10: ⭐️⭐️ code : explanation
- Day 11: ⭐️⭐️ code : explanation
- Day 12: ⭐️⭐️ code : explanation
- Day 13: ⭐️⭐️ code : explanation
- Day 14: ⭐️⭐️ code : explanation
- Day 15: ⭐️⭐️ code : explanation
- Day 16: ⭐️ code : explanation
- Day 17: ⭐️⭐️ code : explanation
- Day 18: ⭐️⭐️ code : explanation
- Day 19: ⭐️⭐️ code : explanation
- Create a folder
inputs/
in the root. - For each day's input, create a
inputs/day_{daynro}.txt
file. - Optionally, create
inputs/day_{daynro}_example.txt
file with an example input from the puzzle description. cd src/
uv run day_1.py
(replace 1 with the day you want to run)- To run with the example code, add
example=True
toread_input
call in that day's code.