Been working on some complex UI for a bit. Defined my no-invalid-states type early on, and it's been relentlessly keeping me honest since.
Conversation
Replying to
It's a type that needs a few things present to be valid; I've a few times gone to create it and realised I'd only worked out half the story.
1
1
Replying to
It's like what alluded to (twitter.com/mxavier/status): it's not punishment; I set myself some rules, & it tells me when I break them.
This Tweet is unavailable.
1
1
5
Replying to
And also like twitter.com/mxavier/status, when I wanted to stop and take stock, I put in some TODO reminders (error) & it compiled what I had.
This Tweet is unavailable.
2
1
Replying to
Follow-up: the type from the first post is still (rightly) kicking my arse. Hot damn.
1
Replying to
(A very belated shout-out to Yaron Minsky's 2009 "Effective OCaml" lecture for the no-invalid-states reference in said post.)
1
2
