diff options
| author | hachem <im@hachem.wtf> | 2026-08-25 11:26:54 +0200 |
|---|---|---|
| committer | hachem <im@hachem.wtf> | 2026-08-25 11:26:54 +0200 |
| commit | 2b0dad9d87b2b663ddc008876a4dbc3d17993d27 (patch) | |
| tree | 7394aef05e1ca7c0518a0f7ff6d785c0304e1863 /README.md | |
| parent | 2806ed7d55266ececb197196af2fb84ae8c3cb35 (diff) | |
chore: refactor repository
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 43 |
1 files changed, 17 insertions, 26 deletions
@@ -1,38 +1,29 @@ -# Advent of Code - 2025
-Yes, I started late.
-Yes, I wrote it in x86_64 assembly.
-No, there is no absolutely no good reason for this.
-No, I'm not okay.
+# aoc
+My [AoC](https://adventofcode.com) solutions, written in x86-64 assembly. There is absolutely no good reason to pick assembly for this. I could have gone with C, C++, Rust, or pretty much anything else, but where's the fun in that? I'm doing this because I was bored, needed a reason to procrastinate, and, in any case, I don't have that many excuses to write assembly these days anymore, so these let me stay up to spec. Since assembly is beyond annoying to deal with between machines, I provide a Dockerfile with all the tools you might need to build and run the solutions.
-### Why assembly?
-Because I was really bored and I wanted more of an excuse to procrastinate.
+I don't particularly care about the AoC leaderboard. December is usually a pretty busy time for me, so I often don't have the time (or energy) to sit down and solve every puzzle on the day it comes out. As a result, some solutions may be uploaded days, weeks, or potentially much later than the actual puzzle release. That's intentional. I'm doing these primarily because I enjoy solving the problems and because they're a fun excuse to write increasingly questionable amounts of assembly. Getting a good leaderboard position isn't really the point for me. If a solution appears suspiciously late, that's probably why.
-also: **aura**.
-
-## Building & Running
-```sh
-$ make run-day[1-12]
-# example:
-$ make run-day1
-$ make run-day2
-```
-If you just want to build the binaries without running them do `make day[1-12]`.
+AoC gives each user their own puzzle input. I keep my inputs locally and do not commit them to this repository. If you're running these solutions yourself, you'll need to provide your own inputs in whatever format the corresponding solution expects.
## Docker
-If you do not have `nasm`/`ld` locally, build the container:
+To build the Docker image, run this from the repository root:
+
```sh
-$ docker build -t aoc-2025 .
+docker build -t aoc .
```
-Run a specific puzzle directly
+
+To run a specific day:
+
```sh
-$ docker run aoc-2025 day4
-$ docker run aoc-2025 day5
+docker run --rm aoc YEAR=2025 DAY=5
```
-Running with no arguments (`docker run aoc-2025`) will list the available targets. If you only want to build a binary, use `build-day[1-12]`.
-When you're done, delete the image:
+
+When you're done, remove the image with:
+
```sh
-$ docker rmi aoc-2025
+docker rmi aoc
```
## License
-[MIT](LICENSE), because you want this code, you need more help than permission.
+[MIT](LICENSE), because if you actually want to use this code, you clearly need more help than permission.
+
|