ps. look out for all my other solutions for Advent of Code challenges here.
See details of the challenge here.
The input for today’s challenge looks like this:
bot 171 gives low to bot 4 and high to bot 84
bot 1 gives low to bot 117 and high to bot 81
bot 82 gives low to bot 209 and high to bot 103
bot 128 gives low to bot 56 and high to bot 91
value 23 goes to bot 8
bot 7 gives low to bot 148 and high to bot 22
To parse this input file, it feels to me that Regex is the best bet; and to answer the challenge we can run the simulation until one of the bots have both value-17 and value-61 chips.
The bulk of the work happens in the definition for the events sequence. I decided to use a Dictionary to track the current state of the bots, but I didn’t want to expose that mutability to the outside hence why it was declare inside the definition for events.
Ultimately events is a sequence of tuples telling us which bot gave low and hi values to which targets as we simulate the behaviour of the bots. It makes answering both parts of the challenge really simple.
What do you get if you multiply together the values of one chip in each of
outputs 0, 1, and 2?
We can consume the same events sequence we created earlier, and collect any values that are given to output 0, 1 and 2 and multiply them.
- Day 10 challenge description
- Advent of Code 2015
- Solution for Day 9
- All my F# solutions for Advent of Code
- Github repo
I specialise in rapidly transitioning teams to serverless and building production-ready services on AWS.
Are you struggling with serverless or need guidance on best practices? Do you want someone to review your architecture and help you avoid costly mistakes down the line? Whatever the case, I’m here to help.
Check out my new course, Complete Guide to AWS Step Functions. In this course, we’ll cover everything you need to know to use AWS Step Functions service effectively. Including basic concepts, HTTP and event triggers, activities, callbacks, nested workflows, design patterns and best practices.
Here is a complete list of all my posts on serverless and AWS Lambda. In the meantime, here are a few of my most popular blog posts.
- Lambda optimization tip – enable HTTP keep-alive
- You are thinking about serverless costs all wrong
- Many faced threats to Serverless security
- We can do better than percentile latencies
- I’m afraid you’re thinking about AWS Lambda cold starts all wrong
- Yubl’s road to Serverless
- AWS Lambda – should you have few monolithic functions or many single-purposed functions?
- AWS Lambda – compare coldstart time with different languages, memory and code sizes
- Guys, we’re doing pagination wrong