Engineering Culture by InfoQ

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Jason Yip about removing friction in the developer experience and DevOps at Spotify

Why listen to this podcast:

• Friction is the feeling that your environment is fighting you – examples include poorly named variables in code, editors configured incorrectly, access to environments etc

• These things often seem small individually, but together they significantly and slow down development activities

• Cultivate refined annoyance; not tolerating these issues but actively resolving them

• Challenges often come mainly from rapid growth – every design will fail if you just try to scale it larger and larger, you need to redesign for larger contexts, what worked yesterday may not work tomorrow and needs to be adapted

• Be careful not to locally optimize one part of the system at the expense of the overall throughput

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

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

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Josh Evans, former engineering manager at Netflix on how Netflix does DevOps and the freedom and responsibility culture that undermines their way of working.

Why listen to this podcast:

• There are many interpretations of the term DevOps, it is a useful shorthand for a wide variety of technologies and approaches

• “You build it, you run it” is the concrete application of the freedom and responsibility culture

• When building a platform tool make it so easy to use that the product teams are not tempted to try and build something for themselves

• Product teams are free to experiment and learn, which can feel chaotic and is a valuable part of the freedom and responsibility culture

• The value of blameless and safe incident reviews – the goal is to learn and find patterns and use that information to present whole classes of failure from happening in the future

• Don’t view the value stream in a fragmented way – see the whole end to end system with all its interactions and dependencies and optimize the system as a cohesive whole rather than different tools and domains

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

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/2mtCIr1

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Sean Dunn and Chris Edwards about professionalism, licensing and ethics in software engineering

Why listen to this podcast:

• Situations where software development intersects with the public interest are widening and software can impact the health and wellbeing of society

• The distinguishing characteristic of a profession is holding paramount the public interest

• Unlike the failure of a bridge unethical results from software will be less visible and more insidious

• What steps can we take within our organisations to instil a sense of responsibility that is beyond getting the product out the door quickly

• A core tenant of professionalism is we cannot detach our actions from the outcomes – ignorance is not an excuse

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

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/2hheRZO

In this podcast Shane Hastie, Lead Editor for Culture & Methods, talks to Don Denoncourt about remaining an engineer as one ages.

Why listen to this podcast:

• Looking back over history and programming language changes since the early 1980’s

• The importance of lifelong learning and putting your personal time into remaining relevant and up to date with new development platforms

• New graduates get to work on new things because they have just learned about them and they are prepared to take the lower paid roles than “experienced” people

• If ongoing learning is not fun, then maybe you are in the wrong profession

• The unconscious bias against older workers in a few teams and how they miss out on great insights

• Some advice for oldies and youngies working together

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

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/2ltre65

In this podcast Shane Hastie, Lead Editor for Culture & Methods, talks to Andrea Goulet & M. Scott Ford about their journey working together as a married couple and business partners, learning to collaborate and communicate despite having vastly different communication styles and viewpoints.

Why listen to this podcast:

- Effective communication is a competitive advantage

- The system that you produce will only be as good as the communication structure you have in place while you build it

- The importance of learning to speak each other’s language – the terminology of development and business is different and it is necessary to take the time and effort to learn the different language

- The concept of “inception layers” relating to how intensively someone is concentrating on an activity and their level of openness to interruption

- The value of writing a daily journal in a wiki to share what’s been happening and make progress and learning visible

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

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/2zwXlnO

This is the Engineering Culture Podcast, from the people behind InfoQ.com and the QCon conferences.

In this podcast Shane Hastie, Lead Editor for Culture & Methods, Pavneet Saund about his ideas on making empathy a superpower and effective team leadership

Why listen to this podcast:

- Showing and receiving empathy is truly life-changing

- The need to assume good intent when communicating using chat and written words

- Leadership is a different set of skills from technology and these need to be learned

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

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/2ztpigM

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke Lee Cunningham of VersionOne about the results from the State of Agile Survey

Why listen to this podcast:

• Agile is not just something that developers do – it’s an enabler of business outcomes

• The emergence of multi-modal organisations where there are multiple different approaches being used simultaneously which holds them back from progressing effectively

• Some organisations are adopting a Taylorism approach to agile adoption – get experts to tell us what to do and control the teams to abide by those rules

• The emergence of business value as an important measure, over productivity (although productivity is a necessary precondition for business value)

• Buying an expensive tool doesn’t make your agile adoption successful, in the same way that buying an expensive treadmill doesn’t make you fit – both need to be used effectively to deliver any value

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

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/2y6NKnY

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Johanna Rothman and Mike Grifiths about the joint PMI & Agile Alliance initiative to produce the Agile Practice Guide.

Why listen to this podcast:

- There is nothing in the PMBOK that says you have to use a waterfall project delivery model

- If we want to influence the people who hold the hearts and minds of senior management, there is no better way than to collaborate with them

- The guide reflects the State of the Practice when it was written

- The prevalence of agile terms in projects, without actually using agile approaches – the veneer of agile without the substance

- Defining agile as a mindset based on values and principles rather than any set of practices

- There are many options for undertaking work; the key is to have an agile mindset about which practices are most appropriate in a particular context and be prepared to change if the chosen practices are not helpful

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

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/2xXIMeU

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Rebecca Parsons, CTO of ThoughtWorks, about their recent report on the need for Courageous Leadership and her forthcoming book on Evolutionary Architecture.

Why listen to this podcast:

- Courageous leadership enables organisations to solve enterprise-scale problems while still allowing empowered development teams to produce software in an agile fashion

- The importance of making the link between technology advances and what they could mean for a business organisation, rather than seeing them in isolation

- If your metric is how many experiments succeed then you will not take enough risks – turn this around and celebrate the learning from failed experiments

- The need to truly put the customer at the centre our focus, understand the kind of relationship we want with customers and how we want to interact with them

- Create an environment where people are recognised and valued for their varied perspectives and recognise that good ideas can come from many different places

- Evolutionary architecture is based on the idea that things are changing so rapidly now that you can’t predict what changes will be needed in the future

- Innovations around databases, architecture and continuous delivery enable evolutionary architecture to be a real thing today

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Joshua Kerievsky CEO of Industrial Logic and Heidi Helfand Director of Engineering Excellence at Procore Technologies and author of the book Dynamic Reteaming about their talk High Performance via Psychological Safety

Why listen to this podcast:

• You cannot have a high performing team unless you have psychological safety

• Creating a safe environment is hard, and it must go beyond just lip service

• Take the time to have crucial conversations early rather than later

• The quality of the products we produce is a direct reflection of the quality of the conversations we have in our teams