kieckerjan

I remember seeing the ZX80 at my parents' friends house and realizing that this was a different kind of beast than the pocket calculator and the electronic dictionary we had at home: you could make this thing do.. well.. anything!

When the ZX81 came out I spent all my pocket money savings on it. First on the thing itself, later I would shell out for its 16K RAM extension.

Restoring software on the ZX81 using cassette tapes was so slow and cumbersome that it was quicker to restore it from my own memory. I had a little scrolling evasion game that I knew by heart, and I would type it in if I felt the need to play. Changing little aspects of that game (first different characters for the obstructions, then game mechanics) was what set me on the path of programming.

My brother somehow salvaged that first ZX81 from our parents' estate and it is now hanging framed on the wall next to me as I type this.

I remember being blown away by this game. It was a taste of 3D on the C64 years before The Eidolon and Rescue on Fractalus...

A simple solution to that is to distribute the chores. For larger parties I always ensure I have help. Many people actually like contributing to a party in non-material ways by doing prep work or some cooking, doing the dishes, selecting the music, etc.

Middle aged European here. I still regularly go to parties (dinner and otherwise) and I notice that there are two kinds of people: people who throw parties, and people who don't. This sounds like a truism, but what I mean is: there are people who regularly throw a party and people who never do it.

I am solidly in the first category. I throw dinner parties, birthday parties, drinking parties, dance parties, midsummer parties, midwinter parties, game parties, etc. Yes, it costs time and money and is a lot of work. But what people (probably the ones that never bother) tend to forget is how unbelievably gratifying it is to get a bunch of people together, to feed them and to make them talk, laugh, dance, etc. Afterwards you are tired but also grateful and socially energized in a way that feels fundamental to my existence.

Another thing that I feel is underappreciated about agentic coding is that you can actually learn from it. I am a programmer with 25+ years of experience and I tend to do a lot of stuff according to fixed patterns/habits. Seeing how my coding agents do stuff helps me break out of these patterns, lets me consider new approaches, helps me pick up idioms and teaches me new hacks and tricks. That is very satisfying in its own right.

Usually when I see a project flaunting its language like this it elicits a sigh. (You probably know what I am talking about.) This is a happy exception since this project actually promotes a deep integration with its language of choice, so the title and name are fully warranted. Kudos for that.

Solve this and you probably have a business. :)

And full of marketing hyperbole. When I have an AI produce a README I always have to ask it to tone it down and keep it factual.

I actually encountered this pretty early in one of these user tuned GPT's in OpenAI's GPT store. It was called Sommelier or something and it was specialized in conversations about wine. It was pretty useful at first, but after a few weeks it started lacing all its replies with tips for wines from the same online store. Needless to say, I dropped it immediately.

Fair enough. But I am talking about 50 years ago or so.

Tangential, but I was once told a story that seems fitting here. It was told to me by a mechanical engineer who was educated at Eindhoven Technical University in the Netherlands.

He claimed that in the early days there was a lecturer or professor there that, at least in Eindhoven, was very important to his field of expertise. If I understood him correctly, this prof's ideas about engineering mechanical systems revolved around restricting the degrees of freedom as much as possible. A three legged table cannot wobble, but a four legged table can and usually does because it is overdetermined. In mechanical systems (for instance sensitive optical mechanics) reducing "wobble" is key. And the best way to reduce wobble is to make sure it cannot occur.

Here it gets interesting. My source claimed that this professor had laid down his ideas in a standard work in Dutch, which was never translated in another language, restricting its influence to Dutch mechanical engineers. He also claimed it is not a coincidence that Philips and later ASML took an early lead in designing optical systems.

Not sure if it is true, but an interesting story nonetheless.

Tangential but interesting tidbit: Botulinum toxin messes with your motor neurons, which is bad news for your heart. For the same reason (but at lower dosage) it eases wrinkles and causes the infamous expressionless Botox look.

Actually Dobelli was the one who got me thinking about this. I tend to agree with him, although eschewing all news is a bit too extreme to my taste. I tried scaling back my intake by switching from a daily paper to a weekly paper, but one has to have tremendous discipline to avoid the news of the day on the internet. Especially if the internet is your job, like it is for me.