I'm not the most active user here, but thought I'd end it all by directing you to a better place. What better way than with a #http redirect for a state transition (HA! #rest#statecharts) for your browser:
301 PERMANENT REDIRECT
Location: https://t.co/b3tEbqefFQ
i love blooper reels.
they offer a peek behind the scenes. a view of the televion and movie development process that we rarely get to see. and they're fun.
so, what's the equivalent of "blooper reels" for software development projects?
a thread... 🧵
1/12
@fraser_drops @chrisshank23 @AndaristRake@DavidKPiano My belief is that the coupling of ui and statechart structures, hinders exploring different ways of modeling behaviour: introducing a parallel state, refining a state, etc. It introduces friction.
@DavidKPiano@fraser_drops For sure there could be overlap (a component's behaviour will often vary as its UI changes), but not always. When you consider micro interactions, you might find the overlap is even less pronounced.
@DavidKPiano@fraser_drops You make it sound as if I'm the only one that advocates for this position. 😇
But indeed, the coupling of state structure and UI is not a good thing, for this and other reasons.
@OliverJAsh Yesterday a form at an *airline carrier* didn't let me pay for my trip because I had clicked on a couple of radio buttons after the page had loaded, but before (apparently) some JavaScript thing happened. I had to rejiggle them to clear up the internal state of the page.