Podcast appearances and mentions of gene kim

We sit down with Pastor Dr. Gene Kim of REAL Bible Believers to decode the rapid, chaotic shifts reshaping our world. We bypass the secular media panic and dive straight into the King James Bible to uncover what is really happening behind the scenes.Dr. Kim breaks down the exact dispensational timeline of current events, exposing how modern tech and geopolitical chess pieces are aligning perfectly with scripture.

https://anchorbaptist1611.com/

In this episode of The IT Experts Podcast, we explore what it really takes for MSPs to build a strong foundation in cybersecurity, compliance, and resilience in a world where risk is constantly evolving. In this special roundtable session, I am joined by Neil Smith, Gene Kim, and David Clarke, who each bring deep, practical experience from the front line of cybersecurity and compliance within the MSP space.     You will hear how the role of the MSP has shifted from simply managing IT systems to becoming a central part of how businesses manage risk. As Neil Smith shares from his own journey, the demand from clients has changed significantly. Businesses are no longer asking for technical support alone. They want reassurance that they are protected, aligned with standards, and prepared for whatever may come next. This is where cybersecurity, compliance, and resilience come together as a core offering rather than an add on.     Gene Kim expands on this by highlighting how trust is now directly linked to revenue. Clients expect MSPs to provide clear visibility, consistent reporting, and confidence that systems are secure and recoverable. This is not about tools alone. It is about outcomes. MSPs are now expected to help clients prove they are operating securely, not only for their own peace of mind, though also for insurers, auditors, and stakeholders.     A strong theme throughout the conversation is education. As Neil Smith explains, many businesses still believe they are not a target or that basic protection is enough. The role of the MSP is to guide clients through understanding their risks in a calm and structured way. This is not about creating fear. It is about building awareness and helping clients make informed decisions that support long term stability.     David Clarke brings a valuable perspective on compliance and governance. He highlights how frameworks such as GDPR and Cyber Essentials provide a strong foundation, though they are not a one-off exercise. Cybersecurity, compliance, and resilience require continuous attention. It is similar to securing your home. You do not lock the door once and forget about it. You maintain awareness and take responsibility over time.     The conversation also explores the importance of clearly defined responsibility. MSPs play a critical role in implementing and managing systems, though the ownership of risk always sits with the client. David Clarke reinforces that understanding who owns the risk leads to stronger, more productive conversations. When this is clear, businesses can make better decisions and avoid confusion during critical moments.     Supply chain security is another key focus. With MSPs relying on a growing number of vendors and tools, every decision introduces potential exposure. Gene Kim and Neil Smith both emphasise the need for transparency, trust, and careful evaluation when selecting partners. It is not only about functionality. It is about reliability, communication, and how those vendors respond when something goes wrong.     When the discussion moves to incident response, the tone becomes even more practical. Every MSP needs a clear and well understood plan. David Clarke explains the importance of rapid escalation, strong leadership, and access to the right expertise at the right time. Decisions need to be made quickly, often with incomplete information, and preparation makes all the difference.     Neil Smith adds that these conversations should happen before an incident occurs. Working through scenarios with clients, even in a simple tabletop format, can highlight gaps and build confidence. Gene Kim reinforces this by stressing the importance of having systems that can recover quickly and maintain control during an incident.     Resilience is the thread that connects everything discussed in this episode. It is not enough to reduce risk. Businesses need to be able to continue operating when challenges arise. Cybersecurity, compliance, and resilience work together to create that outcome. When done well, they provide stability, confidence, and a platform for growth.     This episode makes one thing very clear. MSPs who fully embrace cybersecurity, compliance, and resilience will stand out. As Neil Smith demonstrates through his own positioning, this creates a powerful advantage in the market. It builds trust, strengthens relationships, and supports long term success.     If you want to position your MSP as a trusted advisor and create a more secure, scalable business, this episode offers clear and practical direction. Focus on the fundamentals, build strong frameworks, educate your clients, and keep refining your approach. Over time, this creates a business that not only protects clients, though also grows with confidence.       Connect with Neil Smith through LinkedIn HERE.  Connect with Gene Kim through LinkedIn HERE.  Connect with David Clarke through LinkedIn HERE.    Make sure to check out our Ultimate MSP Growth Guide, a free guide that walks you through a proven process to take your MSP from stuck to scalable, without working even more hours. It's 44 pages rammed with advice, insights and inspiration to help you decide what support is available to you now if you want to grow and scale your business. Click HERE to get your copy.    Connect on LinkedIn HERE with Ian and also with Stuart by clicking this LINK    And when you're ready to take the next step in growing your MSP, come and take the Scale with Confidence MSP Mastery Quiz. In just three minutes, you'll get a 360-degree scan of your MSP and identify the one or two tactics that could help you find more time, engage & align your people and generate more leads.    If you're serious about growth and want to explore what this could look like for your MSP, you can book a Right Fit Clarity Call with us HERE.  OR   To join our amazing Facebook Group of over 400 MSPs where we are helping you Scale Up with Confidence, then click HERE  Until next time, look after yourself and I'll catch up with you soon!   

This episode with Joachim Hill-Grannec asks: How do platforms bloat, and how do you keep them simple and fast with trunk-based dev and small batches? Which metrics prove it works—cycle time, uptime, or developer experience? Can security act as a partner that speeds delivery instead of a gate?   We are always happy to answer any questions, hear suggestions for new episodes, or hear from you, our listeners. DevSecOps Talks podcast LinkedIn page DevSecOps Talks podcast website DevSecOps Talks podcast YouTube channel Summary In this episode of DevSecOps Talks, Mattias speaks with Joachim Hill-Grannec, co-founder of Peltek, a boutique consulting firm specializing in high-availability, cloud-native infrastructure. Following up on a previous episode where Steve discussed cleaning up bloated platforms, Mattias and Joachim dig into why platforms get bloated in the first place and how platform teams should think when building from scratch. Their conversation spans cloud provider preferences, the primacy of cycle time, the danger of adding process in response to failure, and a strong argument for treating security and quality as enablers rather than gatekeepers. Key Topics Platform Teams Should Serve Delivery Teams Joachim frames the core question of platform engineering around who the platform is actually for. His answer is clear: the delivery teams are the client. Platform engineers should focus on making it easier for developers to ship products, not on making their own work more convenient. He connects this directly to platform bloat. In his experience, many platforms grow uncontrollably because platform engineers keep adding tools that help the platform team itself: "Look, I spent this week to make my job this much faster." But Joachim pushes back on this instinct — the platform team is an amplifier for the organization, and every addition should be evaluated by whether it helps a product get to production faster and gives developers better visibility into what they are working on. Choosing a Cloud Provider: Preferences vs. Reality The conversation briefly explores cloud provider choices. Joachim says GCP is his personal favorite from a developer perspective because of cleaner APIs and faster response times, though he acknowledges Google's tendency to discontinue services unexpectedly. He describes AWS as the market workhorse — mature, solid, and widely adopted, comparing it to "the Java of the land." Azure gets the coldest reception; both acknowledge it has improved over time, but Joachim says he still struggles whenever he is forced to use it. They observe that cloud choices are frequently made outside engineering. Finance teams, investors, and existing enterprise agreements often drive the decision more than technical fit. Joachim notes a common pairing: organizations using Google Workspace for productivity but AWS for cloud infrastructure, partly because the Entra ID (formerly Azure AD) integration with AWS Identity Center works more smoothly via SCIM than the equivalent Google Workspace setup, which requires a Lambda function to sync groups. Measuring Platform Success: Cycle Time Above All When Mattias asks how a team can tell whether a platform is actually successful, Joachim separates subjective and objective measures. On the subjective side, he points to developer happiness and developer experience (DX). Feedback from delivery teams matters, even if surveys are imperfect. On the objective side, his favorite metric is cycle time — specifically, the time from when code is ready to when it reaches production. He also mentions uptime and availability, but keeps returning to cycle time as the clearest indicator that a platform is helping teams deliver faster. This aligns with DORA research, which has consistently shown that deployment frequency and lead time for changes are strong predictors of overall software delivery performance. Start With a Highway to Production A major theme of the episode is that platforms should begin with the shortest possible route to production. Mattias calls this a "highway to production," and Joachim strongly agrees. For greenfield projects, Joachim favors extremely fast delivery at first — commit goes to production, commit goes to production — even with minimal process. As usage and risk increase, teams can gradually add automation, testing, and safeguards. The critical thing is to keep the flow and then ask "how do we make those steps faster?" as you add them, rather than letting each new step slow down the pipeline unchallenged. He also makes a strong case for tags and promotions over branch-based deployment, noting his instinctive reaction when someone asks "which branch are we deploying from?" is: "No branches — tags and promotions." The Trap of Slowing Down After Failure Joachim warns about a common and dangerous pattern: when a bug reaches production, the natural organizational reaction is not to fix the pipeline, but to add gates. A QA team does a full pass, a security audit is inserted, a manual review step appears. Each gate slows delivery, which leads to larger batches, which increases risk, which triggers even more controls. He sees this as a vicious cycle. Organizations that respond to incidents by slowing delivery actually get worse security, worse quality, and worse throughput over time. He references a study — likely the research behind the book Accelerate by Nicole Forsgren, Jez Humble, and Gene Kim — showing that faster delivery correlates with better security and quality outcomes. The organizations adding Engineering Review Boards (ERBs) and Architecture Review Boards (ARBs) in the name of safety often do not measure the actual impact, so they never see that the controls are making things worse. Mattias connects this to AI-assisted development, where developers can now produce changes faster than ever. If the pipeline cannot keep up, the pile of unreleased changes grows, making each release riskier. Getting Buy-In: Start With Small Experiments Joachim does not recommend that a slow, process-heavy organization throw everything out overnight. Instead, he suggests starting with small experiments. Code promotions are a good entry point: teams can start producing artifacts more rapidly without changing how those artifacts are deployed. Once that works, the conversation shifts to delivering those artifacts faster. He finds starting on the artifact pipeline side produces quicker wins and more organizational buy-in than starting with the platform deployment side, which tends to be more intertwined and higher-risk to change. Guiding Principles Over a Rigid Golden Path Mattias questions the idea of a single "golden path," saying the term implies one rigid way of working. Joachim leans toward guiding principles instead. His strongest principle is simplicity — specifically, simplicity to understand, not necessarily simplicity to create. He references Rich Hickey's influential talk Simple Made Easy (from Strange Loop 2011), which distinguishes between things that are simple (not intertwined) and things that are easy (familiar or close at hand). Creating simple systems is hard work, but the payoff is systems that are easy to reason about, easy to change, and easy to secure. His second guiding principle is replaceability. When evaluating any tool in the platform, he asks: "How hard would it be to yank this out and replace it?" If swapping a component would be extremely difficult, that is a smell — it means the system has become too intertwined. Even with a tool as established as Argo CD, his team thinks about what it would look like to switch it out. Tooling Choices and Platform Foundations Joachim outlines the patterns his team typically uses when building platforms, organized into two paths: Delivery pipeline (artifact creation): - Trunk-based development over GitFlow - Release tags and promotions rather than branch-based deployment - Containerization early in the pipeline - Release Please for automated release management and changelogs - Renovate for dependency updates (used for production environment promotions from Helm charts and container images) Platform side (environment management): - Kubernetes-heavy, typically EKS on AWS - Karpenter for node scaling - AWS Load Balancer Controller only as a backing service for a separate ingress controller (not using ALB Ingress directly, due to its rough edges) - Argo CD for GitOps synchronization and deployment - Argo Image Updater for lower environments to pull latest images automatically - Helm for packaging, despite its learning curve He notes that NGINX Ingress Controller has been deprecated, so teams need to evaluate alternatives for their ingress layer. Developers Should Not Be Fully Shielded From Operations One of the more nuanced parts of the conversation is how much operational responsibility developers should have. Joachim rejects both extremes. He does not think every developer needs to know everything about infrastructure, but he has seen too many cases where developers completely isolated from runtime concerns make poor decisions — missing simple code changes that would make a system dramatically easier to deploy and operate. He advocates for transparency and collaboration. Platform repos should be open for anyone on the dev team to submit pull requests. When the platform team makes a change, they should pull in developers to work alongside them. This way, the delivery team gradually builds a deeper understanding of how the whole system works. Joachim loves the open-source maintainer model applied inside organizations: platform teams are maintainers of their areas, but anyone in the organization should be able to introduce change. He warns against building custom CLIs or heavy abstractions that create dependencies — if a developer wants to do something the CLI does not support, the platform team becomes a bottleneck. Mattias adds that opening up the platform to contributions also exposes assumptions. What feels easy to the person who built it may not be easy at all; it is just familiar. Outside contributors reveal where the system is actually hard to understand. Designers, Not Artists: Detaching Ego From Code Joachim shares an analogy he prefers over the common "developers as artists" framing. He sees developers more like designers than artists, because an artist's work is tied to their identity — they want it to endure. A designer, by contrast, creates something to serve a purpose and expects it to be replaced when something better comes along. He applies this to platforms and infrastructure: "I want my thing to get wiped out. If I build something, I want it to get removed eventually and have something better replace it." Organizations where ego is tied to specific systems or tools tend to resist change, which leads to the kind of dysfunction that keeps platforms bloated and brittle. Complexity Is the Enemy of Security Mattias raises the difficulty of maintaining complex security setups over time, especially when the original experts leave. Joachim responds firmly: complexity is anti-security. If people cannot comprehend a system, they cannot secure it well. He acknowledges that some problems are genuinely hard, but argues that much of the complexity engineers create is unnecessary — driven by ego rather than need. "The really smart people are the ones that create simple things," he says, wishing the industry would redirect its narrative from admiring complicated systems to admiring simple ones. Security and QA as Internal Consulting, Not Gatekeeping Joachim draws a parallel between security and QA. He dislikes calling a team "the quality team," preferring "verification" — they are one component of quality, not the entirety of it. Similarly, security is not one team's responsibility; it spans product design, development practices, tooling, and operations. His ideal model is for security and QA teams to operate as internal consultants whose goal is to reduce risk and improve the overall system — not to catch every possible issue at any cost. The framing matters: if a security team's mandate is simply "block all security issues," the logical conclusion is to stop shipping or delete the product entirely. That may be technically secure, but it is useless. He frames security as risk management: "Security is a risk management process, not just security for the sake of security. You're managing the risk to the business." The goal should be to deliver faster and more securely — an "and," not an "or." Mattias recalls a PCI DSS consultant joking over drinks that a system being down is perfectly compliant — no one can steal card numbers if the system is unavailable. The joke lands because it exposes exactly the broken incentive Joachim describes. Business Value as the Unifying Frame The episode closes by tying everything back to business outcomes. Joachim argues that speed and security are not opposites; both contribute to business value. Fast delivery creates value directly, while security reduces business risk — and risk management is itself a business operation. He explains why focusing on the highest-impact business bottleneck first builds trust. When you hit the big items first, you earn credibility, and subsequent changes become easier to justify. For example, one of his clients has a security group that is the slowest part of their organization. Speeding up that security process would have a massive impact on business delivery — more than optimizing the artifact pipeline. Mattias reflects that he used to see platform work as separate from business concerns — "I don't care about the business, I'm here to build a platform for developers." Looking back, he would reframe that: using business impact as the measure of platform success does not mean abandoning the focus on developers, it means having a clearer way to prioritize and demonstrate value. Highlights Joachim on platform bloat: "Your job is not to make your job faster and easier — you're an amplifier to the organization." Joachim on his favorite metric: "Cycle time is my favorite metric. I love cycle time metrics." Joachim on deployment strategy: "No branches, no branches — tags and promotions." Mattias on platform design: He calls the ideal early setup a "highway to production." Joachim on simplicity vs. ease: He references Rich Hickey's Simple Made Easy talk — "It's very hard to create simple systems that are easy to reason about. And it's very easy to create systems that are very hard to reason about." Joachim on replaceability: "If swapping a tool out would be extremely hard, that's a pretty big smell." Joachim on complexity and security: "If it's complicated, you just can't keep all the context together. Simple systems are much easier to be secure." Joachim on engineering ego: "I don't particularly like the aspect of [developers as] artists... I want my thing to get wiped out. I want it to get removed eventually and have something better replace it." He prefers the analogy of designers over artists, because artists tie their identity to their creations. Joachim on security as a blocker: "If their goal is we are going to block every security issue, the best way to do that is delete your product." Spicy cloud takes: Joachim calls GCP his favorite cloud for developers, compares AWS to "the Java of the land," and says he still struggles every time he is forced to use Azure. PCI DSS dark humor: Mattias recalls a consultant joking that a downed system is perfectly compliant — you cannot steal card numbers from a system that is not running. Joachim on the slow-down trap: Organizations add ERBs, ARBs, and manual security gates after incidents, but "the faster you can deliver, you actually get better security, better quality, and better throughput — and the more you slow it down, you go the opposite." Resources Simple Made Easy by Rich Hickey (InfoQ) — The influential 2011 talk Joachim references on distinguishing simplicity from ease in system design. DORA Metrics: The Four Keys — The research framework behind cycle time, deployment frequency, and the finding that speed and stability are not tradeoffs. Trunk Based Development — A comprehensive guide to the branching strategy Joachim recommends over GitFlow. Argo CD — Declarative GitOps for Kubernetes — The GitOps tool Joachim's team uses for cluster synchronization and deployment. Release Please (GitHub) — Google's tool for automated release management based on conventional commits, used by Joachim's team for tag-based promotions. Karpenter — Kubernetes Node Autoscaler — The node autoscaler Joachim's team uses with EKS for fast, flexible scaling. Renovate — Automated Dependency Updates — The dependency management bot Joachim uses for both build dependencies and production environment promotions.

Is the church doing enough to invest in the next generation of technical artists? And how do you balance the pressure for a "perfect" Sunday mix with the need to let young volunteers make mistakes and learn?In this episode you'll hear: 0:00 HouseRight Event Recap & Listener Shoutouts6:15 Gene Kim (Lauren Daigle's FOH Engineer) Joins12:30 Are We Investing in the Next Generation of Church Techs?32:30 Mentorship: Allowing Volunteers to Make Mistakes37:30 Core Topics for Mentoring Young Audio Engineers46:00 What It's Like Mixing FOH for Lauren Daigle48:00 Gear Talk: Gene Kim's Favorite Audio Tools Right Now57:00 Disaster Story: “Take it all off”1:00:30 Tech Takeaway: Providing Peace of MindGet expert help and care on your next integration project with our friends at HouseRight here.  Get more money back in your budget and more space in your closet by selling us your used gear here.  Apply to work at ChurchGear here!Resources for your Church Tech MinistrySell Us Gear: Does your church have used gear that you need to convert into new ministry dollars? We can make you an offer here. Buy Our Gear: Do you need some production gear but lack the budget to buy new gear? You can shop our gear store here.  Connect with us: Sales Bulletin: Get better deals than the public and get them earlier too here!Early Service: Get our best gear before it goes live on our site here. Instagram: Hangout with us on the gram here! Reviews: Leaving us a review on the podcast player you're listening to us on really helps the show. If you enjoyed this episode, you can say thank you with a review! 

AI Assisted Coding: How Spending 4x More on Code Quality Doubled Development Speed What happens when you combine nearly 30 years of engineering experience with AI-assisted coding? In this episode, Eduardo Ferro shares his experiments showing that AI doesn't replace good practices—it amplifies them. The result: doubled productivity while spending four times more on code quality. Vibe Coding vs Production-Grade AI Development "Vibe coding is flow-driven, curiosity-based way of building software with AI. It's less about meticulously reviewing each line of code, and more about letting the AI steer the process—perfect for quick experiments, side projects, MVPs, and prototypes."   Edu draws a clear distinction between vibe coding and production AI development. Vibe coding is exploration-focused, where you let AI drive while you learn and discover. Production AI coding is goal-focused, with careful planning, spec definition, and identification of edge cases before implementation. Both use small, safe steps and continuous conversation with the AI, but production code demands architectural thinking, security analysis, and sustainability practices. The key insight is that even vibe coding benefits from engineering discipline—as experiments grow, you need sustainable practices to maintain flexibility. How AI Doubled My Productivity "I was investing four times more in refactoring, cleanup, deleting code, introducing new tests, improving testability, and security analysis than in generating new features. And at the same time, globally, I think I more or less doubled my pace of work."   Edu's two-month experiment with production code revealed a counterintuitive finding: by spending 4x more time on code quality activities—refactoring, cleanup, test improvement, and security analysis—he actually doubled his overall delivery speed. The secret lies in fast feedback loops. With AI, you can implement a feature, run automated code review, analyze security, prioritize improvements, and iterate—all within an hour. What used to be a day's work happens in a single focused session, and the quality improvements compound over time. The Positive Spiral of Code Removal "We removed code, so we removed all the features that were not being used. And whenever I remove this code, the next step is to automatically try to see, okay, can I simplify the architecture."   One of the most powerful practices Edu discovered is using AI to accelerate code removal. By connecting product analytics to identify unused features, then using AI to quickly remove them, you trigger a positive spiral: removing code makes architecture changes easier, easier architecture changes enable faster feature development, which leads to more opportunities for simplification. This creates a self-reinforcing cycle that humans historically have been reluctant to pursue because removal was as expensive as creation. Preparing the System Before Introducing Change "What I want to generate is this new functionality—how should I change my system to make it super easy to introduce this one? It's not about making the change, it's about making the change easy."   Edu describes a practice that was previously too expensive: preparing the system before introducing changes. By analyzing architecture decision records, understanding the existing design, and adapting the codebase first, new features become trivial to implement. AI makes this preparation cheap enough to do routinely. The result is systems that evolve cleanly rather than accumulating technical debt with each new feature. AI as an Amplifier: The Double-Edged Sword "AI is an amplifier. People who already know how to develop software well will continue to develop it well and faster. People who did not know how to develop software well will probably get in trouble much faster than they would otherwise."   Edu's central metaphor is AI as an amplifier—it doesn't replace engineering judgment, it magnifies its presence or absence. Teams with strong practices will see accelerated improvement; teams without them will generate technical debt faster than ever. This has implications beyond individual productivity: the market will be saturated with solutions, making product discovery and distribution channels more important than implementation capability.   In this episode, we refer to Edu's blog post Fast Feedback, Fast Features: My AI Assisted Coding Experiment and Vibe Coding by Gene Kim.   About Eduardo Ferro Edu Ferro is Head of Engineering and Data Platform at ClarityAI, with nearly 30 years' experience. He helps teams deliver value through Lean, XP, and DevOps, blending technical depth with product thinking. Recently he explores AI-assisted product development, sharing insights and experiments on his site eferro.net.   You can connect with Edu Ferro on LinkedIn.

Ben had been riding high on vibe coding—throwaway scripts, zero attachment, pure productivity magic. Then he tried the same approach on a project he actually cares about and watched that 10x feeling crater to something closer to 10%. The bottleneck, it turns out, was never the typing.The hosts dig into what it feels like to let go of code you used to care about, whether "write-only code" is actually the future, and the growing gap between building software and keeping it alive.LinksVibe Coding by Gene Kim & Steve Yegge - The audiobook on AI-assisted development1Password: From Magic to Malware - How OpenClaw's agent skills became a supply chain attack surfaceTLDR Newsletter - Source of the "write-only code" conceptFollow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Thursday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

Adam built a Claude Code skill for his Taffy REST framework and wanted to share it with the CFML community. Simple enough—create a GitHub repo, add some markdown files, done. But somewhere between "this is cool" and "anyone can install this," a familiar chill crept in. These skills are just text files. No checksums. No digital signatures. No verification that the thing you're installing won't quietly exfiltrate your code to some server in Eastern Europe. Sound familiar? It should. We've been here before—back when passwords lived in plain text and "security" meant hoping nobody looked too hard.The hosts dig into the unsettling parallels between today's LLM plugin ecosystem and the wild west of early internet security.LinksAdam's Dotfiles Blog Post - Getting his shit together with dotfiles, Brewfile, and 1Password SSH agentCF Community LLM Marketplace - Adam's community marketplace for CFML-related Claude skillsSteve Yegge's Google Platforms Rant - The infamous accidentally-public Google+ postVibe Coding by Gene Kim & Steve Yegge - The audiobook Ben's been enjoyingSocket.dev - Supply chain security for npm dependenciesFollow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Thursday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

Mathias is Head of Data for Marketing at N26, the Berlin-based neobank valued at over $9 billion. He joined as a Senior Data Analyst in May 2020 and has since scaled the team to 12 people.We cover :

In this episode of The Engineering Room, Dave Farley talks with with Gene Kim, the bestselling author of "The Phoenix Project," "The Unicorn Project," and "Accelerate: The Science of Lean Software and DevOps." They discuss the controversial topic of "Vibe Coding," a concept Gene explored in his recent collaboration with Steve Yegge. While Dave initially described Vibe Coding as "one of the worst ideas of 2025," this conversation unpacks whether AI actually represents a fundamental shift in how we build software.----------------------Gene Kim LinkedIn https://www.linkedin.com/in/realgenekim/Gene Kim ''X'' (formerly "'Twitter") https://x.com/@RealGeneKimEqual Experts is a product software development consultancy with a network of over 1,000 experienced technology consultants globally. They increase the pace of innovation by using modern software engineering practices that embrace Continuous Delivery, Security, and Operability from the outset ➡️ https://bit.ly/3ASy8n0Only Patreon Supporters get to see the FULL VIDEO Episodes of The Engineering Room, sign up here: https://www.patreon.com/c/continuousdelivery

(06:23) Brought to you by Sweep AISweep is the fastest coding assistant for JetBrains. It lets you write code 10x faster. Finally, AI that works in JetBrains. Download for free at sweep.dev.Is the era of writing code by hand coming to an end? Gene Kim explains how vibe coding solved problems he abandoned for 13 years and why the best days of coding might be ahead of us.In this episode, Gene Kim shares his transformation from someone who hadn't written production code in decades to building ambitious projects in minutes. He explains how meeting Steve Yegge and discovering vibe coding reignited his passion for programming.Gene breaks down the FAAFO framework (Fast, Ambitious, Autonomous, Fun, Optionality) of vibe coding benefits and addresses the real risks of vibe coding, from deleted databases to corrupted repos. He emphasizes that developers need to shift from line cook to head chef, mastering delegation, architecture, and faster feedback loops. The conversation also explores whether AI will eliminate or expand developer roles, what skills matter most when hiring, and how organizations can build a vibe coding culture.Key topics discussed:Gene's jaw-dropping a-ha moment solving his 13-year problemThe FAAFO framework for measuring vibe coding benefitsFrom line cook to head chef: the new developer skillsetReal risks and downsides of vibe codingWill we need fewer developers or 10x more software?Why feedback loops must be 100x faster than beforeBuilding vibe coding culture across enterprise teamsTimestamps:(00:00) Trailer & Intro(03:13) What shaped Gene Kim's career in DevOps and technology?(07:26) How did Gene Kim's books like Phoenix Project come about?(09:55) What's the story behind the Phoenix Project graphic novel?(12:21) What was Gene Kim's a-ha moment with vibe coding?(14:41) How did Steve Yegge and Gene Kim collaborate on the book?(21:06) What is vibe coding and how is it different from regular coding?(25:57) What is the FAAFO framework for vibe coding benefits?(32:08) Will AI replace software developers?(36:10) What are the risks and downsides of vibe coding?(41:51) What skills do developers need in the age of vibe coding?(46:56) Why are feedback loops critical when using AI for coding?(51:59) How can organizations adopt vibe coding as a culture?(57:37) What should you look for when hiring developers in the AI era?(59:45) 2 Tech Lead Wisdom_____Gene Kim's BioGene Kim is a WSJ bestselling author and researcher who has studied high-performing technology organizations since 1999. The founder and former CTO of Tripwire, he has authored several industry-defining books, including The Phoenix Project and The DevOps Handbook, with over 1 million copies sold. He also organizes the Enterprise Technology Leadership Summit.Follow Gene:LinkedIn – linkedin.com/in/realgenekimTwitter – @RealGeneKimIT Revolution – itrevolution.com Vibe Coding - https://itrevolution.com/product/vibe-coding-book/Like this episode?Show notes & transcript: techleadjournal.dev/episodes/244.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

In this episode of the Phoenix Cast, hosts John and Kyle kick off 2026 with a jam-packed current events roundup covering the React to Shell vulnerability (think Log4Shell but for the front end), the Marine Corps' new drone training requirements, Google's TPU announcements that might have NVIDIA sweating, and the launch of GenAI.mil. They also share some exciting podcast milestones, dish out their 2026 predictions, and Kyle reveals his holiday vendetta against PowerPoint that resulted in building his own AI-powered presentation tool.We'd love to hear your thoughts! Tweet us at our new handle, @ThePhoenixCast, and don't forget to join our LinkedIn Group to connect with fellow Phoenix Casters. If you enjoyed the episode, help us out by leaving one of those coveted 5-star reviews on Apple Podcasts. Thanks for listening!LinksKyle's “The 8 Levels of AI Learning for Modern Commanders”https://www.linkedin.com/pulse/8-levels-ai-learning-modern-commanders-kyle-kmo-moschetto-mxuycReactShell:https://securityboulevard.com/2026/01/top-cves-of-december-2025/TorchTPU:https://hyperframeresearch.com/2025/12/24/can-googles-torchtpu-eventually-bridge-nvidias-cuda-moat/ WSJ: “Why AI Will Widen the Gap Between Superstars and Everybody Else”https://www.wsj.com/lifestyle/workplace/ai-workplace-tensions-what-to-do-c45f6b51?reflink=desktopwebshare_permalink USMC drone program:  https://www.marines.mil/News/Messages/Messages-Display/Article/4366306/approved-training-requirements-for-small-unmanned-aerial-systems/USMC AI WORKSHOP MARADMINhttps://www.marines.mil/News/Messages/Messages-Display/Article/4367572/united-states-marines-corps-generative-and-agentic-artificial-intelligence-work/II MEF Leadership AI:https://www.iimef.marines.mil/News/article-display/Article/4364616/ii-mef-advanced-ai-command-course/ Self-Paced AI Training (Military discount available)https://ftcg.io/self-paced-training Vibe Coding book (Gene Kim and Steve Yegge):https://itrevolution.com/product/vibe-coding-book/Gas Town:https://steve-yegge.medium.com/welcome-to-gas-town-4f25ee16dd04

It's okay to be confused about Vibe Coding! On this episode of Troubleshooting Agile, Squirrel and Jeffrey respond to a listener's argument from our series with Gene Kim on Vibe Coding and reflect on the question, what stage are we at in the industry when it comes to Vibe Coding and what can we expect for the future? Links: - Community of Needs: https://snowbirdcollaboratory.org/community-of-needs/ - First episode of the podcast series on Vibe Coding: https://soundcloud.com/troubleshootingagile/gene-kim-on-vibe-coding-part-i -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

Steve Martin: When a Distributed Team's Energy Vanishes into the Virtual Void Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "They weren't a team, they were a group of individuals working on multiple different projects." - Vasco Duarte (describing Steve's team situation)   The infrastructure team looked promising on paper: Product Owner in Italy, hardware engineers in Budapest, software engineers in Bucharest, designers in the UK. The team started with energy and enthusiasm, but within a month, something shifted. People stopped showing up for daily stand-ups. Cameras went dark during meetings. Engagement in retrospectives withered. This wasn't just about being distributed—plenty of teams work across time zones successfully. The problem ran deeper. The Scrum Master had a conflict of interest, serving dual roles as both facilitator and engineer. Team members were simultaneously juggling three or four other projects, treating this work as just another item on an impossibly long list. Steve spent a couple of months watching the deterioration before recognizing the root cause: there was no leadership sponsorship or buy-in. Stakeholders weren't invested. The team wasn't actually a team—they were individuals happening to work on the same project. Steve considers this a failure because he couldn't solve it. Sometimes, the absence of organizational support creates an unsolvable puzzle. Without leadership commitment, even the most skilled Scrum Master can't manufacture the conditions for team success.   In this episode, we refer to The Phoenix Project by Gene Kim, a book about organizational culture disguised as a DevOps novel.   Self-reflection Question: Is your team truly dedicated to one mission, or are they a collection of individuals spread across competing priorities? Featured Book of the Week: The Phoenix Project by Gene Kim "There's a lot of good lightning bulb moments that go off." - Steve Martin   Steve describes The Phoenix Project as a book about culture, not just DevOps. Written like a novel following a mock company, it creates continuous light bulb moments for readers. The book resonated deeply with Steve because it exposed patterns he'd experienced firsthand—particularly the anti-pattern of single points of failure. Steve had worked with an engineer who would spend entire weekends doing releases, holding everything in his head, then burning out and taking three days off to recover. This engineer was the bottleneck, the single point of failure that put the entire system at risk. The Phoenix Project illuminates how knowledge hoarding and dependency on individuals creates organizational fragility. The solution isn't just technical—it's cultural. Teams need to share knowledge and understanding, deliberately de-risking the concentration of expertise in one person's mind. Steve recommends this book for anyone trying to understand why organizational transformation requires more than process changes—it demands a fundamental shift in how teams think about knowledge, risk, and collaboration.   [The Scrum Master Toolbox Podcast Recommends]

How do you get the best out of AI tools when you don't have the talent that understands them? In the final of a three part series with guest, Gene Kim, we look at the misconceptions of AI for non-techy people, what happens when you don't have industry-leading talent to discuss leaf nodes and whether vibe coding really means switching your brain off. Links: - Gene Kim: https://itrevolution.com/author/gene-kim/ - Vibe Coding book: https://itrevolution.com/product/vibe-coding-book/ - Claude code: https://www.claude.com/product/claude-code - Erik Meijer: https://en.wikipedia.org/wiki/Erik_Meijer_(computer_scientist) - Vibe Coding podcast: https://www.youtube.com/@VibeCodingWithSteveandGene -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

Hoje o papo é sobre leitura! Neste episódio, mergulhamos naqueles livros que ensinam, que inspiram, e que carregamos todos os dias nas nossas jornadas de dev, de liderança, e além. Vem ver quem participou desse papo: André David, o host que sempre reflete Vinny Neves, Líder de Front-End na Alura Roberta Arcoverde, Software Engineering Manager no Google Simara Conceicao, Senior Software Developer na Thoughtworks Nicolás Morales, IT & Tech Excellence Manager na Ford Links: Grandes livros de Tecnologia – Hipsters #113 Clean Code, por Robert Cecil Martin Algoritmos para viver, de Brian Christian e Tom Griffiths O Programador Pragmático, de Andrew Hunt e David Thomas Trabalho Eficaz com Código Legado, por Michael C. Feathers A Philosophy of Software Design, de John K. Ousterhout O Projeto Phoenix, de Gene Kim, George Spafford e Kevin Behr Nexus, de Yuval Harari AI Snake Oil, de Arvind Narayanan e Sayash Kapoor Building Evolutionary Architectures: Support Constant Change, de Neal Ford, Rebecca Parsons e Patrick Kua Staff Engineer: Leadership beyond the management track, de Will Larson Team Topologies, de Matthew Skelton Organizações Cognitivas, de Kenneth Corrêa Hipsters Network no Instagram TechGuide.sh, um mapeamento das principais tecnologias demandadas pelo mercado para diferentes carreiras, com nossas sugestões e opiniões. #7DaysOfCode: Coloque em prática os seus conhecimentos de programação em desafios diários e gratuitos. Acesse https://7daysofcode.io/ Produção e conteúdo: Alura Cursos de Tecnologia – https://www.alura.com.br Edição e sonorização: Rede Gigahertz de Podcasts

Should you fire all your engineers and replace them with AI? That's what Squirrel pitches to Gene Kim, our guest, when he returns for the second of a three part series exploring the themes of his new book Vibe Coding. Tune in to discover how you can transform your organisation with Vibe Coding and the power of AI assistance. - Vibe Coding book: https://itrevolution.com/product/vibe-coding-book/ - Dr. Pal: https://www.linkedin.com/in/tapabratapal - Jevon's Paradox: https://en.wikipedia.org/wiki/Jevons_paradox - Reinertsen, Principles of Product Development Flow: http://lpd2.com/ - DORA report 2025: https://dora.dev/research/2025/dora-report/ - MIT beer game: https://en.wikipedia.org/wiki/Beer_distribution_game -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

Want to be more productive, creative and joyful? That's the outcome of Vibe Coding, a new concept and book by Gene Kim and Steve Yegge. In the first of a three-part series with co-author Gene Kim, he talks about how he got started on this project and how Vibe Coding offers new ways of working to tech and non-tech people alike. Links: - Gene Kim: https://itrevolution.com/author/gene-kim/ - Vibe Coding book: https://itrevolution.com/product/vibe-coding-book/ - Steve Yegge: https://en.wikipedia.org/wiki/Steve_Yegge - Erik Meijer: https://en.wikipedia.org/wiki/Erik_Meijer_(computer_scientist) -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

This month The Management Brief will explore prominent lean theories that have been guiding organizations in their lean transformations. This week, Josh Howell, LEI President, and Mark Reich, LEI Chief Engineer Strategy, are joined by Dr. Steven Spear, renown lean expert and senior lecturer at MIT.   Steven is co-author of Wiring the Winning Organization: Liberating our Collective Greatness through Slowification, Simplification, and Amplification,1 which examines how some companies over the last 150 years have led markets by solving their most important problems better, faster, and easier than the competition. The trio discuss Steven's work and his 30-plus years of lean learnings.  Steven recalls his start at the Toyota Production System Support Center (TSSC), when Mark was one of his mentors and sensei along with the Hajime Obha. He was thrust into all things lean and trying to grasp the Toyota Production System (TPS), without much clear instruction of principles and tools, instead just guidance to go and see and find things that were broken. “What I realized was going on is that they were teaching me to look for broken things, and the reason why they weren't telling me how is they wanted to first see what was broken in my approach,” says Steven. “So there was this layer of see a problem, solve a problem. That becomes sort of a mantra in my work about how we organize our behavior, how we architect our processes, how we architect our processes so that we can immediately see where we're wrong and use that as an immediate trigger to swarm onto the situation, figure out why it's wrong, and how to make it right.”  Steven grasped that TPS is a system built around the ability to see problems and respond to them quickly. “It's a simple thing to say, but the hard work is to keep pushing and pushing and pushing so you can see problems in greater detail, with greater accuracy, at smaller scale, sooner before they have a chance to become big problems. And everything else I think I've done since that moment ... has been elaboration on those points.”  The trio go on to discuss:  Steven's immersion in Toyota led to the groundbreaking article, “Decoding the DNA of the Toyota Production System,”2 which puts forward rules for how to design systems that establish standards, capture understanding, enable individuals to see when things go wrong, and then fix the problems they find.   High-Velocity Edge,3 Steven's first book, was built on the insights that the way for companies to compete is on solving increasingly more problems at greater depth and breadth and faster (velocity). He eventually wrote Wiring the Winning Organization, which states more explicitly that “winner's win because they're just much better at seeing and solving problems than anybody else.”  Steven describes three layers behind the slowification, simplification, and amplification framework: 1) compete on ability to see and solve problems, 2) understand the instrumentation and ingenuity through which individuals work, and 3) architect the social circuitry in all processes, procedures, and routines by which the work of individuals is integrated into collective action toward common purpose.  A problem-solving danger zone for companies is when iteration and experimentation are inhibited. To get into a winning zone requires slowification (committed time and space to solve problems), simplification (simplify problems at the operating level rather than moving them up and down silos), and amplification (see problems earlier and more often when they are small).  Leaders need to liberate people's ingenuity rather than maximize efficiency, according to Steven. “There's too much in society where leaders think their job is to somehow collect data, do analysis, and then tell other people what to do.” While a fan of AI, Steven fears that leaders who are predisposed to data collection, analytics, and command and control management will turn AI into “an unholy devil for the rest of us” and dismiss creativity, dismiss ingenuity, and commitment to mission.  Steven and his co-author Gene Kim have tried to harmonize problem-solving ideas across different communities of thought. “We've all had the experience where someone says, ‘This must be a lean problem vs. a Six Sigma problem vs. a DevOps problem vs. an agile problem.' Folks, it's a people problem. That's it. It's people who are in a relationship and either relationships aren't working because they can't see problems, they can't solve problems, or they can't systematize what they learned. And so we thought we were doing some kind of service here to simplify the language so people could speak and collaborate across domains.” Optimism about organizations' abilities to transform: “Outside in a personal life, [people are] striving so hard to be valued by others. This is not in sort of any kind narcissistic, weak way. It's just this is what people try to do. This gets back to like our creative origins in that we want to do things useful and valuable to others. And then we bring them into the workplace, and we tell them none of that: we're going to be demeaning of you, of your potential, your opportunity, your chance for appreciation. So all we're saying is, what we've naturally been created or evolved to do, just extend that into the workplace. Mark, that's my source of optimism because when you start having conversations with people that way and get them to talk about all the joy they have as coach of this, as head of that, as volunteer here, it's like, don't leave that at the door. Bring it in. And people, when you say, ‘Oh, that's what you want me to do, yeah,' they're happy to do that.” 

In this special compilation episode of Innovation and the Digital Enterprise, Patrick Emmons highlights key insights on digital transformation from top tech leaders. Featuring perspectives from Andrei Girenkov, Christopher Paquette, Ann Yeung, Sandee Kastrul, Deepak Kaimal, Jeff Miller, Christina Garcia, Tanya Hannah, Dan Kirsche, Dom Scandinaro, Subramanian Kunchithapatham, and Gene Kim. The episode delves into leading transformative tech teams, balancing disruption and protection, the role of AI, the need to stay nimble, and the foundational significance of human connection and communication in achieving successful digital transformation.(00:00) Welcome to Innovation and the Digital Enterprise(02:17) Andrei Girenkov Understanding the Scope of Digital Transformation(03:17) Christopher Paquette on Balancing Protection and Disruption(04:00) Ann Yeung on The Role of Corporate Functions(04:52) Sandee Kastrul on Diversity and Innovation(05:22) Deepak Kaimal Leveraging Gen AI for Business Solutions(07:01) Jeff Miller on Navigating Technological Change(07:21) Christina Garcia on Empowering Teams(07:59) Tanya Hannah on Keeping Nimble(08:28) Dan Kirsche on Org Structure and Accountability(09:17) Dom Scandinaro on Growth, and Agility(10:10) Subramanian Kunchithapatham on the Challenges of Digitization(10:53) Gene Kim on Connecting People Through Norms, Rituals, and ProcessesAndrei Girenkov is Chief Technology Officer at CSC Service Works. Christopher Paquette is Chief Transformation Officer at Personify Health. Ann Yeung is VP of Engineering at GEICO. Sandee Kastrul is President and co-founder of i.c.stars. Deepak Kaimal is Chief Technology Officer at COMPLY. Jeff Miller is Chief Product Officer at Coates Group. Christina Garcia is SVP of Engineering at Echo Global Logistics. Tanya Hannah is Chief Information Officer at OneTen. Dan Kirsche is Chief Technology Officer at Chamberlain Group. Dom Scandinaro is Chief Technology Officer at Cameo. Subramanian Kunchithapatham is Vice President - BI Solutions at Morgan Stanley. Gene Kim is an author, researcher, and founder of Tripwire, Inc.If you'd like to receive new episodes as they're published, please subscribe to Innovation and the Digital Enterprise in Apple Podcasts, Spotify, or wherever you get your podcasts. If you enjoyed this episode, please consider leaving a review in Apple Podcasts. It really helps others find the show.Podcast episode production by Dante32.

Send us a textIn this energetic and introspective episode recorded live at Pax8 Beyond 2025, Joey Pinz talks with Gene Kim, VP of Sales at Absolute, about what MSPs truly need from their security vendors — and how personal resilience echoes in business strategy.Gene opens with reflections on surfing at San Onofre State Beach, how the ocean provides a space for introspection, and how tracking progress — even in hobbies — helps him stay motivated. This passion for metrics carries into his work, where he supports MSPs navigating the challenges of brand visibility, cybersecurity threats, human capital gaps, and delivering operational excellence to SMB clients.The episode also explores Absolute's application persistence and resilience tools, which help MSPs ensure critical software stays active — even after catastrophic failures. With 600M+ devices already embedded at the BIOS level, Gene explains how Absolute provides continuity at a scale few can match.In a powerful moment, Joey shares his 120-pound weight loss journey, prompting Gene to reflect on how discipline, metrics, and mindset shape both personal and business transformations. 

The ever-provocative Steve Yegge joins us fresh off a vibe coding bender so productive, he wrote a book on the topic alongside award-winning author Gene Kim. Steve tells us why he believes the IDE is dead, why babysitting AI agents is more fun than coding, when vibe coding might take over the enterprise, how software devs should approach coding agents, and what it all means for society.

The ever-provocative Steve Yegge joins us fresh off a vibe coding bender so productive, he wrote a book on the topic alongside award-winning author Gene Kim. Steve tells us why he believes the IDE is dead, why babysitting AI agents is more fun than coding, when vibe coding might take over the enterprise, how software devs should approach coding agents, and what it all means for society.

What You'll Learn:In this episode, hosts Shayne Daughenbaugh, Andy Olrich, and guest Steve Spear discuss the evolution of industry, emphasizing the importance of cultural shifts driven by Lean thinking. They interview Steve Spears, a senior lecturer at MIT Sloan, who highlights the role of innovation in organizational transformation.About the Guest:Steve Spear is a senior lecturer at MIT Sloan, founder of the software firm See to Solve, and author of Wiring the Winning Organization (with Gene Kim) and The High-Velocity Edge. His work, featured in Harvard Business Review, MIT Sloan Management Review, and The New York Times, focuses on solving complex organizational challenges through innovation, systems thinking, and technology.Spear's ideas have shaped product design at Pratt & Whitney, accelerated pharma development cycles, and optimized operations at firms like Intel, Alcoa, and DTE Energy. He has advised the U.S. Army's Rapid Equipping Force and the Navy's Chief of Naval Research, aiding in tech deployment and operational innovation.Links:Click Here For Steve Spear's LinkedInClick Here For "See to Solve" Website

In this episode, we're joined by author and researcher Gene Kim for a wide-ranging conversation on the evolution of DevOps, developer experience, and the systems thinking behind organizational performance. Gene shares insights from his latest work on socio-technical systems, the role of developer platforms, and how AI is reshaping the shape of engineering teams. We also explore the coordination challenges facing modern organizations, the limits of tooling, and the deeper principles that unite DevOps, lean, and platform engineering.Mentions and links:Phoenix ProjectDecoding the DNA of the Toyota Production SystemWiring the Winning OrganizationETLS VegasFind Gene on LinkedInDiscussion points:(0:00) Introduction(2:12) The evolving landscape of developer experience(10:34) Option Value theory, and how GenAI helps developers(13:45) The aim of developer experience work(19:59) The significance of layer three changes(23:23) Framing developer experience(32:12) GenAI's part in ‘the death of the stubborn developer”(36:05) GenAI's implications on the workforce(38:05) Where Gene's work is heading

We discuss the four modes of coaching and navigate career growth in expanding / contracting companies with James Birchler. James shares highlights from the recent coaching / mentoring workshop he facilitated, and breaks down how each mode of coaching differs tactically. We also cover the dilemma of linear career/leadership growth vs. exponential company growth, different common communication challenges eng leaders face, why people / organizational challenges are harder than technical issues, and how to prepare for & execute uncomfortable conversations. James also shares his unique journey to technical leadership & how past management roles – even in non-tech spaces – have helped shape his thoughts on coaching & eng leadership today.ABOUT JAMES BIRCHLERJames Birchler is an engineering and product development leader, technical advisor, and an accredited Executive Coach from the UC Berkeley Haas School of Business Executive Coaching Institute.In his coaching practice, James focuses on self-awareness, integrity, accountability, and fostering a growth mindset that supports continuous learning and high performance.He focuses his technical advisory practice on common mechanisms and playbooks required at different phases and inflection points of startup growth and scaling: Hiring and interviewing, product development methodologies including Lean Startup and Agile, operational meeting cadence and communication flow, people management, technical leadership, vision/mission development, alignment, and execution.James implemented the Lean Startup methodologies with Eric Ries at IMVU (literally the first Lean Startup), where his team helped start the DevOps movement by building the infrastructure to ship code to production 50 times a day (which was a lot at the time!) and coining the term “continuous deployment.”He has more than 20 years of experience leading high-performance teams in growth environments, including startups and scaled organizations, including Amazon. He has delivered great consumer software products and implemented product development and innovation processes based on continuous learning and improvement.Presently James advises and coaches Series A+ startups in the US and Europe, and leads innovation practices in hyper-growth areas of last mile delivery technology for Amazon. Previously my roles included VP of Engineering & Operations, VP of Engineering, and Founder at several technology startups including IMVU, Caffeine.tv, SmugMug, iCracked, The Arts Coop, and Letters & Science.You can find James at jamesbirchler.com, LinkedIn, and Substack.SHOW NOTES:Highlights from James' recent coaching & mentoring workshop (2:41)Shared challenges around building trust in eng teams (5:25)The differences between coaching vs. mentoring (7:01)Building trust in order to best support your team members as a manager (9:38)Defining the advising mode of coaching (11:54)How supporting differs from advising (14:29)The story behind James' technical leadership journey (16:55)Transitioning from a PhD program & environmental planning career into tech (20:19)The dilemma of career growth: linear leadership growth vs. exponential company growth (23:53)Why organizational challenges are more complicated than technical puzzles (26:49)Navigating career growth during company contraction from the employee perspective (28:02)Preparing for uncomfortable conversations as a coach / manager (31:50)Strategies for actually having those tough conversations (35:36)Frameworks for helping others identify what they want (37:58)Rapid fire questions (42:44)LINKS AND RESOURCESStop 'Coaching' Your Tech Team (And What To Do Instead) - James' substack post on the four modes of development breaking down the core differences of coaching, advising, mentoring, and supporting roles and explaining how trust is the secret ingredient to all four.jamesbirchler.com - James' website where you can find info about his executive coaching and resources for engineering leaders and founders.How to lead with radical candor | Kim Scott - NYT bestselling author, Kim Scott, has cracked the code on giving valuable feedback in a way that builds genuine relationships, drives results, and creates positive workplaces.What Are People For? - In the twenty-two essays collected here, Wendell Berry conveys a deep concern for the American economic system and the gluttonous American consumer. Berry talks to the reader as one would talk to a next-door neighbor: never preachy, he comes across as someone offering sound advice. In the end, these essays offer rays of hope in an otherwise bleak forecast of America's future. Berry's program presents convincing steps for America's agricultural and cultural survival.New Happy: Getting Happiness Right in a World That's Got It Wrong - Happiness expert Stephanie Harrison draws upon hundreds of studies to offer a life-changing guide to finding the happiness you have been looking for, all based on a decade of research and brought to life with beautiful artwork.Accelerate: Building and Scaling High-Performing Technology Organizations - Through four years of groundbreaking research, Dr. Nicole Forsgren, Jez Humble, and Gene Kim set out to find a way to measure software delivery performance—and what drives it—using rigorous statistical methods. This book presents both the findings and the science behind that research. Readers will discover how to measure the performance of their teams, and what capabilities they should invest in to drive higher performance.Conversations on Science, Culture, and Time: Michel Serres with Bruno Latour - Although elected to the prestigious French Academy in 1990, Michel Serres has long been considered a maverick--a provocative thinker whose prolific writings on culture, science and philosophy have often baffled more than they have enlightened. In these five lively interviews with sociologist Bruno Latour, this increasingly important cultural figure sheds light on the ideas that inspire his highly original, challenging, and transdisciplinary essays.This episode wouldn't have been possible without the help of our incredible production team:Patrick Gallagher - Producer & Co-HostJerry Li - Co-HostNoah Olberding - Associate Producer, Audio & Video Editor https://www.linkedin.com/in/noah-olberding/Dan Overheim - Audio Engineer, Dan's also an avid 3D printer - https://www.bnd3d.com/Ellie Coggins Angus - Copywriter, Check out her other work at https://elliecoggins.com/about/

The key to a life well-lived is prioritization, but people rarely explain how to do it effectively.   In Managing Priorities: How to Create Better Plans and Make Smarter Decisions (Rosenfeld Media, 2024), Harry Max provides a useful guide.  He explains how learning to prioritize is helpful in life as well as at work. He explains how he - and his clients - feel a sense of freedom, as though a weight is lifted, when it's clear what is most important and they are able to focus on those things. In this relatable approach, Max acknowledges that avoidance behavior is natural, and clarifies the need to understand the costs of not prioritizing intentionally. Drawing on methods used at Apple, DreamWorks, NASA, Adobe, Google, Microsoft, and beyond, Harry Max presents a practical method that you can apply either for single large decisions or for ongoing efforts.  In the book he introduces the "daily boot", a way to start the day by clearing out the fog of competing efforts, and his DEGAP® method: Decide, Engage, Gather, Arrange, Prioritize.  Max demystifies common prioritization frameworks by providing guidance on how and when to use them, either together or separately. These include the Eisenhower Matrix, the Analytic Hierarchy Process, Paired Comparison, and Stack Ranking among others.  Mentioned resources: The New How by Nilofer Merchant The Crux: How Leaders Become Strategists by Richard P. Rumelt The Kano model by Noriaki Kano. It's not a prioritization framework per se, but a valuable resource for understanding what is important as it relates to customer satisfaction.  Author recommended reading: Wiring the Winning Organization by Gene Kim and Steven J. Spear Creativity, Inc by Ed Catmull and Amy Wallace Hosted by Meghan Cochran Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/new-books-network

The key to a life well-lived is prioritization, but people rarely explain how to do it effectively.   In Managing Priorities: How to Create Better Plans and Make Smarter Decisions (Rosenfeld Media, 2024), Harry Max provides a useful guide.  He explains how learning to prioritize is helpful in life as well as at work. He explains how he - and his clients - feel a sense of freedom, as though a weight is lifted, when it's clear what is most important and they are able to focus on those things. In this relatable approach, Max acknowledges that avoidance behavior is natural, and clarifies the need to understand the costs of not prioritizing intentionally. Drawing on methods used at Apple, DreamWorks, NASA, Adobe, Google, Microsoft, and beyond, Harry Max presents a practical method that you can apply either for single large decisions or for ongoing efforts.  In the book he introduces the "daily boot", a way to start the day by clearing out the fog of competing efforts, and his DEGAP® method: Decide, Engage, Gather, Arrange, Prioritize.  Max demystifies common prioritization frameworks by providing guidance on how and when to use them, either together or separately. These include the Eisenhower Matrix, the Analytic Hierarchy Process, Paired Comparison, and Stack Ranking among others.  Mentioned resources: The New How by Nilofer Merchant The Crux: How Leaders Become Strategists by Richard P. Rumelt The Kano model by Noriaki Kano. It's not a prioritization framework per se, but a valuable resource for understanding what is important as it relates to customer satisfaction.  Author recommended reading: Wiring the Winning Organization by Gene Kim and Steven J. Spear Creativity, Inc by Ed Catmull and Amy Wallace Hosted by Meghan Cochran Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/psychology

IT'S CHRIIIIIISTMAAAASSSSSSS!!!!!The last couple of years we have seen an increasing cadence of tech innovation, but scaled adoption held back by economic headwinds and incomplete technology suites - at the end of the year, it seems like a good time to reflect and cast forward a bit… In this weeks festive episode of the show, Dave, Esmee and Rob along with friend of the show, Gene Kim, author of the Phoenix Project and Wiring the Winning Organization, have a relaxed mull over the trends in AI and Cloud for 2025, what they are excited about for the coming year, sunny Christmastime and cooking the perfect turkey.Merry Christmas, Happy Holidays and a very Happy and Healthy New Year to all our guests and listeners! Thank you for sharing your time with us this year—we look forward to seeing you at the end of January! TLDR 00:53 Cruising and why don't people use meat probes? 11:00 Cloud conversation with Gene Kim 1:15:08 Excited about 2025! Guest Gene Kim: https://www.linkedin.com/in/realgenekim/ Hosts Dave Chapmanger: https://www.linkedin.com/in/chapmandr/ Esmee van de Glühwein: https://www.linkedin.com/in/esmeevandegiessen/ Rob Snowmanahan: https://www.linkedin.com/in/rob-kernahan/Production Dr Mike van der Baubles: https://www.linkedin.com/in/marcel-vd-burg/ Dave Chapmanger: https://www.linkedin.com/in/chapmandr/ SoundBeneath-the-Mistletoe Corbett : https://www.linkedin.com/in/ben-corbett-3b6a11135/Louis Jinglebells Corbett" : https://www.linkedin.com/in/louis-corbett-087250264/'Cloud Realities' is an original podcast from Capgemini

In this episode of Phoenix Cast, hosts John and Kyle discuss excitement around the Marine Corps birthday, a graphic novel from Gene Kim, DORA's DEVOPS report, Google joining JWCC, a podcast with Gen Nakasone, and some announcements from OpenAI. Share your thoughts with us on Twitter: @USMC_TFPhoenix (Now verified!) Follow MARFORCYBER, MCCYWG, & MCCOG on Twitter, LinkedIn, Facebook, and YouTube. Leave your review on Apple Podcasts. Links: Marine Corps Birthday:  https://www.cmc.marines.mil/Birthday/ Phoenix Proejct Graphic novel:  https://a.co/d/5pDZdip Origional Phoenix Project: https://a.co/d/a2Bapd3 Unicorn Project: https://a.co/d/cd4dwgn DORA DEVOPS:  https://dora.dev/ Google joins JWCC:  https://breakingdefense.com/2024/10/full-house-google-to-be-final-jwcc-partner-authorized-for-secret-level-cloud-work-in-2025/  Nakasone on mic drop:  https://podcasts.apple.com/us/podcast/180-mic-drop-exclusive-gen-nakasone-says-reports-about/id1225077306?i=1000675737757  OpenAI buys chat.com https://techcrunch.com/2024/11/06/openai-acquired-chat-com/ OpenAI websearch https://openai.com/index/searchgpt-prototype/

Новый, с пылу, с жару выпуск подкаста с членом ПК DevOpsConf 2025. На пару с Игорем Курочкиным обсуждали DevOps и развитие инжиниринговых практик. Говорили бодро, обсуждали NextOps, который не то, чем кажется! Вспомнили массу приятных книг и не только. DevOpsConf 2025, 7-8 апреля 2025, Москва CFP DevOpsConf 2025 Встреча докладчиков и Программного комитета DevOpsConf 2025 Gene Kim, Kevin Behr, George Spafford — The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win Джин Ким, Кевин Бер, Джордж Спаффорд — Проект «Феникс». Как DevOps устраняет хаос и ускоряет развитие компании. Gene Kim, Jez Humble, Patrick Debois, John Willis, Nicole Forsgren — The DevOps Handbook: How to Create World-Class Agility, Reliability, & Security in Technology Organizations Джин Ким, Джез Хамбл, Патрик Дебуа, Джон Уиллис — Руководство по DevOps. Как добиться гибкости, надежности и безопасности мирового уровня в технологических компаниях Gene Kim — The Unicorn Project: A Novel about Developers, Digital Disruption, and Thriving in the Age of Data Участники @golodnyj Игорь Курочкин Telegram канал VK группа Яндекс Музыка iTunes подкаст Поддержи подкаст

In this episode of Book Overflow, Carter and Nathan finish their discussion of The Unicorn Project by Gene Kim. Written in the style of a novel, join them as they discuss how businesses bet big on new ideas, dealing with layoffs, and executive politicking! -- Books Mentioned in this Episode -- Note: As an Amazon Associate, we earn from qualifying purchases. ---------------------------------------------------------- The Unicorn Project by Gene Kim https://amzn.to/3XJFg2u (paid link) ---------------- 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

Hey Stewards! Today, we bring in creative director and founder of fashion brand Child Worldwide Samuel Choi (@achildinawe) and his right hand man Ryan Fooks, and we get real about the struggle of surrendering - one's identity, work, and ministry. It can feel so easy to want to do everything for the glory of the Lord, but at the cost of really knowing Him. Listen in as we unpack what it really means to let go and walk as His children. Support our ministry! Join our Patreon for behind-the-scenes and more exclusive content! https://www.patreon.com/GoodServicePodcast Hosts:  Ben Chung | @btek_benchung  Kevin Seo | @thekevinseo  Edited by: Gene Kim | @thegenekim  Music by: Isaac Han | @ihannofficial  Logo by: David Chang | @davidchangstudio

Hey Stewards! On this episode, we grab a meal with grammy award-winning music producer, new pastor and father Alex Hitchens (@akhitchens), and we talk about things from understanding God's love, healthy vulnerability and confrontation, and what its like to be a new pastor, and much more. Tune in for some great moments as we enjoy some hawaiian food from Faka's Island Grill (@fakasislandgrill). Support our ministry! Join our Patreon for behind-the-scenes and more exclusive content! https://www.patreon.com/GoodServicePodcast Hosts:  Ben Chung | @btek_benchung  Kevin Seo | @thekevinseo  Edited by: Gene Kim | @thegenekim  Music by: Isaac Han | @ihannofficial  Logo by: David Chang | @davidchangstudio

Hey Stewards! Today we bring in our friend, co-writer on Letters From Love Itself and president of the non-profit Perspectives Worldwide, Chase Brown (@whereischaseabrown) and we go straight into the vulnerable - talking about all things God's love. Get ready for a great convo as we dig into some delicious food from Bowl Thai Grill (@bowlthaigrill). Support our ministry! Join our Patreon for behind-the-scenes and more exclusive content! https://www.patreon.com/GoodServicePodcast Hosts:  Ben Chung | @btek_benchung  Kevin Seo | @thekevinseo  Edited by: Gene Kim | @thegenekim  Music by: Isaac Han | @ihannofficial  Logo by: David Chang | @davidchangstudio

What is up, stewards! On this episode, we have our good friends, entrepreneurs, co-founders of MILLU and boss women Sarah Hartono and Sena Lee, to talk about all things - from healing generational trauma, sanctification and spiritual gifts, sabbath rhythms, and more. Join in on a great convo as we chow down on some bento boxes from Azuma Japanese Kitchen (@azuma.japanese.restaurant) and salad from Bowl Thai Grill (@bowlthaigrill). Support our ministry! Join our Patreon for behind-the-scenes and more exclusive content! https://www.patreon.com/GoodServicePodcast Hosts:  Ben Chung | @btek_benchung  Kevin Seo | @thekevinseo  Edited by: Gene Kim | @thegenekim  Music by: Isaac Han | @ihannofficial  Logo by: David Chang | @davidchangstudio

Junior coders aren't going to be purged, but trained, just like we taught ditch-diggers to drive excavators. Find out why Squirrel thinks Steve Yegge is wrong, on this episode of Troubleshooting Agile. Links: Enterprise Technology Leadership Summit: https://itrevolution.com/product/enterprise-technology-leadership-summit-las-vegas-2024/ - Steve Yegge's talk at ETLS: article https://sourcegraph.com/blog/the-death-of-the-junior-developer , video https://videos.itrevolution.com/watch/1002959965 - Gene Kim at ETLS: https://itrevolution.com/articles/observing-the-impact-of-ai-on-law-firms-software-and-writing-winners-and-losers/ - Patrick Debois at ETLS: https://videos.itrevolution.com/watch/1002959794 -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

What's good, stewards! This episode, you got us, your hosts for a great catch up on the following: life-giving rhythms, Jesus movements around the world, and the end times. This is a fun one, tune in as we dine on some good ol faithful Chicken Maison (@chicken_maison). Support our ministry! Join our Patreon for behind-the-scenes and more exclusive content! https://www.patreon.com/GoodServicePodcast Hosts:  Ben Chung | @btek_benchung  Kevin Seo | @thekevinseo  Edited by: Gene Kim | @thegenekim  Music by: Isaac Han | @ihannofficial  Logo by: David Chang | @davidchangstudio

What is up, Stewards! On this episode of Good Service, our good friend Dave Gibbons (@davekgibbons) returns, and we talk about everything from being present, navigating trauma, being love to the next generation, and all things related to his new book The Shape Of My Eyes. Pull up a chair with us as we dine on some homely Sul Lung Tang from Jun Ju Sul Lung Tang. Check out Dave's new book, The Shape Of My Eyes: A Memoir on Race, Faith & Finding Myself. https://a.co/d/4i8gcec Support our ministry! Join our Patreon for behind-the-scenes and more exclusive content! https://www.patreon.com/GoodServicePodcast Hosts:  Ben Chung | @btek_benchung  Kevin Seo | @thekevinseo  Edited by: Gene Kim | @thegenekim  Music by: Isaac Han | @ihannofficial  Logo by: David Chang | @davidchangstudio

What's good, stewards! On this episode, we chat with the homie, evangelist, pastor, leader of Circuit Riders and Carry the Love, Sammy Rodriguez (@samuelmrod) to talk about what it's like to be available for ministry, the role of the latino/a community in God's future plans, and the beauty of disruption. Get filled with us as we dine on some burritos from Coco's Tacos (@cocos.tacos). Check out the ministries that Sammy helps to lead: https://circuitriders.com/ https://carrythelove.com/ Support our ministry! Join our Patreon for behind-the-scenes and more exclusive content! https://www.patreon.com/GoodServicePodcast Hosts:  Ben Chung | @btek_benchung  Kevin Seo | @thekevinseo  Edited by: Gene Kim | @thegenekim  Music by: Isaac Han | @ihannofficial  Logo by: David Chang | @davidchangstudio

Welcome Stewards! On this special live episode of Good Service, we sit down with pastor and former industry dancer Tymme Reitz (@tymmereitz) to exchange some bars on using dance and other arts for Jesus, worship as a weapon, and how to steward our gifts well. Get locked in for a great conversation that any follower who's in the creative arts will enjoy. Support our ministry! Join our Patreon for Q&A's, behind-the-scenes, and more exclusive content! https://www.patreon.com/GoodServicePodcast Hosts:  Ben Chung | @btek_benchung  Kevin Seo | @thekevinseo  Edited by: Gene Kim | @thegenekim  Music by: Isaac Han | @ihannofficial  Logo by: David Chang | @davidchangstudio

In this episode of the CTO Advisor Podcast, Keith Townsend interviews Gene Kim, the renowned author of "The Phoenix Project" and "The Unicorn Project." Gene shares his experiences and insights from his extensive DevOps and IT leadership career, exploring how these fictional narratives reflect real-world challenges and triumphs in technology transformations. Gene discusses the role [...]

What is good, Stewards! On this episode, we chat with our friend, founder of Hustle Division and host of Behind The Hustle Podcast Giveon "EG" Cisneros (@egtheplaymaker) as we share about resting and hustling for God, building character and kingdom, and useful tips for people growing in their faith. Pull up a chair with us as we munch on some grilled fish from BlueSalt Fish Grill (@bluesalt_fishgrill). Support our ministry! Join our Patreon for behind-the-scenes and more exclusive content! https://www.patreon.com/GoodServicePodcast Hosts:  Ben Chung | @btek_benchung  Kevin Seo | @thekevinseo  Edited by: Gene Kim | @thegenekim  Music by: Isaac Han | @ihannofficial  Logo by: David Chang | @davidchangstudio

Hey Stewards! on this episode of Good Service we celebrate 1 year of our pod!!! Listen in as we reflect on the past year, and seeing God's fingerprints all the way up until recent events. Join our fun catch-up as we munch on some cupcakes (@sprinklescupcakes) and fish (@bluesalt_fishgrill). Support our ministry! Join our Patreon for behind-the-scenes and more exclusive content! https://www.patreon.com/GoodServicePodcast Hosts:  Ben Chung | @btek_benchung  Kevin Seo | @thekevinseo  Edited by: Gene Kim | @thegenekim  Music by: Isaac Han | @ihannofficial  Logo by: David Chang | @davidchangstudio

What's good, Stewards! On this episode, we sit down with the homie, rapper and father + husband Futuristic (@onlyfuturistic) and have an honest conversation about rediscovering faith, great (and not-so-great) encounters with people of the faith, and also some good practices for those growing in their belief. Buckle up for a great talk as we enjoy a meal from George's Greek Grill (@georgesgreekgrill). Stream ikigai - Futuristic's new album - and catch him on tour! https://onlyfuturistic.komi.io/ Support our ministry! Join our Patreon for behind-the-scenes and more exclusive content! https://www.patreon.com/GoodServicePodcast Hosts:  Ben Chung | @btek_benchung  Kevin Seo | @thekevinseo  Edited by: Gene Kim | @thegenekim  Music by: Isaac Han | @ihannofficial  Logo by: David Chang | @davidchangstudio

How is moving a couch the perfect metaphor for joint problem-solving and joint cognition? Gene Kim explains in this episode. Like what you hear? Connect with Gene on LinkedIn. Explore SAFe courses here.

What's up, Stewards! On this episode of Good Service, we sit down with our good friend, founder of many tech start-ups and certified genius Jon Frendl. Now this is a man who really really loves God. We hope you feel the friendship as we share thoughts about building a godly business, deeper experiencing God's love, and how to navigate AI and technology. Enjoy a meal with us as we dig into some Vietnamese Peruvian cuisine from Nam Kitchen (@namkitchen.california) Support our ministry! Join our Patreon for behind-the-scenes and more exclusive content! https://www.patreon.com/GoodServicePodcast Hosts:  Ben Chung | @btek_benchung  Kevin Seo | @thekevinseo  Edited by: Gene Kim | @thegenekim  Music by: Isaac Han | @ihannofficial  Logo by: David Chang | @davidchangstudio

What is up, Stewards! On this episode, we got a solo round with your hosts, Ben and Kevin, catching up on how God is moving in their lives - walking in the Spirit, making choices, trusting in God's timing, and what saying yes to God looks like. Hope you get to enjoy a meal with us as we dig into some Vietnamese Peruvian pho from Nam Kitchen (@namkitchen.california) Support our ministry! Join our Patreon for behind-the-scenes and more exclusive content! https://www.patreon.com/GoodServicePodcast Hosts:  Ben Chung | @btek_benchung  Kevin Seo | @thekevinseo  Edited by: Gene Kim | @thegenekim  Music by: Isaac Han | @ihannofficial  Logo by: David Chang | @davidchangstudio

In this episode of the Application Security Podcast, hosts Chris Romeo and Robert Hurlbut engage in a deep discussion with guest David Quisenberry about various aspects of application security. They cover David's journey into the security world, insights on building AppSec programs in small to mid-sized companies, and the importance of data-driven decision-making. The conversation also delves into the value of mentoring, the vital role of trust with engineering teams, and the significance of mental health and community in the industry. Additionally, Chris, David and Robert share personal stories that emphasize the importance of relationships and balance in life. Books Shared in the Episode:SRE Engineering by Betsy Beyer, Chris Jones, Jennifer Petoff and Niall Richard Murphy  The Phoenix Project by Gene Kim, Kevin Behr and George Spafford Security Chaos Engineering by Aaron Rinehart and Kelly Shortridge CISO Desk Reference Guide by Bill Bonney, Gary Hayslip, Matt Stamper Wiring the Winning Organization by Gene Kim and Dr. Steven J. Spear The Body Keeps the Score by Bessel van der Kolk, M.D. Intelligence Driven Incident Response by Rebekah Brown and Scott J. Roberts Never Eat Alone by Keith Ferrazzi  Thinking Fast and Slow by Daniel Kahneman Do Hard Things by Steve Magness How Leaders Create and Use Networks, Whitepaper by Herminia Ibarra and Mark Lee HunterFOLLOW OUR SOCIAL MEDIA: ➜Twitter: @AppSecPodcast➜LinkedIn: The Application Security Podcast➜YouTube: https://www.youtube.com/@ApplicationSecurityPodcast Thanks for Listening! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

We took over the Amplio Podcast studio after day one of FILO to recap the conference and bring the party to you!In this episode you'll hear: 1:00 FILO Amplio After Party Pod! 4:00 What happened at FILO 2024 Day 1? 7:00 Toby's horrific Gene Kim introduction 11:00 FILO pre party activities 15:00 Amplio's podcast has launched! 20:00 Game: Classic Rock pop quiz!26:00 Game: Name that song for Toby29:15 Game: Songs the Government plays to torture people 33:00 Rapid round questions 40:00 Worship Sound Guy joins us! 43:00 The Rest of the ChurchGear Crew & Jeff Vandergiessen joins! 53:20 Church Tech Confessional: "I shouldn't have listened to my pastor's wife" Resources for your Church Tech MinistryDoes your church have used gear that you need to convert into new ministry dollars? We can make you an offer here. Do you need some production gear but lack the budget to buy new gear? You can get Certified Church Owned gear here.  Connect with us: Follow us on FacebookHang out with us on InstagramSee all the ways we can serve your church on our WebsiteGet our best gear sent to your inbox each Monday before it goes public via the Early ServiceCome celebrate our new website with us with a never before seen 20% off discount store wide! Code: MEMORIALDAY24 If you've ever attempted to buy gear from us before, you probably experienced:Slow load timesInaccurate search bar results Frustrating check out speeds Those days are over. Check the site out here!