Last Updated on 30 September 2025 at 18:09
The 1960s and 1970s were very influential decades in the history of software development, marking the transition from an era of ad-hoc programming to the nascent stages of software engineering as a discipline.
During this period, the primary focus was on achieving functional code, often at the expense of other considerations like maintainability, scalability, and security. This essay delves into the historical, cultural, and technological factors that shaped this focus on functionality and examines some of its long-term implications in DevOps.
The Historical Context: Post-War Technological Optimism
Join Now
The Shift Towards Structured Programming in the late 1970s
Join Now
The Merits of a Functionality-First Approach
Join Now
As we previously saw, the 1960s and 1970s were a period of rapid innovation and experimentation in software development. This era, constrained by technology and lacking formal methodologies, laid both the innovative foundations and the seeds of future challenges in the software engineering field.
The focus on functionality, driven by historical, cultural, and technological factors, enabled groundbreaking achievements but left a legacy of technical debt that the industry grapples with today.
As we move into an era of ever-increasing software complexity, it is important to remember the pioneering spirit of the early days and add the disciplined engineering practices that have evolved since. The history of software development serves as a compelling study of the trade-offs between functionality and sustainability, a debate that continues to shape the field in our contemporary context.
FinTech Wealth Management expert with 30 years of successful track record, from Unicible/BCV to Odyssey and Temenos, plus hundreds of important banks across EMEA, APAC, and NAM.
► Background — from C-language code to C-suite in 30 years
• WealthSuite Triple’A Temenos TAP Plus expert
• crisis & change management
• complex multi-level project – program – portfolio management
• process architecture & governance, process optimization, BPO
• financial services software engineering FS FinTech
Career start as an innovative software engineer in startups ► to strategic advisory & turnaround for Tier1 & Tier2 Banks at senior C-level.
• T-shaped mastery of the latest key technologies, business, and operational practices in retail banking, asset management, core banking, PMS.
• Keen focus on improving productivity, client retention, and revenues through expertise in Program Management, Process Governance, and Optimized Delivery, augmented by know-how in complex issue resolution and value-driven E2E end-to-end implementations.
Temenos Practitioner accredited across WealthSuite and FrontOffice domains (FO, PM, TTI). Certified modules include Scripts & Formats, Implementation Methodology (T3TIM), Channels PM, APA Attribution, Constraint Management, Order Management, Data Security, WealthSuite Portfolio Management, and T24 Triple’A Interface. The Practitioner status anchors Didier’s capacity to operate as a Transformation Director, bridging certified product mastery with execution governance and program recovery.
Disclaimer —
The views and opinions expressed in this publication are those of the author, Didier Debbaut, and do not represent the views, positions, or policies of Temenos AG, its affiliates, clients, or partners. All information is shared in good faith and in the spirit of professional exchange, as part of an open, constructive contribution to the FinTech and WealthTech community.
Any technical references, opinions, or analyses are based solely on publicly available information and the author’s independent field expertise. They are offered for general informational and educational purposes only.
No confidential, proprietary, or non-public information related to Temenos products, clients, or business operations is disclosed or implied.
© Didier Debbaut — All rights reserved.
Learn when to choose High Availability, Fault Tolerance, or Disaster Recovery in Azure. Didier Debbaut maps costs, risks, and execution trade-offs.
Mixing #Agile with #Waterfall ? Think of it as a cake with the chocolatey structure of Waterfall and the creamy flexibility of Agile. The cherry on the cake is the best of both worlds, and this is how you can win at #software #development and #project #management.
The debate between Agile and Waterfall is not a zero-sum game. Each methodology has its merits and drawbacks, and the choice between the two is often dictated by the specific requirements and constraints of a project or program. However, for projects that demand both structure and flexibility, a hybrid approach can offer a balanced solution.
In practice, it is not about choosing between Waterfall and Agile; it’s about knowing when to use each. Structure and flexibility are complementary and not mutually exclusive. So, the next time someone tries to sell you on the “one true methodology”, remember: the most innovative solutions often come from combining the best of multiple worlds. It’s not about only waterfall or agile, but a lot of other methodologies, too.
Our latest publication explore the complex world of FinTech, focusing on the role of DevOps. Written by Didier Debbaut and Elena Debbaut, both experts in Software Wealth Management and Turnaround & Crisis Management, the piece aims to offer a comprehensive and nuanced understanding of DevOps’ strategic imperatives in the FinTech sector.
