OutSystems product leader defines the shape of 'modern' software – IDG Connect

By
IDG Connect |
What type of CTO are you? “As CTO, the most important thing for me is to make sure I’m creating a…
What advice would you give to someone starting their career in IT/tech? “Jump right in, don’t wait…
What advice would you give to aspiring IT leaders? “Technology will continue to evolve at a rapid…
What advice would you give to aspiring security leaders? “Learn as much as you can, get a mentor,…
Software evolves constantly. By its very nature, we can say that the moment any given piece of software hits live production deployment and goes into the hands of users, it starts to be out of date.
This inconvenient truth has (thankfully, due to the birth of cloud computing) been addressed to a degree, through new approaches to Continuous Integration & Continuous Deployment (CI/CD). Today we can use the massively connected nature of the cloud backbone to update, enhance and augment software long after it is first created.
But even with cloud and its compendium of continuous continuity, there is still a huge amount of technology vendor discussion surrounding the idea of so-called ‘modern application development’, whatever the term itself is really supposed to mean.
Is it even fair to talk about modern software? One school of thought argues that we should be a whole lot more courteous and respectful of older software; after all legacy software is only legacy because it still works.
Legacy stalwarts have a valid point, but it’s a point that wears thin. While legacy software is indeed still functional, the lion’s share of it is arguably in place because it is some behemoth chunk of (often public sector) systems code that nobody has figured out how to unravel and modernise as yet.
To continue reading this article register now
Learn More   Existing Users Sign In
Copyright © 2023 IDG Communications, Inc.

source

Leave a Comment