There are many causes of technical debt - unknown or ill-defined requirements, business pressures to deliver fast, procedural deficiencies during development, and many more. These are often just manifestations of a larger problem - lack of understanding due to limitations of natural language and inability to predict future social and technical developments. Today we talk with Einar W. Høst, a programmer at the NRK, Norwegian public broadcasting company, about these sociolinguistic causes of technical debt. We can't predict the future, but we can adopt strategies to make our code more flexible and resilient. Einar shares with us a few of these strategies. When you finish listening to the episode, connect with Einar on Twitter.
Mentioned in this episode:
Einar on Twitter at https://twitter.com/einarwh?lang=en
Norwegian public broadcasting company NRK at https://www.nrk.no/about/
Ward Cunningham on technical debt metaphor at https://www.youtube.com/watch?v=pqeJFYwnkjE
Ludwig Wittgenstein, Tractus Logico-Philosophicus at https://www.amazon.com/dp/0486404455/ref=cm_sw_r_cp_api_i_bUv-Eb722FCY3
William Kent, Data and Realit: A Timeless Perspective on Perceiving and Managing Information in Our Imprecise World, 3rd Edition at https://www.amazon.com/dp/1935504215/ref=cm_sw_r_cp_api_i_7Uv-EbEH73Z2J
Do you ever feel like we are entering the age of democratization of software development? Do you fear that the platforms enabling novices with little coding experience to develop software applications are commoditizing your service as a developer? Today we talk with James Augeri, a serial entrepreneur, Techstars alumni, U.S. Airforce veteran, and a founder of Jingle, where he is working on making better search experiences. James shares with us his passion for low-code platforms - software applications designed to provide a software development environment through GUI and model-driven logic, instead of hard coding. What are their advantages, and where are their limits? When are they useful, and when do they become a liability? James' answers to these questions will help you navigate this incoming disruption. When you finish listening to the episode, make sure to connect with James on LinkedIn and Twitter.
Mentioned in this episode:
James on LinkedIn at https://www.linkedin.com/in/dotdotjames/
James on Twitter at https://twitter.com/DotDotJames
Jingle at https://heyjingle.com
WordPress at https://wordpress.org
Drupal at https://www.drupal.org
Zapier at https://zapier.com
Workato at https://www.workato.com
Bubble at https://bubble.io/
Knack at https://knack.com/
Duda at https://duda.co/
When dealing with legacy code, it is easy to forget that the pipeline to deploy that code could be just as much "legacy' as the code itself. So how do you puzzle your way through resurrecting the pipeline, and how do you handle a legacy application from a CI/CD pipeline standpoint? Today we talk with Laura Santamaria, a LogDNA's development advocate, and DevOps practitioner. She shares with us the secrets of reconstructing legacy pipelines from the available logs and data, what to do when no data is available, and how to make legacy application's pipeline more usable for the next maintainer down the line. When you finish listening to the episode, connect with Laura on Twitter, and visit her website at https://speaking.nimbinatus.com.
Mentioned in this episode:
Laura on Twitter at https://twitter.com/nimbinatus?lang=en
Laura’s website at https://speaking.nimbinatus.com
LogDNA at https://logdna.com
Rackspace at https://www.rackspace.com