S1E4 - From Connected Vehicles to Connected Software and People (James Simon)

S1E4 - From Connected Vehicles to Connected Software and People (James Simon)

Summary The conversation explores the experiences of working in the EV connected vehicle space and the challenges and differences in software development in the automotive industry. It discusses the shift towards software-defined vehicles and the ability to make changes in the cloud. The importance of developer experience and the ability to deliver work quickly is emphasized. The conversation also touches on the challenges of autonomy in larger organizations and the need for executable governance and domain-driven design. The resistance to adopting new disciplines in software development is also discussed. The conversation covers various topics related to industrial development, domain design, working directly with the business, and the challenges of implementing change in different organizations. They discuss the importance of taking time for domain design and the need for continuous improvement. They also touch on the concept of tech debt and the challenges of managing it in the automotive industry. The conversation concludes with a discussion on the importance of psychological safety and the need for investment in creating a positive work environment. Keywords EV connected vehicle, software development, automotive industry, software-defined vehicles, developer experience, autonomy, executable governance, domain-driven design, industrial development, domain design, working with the business, change management, tech debt, psychological safety Takeaways * Working in the EV connected vehicle space presents unique challenges and differences in software development compared to other industries. * The shift towards software-defined vehicles allows for more flexibility and the ability to make changes in the cloud. * Developer experience is crucial in delivering work quickly and efficiently. * Autonomy in larger organizations requires executable governance and domain-driven design. * Resistance to adopting new disciplines in software development can hinder progress and innovation. Taking time for domain design is crucial for successful industrial development. * Working directly with the business helps in understanding their needs and delivering value. * Implementing change requires breaking old habits and challenging the status quo. * Tech debt is a constant challenge in the automotive industry and needs to be managed effectively. * Creating a psychologically safe work environment is essential for team productivity and well-being. Titles * Overcoming Resistance to New Disciplines in Software Development * The Importance of Developer Experience in Delivering Work Quickly Managing Tech Debt in the Automotive Industry * Working Directly with the Business for Better Results Sound Bites * "Creating features for people, right, on the fly." * "Why can't we deliver today's work today?" * "Every company that has invested in autonomy has reaped the benefits." * "I think as you move from shop to shop to shop, let's go out there and state that I don't think anyone's got any bad intentions." * "Being able to take these things down to the smallest possible level that can be moved around." * "Effectively starts breaking a few eggs and actually trying to break and smash the system in some way, shape or form." Chapters 00:00 Introduction and Background 01:00 Working in the EV Connected Vehicle Space 07:05 The Importance of Developer Experience 09:10 Achieving Autonomy and Delivering Work Quickly 12:01 The Role of Traditional IT and Migration/Modernization 14:18 Executable Governance and Discipline 16:07 Resistance to New Disciplines in Software Development 19:18 Working Directly with the Business 20:28 Challenges of Implementing Change 22:14 Managing Tech Debt in the Automotive Industry 29:27 The Significance of Psychological Safety

S1E3 - From Developer to CEO - the "Accidental Tech Leader"- Aaron Phethean

Summary The conversation explores the journey from developer to CEO, the challenges of transitioning from a technical role to a leadership position, and the importance of developing a well-rounded skill set. It also touches on the need for partnerships and collaboration within a big company, the integration of the human element in technology roles, and the balance between work and personal life. The discussion delves into the role of testing in software development and data pipelines, the impact of AI on developers, and the future of data projects. The conversation explores the challenges and differences between data teams and traditional developer teams. It also discusses the impact of legacy systems on data projects and the importance of agility in data management. The conversation touches on the potential of AI and generative interfaces in data technology. It also addresses the decision-making process for choosing data technologies and strategies. The conversation concludes with a discussion on the biggest opportunities in data for companies, including self-service analytics, data sensing, monetization, and connectivity. Keywords developer to CEO, transitioning roles, leadership, partnerships, collaboration, work-life balance, testing, data pipelines, AI, data projects, data teams, traditional developer teams, legacy systems, agility, AI, generative interfaces, data technologies, data strategies, self-service analytics, data sensing, monetization, connectivity Takeaways * Transitioning from a technical role to a leadership position requires casting off the label of being solely a technologist and developing a well-rounded skill set. * Partnerships and collaboration are crucial within a big company to foster an entrepreneurial spirit and drive innovation. * Integrating the human element in technology roles is essential for creating a more holistic and productive work environment. * Testing is a critical aspect of software development and data pipelines, ensuring the reliability and accuracy of systems. * While AI may automate certain tasks, developers will still play a vital role in managing change and ensuring the quality of data inputs. * Data projects require a focus on high-quality data and the ability to deliver complete data sets, with the potential for a shift in roles and a growing industry. Data teams and traditional developer teams share similarities in the importance of understanding the end user and the business needs. * Legacy systems pose challenges in data projects, requiring a balance between maintaining historical data and modernizing the technology stack. * Agility is crucial in data management, allowing for efficient decision-making and avoiding bottlenecks. * AI and generative interfaces have the potential to revolutionize data technology, enabling more fluid and intuitive interactions. * The decision-making process for choosing data technologies and strategies should consider the full picture, including legacy systems and future scalability. * The biggest opportunities in data for companies include self-service analytics, leveraging more data sources, monetization, and improving connectivity. Titles * The Future of Data Projects * The Impact of AI on Developers The Importance of Agility in Data Management * The Biggest Opportunities in Data for Companies Sound Bites * "Getting rid of the technology, you're a technology person, that I think is the biggest hurdle." * "The easiest thing in the world to do is to pick up the keyboard and write some code. That is like an escape route to feeling productive." * "Go and organize another meeting afterwards and could we, could I really help you with that and give you what you need there." * "You start to need data and you start to spot that you need data, probably in finance, it's pretty common. Marketing is pretty common." * "If you can imagine what the business needs, if you speak to the people in the business, if you are much more connected with the question and the person, well your analytics is going to be an awful lot better." * "You're never really on the new version of data, you're always there." Chapters 00:00 Introduction and Journey from Developer to CEO 03:12 Partnerships and Collaboration in a Big Company 06:14 Integrating the Human Element in Technology Roles 09:28 The Importance of Testing in Software Development and Data Pipelines 13:23 The Impact of AI on Developers 23:29 Challenges and Differences: Data Teams vs. Traditional Developer Teams 25:13 Legacy Systems and the Balancing Act in Data Projects 30:07 The Importance of Agility in Data Management 33:11 The Potential of AI and Generative Interfaces in Data Technology 39:17 Choosing Data Technologies and Strategies: Considering the Full Picture 42:52 The Biggest Opportunities in Data for Companies

S01E02 - Getting Personal About Software Development - Rikard Ottosson

Summary In this conversation, Dave and Rikard discuss various topics related to personal struggles, changes in the workplace, agile methodologies, servant leadership, toxic people, work-life balance, tech debt, pair programming, and the need for regulation in the software development industry. Takeaways * The workplace has undergone significant changes, moving from command and control leadership to more agile and fluid ways of working. * Servant leadership is important, but many organizations claim to practice it without truly understanding or implementing it effectively. * Tech debt is a common challenge in software development, and it requires deliberate efforts to address and reduce it. * Pair programming can be a valuable practice for improving collaboration, knowledge sharing, and code quality. * The software development industry may benefit from some form of regulation or accreditation to ensure competency and accountability. Sound Bites * "Life is what it does. You have death and loss and whatever, but you kind of have to get on with it." * "Everyone claims they're agile, but no one can actually tell you how they're being agile." * "Everyone claims they do servant leadership, but I think 80% of people are doing it wrong."

Chasing Psychological Safety - S1E1 - Inaugural Special Episode with the Godmother of Psychological Safety in Technology Gitte Klitgaard

Summary The conversation covers various topics related to the tech industry, personal challenges, and the need for a psychological safety community. The hosts catch up and discuss the current state of the industry, including issues with online presence and SEO. They also share their experiences with career changes and challenges in the industry. The conversation concludes with a discussion on creating a network of podcasts and the future of the tech industry. This conversation explores the challenges faced by women in the tech industry and the importance of psychological safety in creating inclusive and innovative teams. The speakers discuss the impact of mediocrity in organizations and the need for ego-less leadership. They also highlight the journey to psychological safety and the lack of measurement in this area. Additionally, they touch on the connection between psychological safety and innovation, as well as the cultural differences in fostering psychological safety. This part of the conversation focuses on the importance of neurodiversity in the workplace and the need for psychological safety and health at work. It also discusses the disconnect in diversity and inclusion initiatives and the impact of the mental health crisis on work. The conversation highlights the role of communication and bullying in the workplace and the importance of human work in creating a supportive environment. It emphasizes the need for effective leadership, self-awareness, and reflection, as well as the importance of embracing diversity and cultural differences. The conversation also touches on the need for preventive work, supportive environments, and continuous improvement in teams. Finally, it emphasizes the importance of recognizing and supporting neurodivergent individuals and challenging stereotypes in the workplace. In this conversation, Duena Blomstrom discusses the concept of podders and their potential to have their own podcasts. She emphasizes the importance of psychological safety and human depth in the tech industry. Duena also talks about humanizing engagement and centralizing resources for everyone. She extends an invitation to discuss topics like authenticity and women developers. The conversation concludes with closing remarks and future plans. Takeaways The tech industry is facing challenges related to online presence, SEO, and the dissemination of knowledge. Personal challenges and career changes can impact one's professional journey. Creating a network of podcasts can provide a platform for discussing important topics and amplifying voices. There is a need for a psychological safety community to address issues in the tech industry and promote a supportive and inclusive environment. Women in the tech industry face unique challenges and often struggle to be taken seriously. Psychological safety is crucial for creating inclusive and innovative teams. Mediocrity in organizations can hinder progress and prevent the development of psychological safety. Ego-less leadership is essential for fostering psychological safety and creating a culture of trust and collaboration. Measuring psychological safety is challenging but necessary for understanding team dynamics and identifying areas for improvement. Cultural differences play a role in fostering psychological safety and must be considered in creating inclusive environments. Neurodiversity and psychological safety are crucial for creating a supportive and inclusive workplace. Leadership plays a vital role in fostering psychological safety and promoting effective communication. The mental health crisis and burnout are significant challenges that need to be addressed in the workplace. Embracing diversity, cultural differences, and individual strengths is essential for creating a thriving work environment. Continuous improvement, self-reflection, and learning are key to creating a positive and productive workplace culture. The podders concept involves individuals having their own podcasts. Psychological safety and human depth are crucial in the tech industry. Humanizing engagement and centralizing resources can benefit everyone. Discussions on authenticity and women developers are important. Chapters 00:00 Introduction and Catching Up 08:05 Discussing the Current State of the Tech Industry 09:32 Challenges with Online Presence and SEO 15:30 Personal Challenges and Career Changes 20:40 Creating a Network of Podcasts 23:03 Issues with Google and Microsoft 28:29 The Future of the Tech Industry 31:18 Techlet Culture and Disseminating Knowledge 34:02 Collaboration and Co-hosting Opportunities 35:01 The Need for a Psychological Safety Community 35:31 The Challenges of Being a Woman in Tech 38:06 The Importance of Psychological Safety 43:03 The Impact of Mediocrity in Organizations 46:26 The Need for Ego-less Leadership 53:52 The Journey to Psychological Safety 56:08 The Lack of Psychological Safety in Large Organizations 01:00:43 The Connection Between Psychological Safety and Innovation 01:04:37 The Challenges of Measuring Psychological Safety 01:09:08 The Cultural Differences in Psychological Safety 01:10:57 The Importance of Neurodiversity in the Workplace 01:11:23 The Need for Psychological Safety and Health at Work 01:12:13 The Disconnect in Diversity and Inclusion Initiatives 01:13:08 The Impact of Mental Health Crisis on Work 01:13:32 The Role of Communication and Bullying in the Workplace 01:14:23 The Importance of Human Work in the Workplace 01:15:13 The Focus on Output vs. Value in the Workplace 01:15:48 The Need for User Research and Customer Understanding 01:16:17 The Lack of Sustained Efforts in Design-Led Development 01:17:15 The Importance of Effective Communication and Listening 01:18:08 The Role of Leadership in Creating Psychological Safety 01:18:36 The Importance of Embracing Diversity and Cultural Differences 01:19:01 The Need for Self-Awareness and Reflection in Leadership 01:20:35 The Need for Humility and Learning in Leadership 01:21:05 The Importance of Empowering and Supporting Teams 01:22:06 The Need for Preventive Work and Supportive Environments 01:23:25 The Importance of Daily Human Work in Teams 01:24:57 The Generational Change in Workplace Dynamics 01:26:16 The Need for Human Work in the Face of Automation 01:27:05 The Role of Leadership in Creating Psychological Safety 01:28:27 The Importance of Self-Reflection and Self-Awareness in Leadership 01:29:19 The Need for Research and Understanding of Team Burnout 01:30:07 The Importance of Team Dynamics and Human Work 01:31:01 The Lack of Research and Focus on Human Work in Technology 01:32:21 The Importance of Continuous Improvement and Progress 01:33:18 The Need for Change and Innovation in the Workplace 01:34:57 The Importance of Neurodiversity and Inclusion in the Workplace 01:36:16 The Need for Change in Leadership and Workplace Culture 01:37:43 The Importance of Recognizing and Supporting Neurodivergent Individuals 01:39:29 The Need for a Shift in Mindset and Understanding of Neurodiversity 01:41:06 The Importance of Challenging Stereotypes and Embracing Diversity 01:43:43 The Need for Individualized Support and Understanding of Neurodivergent Individuals 01:45:40 Introduction to Podders Concept 01:46:07 Mission: Psychological Safety and Human Depth 01:47:01 Humanizing Engagement and Centralizing Resources 01:48:20 Invitation to Discuss Authenticity and Women Developers 01:49:15 Closing Remarks and Future Plans