Agile

This episode is a panel discussion from the microservices track QCon Plus, held in May 2021. Track host Nicki Watt asks "What have we learned over the last decade of microservices." The panelists included Chris Richardson, James Lewis, and Katie Gamanji. The discussion started with looking at how the meaning of "microservices architecture" has evolved over the past ten years. There were some great insights about how successfully developing, deploying, and maintaining software depends as much or more on cultural and environmental factors, than simply adopting microservices and all the tools and technology that now exist.

Read a transcript of this interview: https://bit.ly/3rOTrD7

Subscribe to our newsletters:
- The InfoQ weekly newsletter: bit.ly/24x3IVq
- The Software Architects’ Newsletter [monthly]: https://www.infoq.com/software-architects-newsletter/

Upcoming Virtual Events - https://events.infoq.com/

InfoQ Live:
https://live.infoq.com/
- August 17, 2021
- September 21, 2021
- October 19, 2021

QCon Plus online conference:
https://plus.qconferences.com/
- November 1-12, 2021

Follow InfoQ:
- Twitter: https://twitter.com/infoq
- LinkedIn: https://www.linkedin.com/company/infoq/
- Facebook: https://www.facebook.com/InfoQdotcom/
- Instagram: @infoqdotcom
- Youtube: https://www.youtube.com/infoq

InfoQ Podcast

Transcript

What Have We Learned Over the Last Decade of Microservices?

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Alex Qin following on from her QCon London talk “Shaving My Head Made Me A Better Programmer”.

Why listen to this podcast:

- Casual discrimination and unconscious bias is rife in society, and very prevalent in tech
 - The need to have many more people in the field who don’t fit the preconceived mould of a programmer
 - The complexity of the overall system means we need to tackle discrimination at many levels in many different aspects
 - One person can make a difference
 - Call things out when you see things that are wrong – speak up, show up and shield those who can’t shield themselves

More on this: Quick scan our curated show notes on InfoQ http://bit.ly/2ugjaZY

You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

Subscribe: www.youtube.com/infoq
Like InfoQ on Facebook: bit.ly/2jmlyG8
Follow on Twitter: twitter.com/InfoQ
Follow on LinkedIn: www.linkedin.com/company/infoq
Want to see extented shownotes? Check the landing page on InfoQ: http://bit.ly/2ugjaZY

Show Notes

Alex Qin on Leveraging Technology to Create Positive Social Change

Tips for those who are getting ready for a TAC panel.

Tips For TAC Panel - Rev 2 Audio

Gene Kim and John Willis present this nine-part series that includes an oral history of the DevOps movement, as well as discussion around pivotal figures and philosophies that DevOps draws upon, from Goldratt to Deming; from Lean to Safety Culture to Learning Organizations.The audiobook is a great way for listeners to take an even deeper dive into topics relevant to DevOps and leading technology organizations.

The series will launch on February 27 on Audible, Amazon and iTunes.

Beyond The Phoenix Project

Beyond The Phoenix Project Excerpt: Module 1 - The Phoenix Project

Beyond The Phoenix Project Excerpt: Module 2 - Goldratt

Beyond The Phoenix Project Excerpt: Module 3 - Deming

This is the Engineering Culture Podcast, from the people behind InfoQ.com and the QCon conferences.
In this podcast recorded at Agile 2019, Shane Hastie, Lead Editor for Culture & Methods, spoke to Bas Vodde, one of the formulators of Large Scale Scrum (LeSS) about how LeSS is designed to descale an organisation rather than scaling up to cope with complexity 

Why listen to this podcast:

•	LeSS is based on the idea of de-scaling and reducing complexity rather than scaling to cope with complexity
•	A characteristic of LeSS adoptions is that the concepts of projects and programs tend to completely disappear in favour of product-based working
•	With LeSS, you have always one Product Owner for the entire product.  Product owners per team are considered to be an exceptionally bad idea from a LeSS perspective
•	LeSS is based on having largely stable, cross-functional teams working on customer centric functionality
•	 LeSS is based on a set of ten principles which guide the approach, and then imperical feedback based on experiments and constant learning


More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2WcEiwy
You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

Subscribe: www.youtube.com/infoq
Like InfoQ on Facebook: bit.ly/2jmlyG8
Follow on Twitter: twitter.com/InfoQ
Follow on LinkedIn: www.linkedin.com/company/infoq
Check the landing page on InfoQ: https://bit.ly/2WcEiwy

Bas Vodde on LeSS, LeSS Huge and Descaling for Agility

In my 21 years as an entrepreneur, I would come up for air once a month to religiously read the Harvard Business Review. It was not only my secret weapon in thinking about new startup strategies, it also gave me a view of the management issues my customers were dealing with...

When Hell Froze Over – in the Harvard Business Review

Software engineers, architects and team leads have found inspiration to build better, high performing teams by listening to the weekly InfoQ Podcast. We have achieved that by interviewing some of the top CTOs, engineers and technology directors from companies like Uber, Netflix and more. Over 500,000 downloads in the last 3 years.

Bas Vodde on LeSS, LeSS Huge and Descaling for Agility

Engineering Culture by InfoQ

Recent comments

carl jb

Related tracks