HN user

fcatalan

1,494 karma
Posts1
Comments201
View on HN

I spent a few weeks there back in the day. After the ordeal of surviving the spawn I remember it as a haunting and melancholic experience: you kept finding decayed places, huge projects long abandoned, vandalized monuments, vague traces of simpler dwellings, hidden orchards.

I haven't played a lot of Minecraft but I'm glad that most of the little I played was there.

My grandfather was a smith in deep rural Spain. He made and fixed many roman ploughs, well into the 70s. They were called that because they were pretty much the same tool the Romans used.

Exaggerating a bit, I felt like my old self was dead and I just happened to somehow have inherited his memories.

But a more concrete thing: While before I might have been saddened about bad things happening to kids, like any normal person would, after having kids myself I experience an stronger reaction:

I get almost physically ill when I hear about kids getting harmed.

I signed up for one of the first MOOCs ever, about self driving cars by Sebastian Thrun, and of course PID was part of the curriculum.

I think that PID hits a certain sweet spot between cleverness, ease of implementation and practical utility that makes it catnip for the typical programmer's mind.

I liked it so much that when we had to implement it, I downloaded an open source driving simulator to see it work there instead of the simpler python environment we were using.

Thank you for this recommendation. This last week I have read this, and then also Meditations for Mortals, and they felt illuminating and like written specifically for me.

And without really changing anything about what I am actually doing, I now feel much better about it, because these are the right things to be doing now and anguishing about the ones that I can't get to is just sabotaging myself for no gain. It looks so simple now...

I still have a lot to digest, but having read thousands of books in my life, including dozens of self-help and productivity manuals, these have felt instantly life-changing.

Again thank you.

I don't dream or care about things I definitely can't do.

But there are still so many I can actually do that the opportunity cost of choosing any single one of them is infinite, and that leads to paralysis at worst and diluting your self while half-assing dozens of things at best.

Maybe one of them pays the bills, and even a nice house and a decent car. But it's just that, it is not what you really wanted to do, so you keep searching.

The "gift" of being a fast learner becomes a curse. In a few weeks you are an advanced beginner at almost anything. People marvel at how well you are doing, but you know you have just started and can now see how far you are from being any good. But to become good, you'd have to leave behind all the other things, and you can't pick. So you just start a new one for the quick dopamine hits and easy praise...

And then you are 50 and still don't know what you will do when you grow up.

Managers can barely direct me without shitting their pants. What saves them most of the time is my ability to say "No". Until LLMs can do that, which seems quite hard to do so far, good luck replacing me.

I always see these threads and think I'm not working on anything, but I just realised it's a lie, I'm exploring a couple of things right now, both heavily AI supported:

Simracing trainer.

I love simracing, I'm moderately competitive and want to improve, and I like to be efficient with my practice. So having access to and using a lot of telemetry, I noticed that the "turn a few laps, load telemetry, compare against reference lap, try again" is not as efficient as it could be.

Also a lot of my telemetry analysis is very rote and "rules based": Look at the biggest laptime delta jump against reference, try to determine the cause among a few usual suspects".

So I have started experimenting with a system that reads the iRacing telemetry in real time, and compares against the reference telemetry live, finding the biggest delta jumps, and trying to find the root cause of the time loss using an increasingly sophisticated GOFAI rule and pattern matching system. Then this report is fed to a cheap LLM call to be condensed into clear advice, and the result goes to the free Microsoft TTS API. So I get instant feedback of where I'm slow and maybe even why.

So far I fear it's mostly making me faster from all the test laps involved more than the advice itself, but when it clicks it does feel magical and really help.

But sometimes I feel like I'm just speedrunning the collapse of 70s AI, as it feels a bit too brittle and situational.

I also have added additional tools for tracking improvement across sessions, finding statistically problematic corners (where am I plain bad?, where am I inconsistent?) or even training my muscle memory by tracing fast driver brake traces using my pedal.

Yay compiler: The other ongoing thing is a clean room reimplementation of Jon Blow's Jai. I've been curious about the language for years, but it's a closed beta and for some reason I've never felt about asking Jon to get into it. I'm not really a game dev so I wouldn't even know what to put in the request.

So now I have 100k+ lines of Rust that can compile a very significant subset of the publicly available Jai source code. I just used various LLMs to condense the public information about the language and come up with a dev plan and started chipping at it. Once I had something in a kind of working state I started with the Way to Jai big tutorial and make sure every example there compiles and works as intended, fixing errors or missing features one by one.

I mostly use Claude Code or Codex, but sometimes what I do is having them guide me into the new feature and doing the edits myself while they explain, so I get to know how things really work under the hood.

It's a silly pointless project, but for some reason I find very satisfying watching it compile the examples.

For me it has been just saying "yes" when I was offered a job and when that one was getting a bit annoying someone happened to offer me another and I said "yes" too. I have ended up a bit underemployed and underpaid, but life's comfortable and safe and I have ample time to stress over hobbies instead of work.

So comfortable that lately I have declined offers for interesting and much much better paid work, because I can no longer be bothered to take any risks or alter my lifestyle.

But sometimes I wish I could have been the guy managing to get 10k MMR using knowledge I've got in spades.

Making complete coherent products is as hard as ever, or even harder if you intend to trade robustness for max agentic velocity.

What I do very successfully is low stakes stuff for work (easy automations, small QoL improvements for our tooling, a drive-by small Jira plugin)

And then I do a lot of crazy exploring, or hyper-personal just for myself stuff that can only exist because I can now spawn and abandon it in a couple days instead of weeks or months.

Same originating idea: "a language for AI to write in" but then everything else is different.

The features of both are quite orthogonal. Cairn is a general purpose language with features that help in writing probably working code. Mog is more like "let's constraint our features so bad code can't do much but trade that for good agent ergonomy".

Cairn is a crazy sprawling idea, Mog is a little attempt at something limited but practical.

Mog seems like something someone has thought about. No one has thought about Cairn, it's pure LLM hallucination, the fact that it exists and can do a lot of stuff it's just the result of someone (me) not knowing when a joke has gone too far.

A couple weeks ago on a lark I asked Claude/Gemini/Codex to hallucinate a language they would like to program in and they always agreed on strong types, contracts, verification, proving and testing. So they ended up brainstorming a weird Forth-like with all those on top. I then kept prodding for an implementation and burned my weekly token budget until a lot of the language worked. They called it Cairn.

So now I prompted this: "can you generate a fizzbuzz implementation in Cairn that showcases as much as possible the TEST/PROVE/VERIFY characteristics of the language? "

Producing this (working) monstrosity (can't paste here, it's 200+ lines of crazy): https://gist.github.com/cairnlang/a7589de126b14e50a53b9bdc28...

This enables different satisfactions. You can still choose all your options but have a working repl or small compiler where you are trying them within minutes.

Also you decide how much in control you are. Want to provide a hand made grammar? go ahead, want the agent to come up with it just from chatting and pointing it to other languages, ok too. Want to program just the first arithmetic operator yourself and then save the tedium of typing all the others so you can go to the next step? fine...

So you can have a huge toy language in mere days and experiment with stuff you'd have to build for months by hand to be able to play with.

My own 100% hallucinated language experiment is very very weird and still has thousands of lines of generated examples that work fine. When doing complex stuff you could see the agent bounce against the tests here and there, but never produced non-working code in the end. The only examples available were those it had generated itself as it made up the language. It was capable of making things like a JSON parser/encoder, a TODO webapp or a command line kanban tracker for itself in one shot.

I agree, it´s mostly a silly whim taken too far. Too much time in my hands.

In particular the whole stack based thing looks questionable.

In fact the very first answer by Gemini proposed an APL-like encoding of the primitives for token saving, but when I started the implementation Claude Code pushed back on that, saying it would need to keep some sane semantics around the keywords to be able to understand the programs.

The very strict verification story seems more plausible, tracks with the rest of the comments here.

What has surprised me is that the language works at all, adding todo items to a web app written in a week old language felt a bit eery.

There's a lot of language for such a little time, but if you have programmed any Forth it should be easy to pick up, have a look at some of the top level examples.

I have programmed about 3 Forth implementations by hand throughout the years for fun, but I have never been able to really program in it, because the stack wrangling confuses me enormously.

So for me anything vaguely complex is unreadable , but apparently not for the LLMs, which I find surprising. When I have interrogated them they say they like the lack of syntax more than the stack ops hamper them, but it might be just an hallucinated impression.

When they write Cairn I sometimes see stack related error messages scroll by, but they always correct them quickly before they stop.