Looks like our worst fears have been realized: we've got to debug our network traffic.

Day 23 - The Problem

After perfecting our ridiculous shuffling algorithm (but know that every day we're shuffling) we check in with our repair droids. They report that repairs are going well, but the damage is going to require us to diagnose the health of the network traffic.

So, lets boot up 50 of our best IntCode computers and hook them up to our rudimentary network setup and Part 1 has us trying to see who sends anything to network address 255.

Part 2 adds a NAT that checks to see if the network is idle. If the network is idle, then the NAT needs to send the last thing it saw sent to 255 to address 0. Our answer is the first repeated send.

Ongoing Meta

Dev.to List of Leaderboards

• 120635-5c140b9a - provided by Linda Thompson

If you were part of Ryan Palo's leaderboard last year, you're still a member of that!

If you want me to add your leaderboard code to this page, reply to one of these posts and/or send me a DM containing your code and any theming or notes you’d like me to add. (You can find your private leaderboard code on your "Private Leaderboard" page.)

I'll edit in any leaderboards that people want to post, along with any description for the kinds of people you want to have on it. (My leaderboard is being used as my office's leaderboard.) And if I get something wrong, please call me out or message me and I’ll fix it ASAP.

There's no limit to the number of leaderboards you can join, so there's no problem belonging to a "Beginner" and a language specific one if you want.