|
|
||
|---|---|---|
| app | ||
| docs/Advent of Code 2025 | ||
| gradle | ||
| .editorconfig | ||
| .envrc | ||
| .gitattributes | ||
| .gitignore | ||
| devenv.lock | ||
| devenv.nix | ||
| devenv.yaml | ||
| gradle.properties | ||
| gradlew | ||
| gradlew.bat | ||
| README.md | ||
| settings.gradle.kts | ||
Intro
Solving Advent of Code 2025 in Java.
Used libraries
- My own AoC library: https://git.mfocko.xyz/advent-of-code/java.git
Summary
!
Advent of Code itself
I have a bit of mixed feelings. Thankfully, this year, there was only one day that was particularly obnoxious with regards to parsing.
There were only 12 days instead of the usual 25. I have tried to solve all days at 6am (CET) and… I'm not very used to writing Java at 6am to be honest 😄 So I definitely don't mind an early end on that front 👀 Though it is quite known that the complexity of the tasks grows towards the end of the AoC, so this year might seem a bit easy-going? I can understand the need for a bit of a challenge.
Java
Even though Java is the first language I've learnt and also learnt to hate further on, it was quite pleasent experience in my opinion. I confess to abusing the streams and other FP-like “features”.
I definitely hate the boilerplate for each day… but looking back at it, it makes it quite customizable, so, for example, in [day #8] I was able to simply add the constraint (which was different for sample and challenge input) to constructor and it allowed pretty easy testing and computing the challenge at the same time.
Toolchain
I didn't feel comfortable working with either IDEA or VSCode. They each have their own quirks, e.g., not working completion (which is definitely helpful with streams and data structures), or issues running the puzzles in a way that would fit my workflow.
OTOH it was a quite pleasant experience with testing (apart from constructors in classes that are not instantiated) and also doc-generation. Though I feel that javadoc is still… bit obscure format for me.