tomplum/advent-of-code-2019

:gift: My completion of Advent of Code 2019 in an enterprise-style codebase with an emphasis on design, readability and testing.

🔭 I’m currently working on Advent of Code 2023 in Kotlin.

🇯🇵 I’m also working on Nyusu, a small personal project for practing your Japanese reading skills via news articles and headlines.

📗 I'm currently reading Head First Design Patterns by Eric Freeman & Elisabeth Robson.

advent-of-code-2019's Issues

Day 18 (Part 1) - Algorithm Performance Blocking Solution

The graphing algorithm is too slow.

See feature/day18 for an attempt to speed it up.

Gradle Buildscript - Separation of Concerns

Split out configuration and abstract common logic.

I.e. benchmarking.gradle.kts and test-coverage.gradle.kts.

Abstract Common 'Map' Implementations

Classes such as AsteroidMap, ScaffoldMap and ShipFloorMap all have common code that can abstracted into an abstract class.

The toString() implementation is the same as they all have an internal data structure of Map<Point2D, SomeDomainObject>. Generic typing can be used here for the value data type.

Future README Additions

• Favourite days (Technically / Most Fun)
• Most Challenging Day (18 as of this)
• Maybe add any interesting visualisations
• If you create custom JUnit arg provider annotations, add them to the JUnit5/AssertK Section

Also add things learned;

• Design Patterns w/list of them

• Algorithms: Graphing, Pathing, Searching

• Performance related stuff

• Functional Programming (Kotlin) Stuff incl. extension functions

• Maybe add what you prefer in Kotlin over Java?

• Section on Intcode Computer. Mention its progression over the event

• DeteKT Static Code Analyser

Introduce Extension Functions

Some functions would benefit from being transformed into extension function of their parameter types.

Example: Formulae could have its lcm function turned into an extension function of List<Long>.

Add Kotlin Doc To All Classes

Day 19 (Part 2) - Performance Improvement

Currently implemented lazy scanning the DroneSystem so that it scans for the beam 1 block at a time. It also stops scanning in the x-direction once its reached the end of the beam.

TractorBeamScan now also searches the current and the last block in-case Santas ship area overlaps two blocks. This saves having to scan 1 block, then 2, then 3... now it only does 1, then 2, then 2 and just 2 forever.

Solution currently taking ~13s to run with logging turned off.

Split Project Gradle Modules

Source, Common/Math, Solutions?

Day 16 (Part 1) Performance Improvement

Too slow and slows down tests too.

Create Jenkins Pipeline

Build > Test (Unit & JMH?) > Coverage > (Sonar?)

Resolve DeteKT Warnings

Fix Logging Implementation

Replace all println() statements in :implementation with debug() or info() logs. Then maybe introduce profiles to be able to toggle them on off. Will speed up unit tests.

This is having a big impact on the IntCodeComputers System IO. It's logging the I/O every time compute() is called.

Custom Benchmarking Gradle Source Set

Test Support Module

Maybe a new gradle module that the implementation:test src set depends on.

The InputReader could have its functions removed that take strings and just leave the ones with Days in.
A FakeInputReader or something of the sorts could be added for use in test scope.

The same goes for the ExampleMap and ExampleTile objects nested in the AdventMap2DTest. These can be pulled out into their own Fake or Dummy implementations.

JaCoCo Not Genearting Code Coverage

Report is being produced, but there is no coverage, only test pass/fail percentage.