adam/AdventOfCode
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
My (attempted) solutions to Advent of Code. https://adventofcode.com/
33 commits 1 branch 0 tags 420 KiB
Elixir 100%
Find a file
Adam Millerchip 6144ba6159 Day 7 Parts 1 and 2
2020-12-07 18:25:31 +09:00
day1 Add simpler implementation for Day1 2020-12-01 16:48:01 +09:00
day2 bool != bool is xor 2020-12-02 16:30:38 +09:00
day3 Add note about tracking y distance 2020-12-03 14:44:50 +09:00
day4 Remove an unneeded Enum.map 2020-12-04 15:58:50 +09:00
day5 Move alternative Day5 impl to separate files 2020-12-06 11:42:48 +09:00
day6 Add Day 6 better implementation notes 2020-12-06 16:39:18 +09:00
day7 Day 7 Parts 1 and 2 2020-12-07 18:25:31 +09:00
template Commit template 2020-12-06 11:45:43 +09:00
README.md Day 7 Parts 1 and 2 2020-12-07 18:25:31 +09:00

README.md

AdventOfCode2020

My (attempted) solutions to Advent of Code 2020 in Elixir.

image

Strategy

If this year is like 2018, the last time I did this, each problem will be split into two parts. The second part can result in considerable refactoring of the first part, so I will split each part into its own file, like this:

  • day1/
    • day1part1.exs - solution to part 1
    • day1part2.exs - solution to part 2
    • README - my summary and notes relating to the day's problem
    • input - input file downloaded from Advent of Code (if applicable)

If I get stuck, my instinct is to be persistent and take as long as it takes to solve the problem. However I think this year I don't want the pressure of days piling up and this is supposed to be fun, so I will probably limit each problem to one day, and then come back to those that I had problems with later.

No checking other people's solutions until I've solved it myself - or otherwise given up. If I make any refinements as a result of seeing other people's solutions or reading forums, etc., I will commit them to a separate file to leave the original version in tact.