Any change can break us, but we can’t treat every change the same
Here are some excerpts from an incident story told by John Allspaw about his time at Etsy (circa 2012), titled Learning Effectively From Incidents: The Messy Details. In this story, the site goes d…
Error 402: Information Sorta Wants To Be Expensive; Information Almost Wants To Be Free
We took a few weeks off in our Error 402 series on the history of web monetization, but we’re back. If you’re just catching up, we’ve talked about the earliest monetary transactions online, the ris…
Whether or not you’re a fan of math, we’ve always had a need to count things. Maybe it’s to figure out the maximum weight an airplane can safely hold, or the appropriate amount to tip after a meal, or the exact number of minutes in a year so you can accurately write the soundtrack to
Code, Immutability & the Future of Development • Pragmatic Dave Thomas & Hannes Lowette
Listen to this episode from GOTO - Today, Tomorrow and the Future on Spotify. This interview was recorded at GOTO Amsterdam for GOTO Unscripted.gotopia.techRead the full transcription of this interview hereDave Thomas - Author of The Pragmatic ProgrammerHannes Lowette - Head of Learning & Development at Axxes, Monolith Advocate, Speaker & Whiskey LoverRESOURCESyoutu.be/Adu75GJ0w1oyoutu.be/gy44CTCce0ounison-lang.orgDave@pragdavpragdave.megithub.com/pragdavelinkedin.com/in/dave-thomas-53aa1057Hannes@hannes_lowettegithub.com/Belenarlinkedin.com/in/hanneslowetteDESCRIPTIONSoftware 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.RECOMMENDED BOOKSDave Thomas & Andy Hunt • The Pragmatic ProgrammerDave Thomas • Programming ElixirTwitterInstagramLinkedInFacebookLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted almost daily