Show Notes
Coding Chats episode 54 - Nikki Maginn and John Crickett explore the critical role of soft skills in engineering, emphasizing the importance of communication, emotional intelligence, and collaboration. They discuss how engineers can bridge the gap between technical expertise and customer-facing roles, the art of asking questions, and the significance of building trust and meaningful connections. The dialogue also touches on the balance of confidence and humility in leadership, the power of storytelling, and the necessity of understanding context in communication. Ultimately, the conversation highlights that soft skills are essential for engineers to thrive in their careers and contribute effectively to their teams.
Chapters 00:00 The Importance of Soft Skills in Engineering 03:14 Bridging the Gap: Engineers and Customer Interaction 06:26 Nature vs. Nurture: The Art of Asking Questions 09:06 Effective Communication: How to Ask the Right Questions 12:06 Understanding Context: The Key to Effective Dialogue 14:53 Navigating Emotional Reactions in Communication 17:36 Feedback and Conflict Resolution: Building Better Relationships 20:57 The Efficiency of Communication in Engineering 23:32 The Role of Emotions in Engineering 26:38 Team Dynamics: The Myth of the 10x Developer 29:08 The Importance of Communication in Engineering 31:29 Empowering Teams to Reduce Meetings 34:40 Communicating with Impact 38:21 Building Trust with Non-Technical Stakeholders 42:11 Creating Meaningful Connections 48:53 Owning Your Confidence as an Engineer
Nikki's Links: Website: www.insideoutengineering.com LinkedIn: https://www.linkedin.com/in/nikki-maginn/
John's Links: John's LinkedIn: https://www.linkedin.com/in/johncrickett/ John’s YouTube: https://www.youtube.com/@johncrickett John's Twitter: https://x.com/johncrickett John's Bluesky: https://bsky.app/profile/johncrickett.bsky.social
Check out John's software engineering related newsletters: Coding Challenges: https://codingchallenges.substack.com/ which shares real-world project ideas that you can use to level up your coding skills.
Developing Skills: https://read.developingskills.fyi/ covering everything from system design to soft skills, helping them progress their career from junior to staff+ or for those that want onto a management track.
Takeaways Engineering success relies on effective communication and collaboration. Engineers must learn to translate technical work for broader understanding. Emotional intelligence is crucial for engineers in customer-facing roles. Asking the right questions is a teachable skill. Building trust requires meaningful connections with colleagues. Navigating difficult conversations is essential for team dynamics. Context is key in understanding reactions and emotions in communication. Confidence should be balanced with humility in leadership roles. Storytelling can enhance the impact of technical communication. Investing in relationships leads to more efficient conversations.
More from Coding Chats
Coding Chats Episode 83 - In this episode, VB from OpenAI’s developer experience team explains why he thinks plan mode is obsolete and how coding agents have shifted from step-by-step instructions to outcome-driven, long-running work. We cover how to write a good agents.md, why tests still matter when agents write the code, spec-driven development, and why cloud agents may be the future of dev tooling.
Coding Chats Episode 82 - John talks with Dave Westgarth, head of delivery at a Databricks consultancy. Dave shares his path from a psychology degree and McDonald's into tech, and they discuss why the Scrum Master role is so misunderstood, how it differs from a delivery manager, and whether either needs to be technical.They also look at how AI is changing delivery work. Faster code just moves the bottleneck upstream, John argues there's no AI-specific skill you can't learn in a day, and engineering fundamentals are what make AI useful.
Coding Chats Episode 81 - Ben Howdle talks to John Crickett about being a first time CTO in a start-up. Ben, author of The First CTO, shares what changes when you move from building technology to leading a technical team: the pressure, the trade-offs, and the realization that writing code is only part of the job.Drawing on startup experience and lessons learned the hard way, Ben discusses how to balance quality against runway, manage people, and communicate technical decisions in terms that founders and other non-technical stakeholders can understand. He also explores why resourcefulness, resilience, and comfort with ambiguity matter so much—and why CTOs often spend more time selling ideas than they expect.Whether you’re stepping into your first CTO role or leading a technical team at an early-stage company, this conversation offers candid insights into the realities of technical leadership.
Coding Chats Episode 80 - start-up advisor Alexander Berkovich shares his expertise on building successful start-ups, hiring strategies, CTO roles, and the importance of communication between technical and business teams. Discover practical tips for navigating the challenges of early-stage companies and how to align technical excellence with business goals.
Coding Chats Episode 79 - Richmond Alake, Director of AI Developer Experience at Oracle, joins John to discuss agent memory — how AI agents store, retrieve, and adapt to information. He argues that developers building memory on flat files are naively reinventing the database, and that once you factor in concurrency, security, and scalability, a proper database is inevitable. The conversation covers the full memory stack and how Oracle's AI database keeps embeddings and data together without shipping sensitive information to external providers.