SkunkScore is precisely such a tool. Today we talk with Ernesto Tagwerker, founder of Ombu Labs and fastruby.io—and the developer of the SkunkScore—about software maintenance and how to use SkunkScore to identify the most problematic parts of your code and guide you through your refactoring adventure.  Mentioned in this episode: Ernesto on Twitter at <a href="https://twitter.com/etagwerker">https://twitter.com/etagwerker</a>  Ernesto on GitHub at <a href="https://github.com/etagwerker">https://github.com/etagwerker</a>  Ombu Labs at <a href= "https://www.ombulabs.com/">https://www.ombulabs.com</a>  Fastruby at <a href= "https://www.fastruby.io/">https://www.fastruby.io</a>  Download SkunkScore at <a href="https://github.com/fastruby/skunk">https://github.com/fastruby/skunk</a>

Imagine if there were a tool to help you measure your code’s complexity, coverage, and smells, blend it all together and present you with an average score assessing your technical debt.

77: SkunkScore with Ernesto Tagwerker

However, when writing software we are making decisions based on knowledge, and finding knowledge often takes time. This is where we turn to software documentation, only to find it frustrating, incomplete, obsolete, or misleading. Today we talk with Cyrille Martraire, a software developer, finance business analyst, and the author of the book <a href= "https://www.amazon.com/Living-Documentation-Cyrille-Martraire/dp/0134689321"> Living Documentation: Continuous Knowledge Sharing by Design</a>, about how to make your documentation more comprehensive, useful, and intuitive. When you finish listening to the episode, connect with Cyrille on <a href= "https://twitter.com/cyriux?lang=en">Twitter</a>, check out his <a href= "http://cyrille.martraire.com/">website</a>, and take a look at his new <a href= "https://www.amazon.com/Living-Documentation-Cyrille-Martraire/dp/0134689321"> book</a>! Mentioned in this episode: Cyrille on Twitter: <a href="https://twitter.com/cyriux?lang=en">https://twitter.com/cyriux?lang=en</a> Cyrille’s website: <a href="http://cyrille.martraire.com/">http://cyrille.martraire.com</a> Cyrille Martraire, Living Documentation: Continuous Knowledge Sharing by Design: <a href= "https://www.amazon.com/Living-Documentation-Cyrille-Martraire/dp/0134689321"> https://www.amazon.com/Living-Documentation-Cyrille-Martraire/dp/0134689321</a> More on stigmergy at: <a href="https://en.wikipedia.org/wiki/Stigmergy">https://en.wikipedia.org/wiki/Stigmergy</a> Eric Evans, Domain Driven Design: Tackling Complexity in the Heart of Software: <a href= "https://www.amazon.com/gp/product/B00794TAUG/ref=dbs_a_def_rwt_hsch_vapi_tkin_p1_i0"> https://www.amazon.com/gp/product/B00794TAUG/ref=dbs_a_def_rwt_hsch_vapi_tkin_p1_i0</a> ArchUnit: <a href= "https://www.archunit.org/">https://www.archunit.org</a>

The need for speedy delivery is the reality of contemporary business. The requirements of modern software development are no different.

76: Living Documentation with Cyrille Martraire

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 <a href= "https://twitter.com/einarwh?lang=en">Einar W. Høst</a>, a programmer at the <a href= "https://www.nrk.no/">NRK</a>, 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 <a href= "https://twitter.com/einarwh?lang=en">Twitter</a>.  Mentioned in this episode: Einar on Twitter at <a href="https://twitter.com/einarwh?lang=en">https://twitter.com/einarwh?lang=en</a> Norwegian public broadcasting company NRK at <a href= "https://www.nrk.no/about/">https://www.nrk.no/about/</a> Ward Cunningham on technical debt metaphor at <a href= "https://www.youtube.com/watch?v=pqeJFYwnkjE">https://www.youtube.com/watch?v=pqeJFYwnkjE</a> Ludwig Wittgenstein, Tractus Logico-Philosophicus at <a href= "https://www.amazon.com/dp/0486404455/ref=cm_sw_r_cp_api_i_bUv-Eb722FCY3"> https://www.amazon.com/dp/0486404455/ref=cm_sw_r_cp_api_i_bUv-Eb722FCY3</a> William Kent, Data and Realit: A Timeless Perspective on Perceiving and Managing Information in Our Imprecise World, 3rd Edition at <a href= "https://www.amazon.com/dp/1935504215/ref=cm_sw_r_cp_api_i_7Uv-EbEH73Z2J"> https://www.amazon.com/dp/1935504215/ref=cm_sw_r_cp_api_i_7Uv-EbEH73Z2J</a>

There are many causes of technical debt - unknown or ill-defined requirements, business pressures to deliver fast, procedural deficiencies during development, and many more.

75: Sociolinguistics and Technical Debt with Einar W. Høst

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 <a href= "https://www.linkedin.com/in/dotdotjames/">James Augeri</a>, a serial entrepreneur, <a href= "https://www.techstars.com/">Techstars</a> alumni, U.S. Airforce veteran, and a founder of <a href="https://heyjingle.com/">Jingle</a>, 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 <a href= "https://www.linkedin.com/in/dotdotjames/">LinkedIn</a> and <a href= "https://twitter.com/DotDotJames">Twitter</a>. Mentioned in this episode: James on LinkedIn at <a href= "https://www.linkedin.com/in/dotdotjames/">https://www.linkedin.com/in/dotdotjames/</a> James on Twitter at <a href= "https://twitter.com/DotDotJames">https://twitter.com/DotDotJames</a> Jingle at <a href= "https://heyjingle.com/">https://heyjingle.com</a> WordPress at <a href= "https://wordpress.org/">https://wordpress.org</a>  Drupal at <a href= "https://www.drupal.org/">https://www.drupal.org</a>  Zapier at <a href= "https://zapier.com/">https://zapier.com</a> Workato at <a href= "https://www.workato.com/">https://www.workato.com</a>  Bubble at <a href= "https://bubble.io/">https://bubble.io/</a> Knack at <a href="https://knack.com/">https://knack.com/</a> Duda at <a href="https://duda.co/">https://duda.co/</a>

Do you ever feel like we are entering the age of democratization of software development?

74: Low Code Platforms with James Augeri

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 <a href= "https://twitter.com/nimbinatus?lang=en">Laura Santamaria</a>, a <a href= "http://www.logdna.com/">LogDNA's</a> 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 <a href= "https://twitter.com/nimbinatus?lang=en">Twitter</a>, and visit her website at <a href= "https://speaking.nimbinatus.com/">https://speaking.nimbinatus.com</a>. Mentioned in this episode: Laura on Twitter at <a href="https://twitter.com/nimbinatus?lang=en">https://twitter.com/nimbinatus?lang=en</a> Laura’s website at <a href="https://speaking.nimbinatus.com/">https://speaking.nimbinatus.com</a> LogDNA at <a href= "https://logdna.com/">https://logdna.com</a> Rackspace at <a href= "https://www.rackspace.com/">https://www.rackspace.com</a>

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.

73: Legacy Pipelines with Laura Santamaria

Today we talk with <a href= "https://www.linkedin.com/in/pranaysuresh">Pranay Suresh</a>, a Silicon Valley startup expert, a former software engineer at Tesla, and a mentor and angel investor about code reviews. Pranay gives us a few tips on how to approach code reviews, both from the perspective of a reviewer and of a coder. When you finish listening to the episode, make sure to connect with Pranay on <a href= "https://www.linkedin.com/in/pranaysuresh">LinkedIn</a>, and visit his website at <a href= "https://pranaysuresh.com/">https://pranaysuresh.com</a>.  Mentioned in this episode: Pranay on LinkedIn: <a href="https://www.linkedin.com/in/pranaysuresh/">https://www.linkedin.com/in/pranaysuresh/</a> Pranay’s website: <a href="https://pranaysuresh.com/">https://pranaysuresh.com</a>  Bolt at: <a href= "https://bolt.com/">https://bolt.com/</a> GitHub Pull Approve: <a href= "https://www.pullapprove.com/?gclid=CjwKCAjw5Ij2BRBdEiwA0Frc9aNWlyDBIpQIbPkV0-j31HN5GSiGpkcy54vbIEqa5kY7m5Or8NntPRoCH2wQAvD_BwE"> https://www.pullapprove.com/?gclid=CjwKCAjw5Ij2BRBdEiwA0Frc9aNWlyDBIpQIbPkV0-j31HN5GSiGpkcy54vbIEqa5kY7m5Or8NntPRoCH2wQAvD_BwE</a> GitHub code review: <a href="https://github.com/features/code-review/">https://github.com/features/code-review/</a>

How many pairs of eyes are needed to ensure the quality of a newly written code? When do you send your code to an impartial reviewer? Is a review always necessary?

72: Code Review with Pranay Suresh

Many tech leaders have already successfully transitioned, and many others are planning to follow suit. But is it always wise to abandon the monolith and adopt the services approach? And if the answer is yes, how to make the transition least painful? Today we talk with <a href= "https://twitter.com/z00b?lang=en">Rob Zuber</a>, a veteran of software startups, CTO of <a href="https://circleci.com/">CircleCI</a>, and a scalability expert. Rob tells us how to choose the right architecture for your business, and how to transition from one architecture to the other without abandoning already invested years of work, knowledge, and experience. When you finish listening to the episode, connect with Rob on <a href="https://twitter.com/z00b?lang=en">Twitter</a> and <a href= "https://www.linkedin.com/in/robzuber/">LinkedIn</a>.  Mentioned in this episode: Rob on Twitter: <a href= "https://twitter.com/z00b?lang=en">https://twitter.com/z00b?lang=en</a>  Rob on LinkedIn: <a href= "https://www.linkedin.com/in/robzuber/">https://www.linkedin.com/in/robzuber/</a>  CircleCI: <a href= "https://circleci.com/">https://circleci.com</a>  Sam Newman, Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith at <a href= "https://www.amazon.com/gp/product/1492047848/ref=ox_sc_act_title_1?smid=ATVPDKIKX0DER&psc=1"> https://www.amazon.com/gp/product/1492047848/ref=ox_sc_act_title_1?smid=ATVPDKIKX0DER&psc=1</a>

Switching from a monolithic architecture to microservices has become an accelerating trend these days.

71: From Monolith to Microservices with Rob Zuber

But not since 2016 have we taken a step back and dived deep into the subject of empathy, what it means, and how to practice it. Today we talk with Indi Young, a speaker, writer, and UX researcher dedicated to empowering makers and menders to know their problem space through empathy and deep understanding of people's purposes. Indi is an author of two books - <a href= "https://rosenfeldmedia.com/books/mental-models/">Mental Models</a> and <a href= "https://www.amazon.com/Practical-Empathy-Indi-Young-ebook/dp/B00RY9R8H8/ref=sr_1_1?s=books&ie=UTF8&qid=1485488787&sr=1-1&keywords=practical+empathy&pldnSite=1"> Practical Empathy</a>. She tells us how to bring empathy to the developer's table and understand the user's needs beyond what data reveals. When you finish listening to the episode, make sure to visit Indi's <a href= "https://indiyoung.com/">website</a> and connect with her on <a href= "https://twitter.com/indiyoung?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor"> Twitter</a> and <a href= "https://www.linkedin.com/in/indiyoung/">LinkedIn</a>.  Mentioned in this episode: Indi Young at <a href= "https://indiyoung.com/">https://indiyoung.com</a> Indi on Twitter at <a href= "https://twitter.com/indiyoung?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor"> https://twitter.com/indiyoung?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor</a> Indi on LinkedIn at <a href="https://www.linkedin.com/in/indiyoung/">https://www.linkedin.com/in/indiyoung/</a> Indi Young, Practical Empathy: For Collaboration and Creativity in Your Work  at <a href= "https://www.amazon.com/Practical-Empathy-Indi-Young-ebook/dp/B00RY9R8H8/ref=sr_1_1?s=books&ie=UTF8&qid=1485488787&sr=1-1&keywords=practical+empathy&pldnSite=1"> https://www.amazon.com/Practical-Empathy-Indi-Young-ebook/dp/B00RY9R8H8/ref=sr_1_1?s=books&ie=UTF8&qid=1485488787&sr=1-1&keywords=practical+empathy&pldnSite=1</a>  Indi Young,  Mental Models: Aligning Design Strategy with Human Behavior at <a href= "https://rosenfeldmedia.com/books/mental-models/">https://rosenfeldmedia.com/books/mental-models/</a>  Susan Cain, Quiet: The Power of Introverts at <a href= "https://www.amazon.com/Quiet-Power-Introverts-World-Talking-ebook/dp/B004J4WNL2/ref=tmm_kin_swatch_0?_encoding=UTF8&qid=1587223083&sr=8-2"> https://www.amazon.com/Quiet-Power-Introverts-World-Talking-ebook/dp/B004J4WNL2/ref=tmm_kin_swatch_0?_encoding=UTF8&qid=1587223083&sr=8-2</a>

Coding with empathy is one of the Corgibytes' core principles, underlying everything we talk about on this show.

70: Practical Empathy with Indi Young

Today we talk with <a href= "https://www.linkedin.com/in/dokwufulueze/">Daniel Okwufulueze</a>, a technology leader, programming polyglot, writer, and senior engineer at <a href= "https://www.dunnhumby.com/">dunnhumby</a>. Daniel helps us define technical debt and tells us how to quantify it without falling into usual pitfalls while doing so. When you finish listening to the episode, make sure to connect with Daniel on <a href= "https://www.linkedin.com/in/dokwufulueze/">LinkedIn</a> and check out his writings at <a href= "https://medium.com/@DOkwufulueze">Medium.com</a>. Mentioned in this episode: Daniel on LinkedIn at <a href="https://www.linkedin.com/in/dokwufulueze/">https://www.linkedin.com/in/dokwufulueze/</a> Daniel on media.com at <a href="https://medium.com/@DOkwufulueze">https://medium.com/@DOkwufulueze</a> Dunnhumby at <a href= "https://www.dunnhumby.com/">https://www.dunnhumby.com</a>  M.M. Lehman, L.A. Belady, Program Evolution, Processes of Software Change at <a href= "http://informatique.umons.ac.be/genlog/BeladyLehman1985-ProgramEvolution.pdf"> http://informatique.umons.ac.be/genlog/BeladyLehman1985-ProgramEvolution.pdf</a> Code Climate at <a href= "https://codeclimate.com/">https://codeclimate.com</a>

When repaying debt, it helps to know how big it is. The same holds for technical debt. The problem is: how do you measure it?

69: Reducing Technical Debt with Daniel Okwufulueze

Today we talk with <a href= "https://twitter.com/mbembaships?lang=en">Claudius Mbemba</a>, a tech leader, public speaker, and the CTO of <a href="https://www.neucleans.com/">Neu</a>, about personality tests. How useful they are, which one to choose, is it enough to use only one, and how to use them to increase the productivity and happiness of your team. When you finish listening to the episode, visit <a href= "https://claudiusmbemba.com/">Claudius' blog</a> and make sure to connect with him on <a href="https://twitter.com/mbembaships?lang=en">Twitter</a> or <a href= "https://www.linkedin.com/in/mbembac/">LinkedIn</a>.  Mentioned in this episode: Claudius on Twitter at <a href="https://twitter.com/mbembaships?lang=en">https://twitter.com/mbembaships</a> Claudius on LinkedIn at <a href="https://www.linkedin.com/in/mbembac/">https://www.linkedin.com/in/mbembac/</a> Neu at <a href= "https://www.neucleans.com/">https://www.neucleans.com</a> Claudius’ Blog at  <a href="https://claudiusmbemba.com/">https://claudiusmbemba.com</a> Myers-Briggs personality test at <a href="https://www.myersbriggs.org/">https://www.myersbriggs.org</a> iMap Individual Multi-Construct Assessment Profile at <a href= "https://vnacelle.com/our-services/imap/">https://vnacelle.com/our-services/imap/</a>  The Four Tendencies Quiz from Gretchen Rubin: <a href= "https://quiz.gretchenrubin.com/">https://quiz.gretchenrubin.com/</a>  Disc personality assessment at <a href= "https://www.discprofile.com/what-is-disc/overview/">https://www.discprofile.com/what-is-disc/overview/</a>  Personalysis test at <a href= "https://personalysis.wiredtothrive.com/assessment/">https://personalysis.wiredtothrive.com/assessment/</a>  StrengthsFinder at <a href= "https://www.gallup.com/cliftonstrengths/en/254033/strengthsfinder.aspx"> https://www.gallup.com/cliftonstrengths/en/254033/strengthsfinder.aspx</a>

The code is predictable. Binary. It either works, or it doesn't. Working with people is much messier. Their actions and reactions are not easy to predict. Or are they?

Episodes