| floridagram-bot4 | Mehrdadd13711371_bot was added by: lasthuntter | 12:05 |
|---|---|---|
| floridagram-bot4 | MOHAMMADNaseriBot was added by: lasthuntter | 13:57 |
| roaksoax | ss/win 12 | 14:48 |
| floridagram-bot4 | Majid Baseri was removed by: KMyers | 14:59 |
| floridagram-bot4 | MOHAMMADNaseriBot was removed by: KMyers | 14:59 |
| floridagram-bot4 | Mehrdadd13711371_bot was removed by: KMyers | 14:59 |
| floridagram-bot4 | lasthuntter was removed by: KMyers | 14:59 |
| floridagram-bot4 | <Ivoriesablaze> I thought that was a little odd | 15:12 |
| floridagram-bot4 | <KMyers> That person kept adding bots. Most of those accounts were bots that spam Arabic spam | 15:12 |
| floridagram-bot4 | <RazPi> http://gameprogrammingpatterns.com/state.html | 17:32 |
| maxolasersquad | @RazPi: I agree with the author, "they should be more widely known". They are useful in most any application with enough complexity. | 18:29 |
| maxolasersquad | 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 |
| maxolasersquad | Or better, act in an idempotent manner and do nothing. | 18:30 |
| maxolasersquad | Just as one example of how state machines greatly simplify logic and decrease bugs. | 18:31 |
| === meetingology` is now known as meetingology | ||
| floridagram-bot4 | <KMyers> That has @RazPi written all over it | 21:51 |
| floridagram-bot4 | <Ivoriesablaze> i can definitely see that | 21:51 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!