#carbonlang there we go https://codeberg.org/pseyfert/advent-of-code/commits/branch/main/2025/02/carbon first star for day 2.

learned
- how to make bazel tell me how the linker gets called
- std::optional can be shared between carbon and cpp
- maybe advent of code is about dealing with real world projects where half way through the project all requirements and goals and boundary conditions change and i'm not going to do the second half … stupid elves with their product IDs.

#adventofcode

I just completed "Movie Theater" - Day 9 - Advent of Code 2025 #AdventOfCode https://adventofcode.com/2025/day/9

...and once again, needed a massive amount of help on part 2, one hundo cheated.

So, 11 out of 12 days completed for #AdventofCode and my thoughts for this year:
- `nim` is probably the language I've enjoyed coding the most in.
- `python`'s whole ecosystem of libraries just makes things so much easier. Day 10 and `scipy` just destroyed that solution (part 2 specifically)
- `rust` annoys me, but I 100% admit that it's a skill issue on my part.

#nim #python #rust #programming

and day 12, done.

Which means: 524* total, done for the yeah before Christmas (that was touch and go for a minute there), wooo!

https://github.com/Balise42/AoC2025/blob/main/day12.py for the last one

#AdventOfCode #AoC2025

PHEW. Advent of Code day 10b is done.

this was painful and this is ugly af, but THERE.

https://github.com/Balise42/AoC2025/blob/main/day10.py

#AdventOfCode #AoC2025

Season's Greetings to all.

Thank you to everyone on Mastodon that interacted with me to make working on this year's #AdventOfCode puzzles fun, and huge thanks to @ericwastl for making it possible again.

If you've nothing else to do this Christmas Eve (!) here's my account of solving the puzzles in #Fortran 77 (mostly). #RetroComputing for the win!

https://z80.timholyoake.uk/advent-of-code-2025-in-fortran-77-mostly/

Advent of Code - Day 11

Part 1 seemed straightforward enough, and it naively looked like Part 2 would be the same with a bit of filtering… but no! (Or maybe it would've been, if I could be bothered to let my code run for long enough.)

It's amazing how much faster things work with a bit of basic caching. 😅

#AdventOfCode #AdventOfCode2025 #Rust

I just completed "Laboratories" - Day 7 - Advent of Code 2025 #AdventOfCode https://adventofcode.com/2025/day/7

Like I expect most people, I found that a purely recursive strategy worked fine for the test input on part 2, but took an unrealistic amount of time on the real input. So I figured out that if you ever get to a point where another beam has reached, the result from then on is the same, and so we can cache.

https://codeberg.org/diffrentcolours/aoc2025/src/commit/817181a7ae2dab31bea890cea5c63f9de1406896/day7/src/main.rs

I had a lot of faff working out how to pass the cache object (just a HashMap) around functions while keeping it mutable. Turns out that #Rust needs you to declare something as mutable:

and I had missed out the second step.

Also, I figured out how to get rust-analyzer integration working in #HelixEditor which means I'm now learning how to use Helix properly.