Remix.run Logo
majormajor 13 hours ago

The set of developers who say "I want to implement this logic as a state machine" is MUCH larger than the set of developers who say "I should make sure I fully understand every possible state and edge case ahead of time before making a state machine!"

freeone3000 2 minutes ago | parent | next [-]

Implement as a state machine? But. Your program exists as a set of transforms upon memory. Your program is a state machine! You just need to define the proper morpisms to map your problem domain to the computer domain.

throwaway2037 12 hours ago | parent | prev | next [-]

Couldn't this be said about any alternative solution? I fail to see how this is specific to state machines.

What do you suggest instead of a state machine?

bvrmn 4 hours ago | parent [-]

Like properly model a domain in domain terms?

nottorp 3 hours ago | parent [-]

And that won't be a state machine with the states having more fancy names?

InDubioProRubio 2 hours ago | parent [-]

It will be, but the idea of having an overview over the states is gone then. There is just modules-> objects with the transitions being method calls. Nobody will have to know all the things about all the state transitions, resulting in another problem (dys)solved by architecture obscurity.

If needs be the state-machine can be reconstructed on a whiteboard by a team of five.

kayo_20211030 34 minutes ago | parent | prev [-]

I have a coding problem.

I'll use a state machine!

Now, I have two problems :-(