Programming in English = X Programming in French = Y

You're used to X and now it's Y. So it feels weird. English speakers are used to X and it's X. So it feels normal.

I wish this came out earlier, there are a few insights in there that took me me a while to understand :)

Isn’t the slack data model presented here totally possible with hipchats actual data model?

Building a hobby OS taught me how little is just "software". The CPU sets the rules. Page tables exist because the MMU says so. Syscalls are privilege flips. Task switches are register loads and TLB churn. Drivers are interrupt choreography. The OS to me is just policy wrapped around fixed machinery.

Would love to boot on a physical machine eventually though! If you have suggestions, happy to hear them :)

Trying to see how far inference can go given that queries usually specify this information (ex: where(r => r.author == $SESSION.AUTHOR_ID)).

Local-first web applications with a compiled backend – After eight years working on web platforms, the conventional stack feels bloated. The client already defines what it wants to fetch or insert. Usually through queries. So why not parse those queries and generate the backend automatically (or at least, the parts that can be)?

Triple stores as a core abstraction – I’ve been thinking about using a triple-based model instead of traditional in-memory data structures, especially in local-first apps. Facts could power both state and logic, and make syncing a lot simpler.

Lower-level systems programming – I’ve mostly worked in high-level languages, but lately I’ve been writing C libraries (like hash maps) and built a minimal 32-bit bare-metal RISC-V OS.

It’s all still brewing, but I think these ideas tie together nicely. What if the OS didn’t have a file system and just a fact store? Everything could be queried and updated live, like a Lisp machine but built on facts.

Some other things I’ve been playing with:

A jQuery-like framework and element factory - You can pass signals that automatically updates the DOM.

A Datomic-like database on top of OPFS - where queries become signals that react to new triples as they enter the system. Pairs well with the framework above.

If a project I was working on for multiple years and I believed in was shut down and my manager told me “welcome to earth” and “our lives don’t matter” I would one hundred percent leave.

Yes, the markets are cold and ruthless but it doesn’t mean you have to be.

> About 80% of the candidates go for the naive solution first. It’s easiest and most natural.

The “naive solution” will be easier to understand and maintain. Why make it harder if it doesn’t add value?