Podcast appearances and mentions of patrick kua

In this episode of Book Overflow, Carter and Nathan discuss Tidy First? by Kent Beck. Join them as they discuss when you should prioritize tidying your code over feature improvements, what tidying means, and the Beck's thoughts on software and the time value of money! -- Books Mentioned in this Episode -- Note: As an Amazon Associate, we earn from qualifying purchases. ---------------------------------------------------------- Tidy First?: A Personal Exercise in Empirical Software Design by Kent Beck https://amzn.to/40uOEtL (paid link) Refactoring: Improving the Design of Existing Code (2nd Edition) by Martin Fowler https://amzn.to/3C9d5mq (paid link) Building Evolutionary Architectures: Automated Software Governance by Neal Ford, Rebecca Parsons, Patrick Kua, Pramod Sadalage https://amzn.to/4fmoIVC (paid link) A Philosophy of Software Design, 2nd Edition by John Ousterhout https://amzn.to/4ecmYgv (paid link) The Practice of Programming by Brian Kernighan, Rob Pike https://amzn.to/4fuMP4b (paid link) ---------------- 00:00 Intro 03:14 About the Book 05:41 Thoughts on the Book 11:17 Techniques and Approaches for Tidying (Part 1) 36:20 How to prioritize and manage tidying tasks (Part 2) 47:30 Optionality, Reversibility and The Philosophy of Tidying (Part 3) 01:05:38 Final Thoughts ---------------- Spotify: https://open.spotify.com/show/5kj6DLCEWR5nHShlSYJI5L Apple Podcasts: https://podcasts.apple.com/us/podcast/book-overflow/id1745257325 X: https://x.com/bookoverflowpod Carter on X: https://x.com/cartermorgan Nathan's Functionally Imperative: www.functionallyimperative.com ---------------- Book Overflow is a podcast for software engineers, by software engineers dedicated to improving our craft by reading the best technical books in the world. Join Carter Morgan and Nathan Toups as they read and discuss a new technical book each week! The full book schedule and links to every major podcast player can be found at https://www.bookoverflow.io

In this episode of Book Overflow, Carter Morgan and Nathan Toups discuss "Building Evolutionary Architectures" by Neal Ford, Rebecca Parsons, Patrick Kua, and Pramod Sadalage. Join them as they discuss how to evolve your data schema, modern DevOps practices, and common architectural pitfalls and antipatterns.

In this episode of Book Overflow, Carter Morgan and Nathan toups discuss "Building Evolutionary Architecture" by Neal Ford, Rebecca Parsons, Patrick Kua, and Pramod Sadalage. Join them as they discuss how the approaches to designing software architecture have changed over the years, the purpose of fitness functions, and how trying to re-use code can backfire!

"Architekci muszę bez przerwy oceniać cechy architektury, aby upewnić się, że ciągle zapewniają one jakość i nie stają się antywzorcami..." Ten cytat z książki "Building Evolutionary Architectures: Support Constant Change" autorstwa Neala Forda, Rebeki Parsons i Patricka Kua dotyczy jednego z fundamentów architektury ewolucyjnej, czyli tzw. funkcji dopasowania - Fitness Functions.Funkcje te pozwalają konkretnie ocenić dopasowanie architektury oprogramowania względem postawionych wymagań i podejmować świadome decyzje odnośnie wprowadzania zmian. Czym są wspominane tu funkcje, jak można je definiować i weryfikować, a także czym jest architektura ewolucyjna, o tym rozmawiamy z moim dzisiejszym gościem, Sebastianem Buczyńskim.Zapraszam!Materiały dodatkowe:Building Evolutionary Architectures: Support Constant Change, Neal Ford, Rebecca Parsons, Patrick Kua, 2017Building Evolutionary Architectures, prezentacja Rebeki Parsons, Neala Forda i Jamesa Lewisa z konferencji GOTO 2023Evolutionary Software Architectures, prezentacja Neala Forda z Voxxed DaysEvolutionary Architecture from an Organizational Perspective, artykuł jednego z gości Better Software Design, Radka Maziarki na temat dopasowania architektury do przedsiębiorstwa

BONUS: Achieving Agility and Exploring the Product Owner's Impact in DevOps with Zhenya Balyasin   We start this episode by highlighting the challenges that Product Owners (POs) face when working with DevOps teams. Zhenya explains that DevOps work is unique and comes with a variety of incoming tasks and requests on a daily basis. Additionally, DevOps teams also require time to invest in improving their operations, which adds to the workload. The constant interruptions and chaotic nature of the work make it challenging for the PO to manage effectively. Unlike traditional backlogs where POs are used to prioritize tasks, in DevOps teams, the backlog may not always be the main focus. Zhenya identifies a common anti-pattern where DevOps teams have a strong willingness to help others, which can further complicate the role of the PO. From Chaos to Clarity: Addressing Anti-Patterns in DevOps Workflows Zhenya identifies several common anti-patterns that she has observed in DevOps teams. One anti-pattern is the resistance from the team to have their work organized by the Product Owner (PO) when they were already functioning without that role. Another anti-pattern is the team's excessive focus on maintenance tasks rather than prioritizing the development of the product itself. The lack of clarity in identifying the products among the various types of work received is also a common anti-pattern.   Zhenya emphasizes the importance of defining the product or service for the teams and establishing a clear roadmap. She suggests discussing the product development process and the role it plays within the team. It is crucial to involve the team in these discussions rather than imposing processes on them without consultation.   Zhenya also highlights the need for effective communication and collaboration with the team. Merely presenting a process without prior discussion and understanding of the team's dynamics and self-identity can lead to resistance. Instead, she recommends discussing process-related matters with the team beforehand. Customer-Centric DevOps: How the PO Role Revolutionized a DevOps' Team In this segment, Zhenya discusses how she changed her own work and the dynamics of the team after the Product Owner (PO) role was introduced to the DevOps team. She initially encountered an anti-pattern where the team seemed resistant to accepting the perspective and needs of the customers.   To address this challenge, Zhenya offers a couple of tips. First, she suggests initiating a discussion within the team to clarify who the customer is and how they are being served. This helps align the team's understanding and focus on meeting customer needs.   Additionally, Zhenya recommends conducting interviews with customer teams or the company itself. These interviews provide valuable insights and highlight the differences in expectations between the DevOps team and the customer's requirements. By understanding these differences, the team can adjust their approach and ensure their work aligns with the customer's needs.   By implementing these tips, Zhenya was able to foster a better understanding of the customer's viewpoint within the team, leading to improved collaboration and a more customer-centric approach to their work. People-Centric Change: Zhenya's Key Insights for Driving Transformation in Teams Zhenya shares her approach to facilitating change within the team. She emphasizes the importance of change management and highlights the Unfreeze-Change-Refreeze model. Zhenya advises breaking down the steps of change into smaller, manageable tasks while consistently communicating the value behind each step. She encourages the use of data to measure progress and guide decision-making.  Additionally, Zhenya underscores the significance of focusing on the people involved in the change process. She suggests investing time in conversations to understand individual perspectives and values. Zhenya also recommends introducing the Product Owner (PO) role gradually, addressing questions and concerns, and being mindful of the potential impact of introducing multiple changes simultaneously. Building strong relationships with the team is seen as essential in driving successful change. Preparing for Change: How Scrum Masters Can Assist Product Owners in DevOps teams In this segment, Zhenya discusses the support she expects from Scrum Masters in helping Product Owners in similar situations. She advises Scrum Masters to proactively prepare the team for the upcoming changes even before the PO joins the team. Zhenya suggests working collaboratively with the PO, Scrum Master / Agile Coach, and team lead to define a clear strategy for the team. She highlights that the PO can also assist the Scrum Master/Agile Coach in this process by providing inputs such as the roadmap, OKRs (Objectives and Key Results), and defining the team's mission. Zhenya emphasizes the importance of redefining the team's identity to facilitate and embrace the desired change. She encourages close collaboration between the Scrum Master/Agile coach, PO, and team lead to drive successful transformation. Enhance Your Change Management Skills: Zhenya's Top Resource Picks Zhenya recommends further reading and resources related to the topic of change management. She mentions the Lewin Change Management model as a valuable resource to explore. Additionally, Zhenya suggests subscribing to the newsletter of Rob Lambert from Cultivated Management, who provides insightful content and potentially offers workshops on the subject. Another newsletter recommendation is Patrick Kua's level up newsletter.   About Zhenya (Evgeniia) Balyasin Evgeniia, commonly known as Zhenya, is an experienced professional who collaborates closely with DevOps Engineers, assuming the crucial roles of Product Owner and Product Manager. With a strong background in agile software development, Zhenya brings her expertise to drive product strategies, prioritize backlog items, and ensure seamless coordination between development and operations teams. Her insightful approach and deep understanding of the DevOps landscape contribute to successful product delivery and continuous improvement. You can link with Zhenya (Evgeniia) Balyasin on LinkedIn.

“An engineering manager should make sure that the team has a good balance of delivering things that the business needs with enough capacity to do it sustainably over time." Today's clip is from episode 94 with Patrick Kua. In this clip, we discussed Pat's latest course, Engineering Manager Essentials. We discussed what an engineering manager role is, how it differs from a Tech Lead role, and the common manager versus IC career track. Pat also shared his view on why being an engineering manager is not a promotion. Listen out for: Engineering Manager Essentials - [00:00:50] The Role of Engineering Manager - [00:02:46] Difference With Tech Lead - [00:05:43] Manager and IC Paths - [00:07:53] EM Is Not a Promotion - [00:12:27] _____ Patrick Kua's Bio Patrick Kua is a seasoned technology leader with almost 20 years of experience. His personal passion is accelerating the growth and success of tech organisations and technical leaders. He has had many years of hands-on experience, leading, managing and improving complex organisations and software systems as the CTO and Chief Scientist of N26 (Berlin, Germany) and as a Technical Principal Consultant at ThoughtWorks. He is a frequent keynote and conference speaker, author of three books including “The Retrospective Handbook“, “Talking with Tech Leads“ and “Building Evolutionary Architectures“ and runs the free popular newsletter for leaders in tech, “Level Up” and the “Tech Lead Academy“, offering online training for technical leaders, or running his very popular “Shortcut to Tech Leadership“ workshop. Follow Patrick: Website – https://patkua.com/ Twitter – @patkua LinkedIn – https://www.linkedin.com/in/patkua/ EM Essentials Course – https://www.patkua.com/em-essentials/ Tech Lead Academy – https://techlead.academy/ Level Up Newsletter – https://levelup.patkua.com/ _____ Our Sponsors Mental well-being is a silent pandemic. According to the WHO, depression and anxiety cost the global economy over USD 1 trillion every year. It's time to make a difference! Learn how to enhance your lives through a master class on mental wellness. Visit founderswellbeing.com/masterclass and enter TLJ20 for a 20% discount. Skills Matter is the global community and events platform for software professionals. You get on-demand access to their latest content, thought leadership insights as well as the exciting schedule of tech events running across all time zones. Head on over to skillsmatter.com to become part of the tech community that matters most to you - it's free to join and easy to keep up with the latest tech trends. Like this episode? Subscribe on your favorite podcast app and submit your feedback. Follow @techleadjournal on LinkedIn, Twitter, and Instagram. Pledge your support by becoming a patron. For more info about the episode (including quotes and transcript), visit techleadjournal.dev/episodes/94.

Engineers can get promoted to leadership positions without knowing what is expected of them. It's less of the same and more of a sidestep. Pat Kua and I discuss the tech lead and engineering manager roles and what makes a person effective being in that role. On top of that we give perspective for people interested in those positions. Enjoy!

We cover building community & digital transformation with Yvette Pasqua, CTO @ Exos! She shares her leadership journey from MeetUp to Exos and how her experiences shaped her views on the importance of community and effective networking. We also discuss principles for creating authentic meetup experiences, how Yvette navigated her Head of Eng search without a recruiter, the importance of asking others for help, and how Exos navigated the opportunities & challenges through their digital transformation.ABOUT YVETTE PASQUAYvette (@lolarobot) is the CTO of Exos where she leads the product and engineering teams with a focus on continuous improvement, iteration, and using data to launch products that help our members become healthier and achieve their wellness, life, and work goals.Prior to joining Exos, Yvette led Product and Engineering at Haven, a health tech startup, and was the CTO at Meetup. Yvette's career has included leadership roles at startups and product development firms building products like Grindr and the Olympics video player. She's on the Board at Chloe Capital, a VC firm that invests in women-led seed-stage companies.Yvette lives in Brooklyn and Rhinebeck, NY with her wife, daughter, and wheaten terrier.“Yeah, of course during the conversation I will bring up, ‘Hey, I'm looking for a head of engineering. do you know anything? Do you have any advice? What have you thought of are the best characteristics for someone in that role?”It's a long-term play, but I think the important thing is to be really upfront with your intention for the chat. And to deliver on that in an authentic way. And to not BS someone and say, ‘Hey, I wanna network!' And then throw a job in their face and a job description.-Yvette PasquaInterested in joining an ELC Peer Group?ELCs Peer Groups provide a virtual, curated, and ongoing peer learning opportunity to help you navigate the unknown, uncover solutions and accelerate your learning with a small group of trusted peers.Apply to join a peer group HERE: sfelc.com/peerGroupsSHOW NOTES:Building technology with community in mind at MeetUp and Exos (2:20) (0:07)How community and in-person experiences inspire Yvette's career decisions (5:40)What Yvette learned about networking / community building from MeetUp (7:10)Principles for creating meaningful, authentic gatherings (10:54)Why setting boundaries & expectations encourages group psychological safety (12:38)How Yvette successfully navigated her Head of Eng search without a recruiter (14:32)Strategies for targeting potential hires that you haven't met before (17:40)Ask others for advice (21:31)Tactics for reaching out to people in an authentic way (23:40)Prioritizing time for networking conversations (27:55)Behind the digital transformation at Exos from a primarily coaching model (32:37)How Exos continuously models growth mindset (37:42)When digital transformation reaches a turning point (39:44)Rapid fire questions (42:38)LINKS AND RESOURCESThe Pragmatic Engineer by Gergely Orosz (blog/newsletter) - The #1 technology newsletter on Substack. Highly relevant for software engineers and engineering managers, useful for those working in tech. Written by engineering manager and software engineer Gergely Orosz who was previously at Uber, Skype/Microsoft, and at high-growth startups. (follow Gergely on Twitter @GergelyOrosz)Software Lead Weekly by Oren Ellenbogen (newsletter) - A weekly email for busy people who care about people, culture and leadership.Level Up by Patrick Kua (newsletter) - Level Up delivers a curated newsletter for leaders in tech. Ideal for busy people such as Tech Leads, Engineering Managers, VPs of Engineering, CTOs and more.Lenny's Newsletter by Lenny Rachitsky - A weekly advice column about product, growth, and your career.The Art of Gathering by Priya Parker (book) - Priya argues that the gatherings in our lives are lackluster and unproductive — and they don't have to be. At a time when coming together is more important than ever, Parker sets forth a human-centered approach to gathering that will help everyone create meaningful, memorable experiences, large and small, for work and for play. (Patrick's most gifted book)

“An engineering manager should make sure that the team has a good balance of delivering things that the business needs with enough capacity to do it sustainably over time." Patrick Kua is a seasoned technology leader with a passion to accelerate the growth and success of tech organisations and technical leaders. In this episode, we discussed Pat's latest course, Engineering Manager Essentials, which covers all the building blocks required to be an effective Engineering Manager (EM). We first discussed what an EM role is, how it differs from a tech lead role, and the common manager vs IC career track. Pat shared his view on why being an EM is not a promotion and what are some of the success criteria to be a good EM. Towards the end, Pat shared some anti-patterns that EM should avoid to become successful. Listen out for: Pat's Latest - [00:07:30] Engineering Manager Essentials - [00:09:25] The Role of Engineering Manager - [00:11:21] Difference With Tech Lead - [00:14:19] Manager and IC Paths - [00:16:28] EM Is Not a Promotion - [00:21:02] EM Success Criteria - [00:28:08] Multiplier Instead of Maker - [00:30:48] Course Structure - [00:33:21] Interviewing EM - [00:37:20] Antipattern 1: Continuing as a Maker - [00:39:58] Antipattern 2: Assuming Everyone Knows What You Do - [00:43:01] Antipattern 3: Optimizing Parts Instead of The Whole - [00:48:34] 3 Tech Lead Wisdom - [00:51:30] _____ Patrick Kua's Bio Patrick Kua is a seasoned technology leader with 20+ years of experience having done a wide variety of roles including being a developer, tech lead, consultant, CTO and more. His current mission is accelerating the growth of technical leaders through coaching, mentoring and training. Follow Patrick: Website – https://patkua.com/ Twitter – @patkua LinkedIn – https://www.linkedin.com/in/patkua/ EM Essentials Course – https://www.patkua.com/em-essentials/ Tech Lead Academy – https://techlead.academy/ Level Up Newsletter – https://levelup.patkua.com/ Our Sponsors DevTernity 2022 (devternity.com) is the top international software development conference with an emphasis on coding, architecture, and tech leadership skills. The lineup is truly stellar and features many legends of software development like Robert "Uncle Bob" Martin, Kent Beck, Scott Hanselman, Venkat Subramaniam, Kevlin Henney, and many others! The conference takes place online, and we have the 10% discount code for you: AWSM_TLJ. Skills Matter is the global community and events platform for software professionals. It is an easier way for technologists to grow their careers by connecting you and your peers with the best-in-class tech industry experts and communities. You get on-demand access to their latest content, thought leadership insights as well as the exciting schedule of tech events running across all time zones. Head on over to skillsmatter.com to become part of the tech community that matters most to you - it's free to join and easy to keep up with the latest tech trends. Like this episode? Subscribe on your favorite podcast app and submit your feedback. Follow @techleadjournal on LinkedIn, Twitter, and Instagram. Pledge your support by becoming a patron. For more info about the episode (including quotes and transcript), visit techleadjournal.dev/episodes/94.

Don't miss our story of the introduction of the Tech Leads During the podcast, you will find out what Tech Leads are and why we need to build this community of Tech Leads at bol.com. You will learn how we approached this and avoid hiding the Tech Leads in ivory towers. The two tech leads and an IT director share best practices and pitfalls (and what we learned from them). The Why and What of our Tech Lead Community Tech Lead Community Why did we start to define the role? What is the Tech Lead for bol.com, Responsibilities Product Tech Lead Space Tech Lead It's a fun challenge and it's taking time" - Eduardo da Silva The backlog of the tech leads Backlog of community Tech Radar Tech Vision Backlog Space Tech Leads Cloud Migration Backlog of products Examples Introduction of the role (process) Definition Scale, number of Tech Leads needed Rollout / Hiring part Building the Tech Lead Community Lessons Learned so far Best Practices Pitfalls / Challenges.GuestsAlexandra Egher; Product Tech Lead at bol.comMirko van Ede; Director IT - Shopping & Marketing Technology at bol.comEduardo da Silva; Tech Leader & Sociotechnical Architect at bol.comNotesThe book Talking with Tech Leads by Patrick Kua.We talked about API design and development in a previous episode.

Patrick Kua was CTO and Chief Scientist at N26 in Berlin and is now an independent coach and mentor to CTOs and VPs Engineering. Patrick has written several books e.g. about how to talk to tech leads and he co-authored a book about evolutionary architecture. In this episode we will therefore discuss how software architecture can embrace change and support business goals in the long run. Patrick's home page Patrick's newsletter Command line tools for architecture decision records (ADRs) Architecture elevator (Gregor Hohpe)

Pat Kua is our guest for this episode. He will share his thoughts on the pattern “Decide Closest to the Action” from the Cloud Native Patterns repository (https://www.cnpatterns.org/organization-culture/decide-closest-to-the-action). We will discuss technical leadership and management. What that means for a technical management role, and what are the pitfalls, and how to create a healthy environment. Pat recommends “Thinking in System” by Donella Meadows. Patrick Kua (@patkua) is a seasoned technology leader with almost 20 years of experience. His personal passion is accelerating the growth and success of tech organisations and technical leaders. He has had many years of hands-on experience, leading, managing and improving complex organisations and software systems as the CTO and Chief Scientist of N26 (Berlin, Germany) and as a Technical Principal Consultant at ThoughtWorks. He is a frequent keynote and conference speaker, author of three books including The Retrospective Handbook, Talking with Tech Leads and Building Evolutionary Architectures and runs the free popular newsletter for leaders in tech, “Level Up” (http://levelup.patkua.com) and the Tech Lead Academy, offering online training for technical leaders. You can find him online on twitter as @patkua or running his very popular “Shortcut to Tech Leadership” workshop.

Nesse Episódio #5 do quadro de Técnicas do HiDev Podcast eu conversei sobre Dívida Técnica com Ricardo Cavalcanti. Falamos sobre os princípios pra lidar com essas dívidas. Como evitar, como priorizar, como resolver e até convencer a gerência e os clientes da importância de dedicar tempo e esforço pra pagar as Dívidas Técnicas que vão se acumulando em todo projeto de Software. Ricardo tem mais de 15 anos de experiência com desenvolvimento de software. Atuou a maior parte do tempo como arquiteto de software e líder técnico e atualmente é Diretor de Mercado Local na ThoughtWorks Brasil. Ricardo tem graduação e mestrado em Ciência da Computação pelo Centro de Informática da UFPE. Quando terminar de escutar esse episódio dá um pulo lá no Episódio #5 do quadro de Trajetórias do HiDev Podcast. Lá a gente conversou sobre os inúmeros desafios vividos por Ricardo nos seus vários anos de experiência com desenvolvimento de software. CONVIDADO: RICARDO CAVALCANTI [Twitter] [LinkedIn] APRESENTADOR: Bruno Cartaxo [Twitter] REFERÊNCIAS CITADAS NO EPISÓDIO [Conceito] Mikado Refactoring Method [Conceito] Trunk Based Development [Blog Post] Is High Quality Software Worth the Cost? - Martin Fowler [Livro] Refactoring: Improving the Design of Existing Code - Martin Fowler [Livro] Working Effectively with Legacy Code - Michael Feathers [Livro] Practical Object Oriented Design in Ruby - Sandi Metz [Livro] Building Evolutionary Architectures - Neal Ford, Rebecca Parsons, Patrick Kua

“A Tech Lead is a person with a technical background, typically an engineer who is leading a team and particularly responsible and accountable for their technical direction." Patrick Kua is a seasoned technology leader and is passionate about accelerating the growth and success of tech organizations and technical leaders. Before going independent recently, Pat was the CTO and Chief Scientist of N26 (Berlin, Germany), where he transformed the early stage startup culture and led the Product & Technology teams for hypergrowth. Before N26, Pat spent 13+ years in ThoughtWorks as a Technical Principal Consultant, where he researched deep into the Tech Lead role and became a thought leader about it. Pat is a frequent keynote and conference speaker and also an author. In this episode, I had an amazing learning conversation with Pat about the Tech Lead role and discussed deep with him on what it takes to become a good Tech Lead. Pat also shared his journey as a CTO and Chief Scientist of N26, the challenges he faced there and what he did to transform the Product & Technology teams to align for hypergrowth. This is one of those conversations you definitely not want to miss to learn how to become a great technical leader! Listen out for: What Pat is up to - [00:04:22] Pat’s career journey - [00:07:37] Tech Lead definition - [00:16:46] Why Pat is interested about Tech Leads - [00:18:02] Tech Lead attributes - [00:21:58] Effective Tech Lead - [00:26:12] Examples of Tech Lead measures - [00:29:53] Tech Lead business angle - [00:36:27] Pat’s N26 story as a CTO - [00:38:51] How Pat grew N26 engineering team - [00:44:03] How Pat balanced his responsibility and time as a CTO - [00:51:10] Target Operating Model (TOM) - [00:53:05] Why Pat switched to become a Chief Scientist in N26 - [00:57:58] Tech Lead resources - [00:59:38] Pat’s 3 Tech Lead Wisdom - [01:01:05] _____ Patrick Kua’s Bio Patrick Kua is a seasoned technology leader with almost 20 years of experience. He has had many years of hands-on experience, leading, managing and improving complex organisations and software systems as the CTO and Chief Scientist of N26 and as a Technical Principal Consultant at ThoughtWorks. He is a frequent keynote and conference speaker, author of three books, and runs the free popular newsletter for leaders in tech, “Level Up” and the “Tech Lead Academy“, offering training for technical leaders, or running his very popular “Shortcut to Tech Leadership“ workshop. Follow Pat: Website – https://patkua.com LinkedIn – https://www.linkedin.com/in/patkua/ Twitter – https://twitter.com/patkua Our Sponsors Are you a startup in software development which is less than 5 years old? If yes, our sponsor at JetBrains has a 50% startup discount offer which allows Startups to purchase multiple products and subscriptions for up to 10 unique licenses over a period of months. To find out more, go to https://www.jetbrains.com/store/startups. Like this episode? Follow @techleadjournal on LinkedIn, Twitter, and Instagram. Pledge your support by becoming a patron. For more info about the episode (including quotes and transcript), visit techleadjournal.dev/episodes/9.

Hey Tech Leads, This week we've been foraging through the internet looking for great writing on the tech lead role. Today, we're focused on Patrick Kua's post The Definition of a Tech Lead, which has some points I think you might find interesting. To get on the email list and find ways to engage with the Tech Lead Coaching Network, visit https://techleadcoaching.com. SEGMENTS- 0:05 - Intro

Patrick is the CTO of the mobile bank N26, where he is building the engineering group that will change modern retail banking for people like you and me. Formerly a Principal Technical Consultant at ThoughtWorks in London, he is also the author of three books, The Retrospective Handbook, Talking with Tech Leads and most recently, Building Evolutionary Architectures. Patrick is a frequent conference speaker, a blogger and is passionate about bringing a balanced focus between people, organisations and technology.During this interview, we touched on the different roles Patrick's overtook during his career. Pat devised on how his time as a consultant prepared him for his current role as a CTO. We discussed the definition of a Technical Lead and compared it to the CTO Role(s). We finally discussed Pat's personal learning strategies.Here are the links of the show:@patkua https://twitter.com/patkuaBlog https://www.thekua.com/atworkTech Lead Course - http://thekua.io/techlead-courseTalking with Tech Leads book - https://thekua.io/twtlN26 Bank https://n26.comN26 are hiring - https://grnh.se/f64c07431ThoughtWorks https://www.thoughtworks.comThe Retrospective Handbook https://leanpub.com/the-retrospective-handbookeXtreme Tuesday Club London https://www.meetup.com/eXtreme-Tuesday-Club-XTCDan North https://dannorth.netAlistair Cockburn https://alistair.cockburn.usCreditsMusic Aye by Yung Kartz is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 License.Your hostSoftware Developer‘s Journey is hosted and produced by Timothée (Tim) Bourguignon, a crazy frenchman living in Germany who dedicated his life to helping others learn & grow. More about him at timbourguignon.fr.Want to be next?Do you know anyone who should be on the podcast? Do you want to be next? Drop me a line: info@devjourney.info or via Twitter @timothep.Gift the podcast a ratingPlease do me and your fellow listeners a favor by spreading the good word about this podcast. And please leave a rating (excellent of course) on the major podcasting platforms, this is the best way to increase the visibility of the podcast:Apple PodcastsStitcherGoogle PlayThanks!Support the show (http://bit.ly/2yBfySB)

With the conclusion of ArchConf 2018 we've wrapped the 2018 tour. This week I sit with Neal Ford of ThoughtWorks. We talk about the trade-offs of software architecture, how to identify those, and the 19th edition of the ThoughtWorks Tech Radar. Neal co-authored "Building Evolutionary Architectures" along with Rebecca Parsons and Patrick Kua. You can learn more about some of the ideas in the book at evolutionaryarchitecture.com.

The O’Reilly Programming Podcast: How to build evolvable systems.In this episode of the O’Reilly Programming Podcast, I talk with Rebecca Parsons, chief technology officer at ThoughtWorks. She will be leading the workshop Building Evolutionary Architectures Hands-On at the O’Reilly Open Source Convention (OSCON), July 16-19, 2018, in Portland, Oregon. Parsons also is co-author (with Neal Ford and Patrick Kua) of the book Building Evolutionary Architectures.Discussion points: The shift in focus to evolvability rather than predictability: “When you look at the way the technology landscape is changing,” Parsons says, “trying to say you can predict any kind of technology roadmap is simply impractical.” Why evolutionary systems need to be easy to understand: “How easy it is to change an architecture directly correlates with how easy it is to understand what’s happening in the system,” she says. The role of fitness functions: “Fitness functions are defining what outcomes we want the architecture to achieve,” Parsons says.  “Fitness functions guide our decisions about how we are going to evolve the architecture.” An advocate for diversity in the technology industry, Parsons talks about groups she has worked with, including CodeChix and Women Who Code, and the issues that women in the field continue to face. “The climate and culture in the tech industry is still not a comfortable place for women to be,” she says.  “We would like to believe as an industry that we’re a meritocracy, but we’re not. Part of the problem we’re dealing with is that women leave at a significantly greater rate than men do. We can double the number of women who come in, but if they’re leaving at a faster rate, we’re not going to make progress.” Other links: Video of Parsons’ presentation The evolution of evolutionary architectures at the 2016 O’Reilly Software Architecture Conference Parsons praises the work of other groups working to increase diversity, including Black Girls Code and AnitaB.org

The O’Reilly Programming Podcast: How to build evolvable systems.In this episode of the O’Reilly Programming Podcast, I talk with Rebecca Parsons, chief technology officer at ThoughtWorks. She will be leading the workshop Building Evolutionary Architectures Hands-On at the O’Reilly Open Source Convention (OSCON), July 16-19, 2018, in Portland, Oregon. Parsons also is co-author (with Neal Ford and Patrick Kua) of the book Building Evolutionary Architectures.Discussion points: The shift in focus to evolvability rather than predictability: “When you look at the way the technology landscape is changing,” Parsons says, “trying to say you can predict any kind of technology roadmap is simply impractical.” Why evolutionary systems need to be easy to understand: “How easy it is to change an architecture directly correlates with how easy it is to understand what’s happening in the system,” she says. The role of fitness functions: “Fitness functions are defining what outcomes we want the architecture to achieve,” Parsons says.  “Fitness functions guide our decisions about how we are going to evolve the architecture.” An advocate for diversity in the technology industry, Parsons talks about groups she has worked with, including CodeChix and Women Who Code, and the issues that women in the field continue to face. “The climate and culture in the tech industry is still not a comfortable place for women to be,” she says.  “We would like to believe as an industry that we’re a meritocracy, but we’re not. Part of the problem we’re dealing with is that women leave at a significantly greater rate than men do. We can double the number of women who come in, but if they’re leaving at a faster rate, we’re not going to make progress.” Other links: Video of Parsons’ presentation The evolution of evolutionary architectures at the 2016 O’Reilly Software Architecture Conference Parsons praises the work of other groups working to increase diversity, including Black Girls Code and AnitaB.org

The O’Reilly Programming Podcast: The skills needed to make the move from developer to architect.In this episode of the O’Reilly Programming Podcast, I talk with Nathaniel Schutta, a solutions architect at Pivotal, and presenter of the video I’m a Software Architect, Now What?. He will be giving a presentation titled Thinking Architecturally at the 2018 O’Reilly Software Architecture Conference, February 25-28, 2018, in New York City.Discussion points: How Schutta sees the role of the software architect: “I like to say that as architects, we’re like the Rosetta Stone of an organization,” he says. “We’re the ones playing the translation game between the development side, the management side, and the business side. We have to be able to fit comfortably between those groups.” On the challenges in moving from being a software developer to becoming a software architect: “As developers, we’re largely insulated from much of the politics of the organization,” Schutta says. “As an architect, you have to craft your message for many different audiences, and take the core central idea and spin that yarn so it resonates for all these groups.”   The “soft skills” that are needed to succeed in the architect role, including communications, leadership ability, self-promotion, and investing in personal relationships. How to “think architecturally”: “As developers, we have this tendency to chase the shiny new thing, but as an architect, we can’t afford to do that,” Schutta says. “The decisions we make have long-lasting impact, so architects have to be thinking about trade-offs.” Other links: Schutta’s presentation Architect as a Storyteller at the 2017 O’Reilly Software Architecture Conference in London Schutta’s presentation Modeling for Architects at the 2016 O’Reilly Software Architecture Conference The video Presentation Patterns, presented by Neal Ford and Nathanial Schutta The book Building Evolutionary Architectures, by Neal Ford, Rebecca Parsons, and Patrick Kua Spring One Platform, December 4-7, 2017

The O’Reilly Programming Podcast: The skills needed to make the move from developer to architect.In this episode of the O’Reilly Programming Podcast, I talk with Nathaniel Schutta, a solutions architect at Pivotal, and presenter of the video I’m a Software Architect, Now What?. He will be giving a presentation titled Thinking Architecturally at the 2018 O’Reilly Software Architecture Conference, February 25-28, 2018, in New York City.Discussion points: How Schutta sees the role of the software architect: “I like to say that as architects, we’re like the Rosetta Stone of an organization,” he says. “We’re the ones playing the translation game between the development side, the management side, and the business side. We have to be able to fit comfortably between those groups.” On the challenges in moving from being a software developer to becoming a software architect: “As developers, we’re largely insulated from much of the politics of the organization,” Schutta says. “As an architect, you have to craft your message for many different audiences, and take the core central idea and spin that yarn so it resonates for all these groups.”   The “soft skills” that are needed to succeed in the architect role, including communications, leadership ability, self-promotion, and investing in personal relationships. How to “think architecturally”: “As developers, we have this tendency to chase the shiny new thing, but as an architect, we can’t afford to do that,” Schutta says. “The decisions we make have long-lasting impact, so architects have to be thinking about trade-offs.” Other links: Schutta’s presentation Architect as a Storyteller at the 2017 O’Reilly Software Architecture Conference in London Schutta’s presentation Modeling for Architects at the 2016 O’Reilly Software Architecture Conference The video Presentation Patterns, presented by Neal Ford and Nathanial Schutta The book Building Evolutionary Architectures, by Neal Ford, Rebecca Parsons, and Patrick Kua Spring One Platform, December 4-7, 2017

In this episode Patrick Kua from Thoughtworks discusses the importance of having good technical leadership on teams.  He also discusses his new book, "Talking with Tech Leads: From Novices to Practitioners"

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, spoke to Patrick Kua from ThoughtWorks on growing technical leadership and evolutionary architecture Why listen to this podcast: - There is a significant gap in technical leadership capability in teams and across the industry as a whole - Your experience as a developer doesn’t prepare you for a tech lead roleRecognize that the skills and responsibilities are very different and find ways to build the new skills – training, mentoring and support - Software will continue to be changed so it is important to build it for changeability from the beginning - Many of the big decisions which are made at the beginning of a product’s life will change over time, build the ability to change into the core architectural design More on this: Quick scan our curated show notes on InfoQ http://bit.ly/2vy4xl4 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/2vy4xl4

Patrick Kua is a Technical Principal Consultant for ThoughtWorks in London. He is a conference speaker and author of "The Retrospective Handbook" and "Talking with Tech Leads" and is passionate about bringing a balanced focus on people, organization and technology. Show notes at http://hellotechpros.com/patrick-kua-leadership/ Key Takeaways Horrible bosses don't have to be managers, they can be more senior people on the team. Personal issues should be taken offline, after calming down. If you are a junior colleague trying to resolve an issue with a more senior colleague, find another senior individual to act as a mediator. Developer to tech lead is a huge jump and changes the expectations. When you are a dev your workload consists of code, working with fellow devs and solving tech problems. When you are a team lead your workload consists of people issues, planning and whole system architecture. When moving to a tech lead role, it can feel lonely. Your focus is on the broader view, not tech issues. You're not working on the same issues with your old friends. You're starting to spend more time in meetings with people outside the department. However, you have a broader impact on the organization. You set the culture. Instead of having really deep relationships with a small group of people that you pair with every day, you need to invest time with the broader team. You must get outside of your comfort zone and spend time with people with different styles. Your emotional range and capacity to connect with people will grow as your career grows.

Johannes Thönes talks to Patrick Kua about the role of a technical lead and how people become tech leads. The show covers the definition of a tech lead, the responsibilities of the role and the challenges of becoming a tech lead. Venue: Internet   Related Links Episode 228: Software Architecture Sketches with Simon Brown Article: A […]

Johannes Thönes talks to Patrick Kua about the role of a technical lead and how to become one. The show starts with introducing the concept of a lead and contrasts the lead role with other roles, such as technical manager, architect and senior developer.  The discussion continues to the responsibilities of a tech lead (supporting engineering practices, managing, resolving conflict, and growing people). The discussion continues on to talk about the challenges of becoming a tech lead and how to overcome them and closes with the question: “how can you tell if you are succeeding as a tech lead”?

Guest: Patrick Kua @patkua Full show notes are at https://developeronfire.com/podcast/episode-93-patrick-kua-leading-leaders

Les grands leaders techniques travaillent en équipe pour livrer des produits couronnés de succès, sans tenir compte de la complexité des besoin du business, des outils et des techniques. Ils créent des équipes auto-investies, conduites pour réaliser les choses correctement.

Les grands leaders techniques travaillent en équipe pour livrer des produits couronnés de succès, sans tenir compte de la complexité des besoin du business, des outils et des techniques. Ils créent des équipes auto-investies, conduites pour réaliser les choses correctement. Les leaders techniques inefficaces détruisent le potentiel de ces mêmes équipes et génèrent des ondes de ressentiment. Le plus souvent, ce n'est pas parce que le leader technique est "mauvais", simple résultat du "Peter principle", où les systèmes tendent à promouvoir des personnes techniquement parfaitement compétentes dans un rôle exigeant un ensemble de capacités totalement différent. Nos organisations doivent donc trouver un meilleur moyen de construire la prochaine génération de leaders techniques. Nous explorerons donc comment ces organisations peuvent mieux mettre tout cela en application.