Yesterday’s ended up involving drawing shapes on paper and cutting it out. I was convinced I’d find some way of programatically defining the transitions over the edges but ended up just hard-coding the 14 different transitions of my input. Pleased when it worked but not really fun.
Todays was easy enough. I suspect there might be something clever way to do it but my laptop churned through my naive code (with some hideous inefficiencies that I kept thinking “I’ll come back and sort in part 2 when I need it to be faster”) in less than half a second. I’ll leave it there and get on with some proper work.
Part 2 was trivial in mine – I just changed my for loop to execute for ever and added a “if (proposedMoves.isEmpty()){break;}” statement instead.
I’m still waiting for something to cause the levels of pain that the scanners/beacons did last time. That hurt my brain.