Listening to Magma today, an old favourite from my late teens and uni days. I still dig it but I can totally see now why it drove my friends crazy 😆
09.03.2026 15:47
👍 0
🔁 0
💬 0
📌 0
Listening to Magma today, an old favourite from my late teens and uni days. I still dig it but I can totally see now why it drove my friends crazy 😆
So now you know, fellow programmers: keep your code simple!
Also come one, this is just cute!
Just pushed improvements to eventlanes.app default layout. Automatic slicing and GWTs aligned with the slices they refer to. Still plenty to improve, but this is so much more useful now
Oh if you meant libraries, it’s SvelteFlow
Now playing with the auto-layout resolving available GWTs (test scenarios) for the relevant slices in the flow, and positioning them right under. Could be overwhelming on large models, so I'll also explore some "progressive disclosure" approaches. Looking tidier now, though!
Something I’m working on for my own use. Still work on progress. Ill send you an invite. It’s eventlanes.app
Have you got your tickets for Haggis Ruby yet? This time round we’ve more than doubled the fun with two full two days of learning and collaboration and an evening event to boot! April 23rd and 24th, this time in fair Glasgow. We’d love to see you. Tickets and lots of lovely details: haggisruby.co.uk
Domain modelling by telling little stories.
The slices can then work as a TODO list for code generation, via API or MCP (or manual updates).
Still working through this, but I'm exploring better auto-layouts that represent both causality and separate "slices" of functionality. Also placing "external nodes" outside of the grid, to visualise third-party dependencies.
Feels like working with Claude six months ago.
Codex, ever the confident bullshitter
As an exercise, I'm committing to fully modelling the flow before touching any code. Also discussing and tweaking the model with both Codex and Claude, to compare.
To this day the best review of that movie. www.youtube.com/watch?v=-x1Y...
That’s exactly why I chose seat reservations for the demo, because it needs per-seat locking. I’m not sure what your point is but if I need your opinion I’ll make sure to ask, thank you!
I’m not selling anything. I’m building a toy/demo app to explore ideas by myself.
I’m not sure I quite get all your points. I guess I’ll have to find out by myself.
I just started and this is just the UI, but yes I think the idea will be to schedule a future command when the booking starts. The command runs X minutes later and cancels the booking if it’s still open
That’s what I’m building! Also this is the hypothesis, not a clam. It won’t know for sure until I play with it.
... Because you can narrow down consistency guards to be per-seat for some commands, while per-booking for others, without extra orchestration. This should also minimise contention on multi-user scenarios (many users booking seats for the same showing)
Started building a seat reservation demo app, that should be a good playground to test stream-less Event Sourcing (ie "Dynamic Consistency Boundaries")
Call me idealistic but I think there should be legal consequences for bombing schools full of little children.
This particular class of "context / memory management" tools I do find sort of fascinating though, regardless of who survives. I too, as a human, want better ways for my brain to understand codebases and decision-making when designing and maintaining software!
yes, same with "agent orchestration". And a lot of this will eventually be captured by the LLM vendors themselves.
I meant "Git history", though "Gut history" sounds like a great tool for gastroenterologists. Line up that VC money.
I'm trying Deciduous. Building "narratives" you can revisit out of Gut history is such a cool idea, whether you feed it to an LLM or my own puny human brain. deciduous.dev
I'll be doing an Event Sourcing workshop at Haggis Ruby in Glasgow, this April haggisruby.co.uk The rest of the lineup is looking amazing. This should be good!
It can also map out test cases, and then interrogate the model to suggest and model missing scenarios
The eventlanes.app MCP works great for making sense of existing codebases. You can ask Claude to use it to model the high-level flow of existing codebases (in any stack and/or paradigm), and it's helpful!
