Are you using a particular tool for this?I might have a need for a similar visualization and this looks really clean.
08.03.2026 21:40
👍 0
🔁 0
💬 2
📌 0
Are you using a particular tool for this?I might have a need for a similar visualization and this looks really clean.
Hidden input fields are input too and require the same level of server-side scrutiny ... "hidden" does not mean safe to use as-is.
"Datastar martini" is a missed opportunity.
youtube.com/watch?v=TKf0... ... trying not to think of the morning after just yet :-)
youtube.com/watch?v=4EXo... ... nor is that beer gonna drink itself
youtube.com/watch?v=eCwS... ... and that playlist is not gonna compose itself ;-)
Switched from ASPNET MVC to Razor Pages ... lighter and the code that tends to change together is closer together.
I've been slowly tapping into more and more MCP servers for the front-end work I do. The output is stable by design (the irony) for a lot less tokens.
New post: Event-sourced Claude Code Workflows
This is an experimental / proof-of-concept follow-up to my previous posts about Claude Code workflows.
Blame @yves.reynhout.be
nick-tune.me/blog/2026-03...
Somewhat in the same realm is projecting into blob storage. It can be cheap but you need to know the access pattern.
I’m not trying to heckle you, just wondered what your approach was to locking the seat.
I know, I meant the example 😂
How are you going to ensure you and I do not select the same seat? You need a pessimistic lock or a lock that will get auto released after a period of time. We only compete for seats in the same room for the same exhibition, potentially. That’s the seam.
You’re selling tickets / seats, no?!
Iconify MCP if you are into icons.
The real boundary is a period of time in a physical room. You can't have multiple people in the same room, in the same seat for the same exhibition. I personally think the stream-less vs stream-full is a bunch of BS in this case. They are mechanics by which we try to enforce the same constraints.
Anything else is really awkward in terms of UX. You’re balancing hijacking seats vs comfort of booking.
Well, you need to take a pessimistic lock on the user’s selection - if you don’t the UX is gonna suck by the time we get to actually booking the whole thing. The only race here is booking within the time remaining and/or a limited amount of time extensions.
Are you leasing the seats as part of the session (cfr. time remaining count down)?
Example?
People still use Windows?
The ability to move a computation from the query side to the projection side for charts has been invaluable both in reducing the amount of recompute but oddly also in the amount of storage needed.
Inline chart.js data delivery in ASP.NET MVC is now another trick up my sleeve.
Thumbs Up!
with meaningful states, so sometimes you end up recording a few messages before transitioning to the next state. In a way, you could say that the state transition for those messages is to the same state.
To expand on the folding - you can fold both your workflow's input and its outputs (plural) IF you record BOTH in the workflow session's stream / event log. That way, you don't end up with FORCED messages when the decision is "do nothing, simply remember". State machines are usually only modeled
to the static definition of transitions between states, but more about the runtime conditions that make a transition possible or not. Shielding the agent from the runtime context they would otherwise need to know about may be beneficial.
Another useful trait of "introspectable" state machines is the ability to "query" or "expose" which are the next commands / events / transitions it can handle given the current state. The idea of feeding that proactively to the agent may be useful in having it change its behavior. I'm not alluding
