Awesome! It looks sturdy! On the store version the bed is held in place with velcro, with one side stapled to the wood. This works well to keep the bed in place.

If you do decide to make it yourself, I'm curious to see the result^^

It's not actually DIY, though it could have been. This is the store link with more pictures and specs: https://www.zooplus.nl/shop/katten/krabpaal_krabmeubels/natural_paradise/wandmeubels/537547

Mochi had a lazy Sunday morning~

Relevant xkcd: https://xkcd.com/1473/

He looks dashing!

I use OneCalendar, it works with a lot of email/calendar hosts, looks good, and is very responsive.

Alternatively, Thunderbird has a calendar feature built-in.

(Edit) failed to see which community this was, OneCalendar is sadly not open source.

That sounds awesome, thanks for the suggestion!

Reminds me of this gem: https://lizengland.com/blog/2014/04/the-door-problem/

Such a comfy berry nose!

Had that issue too, search in Start for "Default Apps", then scroll to the bottom and click "Choose default application by file type". Then scroll to .pdf and choose Sumatra. The settings window may crash for some reason, but for me the file association did seem to stick after that.

Heavy stuff first, cold things together, fragile stuff last.

Try Bricklink, I've purchased "old" sets there for a decent price. Be sure to check the seller's rating/reviews

Nim

I optimized Part1 by directly referencing workflows between each rule (instead of doing a table lookup between them), in expectation of part 2 needing increased performance. But that turned out to not be needed 😋

I had to dig through my dusty statistics knowledge for part 2, and decided to try out Mermaid.js to create a little graph of the sample input to help visualize the solution.

After that it was pretty straightforward.

Day 19, part 1+2

Thank you too, I'll pass on your compliments to Mochi 😻

Like this? 🙂

This is your life now

This was actually something I learned for my job, it was nice to be able to apply it here.

I like your commitment to wheel-reinvention, it can be a lot more fun than going for an existing or 'intended' approach.

Good job on persevering with this one. Your approach for part 2 sounds quite viable, it is very similar to the Ear clipping method for triangulating a polygon.

Nim

Decided to go for a polygon approach for part 1 using the Shoelace formula to calculate the area. This meant part 2 only resulted in larger values, no additional computation.

Code runs in <1ms for part 1 and 2 combined

Source