26661cbfd8Minor fixes to readme and user agent.chrisly422024-12-08 13:07:05 +0100
8cdfdda1f4Removed all puzzle descriptions, replaced by a link. Not deleting history though: People who want to get the descriptions will do so anyhow.chrisly422024-12-08 12:54:38 +0100
0876e5c92cRefactored CharGrid class to use a generator instead of two for-loops. Deprecated old API.chrisly422024-12-08 08:05:40 +0100
9d61ce1bc4Day 8. Could have been faster if I think first.chrisly422024-12-08 07:14:18 +0100
15ce1ad06eDay 7 Part 2 best brute force optimization without using dynamic programming.chrisly422024-12-07 07:20:08 +0100
8d492486fbDay 7 Part 2 optimized to 666ms (instead of around 3000ms).chrisly422024-12-07 07:13:32 +0100
d2487ed762Day 6 part 2 :'-(
Chris Hodges
2024-12-06 12:31:43 +0100
3cc10ea7c3Day 6, can't seem to get part 2 working :-(chrisly422024-12-06 07:41:33 +0100
a14958b8a6Day 5, total failure, mainly due to testInput containing extra lines without me noticing. Stopping this madness once and for all.chrisly422024-12-05 07:24:28 +0100
782d12c048Very minor day 2 refinement.
Chris Hodges
2024-12-04 10:03:28 +0100
4bf79c0e89Added some utility functions to CharGrid.chrisly422024-12-04 06:38:33 +0100
77618b3534Day 4. CharGrid class could need some improvements.chrisly422024-12-04 06:20:45 +0100
64ba775ca6Bugfix for an edge case that wasn't in the input, gladly.
Chris Hodges
2024-12-03 11:20:38 +0100
b770db22c6Minor tidying.
Chris Hodges
2024-12-03 10:57:11 +0100
7695a005c9Day 3, meh for having multiple lines of input and meh for having two different inputs and meh for being lazy.chrisly422024-12-03 06:23:12 +0100
6b27f3741dWas bored, so started to do 2015.chrisly422023-12-28 20:01:40 +0100
73164a0ee3Unlike other people, I don't have a ready set of graph algorithms ready, so I tried a bit to implement Karger, before I went back and simply added -Kneato to my dot graph output and then the edges to cut became very clearly visible. I could have saved a couple of hours.chrisly422023-12-25 08:10:42 +0100
0acad0121cDay 24. This was a mad thing. I hate you all for using term solving tools under python. Thanks to the other kotlin guy who went the chinese remainder path and give a good amount of inspiration (strangely, the test input fails). I was thinking that some sort of modulo arithmetic could solve it, but it was too hard to figure out. What a waste of an otherwise nice xmas day.chrisly422023-12-24 14:50:09 +0100
6b904bb42cMinor optimization on speed for day 23.chrisly422023-12-23 12:40:51 +0100
3a8a2d79a9Minor update to Day 15 because I should have used a linked hashmap in the first place, if I had only read the instructions clearly enough.chrisly422023-12-16 13:19:03 +0100
b98653f2b9Slept in, didn't hurry to finish Day 10. Considering the solution elegant regarding the traversal of the pipes.chrisly422023-12-10 11:31:09 +0100
1aac27e384Day 4: Lesson learned: Don't make bugs, use pen and paper first.chrisly422023-12-04 07:17:47 +0100
afcfed70d7Reworked day 3, adding a generic class for 2D grids with some special functions for day 3. Modified template to avoid double evaluation.chrisly422023-12-03 15:21:59 +0100
077fbe6e21Day 3 and I am beginning to hate this.chrisly422023-12-03 07:12:48 +0100
15d5e2ade8Day 2: Revisited reg ex parsing, but it really turned out to be too complicated for me. Simplified part 1 a little.chrisly422023-12-02 07:42:10 +0100
db8acdd483Day 2. Spent too much time on input parsing.chrisly422023-12-02 06:29:27 +0100
43cbc17f74Added a downloader and template generator, new template and retrofitted the old days, adding solution to day 4.chrisly422023-11-25 12:30:33 +0100
chrisly42
Chris Hodges