I’m using Finnish keyboard layout (same as Swedish basically).

I like how AltGr+7/8/9/0 gives me { [ ] }, it’s a very nice grouping. The key next to Z is < > and you get | with AltGr, which is very handy.

Only thing that’s mildy annoying from programming viewpoint is that for tilde and backtick, the keys do diacritics - you need to press the diacritic key and space. Backtick is especially fun, because it’s shift+acute, space. Meanwhile, the key next to 1 does § ½, which aren’t that handy most of the time. I often just stick backtick on that key if I’m particularly assed to customise keyboard keyouts. Similarly, shift+4 is ¤, which is another not a particularly useful character (but I don’t mind that, because £ $ € all need to be produced with AltGr, which is at least consistent).

Yeah, the thing is, “a monad is a monoid in the category of endofunctors” is kind of a meme among non-Haskell developers. Personally, I think Haskell is a very interesting language. The mathematical jargon, however, is impenetrable, and this particular expression is kind of the poster child. I’mma go look at Erlang if I want my functional language fix without making my head hurt, thank ye very much.

It’s a thing! Sadly it won’t rewrite Haskell codebases for you, though.

I was about to say “this reminds me of the Hot Dog Stand”.

…but someone actually made Hot Dog Stand. Shit.

Look, I’m a Linux nerd, and there are very few things that scare me. Linux Kernel programmers, maybe - you don’t meddle with them unless the hour is truly dire and we form a delegation to seek their aid after a complex debate as the world burns around us and we climb their mountain together. …And the other thing that scares me are some particular brands of Microsoft ultra fans, for thereover lies madness like we have not seen before.

Oh you fancy PC people and your fancy syscall instruction.

I still don’t know why I could remember jsr $ab1e. I didn’t even write that much assembly.

Well, Google Photos shouldn’t be considered a “backup” solution to begin with. Never mind that both Google and Apple scan the content in their respective services, but there’s just no guarantee that they don’t modify the data on cloud. “Oooh guys, we just invented a revolutionary new photo compression algorithm! Also hosting data is kinda expensive! So pay up if you want your originals.” …and there’s occasional reports that these services just straight up corrupted some old files while no one was looking at them. Good going.

I just treat my Android phone like any other camera I own and use. Copy the files from phone to PC and from there to my NAS, and I use ACDSee’s DAM functionality.

In Ruby, the convention is usually that things are duck-typed (the actual types of your inputs don’t matter as long as they implement whatever you’re expecting of them, if not, we throw an exception). Type hinting could be possible, but it basically runs contrary to the idea.

Now, Ruby on Rails developers are expecting some kind of magic conversion happening at the interfaces. For example, ActiveRecord maps the database datatypes to Ruby classes and will perform automated conversions on, say, date/time values. But from the developer perspective it doesn’t generally matter how this conversion actually happens, as long as there’s something between the layers to do the thing.

I have a Zyxel NAS server that just offers a SMB share. I’m just dumping my photos there under YYYY/MM/DD scheme, and converting all of my Nikon NEF files to DNG. (For importing photos to the NAS and generating backups, I have a PowerShell script and a PowerAutomate action. Also mild usage of Dropbox to transfer files from my cellphone.)

For actual management of photos, I use ACDSee Photo Studio Professional, and it just writes all tag information to the files themselves, so I can basically use any other software for photo management. For actual photo editing, I use DXO PhotoLab and Affinity Photo most of the time.