Procedures Are Like Following a Recipe
I’m a firm believer that procedures are like recipes—frameworks for repeatable tasks that can be improved and automated. Their frequency determines whether they are “savory” or “sweet” (baking) procedures.
I’m a firm believer that procedures are like recipes—frameworks for repeatable tasks that can be improved and automated. Their frequency determines whether they are “savory” or “sweet” (baking) procedures.
I’m sure you know the mantra “If it isn’t broken, then don’t fix it,” and you might argue that this is sound advice. However, complex software systems break in complex ways, often invisible to the casual observer. Luckily, we’re here to help you bring the complexity back down, to something as simple as a banana….
Why don’t we talk about software lifecycle management regularly? It could be that most IT Operations folks follow the principle of “if it ain’t broke, don’t fix it.” It could also be a lack of knowledge, resources, budget, or anything else.
When I buy new technology, I know it has a limited shelf life—hardware lasts 5-10 years, while software often needs updates every 6-12 months. So why do many companies storing our personal information push their hardware and software to the brink of obsolescence?