ps. look out for all my other solutions for Advent of Code challenges here.
Sorry for the delay in getting this post out today, I enjoyed some really fine Ramen with some of the lovely people I worked with at Yubl and only managed to find time to do the challenge and write this post late in the evening.
(ps. here are some of the best people I have ever had the pleasure to work with )
anyways, let’s get back to the main topic…
See details of the challenge here.
The input for today’s challenge looks like this:
Looking at the input, they all follow a similar pattern and we can separate them out with String.Split(‘[‘, ‘]’) and end up with an array where the odd number elements are the hypernet sequences.
We still need a way to look for ABBAs, which fortunately can be achieved easily with Seq.windowed and a bit of pattern matching (see the hasABBA function below).
You would also like to know which IPs support SSL (super-secret listening).
An IP supports SSL if it has an Area-Broadcast Accessor, or ABA, anywhere in the
supernet sequences (outside any square bracketed sections), and a corresponding
Byte Allocation Block, or BAB, anywhere in the hypernet sequences. An ABA is any
three-character sequence which consists of the same character twice with a
different character between them, such as xyx or aba. A corresponding BAB is the
same characters but in reversed positions: yxy and bab, respectively.
aba[bab]xyz supports SSL (aba outside square brackets with corresponding bab
within square brackets).
xyx[xyx]xyx does not support SSL (xyx, but no corresponding yxy).
aaa[kek]eke supports SSL (eke in supernet with corresponding kek in hypernet;
the aaa sequence is not related, because the interior character must be different).
zazbz[bzb]cdb supports SSL (zaz has no corresponding aza, but zbz has a
corresponding bzb, even though zaz and zbz overlap).
How many IPs in your puzzle input support SSL?
Part 2 is slightly more challenging as it requires to track the ABAs from the sequences that are not part of the hypernet sequences, and look for corresponding BABs in the hypernet sequences (seriously, who thought of these acronym…).
We can use the same technique of Seq.windows + pattern matching to find all the ABAs, but we also need a hasBAB function to check if any of the corresponding BABs exists in a hypernet sequence.
Whilst I was at it, I also threw in a ToBABs active pattern to convert an array of ABAs into their corresponding BABs.
The question was slightly ambiguous – I wasn’t sure if all the corresponding BABs need to exist in the hypernet sequences or just one, I went with the later and that got me the right answer so I guess I got lucky there.
- Day 7 challenge description
- Advent of Code 2015
- Solution for Day 6
- All my F# solutions for Advent of Code
- Github repo
Enjoy what you’re reading? Subscribe to my newsletter and get more content on AWS and serverless technologies delivered straight to your inbox.
I’m an AWS Serverless Hero and the author of Production-Ready Serverless. I have run production workload at scale in AWS for nearly 10 years and I have been an architect or principal engineer with a variety of industries ranging from banking, e-commerce, sports streaming to mobile gaming. I currently work as an independent consultant focused on AWS and serverless.
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, 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