c# - State machines everywhere? -


after learning state machines, want place in every class of code. that's great pleasure me declaratively (or "fluently") construct machine, handle events , sure logic violation throw exception.

can please critisize me on practice? or, may be, install stateless package habitually each project (like do)?

any examples of state machines overusing?

whilst design-patterns practice, should cutting code solve particular problem potentially use design-pattern solve problem in tried-and-tested manner.

we not write code "let's use design-pattern" perspective because single design-pattern not one-size fits solution!

do not write code around state machine idiom. make many simple tasks over-complicated , difficult maintain.


Comments

Popular posts from this blog

jquery - How can I dynamically add a browser tab? -

node.js - Getting the socket id,user id pair of a logged in user(s) -

keyboard - C++ GetAsyncKeyState alternative -