My Advent of Code tracker
  • Go 95.8%
  • HTML 3.4%
  • Rust 0.8%
Find a file
2025-12-15 10:12:01 +00:00
.vscode Updating for go modules... 2021-12-01 09:52:56 +00:00
2015 Removing data AoC doesn't want shared 2023-12-08 11:10:56 +00:00
2016 Removing data AoC doesn't want shared 2023-12-08 11:10:56 +00:00
2017 some updates 2025-01-02 15:53:46 +00:00
2018 Removing data AoC doesn't want shared 2023-12-08 11:10:56 +00:00
2019 Day 20 Year 2019 - func drawing mazes 2023-12-15 21:21:16 +00:00
2020 Removing data AoC doesn't want shared 2023-12-08 11:10:56 +00:00
2021 Removing data AoC doesn't want shared 2023-12-08 11:10:56 +00:00
2022 a bunch of updates 2025-01-02 15:53:46 +00:00
2023 updates 2024 2025-01-02 15:53:40 +00:00
2024 Bunch of 2025 2025-12-09 16:24:22 +00:00
2025 Advent of Code 2025 - done 2025-12-15 10:12:01 +00:00
aoc Advent of Code 2025 - done 2025-12-15 10:12:01 +00:00
html/2023 Removing data AoC doesn't want shared 2023-12-08 11:10:56 +00:00
not_public Removing data AoC doesn't want shared 2023-12-08 11:10:56 +00:00
rust/aoc-2019-intcode Add rust implementation of the intcode interpreter 2019-12-06 09:31:31 +00:00
uiua/2023-01 Up to day 6 2023-12-06 16:54:03 +00:00
.gitignore updates 2024 2025-01-02 15:53:40 +00:00
go.mod a bunch of updates 2025-01-02 15:53:46 +00:00
go.sum Add day 15 - add puzzle auto-downloader 2023-12-15 09:56:03 +00:00
main.go Advent of Code 2025 - done 2025-12-15 10:12:01 +00:00
parse_stats_test.go fix stat parsing for 2025 2025-12-02 13:30:25 +00:00
README.md Removing data AoC doesn't want shared 2023-12-08 11:10:56 +00:00

Advent of Code: https://adventofcode.com/

My solutions to the advent of code problems.

I started in Nov 2017 with the 2016 problem set. I didn't finish before the 2017 set started and I only got so far through that. But these problems can be solved anytime and I was never intending to top the scoreboard.

As I mostly use Go for these, there is a main.go script here in the repo.

Running go run main.go -year 2018 -day 1 will generate a skeleton problem for the year and day. -year is optional and defaults to this year. -day is optional only in December.

If the problem already exists then it simply executes the main.go file in the problem dir.

The template is simple because all the problems essentially boil down to: convert this long string into a (certain) short string.

(2023/12/08): I also just read this bit in the "about" section of the AoC website:

Can I copy/redistribute part of Advent of Code?

Please don't. Advent of Code is free to use, not free to copy. If you're posting a code repository somewhere, please don't include parts of Advent of Code like the puzzle text or your inputs. If you're making a website, please don't make it look like Advent of Code or name it something similar.

I want to keep the puzzle text and input (for me) so I can easily see what the problems where when looking back over this. Occasionally I refactor and want to run the whole thing again. While I could make this whole repo private, I feel like that takes all the fun out of sharing solutions.

I guess I need to keep the "puzzle text" and "input" separately, and privately. I have moved them to a not_public/ folder - and I now just have to remember to keep that backed up!

It's not perfect - the data are still in git history, and there are a few exceptions like when I have done work in specific languages other than go.