0 Comments

IT professionals know the phrase “future-proofing,” whether from an infrastructure, network, storage, or application development perspective. The idea behind future proofing is that it “is the process of anticipating the future and developing methods of minimizing the effects of shocks and stresses of future events,” as defined by Wikipedia. Yet in this anticipation, technologists tend to create features and redundancy that may never be needed.

The software development life cycle is often referred to as building a house. The reality: It’s more akin to building a beautiful garden in harsh conditions.

The software development life cycle is often referred to as building a house, having a sturdy foundation to build amazing applications: But the reality is that the software development life cycle is more akin to building a beautiful garden in harsh conditions. It is the idea of learning how to navigate landscaping challenges, whether by discovering innovative solutions, employing best practices, or discovering what can thrive in those conditions.

[ How can automation free up more staff time for innovation? Get the free eBook: Managing IT with Automation. ] 

SLDC: Reality vs. myth

If you look at your software like a house, you will assume some pieces of your foundation never change – but working with that assumption is incorrect as we have seen the constant changes and technological improvements within computing over time. If this perspective of the software development process does not change, the fallacy of software foundations rarely changing will continue.This is dangerous because it can lead to excessive
Source…