Advent of Code

I know from my experience as a TA for an entry programming class that putting together problems (especially some of the difficult ones he had to explain) is not an easy task, and he ended up doing 49 problem statements, though probably 15-20 shared significantly with their first part predecessors.

I've had to deal with x/y-coordinates so many times in this year's advent of code and in Python, you can throw together some things pretty easily, but in Java, it just seems like you're pushing in a direction that no one things you should be pushing.

Part two was a different beast, and to be clear, I started it right after part one and the attempt using my part one code to get the part two answer is STILL running (this is after now 10 hours of running) I let it run overnight as I slept, because I was curious if my logic worked to begin with.

The reason my part two solution took so long was that I misread the first rule.

So, Day 20 [https://adventofcode.com/2020/day/20] was rough and maybe it was rough because I took shortcuts

The real issue is that I didn't have any easy test string to look for those issues, but when I first did the string replace option, I THOUGHT I might encounter it, but didn't end up thinking I really would encounter a problem, I guess I was wrong.

oh my gosh, I now see where I went wrong in day 11 because in that case, the rows wasn't equal to the columns

Streams kind of acts like MapReduce in some ways, but also more like serial calculations in other ways, and it seems you can support both from a greater perspective going forward.