owi @owi@mastodon.social

#introduction time! I'm Oskar, and I spend most of my time online talking and writing about #programming, including but not limited to #Haskell and #FP, #testing, #architecture, #FOSS, #Linux, and #web. I have a blog at https://wickstrom.tech and I produce screencasts at https://haskell-at-work.com when there's time.

I also do #music, mostly acoustic #guitar nowadays, and only spare time.

See you around!

I'm also getting to confront my highly irrational fear of snakes (I dug up a harmless baby snake.) Guessing that they have hatched in this ridge soil. Not sure how to reconcile that with progress bars, though.

The neat thing about my current digging project (removing an artificial ridge by hand 😓) is that it implements its own progress bar.

Either I'm writing boring enough titles, or boring enough content, to stay off the orange front page. Which ever it is, I'm happy.

New blog post:

Specifying State Machines with Temporal Logic

https://wickstrom.tech/programming/2021/05/03/specifying-state-machines-with-temporal-logic.html

Writing about LTL is scary. It's been around since 1977 and a lot of people know it way better than I do. On the other hand, the @quickstrom_io@twitter.com use case hopefully makes it relevant to a new group of users, and that warrants more writing. I'm excited to see where this goes!

First blog post draft on writing state machine specs with LTL is done. Anyone that's good with LTL and formal methods that would like to review?

I'm writing an intro to specifying stateful systems using LTL, in a way that's useful for Quickstrom specs. Anything specific you wish that I cover? Hard concepts to grasp, pain points, etc.

Good riddance.

Beech, finally!

Feels a bit lite archeology at this point, given the project seems close to abandoned. Is https://github.com/gothinkster/realworld the new hot thing? Or something else?

Wohooo, finding bugs in TodoMVC editing mode impls with the new spec. Editing mode is pretty well-defined in the Application Specification, so I can actually call them bugs, I guess.

https://github.com/tastejs/todomvc/blob/master/app-spec.md

TodoMVC has been an extremely interesting case study with all these minor differences in how the frameworks do things, and how they encourage implementations to do things in certain ways. It's really hard to write a single spec that works reasonably for all of them.

This mostly makes writing the Quickstrom spec harder (only having access to the DOM), but it also seems quite weird from a state change perspective, even if the user cannot visibly tell the difference.

So there's probably some JS state what the item used to be before starting the edit. And when you press Escape, that's used to restore the item.

Hmm, quite a few TodoMVC implementations share the backing model for existing items and the editing mode. So when you start typing in the edit input, the existing item's DOM element in the list also changes, i.e. before the edit is committed.

Finally I'm getting to adding the last piece of the TodoMVC spec: editing mode. I have a hunch that it might uncover some interesting things.

Cleaning done. Next step is wood oil. 👍

I'm overwhelmed with gratitude at this point.

6% towards the goal already! 👌

Maybe it's time to make short and snappy screencast on Quickstrom. I'll have to dust off the old Haskell at Work chops.