Added wind and solar generators, which respond to wind and sun availability curves. As you edit those curves, the dispatch updates. (Need to work on the color coding to make the correspondences more clear)

Here's a power grid simulator (mostly vibecoded), showing two generators being dispatched to satisfy load changing over time. The cheaper generator (blue region) is dispatched first; the more expensive one (pink region) only when needed.

and of course the classics, 'filter to this value' and 'sort asc/desc'.

I lose my mind when table UIs don't have 'filter to this value' 😂

you can also filter by clicking on the histograms, inspired by Datadog's log search UI

Used Claude Code to vibecode a UI for @duckdb.org in a few days. Here it is navigating foreign keys

whoops, that lock implementation had a bug — forgot to set holder back to null, messing up next acquire. now fixed gist.github.com/vilterp/bf02...

If we make the client grab a lock around reading & writing the new balance, it's impossible to get a double spend:

the first client to acquire the lock wins; the next sees that there's not enough in the account.

Distributed systems should feel like physical puzzles we can manipulate!

As an example, I modeled a bank in my simulator.

Without a lock, there's a race condition: if the two clients' gets and puts of the balance are interleaved, the same money can be withdrawn twice.

It's hard to wrap your head around all the failure modes of a distributed system.

What if you could play with the sequence diagram of a run to see how it responds, and see if you can get it into a failure state?

dist-sys-simulator.netlify.app

Little script to make a flamegraph of a codebase by lines of code github.com/vilterp/cloc...

Am I becoming a fintech person? 😂

Added a simulation of a commodity market to my distributed system simulator.

Clients submit buy and sell orders (blue/right and orange/left, respectively); the server uses DB triggers to execute a trade when there's a match.