Solving #AdventOfCode2022 day 15 in #golang with An Algorithm I Found on the Internet™ runs in 1700ms. Simplified based on the specific case (biggish change) -> 900ms. Split work into goroutines (easy) -> 300ms. Moved array allocation out of loop (easiest) -> 170ms. That'll do!

My solution for day 22... Part 2 in 0,5 sec.

#AdventOfCode2022 #AoC22 #Kotlin

https://github.com/sukes13/adventOfCode2022/blob/master/src/main/kotlin/be/fgov/sfpd/kata/aoc22/day22/MonkeyMap.kt

My To-Do list has grown so much in December, but I haven't actually managed to do anything.

Rough To-Do list for January and February (in no particular order):
1. Spiderfire Rewrite Merge + Lots of Documentation
2. Upgrade to Iced 0.5 for die-yield-calculator
3. Finish Day 21 to 25 of #AdventOfCode2022
4. Try SvelteKit out for https://silicon.redfire.dev/ (Currently using Gatsby)
5. Improve the UI and UX of a (private) GUI software
6. Learn some HDL, either Verilog or (higher-level) Chisel

My solution for day 18...
Solved by refactoring Dijkstra-algorithm from day 12 to count where all empty spots in a path in an enclosing cube, starting outside the droplet, have sides touching the droplet. Part 2 in 1,5 sec. #AdventOfCode2022 #Kotlin

https://github.com/sukes13/adventOfCode2022/blob/master/src/main/kotlin/be/fgov/sfpd/kata/aoc22/day18/BoilingBoulders.kt

My solution for day 17...
Solved by using a tower of lists of booleans. Solved part 2 by looking for a pattern and using that to calculate the total height after 1 trillions rocks. Part 2 in < 100ms
#AdventOfCode2022 #Kotlin

https://github.com/sukes13/adventOfCode2022/blob/master/src/main/kotlin/be/fgov/sfpd/kata/aoc22/day17/PyroclasticFlow.kt

#RakuLang #AdventOfCode2022/19 https://www.reddit.com/r/adventofcode/comments/zpihwi/comment/j1w34dq/ - with a little help from #Perl.

In hindsight, it was not that hard. But... hindsight is 20/20.

An interesting report:
https://blog.sulami.xyz/posts/aoc-in-one-second/
#AdventOfCode #AdventOfCode2022 #RustLang

#AdventOfCode2022 #RakuLang I finally made it to the end... with a little help from #Perl (@Perl), day 19 was very hard and I wanted to address it with something I feel a bit more confident with!

working on the last #adventofcode problem of the year. #adventofcode2022 after having skied all day at #trysil #norway

That's it for Advent of Code gifs from me for this year.
If you want to check them all out, they're all here: https://cohost.org/sol-hsa
#AdventOfCode #AdventOfCode2022 #gif #animation #visualization #motiongraphics #hashtag #wtfbbq

#AdventOfCode2022 meta post-game thoughts:
I’d hoped to solve all the puzzles, but I’m glad they were hard enough to provide a challenge. Proud of myself for giving it a shot every day and not giving up. Apologies for nerd-sniping a couple friends who had other things they needed to be spending time on.

#AdventOfCode2022 coded up the snafu-to-decimal function with no problem. Did the final decimal-to-snafu in my head after struggling to code it for a bit. That gave the correct answer for part 1, leaving me at 40 stars – 9 short of what I need for the part 2 reveal 😩

- day 16: I really struggled with those dual-elephant valves, and finished it multiple days later. I had to rewrite my solution to be much simpler after reading how others did it.
- day 19: again, the part 2 here was quite complex and I would have struggled much longer without a colleague's tip on how to cut branches (which was very obvious in retrospect, but hey, hindsight is 20/20)
- day 22: making and rotating that cube was fun but cumbersome. Lots of inputting with my solution. Wondering if I shouldn't have hard coded the 7 cube edges for speed.
- day 18: I missed the obvious flood fill for part 2, so I iterated over the adjacent cube surfaces and counted those. Oops.
- day 20: that circular list should have been trivial, but I had to rewrite my working part 1 solution because it did not pass a test. But the test did not take the circularity into account, so the code was correct ! So in the end I had two different but correct solutions for something that should have been a relatively simple to solve.

#AdventOfCode2022

Advent of Code the gifs;
https://cohost.org/sol-hsa/post/708228-advent-of-code-2022
#AdventOfCode #AdventOfCode2022

#AdventOfCode2022 I read the puzzle description this morning and closed my laptop. Feel like the correct approach here is to nail puzzle 16, then 19, then 24. I’d gone back to number 16 last night, and found a flaw in my distance function but didn’t manage to fix it.

Advent of Code the gifs;
https://cohost.org/sol-hsa/post/700138-advent-of-code-2022
#AdventOfCode #AdventOfCode2022

#AdventOfCode2022 found a couple run-of-the-mill common “oops” bugs plus one “maybe you should re-read the instructions “bug”. Part 2 way simpler than most days

39/46 stars

#AdventOfCode2022 Another puzzle that *should* be easy but I’ve got a bug somewhere and I’m not getting the expected output past the first iteration. I think I’ll get this one eventually 😅

Heute gibt es Teil 2 vom Advent of Code Spezial Stream. 4 Aufgaben 4 unterschiedliche Programmiersprachen! Sei dabei ->  https://twitch.tv/reinventorofwheel​​​​
#twitch #twitchde #twitchdeutschland #streamer #smallstreamer​ #adventofcode #adventofcode2022

#AdventOfCode2022/23 #RakuLang https://www.reddit.com/r/adventofcode/comments/zt6xz5/comment/j1co1qp/

More relaxing than previous days, I'm really worrying about tomorrow.

And yes, I still have to solve day 19!