Coding Chats

Coding Chats episode 66 - Alex Garella discusses the current state of the Rust job market, highlighting its mixed nature amidst broader software development trends. He emphasizes the importance of specific skills and industry experience, particularly in emerging technologies like data infrastructure. The impact of AI tools on software development and hiring practices is explored, along with strategies for breaking into the Rust market, including open source contributions and leveraging LinkedIn effectively.Chapters00:00 The Current State of the Rust Job Market03:15 Skills in Demand for Rust Developers05:46 Emerging Domains for Rust Applications08:44 Rust's Role in AI and Machine Learning11:38 The Evolution of Interview Processes14:30 Challenges in Hiring Rust Developers17:28 Navigating the Job Market as a New Rust Developer20:27 Leveraging LinkedIn for Job Opportunities23:21 Final Tips for Aspiring Rust DevelopersAlex's Links:https://rustjobs.dev/https://scalajobs.com/John's Links:John's LinkedIn: https://www.linkedin.com/in/johncrickett/John’s YouTube: https://www.youtube.com/@johncrickettJohn's Twitter: https://x.com/johncrickettJohn's Bluesky: https://bsky.app/profile/johncrickett.bsky.socialCheck 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.TakeawaysThe Rust job market is currently mixed, with both opportunities and challenges.Experience in specific industries is often more valuable than tool-specific knowledge.Emerging technologies, especially in data infrastructure, are driving demand for Rust.AI tools are changing the landscape of software development and hiring.Hiring managers need to adapt their interview processes to account for AI usage.Open source contributions can significantly enhance a developer's profile.Tailoring CVs too specifically can raise red flags for recruiters.Remote work options can broaden the talent pool for Rust developers.Developers should not limit themselves to Rust when seeking jobs.Persistence and passion for Rust can lead to job opportunities.

Coding Chats episode 65 - Mike Rispoli discusses his experience of building a Loom replacement through vibe coding, the economic implications of AI for small agencies, and the evolving landscape of software engineering. He emphasizes the importance of hand coding, the challenges of interviewing in the age of AI, and the necessity of clear requirements when working with AI tools. The discussion also touches on the future demand for software engineers and the role of UX in AI-generated code.Chapters00:00 Building a Loom Replacement in 30 Minutes03:40 The Challenges of SaaS Pricing Models06:29 AI's Impact on Small Businesses and Enterprises09:19 Interviewing in the Age of AI11:59 The Future of Coding and AI Integration26:45 The Importance of Clear Requirements28:31 Navigating AI in Development31:31 Feature Creep and Planning32:30 The Evolving Role of Engineers34:34 Workflow and Planning with AI38:45 Iterative Development and Feedback42:28 Leveraging AI for UX and Design45:59 The Future of Software EngineeringMike's Links:https://www.linkedin.com/in/michael-rispoli-ctohttps://x.com/michael_rispolihttps://www.instagram.com/mike_rispoli_ctohttps://michaelrispoli.com/John's Links:John's LinkedIn: https://www.linkedin.com/in/johncrickett/John’s YouTube: https://www.youtube.com/@johncrickettJohn's Twitter: https://x.com/johncrickettJohn's Bluesky: https://bsky.app/profile/johncrickett.bsky.socialCheck 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.TakeawaysMike built a Loom replacement in just 30 minutes using vibe coding.AI tools can significantly enhance productivity for software engineers.The SaaS pricing model can be complicated for small agencies.It's acceptable to pass on good candidates but not to hire the wrong ones.AI is likely to amplify the demand for software engineers rather than replace them.Feature creep is a common challenge in software development.Clear requirements are essential when working with AI tools.The future of software engineering is promising and exciting.AI can help engineers improve their design capabilities.Navigating the evolving landscape of software engineering requires adaptability.

Coding Chats episode 64 - Jakob Sagatowski discusses his unique collaboration with YouTuber Mark Rober to build a robot goalie that plays against Cristiano Ronaldo. He delves into the technical challenges of motion control and computer vision, the role of software engineers in industrial automation, and the importance of real-time systems. Jakob emphasizes the need for better software development practices in the industrial automation sector and shares insights on how aspiring engineers can break into this field.Chapters00:00 Introduction to the YouTube Collaboration Project03:22 Challenges in Motion Control and Computer Vision06:29 Trial and Error in Robotics Development09:15 Understanding Industrial Automation12:05 Programming Languages in Industrial Automation14:31 The Role of Real-Time Systems17:49 Constraints in Real-Time Programming21:22 Understanding Hardware Constraints in Industrial Automation24:46 The Role of PLCs in Industrial Control Systems28:45 Challenges in Software Development Practices35:32 Breaking into Industrial Automation CareersJakob's Links:Website: www.sagatowski.comPLC-programming course: https://www.youtube.com/playlist?list=PLimaF0nZKYHz3I3kFP4myaAYjmYk1SowOUnit testing framework for Beckhoff PLC’s (the course talks about this), if you want to apply TDD in industrial automation:www.tcunit.orghttps://github.com/tcunitJohn's Links:John's LinkedIn: https://www.linkedin.com/in/johncrickett/John’s YouTube: https://www.youtube.com/@johncrickettJohn's Twitter: https://x.com/johncrickettJohn's Bluesky: https://bsky.app/profile/johncrickett.bsky.socialCheck 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.TakeawaysJakob collaborated with Mark Rober on a robot goalie project.The project involved significant motion control and computer vision challenges.Real-time systems require deterministic execution within strict time frames.Industrial automation is evolving, integrating more software engineering practices.Software engineers are increasingly needed in industrial automation roles.The development environment in industrial automation is often proprietary and closed.AI's impact on industrial automation is still developing, with challenges in integration.Real-time programming constraints differ significantly from web development.PLCs are essential for controlling industrial processes and machinery.Aspiring engineers can learn about industrial automation through online resources and experimentation.

Coding Chats episode 63 - John Crickett and Rob Bowley discuss the evolving role of the CTO, emphasizing the importance of strategic leadership that integrates people, process, and technology. They explore the challenges and opportunities presented by AI and other technological trends, highlighting the need for adaptability and effective communication within leadership teams. The discussion also touches on the significance of assessing technology teams and strategies to ensure successful outcomes in software development and organizational growth.Chapters00:00 Introduction to the CTO Role02:49 The Misconceptions of the CTO Position05:05 The Importance of Feedback and Adaptability11:50 Navigating AI and Emerging Technologies19:08 Testing Hypotheses in Technology Implementation22:19 The Transformative Potential of AI in Software Engineering27:09 The Economic Impact of Generative AI29:24 Concerns Over AI Subscription Costs31:32 Adoption Challenges in Software Development35:14 Assessing Technology and Team Effectiveness38:44 The Future of Software Engineering and AI50:12 Exploring Related ContentRob's Links:Blog: https://blog.robbowley.net/LinkedIn: https://www.linkedin.com/in/robertbowley/Bluesky: https://bsky.app/profile/robbowley.netCompany URL: https://www.pragmaticpartners.co.uk/John's Links:John's LinkedIn: https://www.linkedin.com/in/johncrickett/John’s YouTube: https://www.youtube.com/@johncrickettJohn's Twitter: https://x.com/johncrickettJohn's Bluesky: https://bsky.app/profile/johncrickett.bsky.socialCheck 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.TakeawaysThe role of a CTO is a strategic leadership position that intersects people, process, and technology.CTOs should focus on understanding their strengths and how to leverage them within their organization.Effective communication and collaboration with the senior leadership team are crucial for a CTO's success.Many misconceptions about the CTO role stem from a focus on technical skills rather than strategic business outcomes.Adaptability and awareness of one's strengths are key attributes of good leadership.Feedback from peers and team members is essential for recognizing gaps in skills and performance.Learning from failure is a critical aspect of leadership growth.The integration of AI into products should be approached with caution and thorough exploration.Organizations must focus on proven, common technologies rather than chasing every new trend.The assessment of technology teams should prioritize people and their capabilities over just the technology itself.

Coding Chats episode 62 - John Crickett engages in a deep conversation with James about personal branding, building in public, and the challenges of launching a product. James shares his journey of using LinkedIn to build his personal brand, emphasizing the importance of transparency and community feedback in his projects. He recounts how his social network gained 20,000 users in the first 24 hours due to his public approach, which not only helped him secure jobs but also fostered a sense of community around his work. The discussion also touches on the significance of mental health awareness and the need for open conversations in the workplace, particularly in the tech industry.As they delve into James's latest project, Bearly Fit, they explore the balance between creating a minimum viable product and ensuring quality. James reflects on the expectations that come with building in public and how he has navigated the challenges of app development while maintaining a connection with his audience. The conversation wraps up with insights on the role of AI in coding and the importance of mentoring junior developers, highlighting the need for a supportive environment in tech.Chapters00:00 The Power of Personal Branding06:35 Agility in Development: Lessons Learned18:29 Building in Public: Success and Challenges26:08 Streaming and Job Search: A Double-Edged Sword35:36 The Importance of Mentoring New Developers40:22 Building in Public: The Journey of Barely Fit52:58 Challenges and Expectations in App Development58:54 Leveraging AI in Development01:05:39 Final Thoughts and Future Plans01:06:06 Exploring Related ContentJames's Links:https://linktr.ee/mahybehttps://bearly.fitJohn's Links:John's LinkedIn: https://www.linkedin.com/in/johncrickett/John’s YouTube: https://www.youtube.com/@johncrickettJohn's Twitter: https://x.com/johncrickettJohn's Bluesky: https://bsky.app/profile/johncrickett.bsky.socialCheck 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.TakeawaysBuilding in public can lead to unexpected success.Transparency in struggles fosters community support.Personal branding is crucial for career advancement.Quality matters in app development, especially when building in public.Mentoring junior developers is an investment in the future.

Coding Chats episode 61 - John Crickett interviews Austen about his new book and the significance of behavioural interviews in the hiring process, especially in today's competitive job market. Austen shares insights on what interviewers look for, how to tailor preparation for specific companies, and the importance of storytelling in interviews. He emphasizes the impact of AI on the interview process and discusses how candidates can effectively present their experiences, particularly in conflict resolution scenarios. The conversation also covers the different expectations for candidates at various career stages and the importance of preparation and practice in mastering behavioural interviews.Chapters00:00 The Importance of Behavioral Interviews02:43 What Interviewers Look For05:32 Understanding Company Expectations07:48 Austen's Background and Expertise09:59 The Impact of AI on Interviews12:10 Behavioral Interviews Beyond Big Tech14:11 Crafting Your Introduction18:55 Selecting Stories for Interviews24:32 Creating Compelling Interview Stories28:38 The Difference Between Junior and Senior Engineers29:50 Crafting Compelling Stories for Interviews31:28 Timing and Length of Stories in Interviews33:34 Selecting the Right Story for the Interview37:05 The Importance of Scope and Relevance in Storytelling37:52 Using the Menu Technique for Story Selection40:37 Enhancing Conflict Resolution Stories43:48 The Drama in Conflict Resolution48:12 Improving Conflict Resolution Narratives55:00 The Role of Escalation in Conflict Resolution58:11 The Big Three Questions in Behavioral Interviews59:54 Understanding Interview Dynamics01:03:08 The Importance of Asking Questions01:06:56 Feedback Loops in Behavioral Interviews01:12:04 Navigating Different Career Stages01:17:52 Adapting Stories for Different Organizations01:23:02 Leveraging Personal Projects in Interviews01:24:41 Key Takeaways for Interview SuccessAusten's Links:https://thebehavioral.substack.com/https://www.amazon.com/dp/B0G6CM9T87John's Links:John's LinkedIn: https://www.linkedin.com/in/johncrickett/John’s YouTube: https://www.youtube.com/@johncrickettJohn's Twitter: https://x.com/johncrickettJohn's Bluesky: https://bsky.app/profile/johncrickett.bsky.socialCheck 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.TakeawaysBehavioral interviews are crucial for differentiating candidates in a competitive job market.Understanding what interviewers are looking for can significantly improve your chances of success.Tailoring your preparation to the specific company and role is essential.Your past experiences and stories are likely more valuable than you think.Practice and preparation are key to performing well in interviews.

Coding Chats episode 60 - John Crickett and Paul discuss the transformative impact of AI on software engineering, exploring topics such as spec-driven development, the importance of small batches, and the challenges of requirements gathering. They delve into the evolving role of AI tools, the need for effective communication, and the balance between productivity and code quality. The discussion also touches on the future of AI in development, the significance of ownership in coding, and the potential for specialized AI agents to enhance workflows. Paul shares valuable tips for leveraging AI in software engineering, emphasizing the importance of joy, working in small units, and maintaining humility in the face of rapid technological change.Chapters00:00 AI in Software Engineering: A New Era03:36 The Revelation of Prompt-Driven Development06:08 Spec-Driven Development vs. Waterfall09:16 The Importance of Small Batches in AI Development12:05 Ownership and Responsibility in AI-Generated Code14:57 The Challenges of Outsourcing and Communication in Software Development20:15 The Future of Programming and Communication23:38 AI Tools and Upstream Bottlenecks27:18 Understanding JetBrains' AI Integration31:40 User Experience and AI Interaction35:42 Opinionated Workflows in Software Development37:24 Finding Joy in AI-Assisted EngineeringPaul's Links:https://buildermethods.com/agent-osJohn's Links:John's LinkedIn: https://www.linkedin.com/in/johncrickett/John’s YouTube: https://www.youtube.com/@johncrickettJohn's Twitter: https://x.com/johncrickettJohn's Bluesky: https://bsky.app/profile/johncrickett.bsky.socialCheck 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.TakeawaysAI is revolutionizing software engineering practices.Spec-driven development formalizes the way we instruct AI agents.Small batches improve productivity and maintain context.Ownership of code is crucial for long-term success.Quality of code generated by AI is more important than quantity.Effective communication is key in AI-assisted development.Specialized AI agents will enhance the development process.JetBrains is evolving its tools to integrate AI effectively.Developers should find joy in their work, even with AI assistance.Humility is essential as we navigate the future of AI in programming.

Coding Chats episode 59 - Josh discusses the AI agent framework Rig, its functionalities, and the benefits of using Rust for its implementation. He explains the concept of agents and embeddings, their applications, and the importance of managing context windows in AI models. Josh shares his journey of learning Rust, transitioning from a technical content writer to a co-maintainer of Rig, and the challenges faced while building a coding agent. He emphasizes effective prompting strategies and the importance of concise communication with AI models. The conversation concludes with insights on contributing to Rig and the future of AI frameworks.Chapters00:00 Introduction to Rig and AI Frameworks02:56 Understanding Agents and Embeddings05:24 Use Cases for Embeddings and Context Management07:53 Benefits of Using Rig in Rust10:10 Learning Rust and Overcoming Challenges12:56 Transitioning to Rig and AI Focus15:21 Building a Coding Agent: Challenges and Insights17:45 Prompting Techniques and Best Practices20:06 Contributing to Rig and Community Engagement22:49 Final Thoughts and Future DirectionsJosh's Links:https://github.com/0xPlaygrounds/righttps://www.rustnationuk.com/speaker/joshua-mohttps://www.linkedin.com/in/joshua-mo-4146aa220/John's Links:John's LinkedIn: https://www.linkedin.com/in/johncrickett/John’s YouTube: https://www.youtube.com/@johncrickettJohn's Twitter: https://x.com/johncrickettJohn's Bluesky: https://bsky.app/profile/johncrickett.bsky.socialCheck 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.TakeawaysRig is an AI agent framework that simplifies AI integration.Agents in AI are often misunderstood due to marketing hype.Embeddings serve as data representations for various applications.Retrieval augmented generation is a common use case for embeddings.Managing the context window is crucial for effective AI performance.Using Rust for Rig provides type safety and performance benefits.Learning Rust can be challenging but rewarding with the right approach.Josh transitioned from content writing to engineering at Rig.Building a coding agent revealed the complexities of AI.Concise prompts are essential to avoid overwhelming AI models.

In this special holiday episode of Coding Chats, John Crickett answers audience questions about software engineering careers, the impact of AI, programming languages, and the importance of leadership. He discusses how to rebuild an engineering career, the significance of meaningful projects, and the readiness of self-taught developers. The conversation also touches on insights gained from hosting the podcast and the evolving landscape of software development.Chapters00:00 Introduction to the Coding Chats Holiday Special00:22 Rebuilding an Engineering Career in 202501:01 The Future of Software Engineering with AI01:27 Learning Programming: Starting Points and Languages02:27 Breaking the No Experience Loop for Developers04:17 Meaningful Experience: Projects and Contributions05:02 Self-Taught Developers: Readiness and Opportunities06:07 Qualities of a Good Software Engineering Leader06:52 Insights from 18 Months of Coding Chats07:43 Architecture as a Strategic Concern in EngineeringJohn's Links:John's LinkedIn: https://www.linkedin.com/in/johncrickett/John’s YouTube: https://www.youtube.com/@johncrickettJohn's Twitter: https://x.com/johncrickettJohn's Bluesky: https://bsky.app/profile/johncrickett.bsky.socialCheck 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.TakeawaysLeverage AI to find answers quicker than before.Reading and curiosity are key habits for growth.All parts of software engineering will survive AI advancements.Focus on learning computer science fundamentals first.Choose programming languages based on your interests.Building personal projects can help you get noticed.Self-taught developers can be just as capable as those with degrees.Good leadership adapts to the situation and team needs.The software development field is diverse and evolving.Architecture should be treated as a strategic concern.

Coding Chats episode 58 - John Crickett and Melinda Fekete delve into the concept of feature ops, emphasizing the importance of managing code in production effectively. They discuss feature flags as a mechanism for safe testing and releasing of code, the challenges of managing feature flags, and the significance of user feedback in software development. The conversation also touches on deployment strategies like canary releases, learning from recent outages, and the benefits of testing in production. Additionally, they explore the role of feature flag providers and the trade-offs associated with adopting feature flags in software projects.Chapters00:00 Introduction to Feature Ops02:46 Managing Feature Flags Effectively07:41 Deployment Strategies: Canary Releases and Gradual Rollouts12:23 The Importance of Dogfooding and User Feedback15:05 Learning from Recent Outages19:13 Testing in Production and Its Benefits21:51 Managing Feature Flags at Scale27:01 Feature Flag Providers and Their Benefits30:50 Involving Product Teams in Feature Flag Management31:45 Trade-offs and Downsides of Feature Flags39:35 Exploring Related ContentMelinda's Links:A guide on working with feature flags in code: https://docs.getunleash.io/guides/manage-feature-flags-in-codeOpen-source repo: https://github.com/Unleash/unleashJohn's Links:John's LinkedIn: https://www.linkedin.com/in/johncrickett/John’s YouTube: https://www.youtube.com/@johncrickettJohn's Twitter: https://x.com/johncrickettJohn's Bluesky: https://bsky.app/profile/johncrickett.bsky.socialCheck 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.TakeawaysFeature ops focuses on managing code in production effectively.Feature flags allow for safe testing and releasing of code without redeployment.Managing the lifecycle of feature flags is crucial for maintenance.Canary releases and gradual rollouts help mitigate risks during deployment.User feedback is essential for improving software products.Recent outages highlight the need for better feature management practices.Testing in production can catch issues that staging environments may miss.Feature flag providers offer tools for managing flags at scale.Trade-offs exist when adopting feature flags, especially for smaller projects.Effective management of feature flags can empower teams and improve deployment speed.

Coding Chats episode 57 - Owain Lewis and John Crickett explore the role of AI in software engineering, discussing the integration of AI into production systems and the challenges faced by AI engineers. They delve into the nuances of AI application, from building scalable systems to the importance of human oversight in AI-driven workflows.Chapters00:00 Defining the Role of AI Engineer03:13 Exploring Large Language Models (LLMs)06:15 Use Cases for LLMs in Business09:22 The Non-Deterministic Nature of AI12:12 AI in Software Engineering: The Future15:11 The Role of AI in Code Review17:53 The Bottleneck of Requirements Gathering20:38 Leveraging AI Throughout the Software Lifecycle29:53 Leveraging AI for Efficient Documentation30:47 AI in API Design and Review32:22 Spectrum Driven Development with AI34:06 The Role of Requirements in Software Engineering40:05 The Future of Programming Languages and AI49:54 Understanding Context and Prompt Engineering56:38 Exploring Related ContentOwain's Links:Substack: https://newsletter.owainlewis.com/subscribe AI Engineer: https://skool.com/aiengineerJohn's Links:John's LinkedIn: https://www.linkedin.com/in/johncrickett/John’s YouTube: https://www.youtube.com/@johncrickettJohn's Twitter: https://x.com/johncrickettJohn's Bluesky: https://bsky.app/profile/johncrickett.bsky.socialCheck 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.TakeawaysAI engineering involves building software with AI, focusing on production systems.AI engineers bridge the gap between AI model builders and software developers.Understanding AI's unique paradigm is crucial for effective system architecture.AI should be used minimally and where it makes sense, not everywhere.Human oversight is essential in AI-driven workflows to ensure reliability.Large language models (LLMs) are a significant focus in current AI trends.AI can enhance business processes through automation and natural language interfaces.AI's role in software engineering includes improving code quality and efficiency.AI tools can amplify both good and bad engineering practices.Experimentation and building real projects are key to learning AI engineering.

Coding Chats episode 56 - Paul Grenyer discusses his journey to writing a book on team leadership, sharing insights on the differences between leadership and management, common mistakes new leaders make, the importance of delegation, and building trust within teams. He emphasizes the need for curiosity in understanding both technical and business domains, and reflects on the role of AI in software development. The discussion culminates in insights from his book, which aims to guide new leaders in navigating their roles effectively.Chapters00:00 The Journey to Team Leadership08:44 Leadership vs Management10:33 Common Mistakes of New Leaders15:58 The Importance of Delegation19:46 Curiosity in Leadership22:33 Insights from the Book27:57 The Role of Technical Skills in Leadership31:58 The Impact of AI on Software EngineeringPaul's Links:Paul's website: https://paulgrenyer.com/John's Links:John's LinkedIn: https://www.linkedin.com/in/johncrickett/John’s YouTube: https://www.youtube.com/@johncrickettJohn's Twitter: https://x.com/johncrickettJohn's Bluesky: https://bsky.app/profile/johncrickett.bsky.socialCheck 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.TakeawaysLetting go of doing the work is crucial for leaders.Listening to your team is essential for effective leadership.Delegation is often the hardest skill for new leaders to master.Building trust requires admitting mistakes and being approachable.Curiosity about team members' experiences can lead to better solutions.Technical knowledge helps leaders mediate and understand team dynamics.AI can enhance productivity but requires careful implementation.Leadership is about guiding a team towards a common goal.Understanding the business domain is vital for effective leadership.Encouraging a fun and open team culture fosters collaboration.

Coding Chats episode 55 - Emma Nedelcu discusses her experience managing teams that transitioned to Rust at Amazon Prime Video. She highlights the reasons for choosing Rust, including its performance and safety features, and the challenges faced during the transition from JavaScript. Emma explains the importance of over-the-air updates, device constraints, and effective onboarding strategies for engineers. The conversation also covers testing strategies, managing technical debt, and hiring practices for Rust teams, emphasizing the need for a mindset focused on problem-solving and adaptability.Chapters00:00 Introduction to Rust and Its Adoption03:49 Performance Gains with Rust06:37 Challenges of Over-the-Air Updates09:36 Onboarding Developers to Rust12:33 Team Collaboration and Trust14:53 Testing Strategies for Rust Applications17:38 Trade-offs and Considerations with Rust20:13 Hiring and Team Building for Rust23:02 Advice for Organizations Considering Rust26:00 Managing Technical Debt in Rust28:48 Conclusion and Final Thoughts33:52 Exploring Related ContentLINKSEmma's Linkshttps://www.linkedin.com/in/emmanedelcu/John's Links:John's LinkedIn: https://www.linkedin.com/in/johncrickett/John’s YouTube: https://www.youtube.com/@johncrickettJohn's Twitter: https://x.com/johncrickettJohn's Bluesky: https://bsky.app/profile/johncrickett.bsky.socialCheck 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.TakeawaysRust was chosen for its performance and safety guarantees.Transitioning from JavaScript to Rust involves a steep learning curve.Over-the-air updates are crucial for device management.Device constraints significantly impact application performance.Onboarding to Rust can take about three months for JavaScript developers.Building trust within teams is essential for fast-paced development.Testing strategies must be robust to handle diverse devices.Rust's compile-time checks require strict runtime discipline.Compiling for WebAssembly requires careful optimization to manage bundle size.The Rust ecosystem is maturing but still evolving.Organizations should engage with the Rust community for better integration.Prototyping can effectively demonstrate Rust's potential to stakeholders.Managing technical debt in Rust involves understanding complexity depth.Hiring for mindset and adaptability is more important than experience.Ideal Rust engineers should have a deep understanding of low-level systems.Candidates should demonstrate initiative and impact in their projects.

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.Chapters00:00 The Importance of Soft Skills in Engineering03:14 Bridging the Gap: Engineers and Customer Interaction06:26 Nature vs. Nurture: The Art of Asking Questions09:06 Effective Communication: How to Ask the Right Questions12:06 Understanding Context: The Key to Effective Dialogue14:53 Navigating Emotional Reactions in Communication17:36 Feedback and Conflict Resolution: Building Better Relationships20:57 The Efficiency of Communication in Engineering23:32 The Role of Emotions in Engineering26:38 Team Dynamics: The Myth of the 10x Developer29:08 The Importance of Communication in Engineering31:29 Empowering Teams to Reduce Meetings34:40 Communicating with Impact38:21 Building Trust with Non-Technical Stakeholders42:11 Creating Meaningful Connections48:53 Owning Your Confidence as an EngineerNikki'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/@johncrickettJohn's Twitter: https://x.com/johncrickettJohn's Bluesky: https://bsky.app/profile/johncrickett.bsky.socialCheck 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.TakeawaysEngineering 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.

Coding Chats episode 53 - John Crickett and Mary Fidler discuss the evolving landscape of job applications, focusing on common CV mistakes, the importance of showcasing skills and achievements, and the role of AI in recruitment. They explore the relevance of cover letters, salary transparency, and the current state of the job market, including signs of recovery. Mary emphasizes the significance of LinkedIn for job seekers and shares insights on adapting to the changing recruitment landscape, particularly for contractors.Chapters00:00 Introduction to Recruitment Challenges03:37 Common CV Mistakes in Job Applications09:19 The Evolution of Job Market Dynamics14:56 Leveraging AI in Job Hunting18:34 The Role of Cover Letters in Modern Applications23:13 Understanding Salary Expectations and Market Trends24:28 Market Recovery and Hiring Trends28:01 The Impact of AI on Employment28:53 Leveraging LinkedIn for Job Seekers38:14 Navigating Recruitment in a Changing Market40:52 The Rise of Project-Based Work46:34 Final Tips for Job SeekersLINKSMary's LinkedIn - https://www.linkedin.com/in/mary-fidler/Mary's Career Page https://trusttechrecruitment.zohorecruit.eu/jobs/Careers John's Links:John's LinkedIn: https://www.linkedin.com/in/johncrickett/John’s YouTube: https://www.youtube.com/@johncrickettJohn's Twitter: https://x.com/johncrickettJohn's Bluesky: https://bsky.app/profile/johncrickett.bsky.socialCheck 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.TakeawaysOne page CVs are a common mistake.Highlight achievements over duties in CVs.AI tools are increasingly important for developers.Cover letters are often unnecessary if CVs are strong.Salary transparency can build trust between candidates and recruiters.The job market is showing signs of recovery.LinkedIn is essential for job seekers to stand out.Contractors can provide cost-effective solutions for companies.Personal branding on LinkedIn can lead to job opportunities.Networking and asking for impact details can enhance CVs.

Coding Chats episode 52 - Robert Balicki discusses Isograph, an opinionated framework designed to simplify the development of data-driven applications, particularly with GraphQL and React. He explains the challenges faced in web development, such as over-fetching data and network waterfalls, and how Isograph addresses these issues by allowing developers to focus on specific components and their data needs. The discussion also covers the technical foundation of Isograph, built using Rust, and the challenges of compiler development. Robert emphasizes the importance of testing, CI/CD integration, and the potential for Isograph to scale effectively in large projects. He invites developers to get involved in the project and contribute to its growth.Chapters00:00 Introduction to Isograph05:11 Understanding the Problem Isograph Solves09:57 The Concept of Opinionated Frameworks13:40 Exploring Network Waterfalls16:43 Testing and CI/CD Integration20:49 Scaling with Monorepos and Integration27:57 Future Vision for Isograph28:04 Understanding Isograph's Runtime and Compiler29:40 The Influence of Rust in Compiler Development32:04 The Challenges of Building a Compiler35:53 Transitioning from Batch to Incremental Compilation45:28 Leveraging Rust for Enhanced Developer Experience52:55 Community Engagement and Future of Isograph56:32 Exploring Related ContentLINKSRobert's Links:Isograph: http://isograph.dev/John's Links:John's LinkedIn: https://www.linkedin.com/in/johncrickett/John’s YouTube: https://www.youtube.com/@johncrickettJohn's Twitter: https://x.com/johncrickettJohn's Bluesky: https://bsky.app/profile/johncrickett.bsky.socialCheck 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.TakeawaysIsograph simplifies building data-driven applications.The framework is opinionated, promoting best practices.Network waterfalls can degrade user experience.Isograph allows for precise data fetching.Testing is a key focus in Isograph's development.Rust provides safety and performance benefits.The framework aims to support SQL backends in the future.Isograph encourages a full-stack development approach.Community involvement is welcomed through Discord.The developer experience with Isograph is superior to other frameworks.

Coding Chats episode 51 - Shane Harger shares her unique career journey from web development and graphic design to firefighting and back to tech, emphasizing the importance of pair programming, incident management lessons, and the evolving role of AI in software development. She discusses the significance of DevOps and platform engineering in enhancing team collaboration and efficiency, while also highlighting the value of junior developers in fostering a learning environment within teams.Chapters00:00 Shane Harger's Unique Career Journey05:32 Transitioning from Firefighting to Tech10:12 The Importance of Pair Programming15:01 Lessons from Incident Management20:02 DevOps and Platform Engineering Insights27:44 The Dynamics of Code Review and Pair Programming29:54 AI as a Partner in Programming34:03 Key Learnings from AI Pair Programming Experiments45:37 The Importance of Diverse Pairing in Development TeamsShane's links:https://www.linkedin.com/in/shaneharger/John's Links:John's LinkedIn: https://www.linkedin.com/in/johncrickett/John’s YouTube: https://www.youtube.com/@johncrickettJohn's Twitter: https://x.com/johncrickettJohn's Bluesky: https://bsky.app/profile/johncrickett.bsky.socialCheck 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.TakeawaysShane's career spans web development, firefighting, and consulting.Firefighting provided unexpected tech opportunities in incident management.Pair programming fosters camaraderie and knowledge sharing.DevOps emphasizes ownership and collaboration in software development.AI can assist in coding but lacks the human element of teamwork.Juniors bring fresh perspectives and questions that benefit teams.Effective incident management requires calmness and basic troubleshooting skills.Automation in DevOps enhances response times and reduces handovers.Product thinking is essential for infrastructure teams to meet customer needs.The transition from POC to production can be challenging without clear requirements.

Coding Chats episode 50 - Lou Franco discusses the concept of technical debt, its implications for software development, and the importance of quantifying it. He emphasizes that technical debt is not just a financial metaphor but a real issue affecting developer productivity and team dynamics. The discussion also covers the role of managers in understanding and addressing technical debt, the importance of metrics, and the eight questions that can help teams evaluate their technical debt. Additionally, the conversation touches on the impact of AI on technical debt management, highlighting both its potential benefits and challenges.Chapters00:00 Understanding Technical Debt03:17 The Financial Metaphor of Tech Debt06:04 Defining Technical Debt: Internal vs External Effects08:59 The Role of Developer Productivity12:05 The Team Responsibility of Technical Debt14:51 Why Managers Should Care About Tech Debt18:05 Quantifying Technical Debt for Visibility20:57 Improving Developer Productivity23:43 Communicating Tech Debt to Executives26:41 Understanding Technical Debt and Its Management36:37 The Eight Questions for Managing Technical Debt46:29 AI's Role in Technical Debt: A Double-Edged SwordLou's Links:LinkedIn: https://www.linkedin.com/in/loufranco/Book: https://loufranco.com/tech-debt-bookJohn's Links:John's LinkedIn: https://www.linkedin.com/in/johncrickett/John’s YouTube: https://www.youtube.com/@johncrickettJohn's Twitter: https://x.com/johncrickettJohn's Bluesky: https://bsky.app/profile/johncrickett.bsky.socialCheck 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.TakeawaysTechnical debt is often misunderstood and miscommunicated.The financial metaphor of technical debt can be misleading.Technical debt can arise from changing technologies, not just poor choices.Developers experience anxiety due to technical debt affecting estimates.Managers need to understand the visible effects of technical debt.Quantifying technical debt helps in communicating its impact.The eight questions framework aids in evaluating technical debt.AI can assist in managing technical debt but requires careful oversight.Collaboration with other teams can provide valuable insights into technical debt.Technical debt should be viewed as a team responsibility, not just an individual issue.

Coding Chats episode 49 - John Crickett and Kev Milne delve into the critical realm of cybersecurity, exploring its various facets from social engineering to the importance of penetration testing. They discuss the evolution of attacks, the role of AI, and the significance of mainframes in modern security. The conversation also highlights the career paths in cybersecurity and the necessity for continuous investment in security measures to protect digital assets.Chapters00:00 Understanding Cybersecurity03:38 The Evolution of Attacks: Physical vs. Digital06:18 Social Engineering: The Art of Deception09:15 The Importance of Penetration Testing12:02 Career Paths in Cybersecurity14:49 The Diverse Landscape of Cybersecurity17:56 The Necessity of Ongoing Security Measures20:34 The Cost of Neglecting Cybersecurity25:48 The Evolution of Wi-Fi Security27:04 Mainframes: The Misunderstood Giants28:15 Mainframe Security: Myths and Realities30:02 The Challenge of Legacy Code32:20 Balancing Security and Functionality34:12 Defense in Depth: A Security Strategy35:35 AI's Role in Cybersecurity37:50 The Threat Landscape: Script Kiddies and Beyond38:34 Training the Next Generation of Cybersecurity Experts41:36 The Importance of Conferences in CybersecurityKev's Links:LinkedIn: https://www.linkedin.com/in/kevinmilne/Website where folks can obtain the Mainframe Offensive Security Tester course, download the Gibson Mainframe Simulator or purchase the Cyber Coach labs: https://offensivesec.orgTry out some free labs Kev has created: https://cyber-coach-labs-bd010da0.base44.app/FreeLabsJohn's Links:John's LinkedIn: https://www.linkedin.com/in/johncrickett/John’s YouTube: https://www.youtube.com/@johncrickettJohn's Twitter: https://x.com/johncrickettJohn's Bluesky: https://bsky.app/profile/johncrickett.bsky.socialCheck 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.TakeawaysCybersecurity is essential for protecting digital assets.Social engineering remains a significant threat today.Red teaming involves advanced penetration testing techniques.Understanding networking is crucial for aspiring penetration testers.Mainframes are still vital for processing transactions.AI can both aid and complicate cybersecurity efforts.Continuous investment in cybersecurity is necessary for businesses.Penetration testing should be a standard practice for all companies.Security requires a layered defense approach.Conferences are valuable for staying updated in cybersecurity.

Coding Chats episode 48 - John Crickett and Gilad Naor explore the differences between working at startups and big tech companies, discussing the pros and cons of each environment. They delve into career growth, the importance of mentorship, and the balance between specialization and generalization in tech careers. The discussion also covers the management track versus individual contributor roles, the role of managers in creating positive change, and the significance of interview preparation. Additionally, they highlight the value of side projects and the necessity for managers to build empathy through understanding various roles within their organizations. The conversation concludes with advice on taking ownership of one's career and the importance of continuous personal development.Chapters00:00 Startups vs. Big Tech: A Comparative Overview03:19 Navigating Career Growth in Tech06:08 The Reality of Big Tech Work09:06 Specialization vs. Generalization in Tech Careers11:39 The Management Track: Leadership vs. Management14:28 Creating Positive Change as a Manager17:14 Interview Preparation for Managers20:33 Choosing the Right Stories for Interviews26:59 Navigating Conflict in Technical Leadership29:12 Addressing Gaps in Management Experience32:15 Interview Strategies for Senior Roles35:17 Demonstrating Depth of Experience in Interviews38:52 The Role of Side Projects in Personal Development42:02 The Importance of Technical Empathy in Management47:32 Taking Ownership of Your CareerGilad's Links:Gilad's LinkedIn: https://www.linkedin.com/in/giladnaorGilad's Website: https://managementdeltas.com/ John's Links:John's LinkedIn: https://www.linkedin.com/in/johncrickett/John’s YouTube: https://www.youtube.com/@johncrickettJohn's Twitter: https://x.com/johncrickettJohn's Bluesky: https://bsky.app/profile/johncrickett.bsky.socialCheck 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.TakeawaysWorking at startups allows for a broader range of experiences.Big tech offers more mentorship opportunities for career growth.The term 'startup' can encompass a wide range of company sizes and structures.Career growth in tech often requires navigating internal mobility.Specialization can provide a competitive advantage in tech careers.Management and leadership are distinct roles that require different skill sets.Interview preparation is crucial for both managers and individual contributors.Building empathy as a manager involves understanding various roles in the organization.Side projects can help maintain technical skills and foster personal development.Taking ownership of your career is essential for success.