[12:05] Mehrdadd13711371_bot was added by: lasthuntter [13:57] MOHAMMADNaseriBot was added by: lasthuntter [14:48] ss/win 12 [14:59] Majid Baseri was removed by: KMyers [14:59] MOHAMMADNaseriBot was removed by: KMyers [14:59] Mehrdadd13711371_bot was removed by: KMyers [14:59] lasthuntter was removed by: KMyers [15:12] I thought that was a little odd [15:12] That person kept adding bots. Most of those accounts were bots that spam Arabic spam [17:32] http://gameprogrammingpatterns.com/state.html [18:29] @RazPi: I agree with the author, "they should be more widely known". They are useful in most any application with enough complexity. [18:30] For example, we have Work Orders that are always in one state, and a configuration that defines what state transitions are allowed. So when the `cancel` method is called it just asks the state machine, "can I be cancelled" and then we either cancel the work order or return some sort of error. [18:30] Or better, act in an idempotent manner and do nothing. [18:31] Just as one example of how state machines greatly simplify logic and decrease bugs. === meetingology` is now known as meetingology [21:51] That has @RazPi written all over it [21:51] i can definitely see that