Chris (@crimondi) and John (@jbecker42) talk about the important of thinking in systems. If you aren't familiar with system thinking this covers some of the basics and applies it to software. 

We began the episode reviewing the State of DevOps report for 2019. Somehow we ended up discussing why your organizations KPI's should include memes. 

Reference:

• https://cloud.google.com/blog/products/devops-sre/the-2019-accelerate-state-of-devops-elite-performance-productivity-and-scaling
• https://www.nytimes.com/2016/02/28/magazine/what-google-learned-from-its-quest-to-build-the-perfect-team.html
• https://www.inc.com/michael-schneider/google-thought-they-knew-how-to-create-the-perfect.html
• https://rework.withgoogle.com/blog/five-keys-to-a-successful-google-team/

Longtime Ruby developer and community figure, Marty Haught (@mghaught) joins the show to talk the state of Ruby in 2019. Marty shares his history in software development, the current state of Ruby, and his thoughts on the future of Rails framework. 

Reference:

• https://www.infoq.com/articles/programming-language-trends-2019/

Are CMDBs still a thing in 2019? How do you keep up with asset inventories when more workloads are becoming ephemeral? Questions lead mostly to more questions but we do are best in thinking through. Plus, @jbecker42 hates on file integrity monitoring.  

References:

• https://aws.amazon.com/answers/account-management/aws-tagging-strategies/

We all appreciated the HBO Miniseries 'Chernobyl'. An episode talking about software engineering lessons learned was inevitable. We bring in Andrei Secea (@asecea) as we explore parallels between his career in software engineering and the highlights of the show.  Great episode talking to someone who was a bit closer to the events than most of us.  

John (@jbecker42) and Chris (crimondi) talk about 'An Elegant Puzzle: Systems of Engineering Management' by Will Larson (@Lethain). This great book made for great conversation!

Fresh off his European vacation, John (@jbecker42) discusses the importance of downtime. Comparisons are made between engineering teams and individuals as organisms; think what is your personal equivalent of paying down tech debt?

What is John's work philosophy? Find out how walking, cubicles, and the Beastie Boys are central to his career. 

Reference:

• Passionate Programmer - https://www.amazon.com/Passionate-Programmer-Remarkable-Development-Pragmatic-ebook/dp/B00AYQNR5U
• The Power Within - https://www.amazon.com/Unleash-Power-Within-Personal-Transform/dp/1442352663
• Thou Shalt Prosper - https://www.amazon.com/Thou-Shall-Prosper-Commandments-Making/dp/0470485884

We visit the mono-repo vs multi-repo debate in this episode. We consider the decision from a security, usability, and of course pragmatic standpoint.

Reference:

1. https://medium.com/@patrickleet/mono-repo-or-multi-repo-why-choose-one-when-you-can-have-both-e9c77bd0c668 
2. https://medium.com/@mattklein123/monorepos-please-dont-e9a279be011b