The command pattern is one of the most versatile and useful of all the Gang-of-Four design patterns, but surprisingly it’s not used much. Or is it? I think you’ll find you’ve used it more often than you think you have, maybe without even knowing it had a name!
Sometimes called the transaction pattern, it can be applied to a large variety of application domains from UI menu structures, command-line applications, logging systems, and just about any system required a transaction to be stored and executed at a later time. In this talk we’ll take an in-depth look at the pattern, discussing why it’s useful, when you might use it, and how to implement it.
Bio: Ken Baum is a senior consultant for Ingage Partners, a certified B-Corp seeking to use consulting as a force for good. He is a software developer with over 25 years of experience, predominately on the Microsoft stack in C++ and C#. He is currently working as an SDET, mentoring apprentices and writing functional tests for a Vue.js front-end and a Java/AWS back-end. He’s an experienced teacher, presenter and mentor. When he’s not learning new technology or volunteering, he loves reading and watching Netflix shows. He loves The Tick (cartoon and live action), Firesign Theater, all things Monty Python, and Call the Midwife. He considers Fringe the greatest TV show ever, and when he saw Stranger Things, he felt like he was finally home.