Happy new year from Latvia! Coding highlights:

- Built a website for playing Riichi Mahjong https://online-riichi.com

huh?

Ghost of Questionable New Users Present ;)

You never know who's going to drop in and say humbug :\

Merry Christmas to you too.

This looks like the real Mahjong, very well done.

Back in the 1960's I played with old timers on a set that was antique back then, mostly bamboo but a few ivory pieces.

hey! thanks for the comment! thought the post drowned, as it should on Christmas :) where did you come across mahjong players back in 1960? sounds like a good time.

Apparently some of the older ladies who had moved down from New York to South Florida had been playing it socially since World War II.

I got the idea they had been doing it in Europe beforehand, one was a Holocaust survivor.

They loved it when some of us teenagers took an interest and joined in. That was by the 1970's.

What worries me about this is that the benefit of well practiced developers using AI to boost their productivity is there, but what happens to the new developers that piggyback off of LLM tooling too much and end up with worse understanding as a whole?

I think this has always been a problem; eg the students who do all their assignments in groups and coast through with a cursory understanding of their degree. Or those who cheat.

If someone doesn't want to learn, there have always been ways to avoid it. Now it's easier with LLMs, that's true. But for people who do want to learn, I think it's also easier now with LLMs.

I'm not sure where the equilibrium will land, in terms of whether we'll end up with more people with a deep understanding, or more people with a shallow understanding. Or maybe the ratio will end up being the same, but there will just be more people in both groups! Ie the ease of learning will pull some of the previously shallow learners into developing a deep understanding, and the ease of coasting will pull up people who were never into development before into being shallow learners.

It sounds like it might be a good use case for testing documentation - verifying whether what documentation describes is actually in accordance with the code, and then you can act on it. With that in mind, it's also probably pointless to re-run if relevant code or documentation hasn't changed.

Working on a full on Riichi Mahjong web client because I really like the game and want to make a more serious english client without anime.

Did it also to learn rust, which made it easy to convert the engine code into webassembly and create a hand score calculator for the game :)! https://cerpins.com/mahjong-tool

Plans now are to finish the client, then freshen up the calculator with some QOL and visuals, surely a bug fix might be needed here and there as well.