Code, Immutability & the Future of Development

Software development in the 1990s was characterized as a chaotic period with projects often failing or delivering buggy software. The traditional approach involved lengthy requirement gathering, design and coding phases, fraught with issues, such as static requirements that didn't account for evolving business needs and poor assumptions about value and functionality. The rapid evolution of frameworks, tools and techniques in the software industry came as a blessing and fostered innovation. However, it was challenging for developers as they struggled to keep up with the constant changes. In this GOTO Unscripted conversation, Dave Thomas, original signatory and author of The Manifesto for Agile Software Development and co-author of The Pragmatic Programmer, spoke to Hannes Lowette about the future of software development, focusing on the concept of immutability in code and databases. Immutability in code refers to the idea that once code is made shareable, it becomes unchangeable, and it is identified by a unique identifier rather than its name. This approach allows for frequent code changes without breaking interfaces used by others. Regarding databases, Dave highlights the advantages of immutable databases, which, when combined with unique identifiers, make it easier to manage and work with data. Tune in to get insights into the dynamic landscape of software engineering and the need for continuous self-improvement in an era of advanced AI tools.