automation is a multiplier
Multipliers. They’re ubiquitous – from ratchet wrenches to fertilizer, blocks-and-tackle to calculators, humans rely on multipliers all the time.
Multipliers are amazing things because they allow an individual to “do more with less” – a single person can build a coral castle with nothing more complex than simple machines. Or move 70 people at 70 miles per hour down an interstate merely by flexing his foot and twitching his arm.
Feats and tasks otherwise impossible become possible due to multipliers.
Automation is a multiplier. Some automating is obviously multiplicative – robots on assembly lines allow car manufacturers to output far more vehicles than they could in the pre-robot era. Even the assembly line is an automating force, and multiplier regarding the number of cars that could be produced by a set number of people in a given time period.
In the ever-more-constrained world of IT that I orbit and transit through – with salary budgets cut or frozen, positions not backfilled, and the ever-growing demands of end-users (whether internal or external), technicians, engineers, project managers, and the like are always being expected to do more with the same, or do more with less.
And that is where I, and the toolsets I work with, come into play – in the vital-but-hidden world of automation. Maybe it’s something as mundane as cutting requisition-to-delivery time of a server or service from weeks to hours. Maybe it’s something as hidden as automatically expanding application tiers based on usage demands – and dropping extra capacity when it’s no longer needed (one of main selling points of cloud computing). The ROI of automation is always seen as a multiplier – because the individual actor is now able to Get Things Done™ and at least appear smarter (whether they are actually any smarter or not is a totally different question).
Go forth and multiply, my friends.
