Advent of code reddit

Something is wrong with global snow production, and you've been selected to take a look.

Advent of Code is an excellent annual collection of programming puzzles. It's quickly become my favorite part of the holiday season as a celebration of programming: carefully crafted puzzles, amazing solutions spanning astonishing technical stacks, beautiful visualizations — with a sense of humor and joy around it all. The reason I recommend AoC strongly is because it's simply so much fun : there's a surreal and light-hearted Santa-themed story wound around each year's story, an amazing — and inspiring — community on Reddit ; and the puzzles are generally aimed towards teaching something new. I'd strongly recommend it even if you don't generally enjoy programming competitions like Code Jam or Hacker Cup. Very briefly: a new puzzle unlocks every night at midnight, Eastern time from 1st to 25th December.

Advent of code reddit

.

This is advent of code reddit valuable when exploring solutions from excellent programmers like Peter Norvig. Organizing my solutions Looking through other people's Rust solutions I've seen several different mechanisms for organizing repos: some people have a Cargo project per day, per part, and some of us including me decided to use Cargo's bin support: Cargo Targets binaries.

.

The wind has changed direction enough to stop sending lava droplets toward you, so you and the elephants exit the cave. As you do, you notice a collection of geodes around the pond. Perhaps you could use the obsidian to create some geode-cracking robots and break them open? To collect the obsidian from the bottom of the pond, you'll need waterproof obsidian-collecting robots. Fortunately, there is an abundant amount of clay nearby that you can use to make them waterproof. In order to harvest the clay, you'll need special-purpose clay-collecting robots. To make any type of robot, you'll need ore , which is also plentiful but in the opposite direction from the clay. Collecting ore requires ore-collecting robots with big drills. Fortunately, you have exactly one ore-collecting robot in your pack that you can use to kickstart the whole operation. Each robot can collect 1 of its resource type per minute.

Advent of code reddit

You feel the ground rumble again as the distress signal leads you to a large network of subterranean tunnels. You don't have time to search them all, but you don't need to: your pack contains a set of deployable sensors that you imagine were originally built to locate lost Elves. The sensors aren't very powerful, but that's okay; your handheld device indicates that you're close enough to the source of the distress signal to use them. You pull the emergency sensor system out of your pack, hit the big button on top, and the sensors zoom off down the tunnels. Once a sensor finds a spot it thinks will give it a good reading, it attaches itself to a hard surface and begins monitoring for the nearest signal source beacon. Sensors and beacons always exist at integer coordinates.

Nassir little stats

This was surprisingly satisfying and still let me get an idea of what I was doing and how long I took to do it. I wrote some code to break the input into tokens manually, and then simply evaluate left to right eagerly for part 1. Collect stars by solving puzzles. Organizing my solutions Looking through other people's Rust solutions I've seen several different mechanisms for organizing repos: some people have a Cargo project per day, per part, and some of us including me decided to use Cargo's bin support: Cargo Targets binaries. Of course, since version 3. The magic of Itertools Itertools almost feels like cheating with all the helpful functions it provides; I imagine I'm back in Python when applying it liberally. And finally I decided to trade off memory for speed and brought it down to 1s by simply using a Vec in the final solution:. Red Blob Games has an excellent article on hexagonal grids that I'd read several years ago, but I must admit I never really internalized it till I worked things out myself this time around. Consequently, the Elves are having trouble reading the values on the document. Building familiarity with the Regex crate BurntSushi's regex crate is fairly famous and really fast: though I must admit to being a little disappointed that a regex implementation doesn't ship in the std library for Rust. Cheap screen recordings My personal laptop is a Macbook Air running Arch Linux, so it's not particularly powerful: running OBS to record my screen at a readable resolution started causing my keystrokes to lag. A refresher in modular arithmetic, Chinese Remainder Theorem, etc. Scores are tracked for people who manage to be the first hundred to submit their solutions; the first explicitly get a rank back on submission. This is generally my favorite part of the contest — I can see how other programmers approach exactly the same problem, and learn from them. Thank you!

You're already almost 1.

I tried to profile my solution to Day I was a little surprised to learn that benchmarks needed nightly support, and ultimately ended up settling on using Inferno to generate Flamegraphs instead. The changes I needed to make included adding debug symbols for releases, [profile. My favorite functions include cartesian product which is very useful for generating all possible neighbors for a given grid point. An exercise in parsing I'd become fairly arrogant with my abilities writing parsers after writing a few trivial procfile and s expression parsers. Axel Lind 's rust solutions: I found these really useful to be able to see significantly more idiomatic Rust than what I'd been writing. This is generally my favorite part of the contest — I can see how other programmers approach exactly the same problem, and learn from them. A little bit of tweaking allowed me to get the same functionality in Emacs with support for everything else I'm already comfortable with thanks to lsp-mode , lsp-rust-analyzer-server-display-inlay-hints and lsp-rust-analyzer-display-parameter-hints : I'll share my Rust based configuration separately. There's a little more detail around what goes into the sausage in this video and the FAQ , and I can't even imagine the amount of work that goes into making good puzzles. Discuss this post on Reddit , message me on Twitter or email. I'd become fairly arrogant with my abilities writing parsers after writing a few trivial procfile and s expression parsers. I do wish there was a way to ask for more compact output. Using AoC as means to polish up my command of Rust seemed like an excellent opportunity.