Nice, can't wait to get rid of eslint in even more projects!

The last one was a head scratcher. I was like "nah, he won't use such a weird curve" and then you did 😅

Is this similar to the `"user" | "admin" | (string & {})` to keep autocomplete when also allowing for other string values?

Bertie Botts Bohnen, sollte eigentlich alle Farben abdecken!

good thing I always specify the version in all of my Dockerfiles 👀

yeah, would have been an option, but in our case we just wanted a quick way to check if one element on the first array is part of the second array. not too difficult to write without sets

I love sets, but we had to remove a Set.intersection call as we had a lot of users with old browsers and it broke the website for all of them. It was a sad day.

as a former physician: can confirm

I have written a linked list once for my job. but it's not really a linked list, just a neat way to keep the correct order from the returned data of the database...

thankfully there's some 4/4 hidden in their music somewhere most of the time, so you can at least nod mindlessly 😀

As a full-stack dev who is way more interested in the backend I feel attacked. Also this is 100% accurate.

Switched from Warp to Wezterm this year. Could still squeeze the change to Ghostty in

really like your approach of using a `row, col` set for the antennas! I mostly opt for an array of [row, col] which can be quite annoying to work with... might try your approach in the next 2D-array challenge 🙌