4 ms·
This is a great video. Next I’d love to see, “Why online checkout forms are so hard to get right.” Software is hard.
by sparker72678 5y ago
This is a great video.
Next I’d love to see, “Why online checkout forms are so hard to get right.”
Software is hard.
- ehnto 5y agoPart of the reason is that the state can be extremely complex. It looks like some simple forms, but if you were to write out all the state combinations for tax, location, shipping, product combinations, configurations, logged in/out, guest/account, pricing rules, payments, inventory, warehousing, internationalization, so on and so fourth, you get a pretty complex state machine.
- falcor84 5y agoI'm not quite following you there, other than possibly the authentication piece, all of the other variables seem to me to be recalculable from scratch every time - where else would you need state transitions? (i.e. where is there Path Dependency?)
- matsemann 5y agoValidation. A field is incorrect, but only because it hasn't been touched yet so don't show an error. Or it's incorrect because the value isn't allowed based on another change you made in the form.
- ehnto 5y agoI was mostly using a state machine as a way to frame the complexity of the domain, most checkouts don't use state macines but the possible state permutations exist even if only calculated once.
- fsckboy 5y agoyes, the state machine can be complex, but there's no excuse for throwing away the state that represents everything the user has gone to the trouble to enter in, that is not complex and should be preserved.