Brent Crossman
@bcrossman.bsky.social
Mainer, ex-banker, ex-distressed debt private equity, probably staring at a spreadsheet right now. Here's a little game I made http://reelationshipsgame.com
December 9, 2025 at 12:35 AM
Part 2 churns for a bit but it didn't seem worth speeding up. And, as usual, I use igraph instead of trying to code graph algos.
December 9, 2025 at 12:35 AM
Part 2 churns for a bit but it didn't seem worth speeding up. And, as usual, I use igraph instead of trying to code graph algos.
December 7, 2025 at 4:29 PM
Was pretty happy with this, as I knew as soon as I went with distinct_all in part one, that part 2 was likely a counting of the passes instead (kind of a classic AoC solution when doing a large number of paths).
December 7, 2025 at 4:29 PM
Was pretty happy with this, as I knew as soon as I went with distinct_all in part one, that part 2 was likely a counting of the passes instead (kind of a classic AoC solution when doing a large number of paths).
I feel like match .fun is my new eval(parse) for advent of code...and is something I will never use in real life
December 6, 2025 at 3:09 PM
I feel like match .fun is my new eval(parse) for advent of code...and is something I will never use in real life
Ahhh, that second read with read_fwf... that's slick and I could see myself using that at work (read it in, figure some good splits out, run it again) so I'll have to remember that.
December 6, 2025 at 3:09 PM
Ahhh, that second read with read_fwf... that's slick and I could see myself using that at work (read it in, figure some good splits out, run it again) so I'll have to remember that.
This may be the longest pipe chain I've ever written but it actually really helped me to just be able to sequentially move through the data manipulation until I could get back to my part 1 method.
December 6, 2025 at 12:31 PM
This may be the longest pipe chain I've ever written but it actually really helped me to just be able to sequentially move through the data manipulation until I could get back to my part 1 method.
But part II was too big every way I tried it with the join
December 5, 2025 at 9:43 PM
But part II was too big every way I tried it with the join
I kept trying to see if I could make it work somehow ("I'll just cross join the overlaps..."), stuff like that.
December 5, 2025 at 9:43 PM
I kept trying to see if I could make it work somehow ("I'll just cross join the overlaps..."), stuff like that.
I knew Part 1 wouldn't hold up for Part 2. I also knew, in my head, it was like drawing a plot where you could order it and hunt for gaps but it took forever to get it right (getting the edges and starts right with the inclusive was weird so I got some llm help on that).
December 5, 2025 at 11:53 AM
I knew Part 1 wouldn't hold up for Part 2. I also knew, in my head, it was like drawing a plot where you could order it and hunt for gaps but it took forever to get it right (getting the edges and starts right with the inclusive was weird so I got some llm help on that).
Grid problems are some of my favorites (in part because I've built a bunch of functions over the years for them)
December 4, 2025 at 10:46 AM
Grid problems are some of my favorites (in part because I've built a bunch of functions over the years for them)
Took me a bit to figure out how to use part 1 to do part 2. Seriously debated igraph ....
December 3, 2025 at 12:56 PM
Took me a bit to figure out how to use part 1 to do part 2. Seriously debated igraph ....