History has passed judgement on Pyrrhus of Epirus, cementing his legacy with a term based on his name, the definition of which casts Pyrrhus as irresponsible. With the passage of time and the value of hindsight, we are able to make our own judgements as to whether or not he was responsible. We can make similar judgements on other figures from our history and from our own careers.
Being responsible means exercising good judgement. Despite this, however, we often eschew good judgement and embark on quixotic quests for “complete, end-to-end automation” or “automate at all cost”; these quests distract us from providing value while we build an unsustainable Rube Goldberg machine of automation sadness. These are not responsible approaches. It is incumbent on us to undertake automation initiatives in a responsible, value-based way. This value can take many forms, but in order to capitalize on that value we must be aware of many factors that affect it.
Join us as Paul Grizzaffi explains responsible ways to approach automation, some of the knowledge we’ll need in order to be responsible, and shares insights about automation responsibility from his own career. Let’s allow history to remember our automation initiatives fondly instead of as Pyrrhic forays into irresponsibility.