adventofcode.com

                        *
                       <o>
                      <o>O>
                     <o>>O>>
                    <<O>>>o>>
                   <<o<O>>@>>>
                  <<*<<@>>>*>>>
                 <<@<<<O>>>@>@>>
                <<O>>o<<<o<<*>>>>
               <<o<<<O<*<@>@>>>O>>
              <@<O<<<*<@<<@<o>@>>>>
             <<*>o<*>>>*<<<O<<<O>>>>
            <*>>>O>>>@<@>>>O<<<@<<<*>
           <<o>*<o>O<<O>>>O>>*>>>o>>o>
          <<@<<<@>>O<o<@<<<*>>>o>>>*<O>
         <O<<<o<o<<*<<<@>@>>>O<<<o>>>o>>
        <<o>>*<O<@<<*>*>>*<@<<O<<<O>>>*>>
       <O>>O>>>*<<O<*<<o<*<<o<O<*>>>@<<o>>
      <<O<@<O<<<o<o>>>O<o>O>>>O<<*>>@>>o>*>
     <<@<<<O<<o<o<<*>o>*<*<<o<<<*>>o>o>o<@>>
    <<@<<<O>>O<<<*>@>>>@<<*<@>>O>>>o<*>>>O>O>
   <<o<*<<<*>>>o<<@<<<O>@<<*<*>>*<<o<<<@<@>>*>
  <*>o<<<O>>>o<<O>*>@<<@>O>@>@>>@<O<@>>>@<O<o>>
 <o>>>O>O<<O<<<*<O>>O>>>O<o<<@<<<o>>>O<o>>>O>>>>
<@<<@>o>*>>O<o>>o<*>>>O<<<@>>*<<<O<O>O>@>>>o<<*>>
                      |   |
                      |   |
           _  _ __ ___|___|___ __ _  _

Advent of Code is an Advent calendar of small programming puzzles for a variety of skill sets and skill levels that can be solved in any programming language you like. People use them as a speed contest, interview prep, company training, university coursework, practice problems, or to challenge each other.

• Ad private
• Chiel
• Jack
• Lannie
• Laura
• Renzo

• 2022
• 2023

I started participating in 2020. I have, since then, also solved others. Furthermore, living in the Netherlands, and being a night owl, getting myself behind a screen at 6:00 (local time) is hard. Nevertheless, I solved some of them within an hour. All results can fe found here: Solving.md.

When a measure becomes a target, it ceases to be a good measure. We all know it to be true, so keeping track of the lines of code per puzzle is questionable, nevertheless, I do: LoC.md.

Note that comments, whitespace, namespace declarations, main class declarations, and lines only containing brackets or attributes are ignored.

Another measure that should not become a target (but secretly is): durations. An overview of my results can be found here: Durations.md.

All puzzles can be run as unit tests. To reduce plumbing code I've extended on NUnit. All puzzles have the following template:

namespace Advent_of_Code_@Year;

[Category(Category.SomeCatagory)]
public class Day_@Day
{
    [Example(answer: 666, "Short Example")]
    [Puzzle(answer: 666, O.μs10)]
    public long part_one(string str)
    {
        throw new NoAnswer();
    }

    [Example(answer: 666, "Short Example")]
    [Puzzle(answer: 666, O.μs10)]
    public long part_two(string str)
    {
        throw new NoAnswer();
    }
}