Benki → Bookmarks

next page ⇢

A subset of BEAM for small devices. Enables you to program microcontrollers with Erlang, Elixir, or Gleam.

Compares occupational pension (bAV), the upcoming Altersvorsorgedepot, and a private ETF depending on your situation.

Made with Claude. Available in German, English, Latin, and Japanese among others.

It isn’t legal or financial advice, I haven’t verified its accuracy meticulously, and it probably doesn’t catch all cases and possible inputs. But it’s very likely better than I could do by hand.

Keep in mind, too, that there are many additional factors other than the pure numbers game that you have to take into consideration and that ultimately you can only evaluate yourself, such as:

  • liquidity / flexibility
  • availability of funds for early retirement
  • psychology / savings discipline
  • trust in the financial system / insurance companies / the government

Advanced general-purpose physics simulation library with both C and C++ APIs. Also has official Python bindings.

“Breakthrough Method for Agile AI-Driven Development.” I have no idea what it is, but it sounds cool.

In AI, whatever scales with compute wins. Human preconceptions are one example of what always loses out in the long run.

This is because our human way of thinking rests on simplifications and abstractions, both of which progressively lose value the more compute you have.

The Bitter Lesson: In AI, whatever scales with compute wins. Human preconceptions are one example of what does not scale well.

Many AI agent harnesses get this wrong and encode their human creators’ ideas about workflows too strongly.

A Gerbil Scheme REPL MCP server for coding agents.

REPL-driven workflows have been agent-unfriendly so far, so I welcome this. Personally I would have implemented a Claude Code skill instead of an MCP server, but as long as it works…

A sandboxing tool for macOS (sandbox_exec) and GNU/Linux (Bubblewrap).

Restricts:

  • Filesystem. The heart of every sandboxing solution.
  • Network. Forces outbound connections through a SOCKS or HTTP proxy, which enables fine-grained control.
  • Commands. Not sure how this works; regardless, I am skeptical of this one. After all, what does it help to catch a shell command when the sandboxed application can just implement the same behavior directly?

I like the network part. In fact I explored the possibility of this kind of sandboxing combined with HTTP proxying just a week ago; Claude also suggested using Bubblewrap, which matches. I did not think of SOCKS proxying for non-HTTP connections, so I’m glad I found this.

That said, I think the HTTP proxying part here falls a bit short of my ideal solution, which would try harder to prevent data extrusion.

next page ⇢