Why Developers Never Use State Machines (2011)
1–10 of 164 posts
Re: Why Developers Never Use State Machines (2011)
#2Can't read the article as site is down but: fear of the unknown, along with some of the unnecessarily complex language around the topic.
I got over both of these and now use state machines in production where they make sense as a model.
Re: Why Developers Never Use State Machines (2011)
#3Developers use state machines a lot more than they would admit to. Often code would be more readable if the state machine was succinctly defined.
Re: Why Developers Never Use State Machines (2011)
#4I don't think I've ever programmed anything more than a hundred lines without a state machine...
Re: Why Developers Never Use State Machines (2011)
#5If you've ever do any game programming you'll be drowning in state machines.
Re: Why Developers Never Use State Machines (2011)
#6Discussed at the time (over 90 comments):
Re: Why Developers Never Use State Machines (2011)
#7> I am the only kind of developer there is and so therefore I will speak with authority as to what all developers do.
I use state machines regularly when producing performance statistics where I need to individually isolate many history dependent outcomes in a large sample space. I tried doing it without them and ended up with unreadable and thus unmaintainable buggy code. Never again.
Re: Why Developers Never Use State Machines (2011)
#8Re: Why Developers Never Use State Machines (2011)
#9If you've ever do any game programming you'll be drowning in state machines.
network protocol as well, hell, any non-toy network application ends up containing a state machine either implicitly or explicitly