(#zkjovca) @movq@www.uninformativ.de Ahh I can sort of see the visualization (sort of), but it’ll be faster if you explain wtf the algorithm is in textual form 😅
#swbi3eq
(#zkjovca) @movq@www.uninformativ.de Ahh I can sort of see the visualization (sort of), but it’ll be faster if you explain wtf the algorithm is in textual form 😅
(#s7b6peq) That second photo is from our local pond. See all those tracks in the snow? Those are from the ducks and the other birds that stayed here.
This video is from a couple of days ago – just frozen, no snow yet:
(#ghidsjq) @jason@jasonsanta.xyz If you can describe the problem, maybe I can help.
(#zkjovca) @prologic@twtxt.net I can try to explain, if you want to know. 😅 Or maybe this guy’s visualization will help (if you can see it, not sure): https://old.reddit.com/r/adventofcode/comments/18af47j/2023_day_4_scratchcard_counting/
A couple centimeters of snow today. 😊 And I’ve got a loooooooong vacation coming up. Time to relax. 😃
This is my favorite time of the year – by far. Even if it means the snow will freeze in my beard. 😂
(#zkjovca) @movq@www.uninformativ.de Haha I’m too stupid to work out what that trick is 😆 Or too tied or both 🤣
(#zkjovca) @prologic@twtxt.net (Mild spoilers ahead.)
Today’s puzzle was one of those where I immediately knew that there must be a solution that does not require actually copying anything. AoC often has these kinds of problems that make it look like you have to create lots of duplicates, multiply objects, stuff like that. That’s often a sign that you can solve it by doing something simple. 😅 (If only that was true in real life as well. 😂)
Today’s #AdventofCode #2023 was a bit of a whoozie 🤣 Not only did I have to work today (today being Monday et all), but also had to deal with a minor incident, then have dinner, etc and by the time I got back to my half-finished day 4 puzzle, I got a bit stuck with the 2nd part 🤦♂️ I guess I don’t really like array manipulation, it’s so easy to get lost 🤣
Current #AdventOfCode #2023 Twtxt/Yarn Leaderboard
Day 4, Part 1 and Day 4, Part 2 of #AdventOfCode #2023 done 🥳
My solution to the 2nd part is really, really slow 😢 But it works so oh well 🤷♂️
(#u3exsfa) @shreyan@twtxt.net What are you stuck on? 🤔
(#ghidsjq) @jason@jasonsanta.xyz Yes it does ! 😁
(#ghidsjq) @jason@jasonsanta.xyz At the very least you can copy/paste the subject and hash in your reply 😆
(#sphxweq) @jason@jasonsanta.xyz Welcome back buddy! 🤗
(#sphxweq) @jason@jasonsanta.xyz if you do see this.. Welcome back! 👋🏼
This day one advantage of code was pretty neat looking.
https://twitter.com/gereleth/status/1730495736070938786?s=09
Code here: https://github.com/gereleth/aoc_python/blob/main/src/year2023/day01vis.py
(#msw64qq) Ahh I see how someone did it.
https://github.com/immannino/advent-of-go/blob/master/cmd/2023.go#L30-L40
(#6oq4ywq) I could have made my search smarter using a prefix search rather than scanning the full buffer for each iteration.
(#msw64qq) @movq@www.uninformativ.de haha! I’m sure they had fun working around stuff like nineight
(#qwm7hha) @movq@www.uninformativ.de Dang. Really going overboard with this!
@prologic@twtxt.net I didn’t have to do much backtracking. I parsed into an AST-ish table and then just needed some lookups.
The part 2 was pretty easy to work into the AST after.
https://git.sour.is/xuu/advent-of-code-2023/commit/c894853cbd08d5e5733dfa14f22b249d0fb7b06c
(#qwm7hha) A little “visualization” / “progress bar” of day 3 part 2:
https://movq.de/v/6fc13f8ce1/MVI_6766.MOV.mp4
Running in a DOS box under OS/2 Warp 4, including some of OS/2’s silly sound effects. 🤣
(#apnoyca) @movq@www.uninformativ.de Hah 😅 Hmm 🤔 Yeah all I had to do in the 2nd part was store the YX coordinate of the Symbol for the part, then transpose all the parts into a map of SymbolYX -> Part(s)
Note that I call it YX
and not XY
because the usual way of dealing with this in code, is rows first, then columns, ro Y then X 😅
(#apnoyca) @prologic@twtxt.net Yours is more clever and cleaner, I think. 🤔 You were able to reuse more code for the second part. I, instead, wrote a different search logic for part 2. 😅
(#apnoyca) @movq@www.uninformativ.de Hah looks like your logic is quite similar to mine actually and we wrote similar amounts of lines of code 🤔
(#apnoyca) @movq@www.uninformativ.de Nice! 👌 But you still beat me 😆
(#ebrldga) @prologic@twtxt.net Oh boy, that’s too hot, I’m not gonna trade you. :-D
I messed up on the date. That’s the corrected link: https://lyse.isobeef.org/morgensonne-2023-12-03/
(#apnoyca) @prologic@twtxt.net
Did I write too much code again? 😅
I don’t know. 😅 My solution is rather long as well:
https://www.uninformativ.de/git/advent-of-code/file/2023/day03/s.c.html
Still happily runs on DOS.
(#vdtfw2a) @movq@www.uninformativ.de @prologic@twtxt.net At least my recent messages seem to still work then. :-) Thanks to both of you.
(#ebrldga) @lyse@lyse.isobeef.org Meanwhile we’re sitting outside in 28C 🥵 ‘Twas a top of 34 😱
Current #AdventOfCode #2023 Twtxt/Yarn Leaderboard
(#6oq4ywq) @movq@www.uninformativ.de I’m pretty sure it’s experience from doing past AoC puzzles 😅
(#vdtfw2a) @movq@www.uninformativ.de I don’t even think I notice 😅
(#qwm7hha) @movq@www.uninformativ.de Yeah! Tell me about it. Grid searching, looking around, backtracking uggh I hate this stuff, this is why I’m not really a true Software Engineer, because in reality you almost never write this stuff yourself from scratch 🤣
(#7whe4xa) @shreyan@twtxt.net Don’t worry, plenty of time to catch up 😅
(#apnoyca) @movq@www.uninformativ.de @taigrr@ndl.taigrr.com again, I dunno how you both beat me 🤣 But well done! 👏 Did I write too much code again? 😅
Day 3, Part 1 and Day 3, Part 2 of #AdventOfCode #2023 done 🥳 – My solution isn’t very efficient though 🤦♂️ But it’ll do 🤣
(#qwm7hha) @prologic@twtxt.net Oof, it’s already getting a bit tricky. 😬
Day 3 of #AdventOfCode puzzle 😅
Let’s go! 🤣
Come join us! 🤗
👋 Hey you Twtxters/Yarners 👋 Let’s get a Advent of Code leaderboard going!
Join with
1093404-315fafb8
and please use your usual Twtxt feed alias/name 👌
(#vdtfw2a) @lyse@lyse.isobeef.org All I can say is: My client didn’t report any errors. :-) (Does that mean anything? 😅)
(#6oq4ywq) @xuu@txt.sour.is Ah, you went with the “scanning” approach as well. I did that, too.
It’s quite surprising to see (imho) how many people on reddit started substituting strings (one
becomes 1
etc.). That makes the puzzle much harder by introducing nasty corner cases.
(Maybe I was just lucky this time to pick the correct approach right from the start. 🤣 Or maybe it’s a bit of experience from doing past AoC events …)
(#6oq4ywq) @xuu@txt.sour.is Interesting 🤔 I mean I only wrote ~3x more code, not too bad considering:
$ wc -l day2*.go
270 day2.go
69 day2_test.go
339 total
(#6oq4ywq) My code is here. https://git.sour.is/xuu/advent-of-code-2023
(#wg7xx5q) @xuu@txt.sour.is Yeah or in my case a lot of strings.TrimSpace()
and strings.Split()
because I hand-built a custom parser 🤣
(#wg7xx5q) Day 2 used lots of Cut and Split.
(#mldneoa) Oof. Its quite everywhere here in my area. Hope its not too bad there.
(#mldneoa) @lyse@lyse.isobeef.org Actually my wife and I are fine so far 🤞 Maybe we’ll get lucky and not catch the nasty shit™ ?! 🤣
(#7whe4xa) @shreyan@twtxt.net Nice! 👌 Welcome! 🤗
I rotated June to September into their own archive feeds. I hope I didn’t mess up. There’s still one or the other manual step involved. I should write a few tests and automate it fully. It might also be a good idea to write a validator program which can check all the feeds for consistency.
(#mldneoa) @prologic@twtxt.net Oh crap, hope you get well soon!