@email@example.com 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 😅
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:
@firstname.lastname@example.org If you can describe the problem, maybe I can help.
@email@example.com 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. 😂
@firstname.lastname@example.org Haha I’m too stupid to work out what that trick is 😆 Or too tied or both 🤣
@email@example.com (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. 😂)
genially… Pourquoi faut-il payer pour avoir le contenu hors ligne. Que c’est nul, c’est autant de ressources qui ne serviront jamais pour l’éducation. Quelqu’un saurait comment exporter un genially. Par exemple celui-ci : https://college.hachette-education.com/ressources/0002017238904/st6_2023_exploration_06/
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 🤣
My solution to the 2nd part is really, really slow 😢 But it works so oh well 🤷♂️
logs/blog: notes on the year’s events; garden/gamedev: chaos awakening synopsis updated
@firstname.lastname@example.org Great now I can start using twtxt and reply.
@email@example.com What are you stuck on? 🤔
@firstname.lastname@example.org Yes it does ! 😁
literally cannot get past day one. what’s the trick?
@email@example.com Does putting the hash in my reply work?
@firstname.lastname@example.org At the very least you can copy/paste the subject and hash in your reply 😆
@email@example.com @firstname.lastname@example.org Don’t think I can reply to the thread in twtwt. Right now Jenny is not working for some reason. I wonder if @email@example.com has any ideas. Anyway I am happy to be back and will see if I can get jenny working. Though my following list is gone now. Plus I can’t see when someone mentions me if I am not follwing them so I should work on that.
@firstname.lastname@example.org Welcome back buddy! 🤗
@email@example.com if you do see this.. Welcome back! 👋🏼
I am back on twtxt for now. I am using twtwt client. Don’t think that it does replies so I should try jenny with mutt again.
This day one advantage of code was pretty neat looking.
Ahh I see how someone did it.
I could have made my search smarter using a prefix search rather than scanning the full buffer for each iteration.
@firstname.lastname@example.org haha! I’m sure they had fun working around stuff like
@email@example.com Dang. Really going overboard with this!
@firstname.lastname@example.org 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.
A little “visualization” / “progress bar” of day 3 part 2:
Running in a DOS box under OS/2 Warp 4, including some of OS/2’s silly sound effects. 🤣
@email@example.com 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 😅
@firstname.lastname@example.org 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. 😅
@email@example.com Hah looks like your logic is quite similar to mine actually and we wrote similar amounts of lines of code 🤔
@firstname.lastname@example.org Nice! 👌 But you still beat me 😆
@email@example.com 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/
Did I write too much code again? 😅
I don’t know. 😅 My solution is rather long as well:
Still happily runs on DOS.
@firstname.lastname@example.org Meanwhile we’re sitting outside in 28C 🥵 ‘Twas a top of 34 😱
@email@example.com I’m pretty sure it’s experience from doing past AoC puzzles 😅
@firstname.lastname@example.org I don’t even think I notice 😅
@email@example.com 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 🤣
@firstname.lastname@example.org Don’t worry, plenty of time to catch up 😅
@email@example.com now i just need to actually start solving the problems lol
@firstname.lastname@example.org 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!
1093404-315fafb8and please use your usual Twtxt feed alias/name 👌
@email@example.com All I can say is: My client didn’t report any errors. :-) (Does that mean anything? 😅)
@firstname.lastname@example.org 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 (
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 …)
@email@example.com 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