Podcasts about Software development

AI Assisted Coding: From Deterministic to AI-Driven—The New Paradigm of Software Development, With Markus Hjort In this BONUS episode, we dive deep into the emerging world of AI-assisted coding with Markus Hjort, CTO of Bitmagic. Markus shares his hands-on experience with what's being called "vibe coding" - a paradigm shift where developers work more like technical product owners, guiding AI agents to produce code while focusing on architecture, design patterns, and overall system quality. This conversation explores not just the tools, but the fundamental changes in how we approach software engineering as a team sport. Defining Vibecoding: More Than Just Autocomplete "I'm specifying the features by prompting, using different kinds of agentic tools. And the agent is producing the code. I will check how it works and glance at the code, but I'm a really technical product owner." Vibecoding represents a spectrum of AI-assisted development approaches. Markus positions himself between pure "vibecoding" (where developers don't look at code at all) and traditional coding. He produces about 90% of his code using AI tools, but maintains technical oversight by reviewing architectural patterns and design decisions. The key difference from traditional autocomplete tools is the shift from deterministic programming languages to non-deterministic natural language prompting, which requires an entirely different way of thinking about software development. The Paradigm Shift: When AI Changed Everything "It's a different paradigm! Looking back, it started with autocomplete where Copilot could implement simple functions. But the real change came with agentic coding tools like Cursor and Claude Code." Markus traces his journey through three distinct phases. First came GitHub Copilot's autocomplete features for simple functions - helpful but limited. Next, ChatGPT enabled discussing architectural problems and getting code suggestions for unfamiliar technologies. The breakthrough arrived with agentic tools like Cursor and Claude Code that can autonomously implement entire features. This progression mirrors the historical shift from assembly to high-level languages, but with a crucial difference: the move from deterministic to non-deterministic communication with machines. Where Vibecoding Works Best: Knowing Your Risks "I move between different levels as I go through different tasks. In areas like CSS styling where I'm not very professional, I trust the AI more. But in core architecture where quality matters most, I look more thoroughly." Vibecoding effectiveness varies dramatically by context. Markus applies different levels of scrutiny based on his expertise and the criticality of the code. For frontend work and styling where he has less expertise, he relies more heavily on AI output and visual verification. For backend architecture and core system components, he maintains closer oversight. This risk-aware approach is essential for startup environments where developers must wear multiple hats. The beauty of this flexibility is that AI enables developers to contribute meaningfully across domains while maintaining appropriate caution in critical areas. Teaching Your Tools: Making AI-Assisted Coding Work "You first teach your tool to do the things you value. Setting system prompts with information about patterns you want, testing approaches you prefer, and integration methods you use." Success with AI-assisted coding requires intentional configuration and practice. Key strategies include: System prompts: Configure tools with your preferred patterns, testing approaches, and architectural decisions Context management: Watch context length carefully; when the AI starts making mistakes, reset the conversation Checkpoint discipline: Commit working code frequently to Git - at least every 30 minutes, ideally after every small working feature Dual AI strategy: Use ChatGPT or Claude for architectural discussions, then bring those ideas to coding tools for implementation Iteration limits: Stop and reassess after roughly 5 failed iterations rather than letting AI continue indefinitely Small steps: Split features into minimal increments and commit each piece separately In this segment we refer to the episode with Alan Cyment on AI Assisted Coding, and the Pachinko coding anti-pattern.  Team Dynamics: Bigger Chunks and Faster Coordination "The speed changes a lot of things. If everything goes well, you can produce so much more stuff. So you have to have bigger tasks. Coordination changes - we need bigger chunks because of how much faster coding is." AI-assisted coding fundamentally reshapes team workflows. The dramatic increase in coding speed means developers need larger, more substantial tasks to maintain flow and maximize productivity. Traditional approaches of splitting stories into tiny tasks become counterproductive when implementation speed increases 5-10x. This shift impacts planning, requiring teams to think in terms of complete features rather than granular technical tasks. The coordination challenge becomes managing handoffs and integration points when individuals can ship significant functionality in hours rather than days. The Non-Deterministic Challenge: A New Grammar "When you're moving from low-level language to higher-level language, they are still deterministic. But now with LLMs, it's not deterministic. This changes how we have to think about coding completely." The shift to natural language prompting introduces fundamental uncertainty absent from traditional programming. Unlike the progression from assembly to C to Python - all deterministic - working with LLMs means accepting probabilistic outputs. This requires developers to adopt new mental models: thinking in terms of guidance rather than precise instructions, maintaining checkpoints for rollback, and developing intuition for when AI is "hallucinating" versus producing valid solutions. Some developers struggle with this loss of control, while others find liberation in focusing on what to build rather than how to build it. Code Reviews and Testing: What Changes? "With AI, I spend more time on the actual product doing exploratory testing. The AI is doing the coding, so I can focus on whether it works as intended rather than syntax and patterns." Traditional code review loses relevance when AI generates syntactically correct, pattern-compliant code. The focus shifts to testing actual functionality and user experience. Markus emphasizes: Manual exploratory testing becomes more important as developers can't rely on having written and understood every line Test discipline is critical - AI can write tests that always pass (assert true), so verification is essential Test-first approach helps ensure tests actually verify behavior rather than just existing Periodic test validation: Randomly modify test outputs to verify they fail when they should Loosening review processes to avoid bottlenecks when code generation accelerates dramatically Anti-Patterns and Pitfalls to Avoid Several common mistakes emerge when developers start with AI-assisted coding: Continuing too long: When AI makes 5+ iterations without progress, stop and reset rather than letting it spiral Skipping commits: Without frequent Git checkpoints, recovery from AI mistakes becomes extremely difficult Over-reliance without verification: Trusting AI-generated tests without confirming they actually test something meaningful Ignoring context limits: Continuing to add context until the AI becomes confused and produces poor results Maintaining traditional task sizes: Splitting work too granularly when AI enables completing larger chunks Forgetting exploration: Reading about tools rather than experimenting hands-on with your own projects The Future: Autonomous Agents and Automatic Testing "I hope that these LLMs will become larger context windows and smarter. Tools like Replit are pushing boundaries - they can potentially do automatic testing and verification for you." Markus sees rapid evolution toward more autonomous development agents. Current trends include: Expanded context windows enabling AI to understand entire codebases without manual context curation Automatic testing generation where AI not only writes code but also creates and runs comprehensive test suites Self-verification loops where agents test their own work and iterate without human intervention Design-to-implementation pipelines where UI mockups directly generate working code Agentic tools that can break down complex features autonomously and implement them incrementally The key insight: we're moving from "AI helps me code" to "AI codes while I guide and verify" - a fundamental shift in the developer's role from implementer to architect and quality assurance. Getting Started: Experiment and Learn by Doing "I haven't found a single resource that covers everything. My recommendation is to try Claude Code or Cursor yourself with your own small projects. You don't know the experience until you try it." Rather than pointing to comprehensive guides (which don't yet exist for this rapidly evolving field), Markus advocates hands-on experimentation. Start with personal projects where stakes are low. Try multiple tools to understand their strengths. Build intuition through practice rather than theory. The field changes so rapidly that reading about tools quickly becomes outdated - but developing the mindset and practices for working with AI assistance provides durable value regardless of which specific tools dominate in the future. About Markus Hjort Markus is Co-founder and CTO of Bitmagic, and has over 20 years of software development expertise. Starting with Commodore 64 game programming, his career spans gaming, fintech, and more. As a programmer, consultant, agile coach, and leader, Markus has successfully guided numerous tech startups from concept to launch. You can connect with Markus Hjort on LinkedIn.

AI Assisted Coding: Pachinko Coding—What They Don't Tell You About Building Apps with Large Language Models, With Alan Cyment In this BONUS episode, we dive deep into the real-world experience of coding with AI. Our guest, Alan Cyment, brings honest perspectives from the trenches—sharing both the frustrations and breakthroughs of using AI tools for software development. From "Pachinko coding" addiction loops to "Mecha coding" breakthroughs, Alan explores what actually works when building software with large language models. From Thermomix Dreams to Pachinko Reality "I bought into the Thermomix coding promise—describe the whole website and it would spit out the finished product. It was a complete disaster." Alan started his AI coding journey with high expectations, believing he could simply describe a complete application and receive production-ready code. The reality was far different. What he discovered instead was an addictive cycle he calls "Pachinko coding" (Pachinko, aka Slot Machines in Japan)—repeatedly feeding error messages back to the AI, hoping each iteration would finally work, while burning through tokens and time. The AI's constant reassurances that "this time I fixed it" created a gambling-like feedback loop that left him frustrated and out of pocket, sometimes spending over $20 in API credits in a single day. The Drunken PhD with Amnesia "It felt like working with a drunken PhD with amnesia—so wise and so stupid at the same time." Alan describes the maddening experience of anthropomorphizing AI tools that seem brilliant one moment and completely lost the next. The key breakthrough came when he stopped treating the AI as a person and started seeing it as a function that performs extrapolations—sometimes accurate, sometimes wildly wrong. This mental shift helped him manage expectations and avoid the "rage coding" that came from believing the AI should understand context and maintain consistency like a human collaborator. Making AI Coding Actually Work "I learned to ask for options explicitly before any coding happens. Give me at least three options and tell me the pros and cons." Through trial and error, Alan developed practical strategies that transformed AI from a frustrating Pachinko machine into a useful tool: Ask for options first: Always request multiple approaches with pros and cons before any code is generated Use clover emoji convention: Implement a consistent marker at the start of all AI responses to track context Small steps and YAGNI principles: Request tiny, incremental changes rather than large refactoring Continuous integration: Demand the AI run tests and checks after every single change Explicit refactoring requests: Regularly ask for simplification and readability improvements Take two steps back: When stuck in a loop, explicitly tell the AI to simplify and start fresh Choose the right tech stack: Use technologies with abundant training data (like Svelte over React Native in Alan's experience) The Mecha Coding Breakthrough "When it worked, I felt like I was inside a Lego Mecha robot—the machine gave me superpowers, but I was still the one in control." Alan successfully developed a birthday reminder app in Swift in just one day, despite never having learned Swift. He made architectural decisions and guided the development without understanding the syntax details. This experience convinced him that AI represents a genuine new level of abstraction in programming—similar to the jump from assembly language to high-level languages, or from procedural to object-oriented programming. You can now think in English about what you want, while the AI handles the accidental complexity of syntax and boilerplate. The Cost Reality Check "People writing about vibe coding act like it's free. But many people are going to pay way more than they would have paid a developer and end up with empty hands." Alan provides a sobering cost analysis based on his experience. Using DeepSeek through Aider, he typically spends under $1 per day. But when experimenting with premium models like Claude Sonnet 3.5, he burned through $5 in just minutes. The benchmark comparisons are revealing: DeepSeek costs $4 for a test suite, DeepSeek R1 plus Sonnet costs $16, while Open AI's O1 costs $190. For non-developers trying to build complete applications through pure "vibe coding," the costs can quickly exceed what hiring a developer would cost—with far worse results. When Thermomix Actually Works "For small, single-purpose scripts that I'm not interested in learning about and won't expand later, the Thermomix experience was real." Despite the challenges, Alan found specific use cases where AI truly delivers on the "just describe it and it works" promise. Processing Zoom attendance logs, creating lookup tables for video effects, and other single-file scripts worked remarkably well. The pattern: clearly defined context, no need for ongoing maintenance, and simple enough to verify the output without deep code inspection. For these thermomix moments, AI proved genuinely transformative. The Pachinko Trap and Tech Stack Matters "It became way more stable when I switched to Svelte from React Native and Flutter, even following the same prompting practices. The AI is just more proficient in certain tech stacks." Alan discovered that some frameworks and languages work dramatically better with AI than others, likely due to the amount of training data available. His e-learning platform attempts with React Native and Flutter kept breaking, but switching to Svelte with web-based deployment became far more stable. This suggests a crucial strategy: choose mainstream, well-documented technologies when planning AI-assisted projects. From Coding to Living with AI Alan has completely stopped using traditional search engines, relying instead on LLMs for everything from finding technical documentation to getting recommendations for books based on his interests. While he acknowledges the risk of hallucinations, he finds the semantic understanding capabilities too valuable to ignore. He's even used image analysis to troubleshoot his father's cable TV problems and figure out hotel air conditioning controls. The Agile Validation "My only fear is confirmation bias—but the conclusion I see other experienced developers reaching is that the only way to make LLMs work is by making them use agility. So look at who's dead now." Alan notes the irony that the AI coding tools that actually work all require traditional software engineering best practices: small iterations, test-driven development, continuous integration, and explicit refactoring. The promise of "just describe what you want" falls apart without these disciplines. Rather than replacing software engineering principles, AI tools seem to validate their importance. About Alan Cyment Alan Cyment is a consultant, trainer, and facilitator based in Buenos Aires, specializing in organizational fluency, agile leadership, and software development culture change. A Certified Scrum Trainer with deep experience across Latin America and Europe, he blends agile coaching with theatre-based learning to help leaders and teams transform. You can link with Alan Cyment on LinkedIn.

For episode 611 of the BlockHash Podcast, host Brandon Zemp is joined by Tim Lewis, Co-founder of tea.xyz.Tea Protocol's CoinList token launch comes at a pivotal moment as critical open-source infrastructure faces a funding crisis. With Shipyard ceasing support for libp2p, the networking backbone powering Ethereum, IPFS, and $100B+ worth of blockchain networks, on September 30th due to resource constraints, Tea.xyz's blockchain-based solution for compensating open-source maintainers has never been more relevant.  Founded by Homebrew creator Max Howell, Tea represents the convergence of crisis and solution, demonstrating how crypto can finally solve real infrastructure problems rather than fueling speculation. ⏳ Timestamps: (0:00) Introduction(1:17) Who is Tim Lewis?(6:10) What is Tea Protocol?(10:36) Solutions for open source software development(18:45) Dev incentivization & contributors(20:52) Tea Token Sale(22:47) Tea roadmap(26:12) Events & Conferences(27:25) Tea website, socials & community 

Conference videos

A couple of years ago, I tweeted that “the best tech stack is the one you already know.” To this day, this is one of my most resonating tweets. People keep bringing it back, and founders who've been around for a while seem to particularly agree with it. But AI changes things. Or does it?This episode of The Bootstraped Founder is sponsored by Paddle.comThe blog post: https://thebootstrappedfounder.com/the-best-tech-stack-in-the-age-of-ai/ The podcast episode: https://tbf.fm/episodes/417-the-best-tech-stack-in-the-age-of-aiCheck out Podscan, the Podcast database that transcribes every podcast episode out there minutes after it gets released: https://podscan.fmSend me a voicemail on Podline: https://podline.fm/arvidYou'll find my weekly article on my blog: https://thebootstrappedfounder.comPodcast: https://thebootstrappedfounder.com/podcastNewsletter: https://thebootstrappedfounder.com/newsletterMy book Zero to Sold: https://zerotosold.com/My book The Embedded Entrepreneur: https://embeddedentrepreneur.com/My course Find Your Following: https://findyourfollowing.comHere are a few tools I use. Using my affiliate links will support my work at no additional cost to you.- Notion (which I use to organize, write, coordinate, and archive my podcast + newsletter): https://affiliate.notion.so/465mv1536drx- Riverside.fm (that's what I recorded this episode with): https://riverside.fm/?via=arvid- TweetHunter (for speedy scheduling and writing Tweets): http://tweethunter.io/?via=arvid- HypeFury (for massive Twitter analytics and scheduling): https://hypefury.com/?via=arvid60- AudioPen (for taking voice notes and getting amazing summaries): https://audiopen.ai/?aff=PXErZ- Descript (for word-based video editing, subtitles, and clips): https://www.descript.com/?lmref=3cf39Q- ConvertKit (for email lists, newsletters, even finding sponsors): https://convertkit.com?lmref=bN9CZw

On this episode of Screaming in the Cloud, Corey welcomes back Chris Weichel, CTO of Ona (formerly Gitpod). Chris explains the rebrand and why Ona is building for a future where coding agents, not just humans, write software.They discuss what changes when agents spin up environments, why multi-agent workflows feel addictive, and how Ona is solving the scaling and safety challenges behind it.If you're curious about the next wave of software engineering and how AI will reshape developer tools, this episode is for you.About Chris: Chris Weichel is the Chief Technology Officer at Ona (formerly Gitpod), where he leads the engineering team behind the company's cloud-native development platform. With more than two decades of experience spanning software engineering and human–computer interaction, Chris brings a rare combination of technical depth and user-centered perspective to the systems he helps design and build.He is passionate about creating technology that empowers people and tackling complex engineering challenges. His expertise in cloud-native architecture, programming, and digital fabrication has earned him multiple publications, patents, and industry awards. Chris is continually exploring new opportunities to apply his broad skill set and enthusiasm for building transformative technology in both commercial and research settings.Show Highlights(00:00) Introduction to Modern Software Interfaces(00:55) Welcome to Screaming in the Cloud(01:02) Introducing Chris Weichel and Ona(02:23) The Evolution from Git Pod to Ona(03:26) Challenges and Insights on Company Renaming(05:16) The Changing Landscape of Software Engineering(05:54) The Role of AI in Code Generation(12:04) The Importance of Development Environments(15:44) The Future of Software Development with Ona(21:31) Practical Applications and Challenges of AI Agents(30:01) The Economics of AI in Software Development(38:11) The Future Vision for Ona(39:41) Conclusion and Contact InformationLinks: Christian Weichel LinkedIn: https://www.linkedin.com/in/christian-weichel-740b4224/?originalSubdomain=deOna: https://ona.com/https://csweichel.de/Sponsor: Ona: https://ona.com/

Where are we at in software development? Is software development going away? How is AI changing what it means to be a software developer? Is it possible to get a job as a software developer? These are the questions we will answer in today's episode of Dev Questions.Website: https://www.iamtimcorey.com/ Ask Your Question: https://suggestions.iamtimcorey.com/ Sign Up to Get More Great Developer Content in Your Inbox: https://signup.iamtimcorey.com/

In this episode, Sean and Kelly welcome Pritesh Patel, a computer scientist specializing in AI who brings over 20 years of experience from companies like Turner Broadcasting, Walmart, and GE to his current role at Fisher Phillips law firm. Pritesh shares fascinating insights about implementing AI in knowledge-based industries, from automating his parents' frozen yogurt shop to helping lawyers transform their workflows. The conversation explores crucial concepts like the "Jobs to Be Done" framework, which emphasizes focusing on outcomes rather than getting stuck in existing processes. Pritesh explains how he approaches AI education through playfulness and intuition-building—whether that's getting Batman to sing "Twinkle, Twinkle Little Star" in ChatGPT or creating AI personalities that debate humans. The discussion touches on the importance of maintaining accountability while delegating responsibility to AI tools, the power of curiosity in adoption, and how reinforcement learning might shape the future of AI integration. Key resources mentioned: - Strategyn Jobs to Be Done Framework (https://strategyn.com/) - Tony Ulwick's innovation methodology - NotebookLM (https://notebooklm.google.com/) - Google's AI-powered research tool - Suno.ai (https://suno.com/) - AI music generation platform - OpenAI's Real-time API for voice interactions Special Guest: Pritesh Patel.

Meetups and Conferences

Connect with Will at: https://bsky.app/profile/wiverson.com https://www.linkedin.com/in/wiverson Mentioned during the series: Will's Youtube channel: https://changenode.com/ https://www.youtube.com/@ChangeNode Robots, Trump, manufacturing: https://youtu.be/kdHOwXw2B2g?si=vAqzrR5yj3ZRS4do Svelte: https://madewithsvelte.com/ui-library The post 309 Are Software Development jobs GONE FOR GOOD—or just Evolving? first appeared on Agile Noir.

Expo SDK 54 and React Native 0.81 are a perfect match—and our hosts Mazen Chami, Frank Calise, and Tyler Williams are here to break it all down. In this episode, they dive deep into everything new in Expo SDK 54, from faster precompiled iOS builds to the sleek Liquid Glass feature and Android 16 support. If you want the complete rundown of what's fresh, powerful, and ready to use in Expo SDK 54, this episode has you covered. Show NotesExpo SDK 54 beta is now availablePrecompiling the Expo SDK for iOSExpo AutolinkingInfinite Red's articlePhil Pluckthun's article Connect With Us!Mazen Chami: @mazenchamiFrank Calise: @frankcaliseTyler Williams: @coolsoftwaredevReact Native Radio: @reactnativerdio This episode is brought to you by Infinite Red!Infinite Red is an expert React Native consultancy located in the USA. With nearly a decade of React Native experience and deep roots in the React Native community (hosts of Chain React and the React Native Newsletter, core React Native contributors, creators of Ignite and Reactotron, and much, much more), Infinite Red is the best choice for helping you build and deploy your next React Native app.

In this episode of Tech Bytes, Dan Hafner speaks with Tatiana Kobzar, the founder of Diversito, an award-winning software development company. They discuss the journey of building a software company, the common blind spots startups face, the importance of gamification in user engagement, and the challenges of managing multiple roles as an entrepreneur. Tatiana shares insights on how to motivate users and the significance of understanding user experience in product development. The conversation emphasizes the need for effective marketing strategies and the value of documentation in software development.

This episode was recorded at https://www.imaginationinaction.co/  Get access to metatrends 10+ years before anyone else - https://qr.diamandis.com/metatrends    Amjad Masad is the Co-Founder & CEO of Replit Salim Ismail is the founder of OpenExO Dave Blundin is the founder & GP of Link Ventures  – Connect with Amjad: https://replit.com/  X: https://x.com/amasad  Connect with Peter: X Instagram Connect with Dave: X LinkedIn Connect with Salim: X Listen to MOONSHOTS: Apple YouTube – *Recorded on Sep 9th, 2025 *The views expressed by me and all guests are personal opinions and do not constitute Financial, Medical, or Legal advice. Learn more about your ad choices. Visit megaphone.fm/adchoices

This interview was recorded for the GOTO Book Club.http://gotopia.tech/bookclubRead the full transcription of the interview hereAshley Peacock - Staff Software Engineer at Simply Business & Author of "Serverless Apps on Cloudflare" & "Creating Software with Modern Diagramming Techniques"Ricky Robinett - VP Developer Relations & Community at CloudflareRESOURCESAshleyhttps://twitter.com/_ashleypeacockhttps://www.linkedin.com/in/ashley-peacock-133749120https://medium.com/@ashley-peacockhttps://github.com/apeacock1991Rickyhttps://twitter.com/rickyrobinetthttps://www.linkedin.com/in/rickyrobinetthttps://about.me/rickyrobinetthttps://github.com/rickyrobinettLinkshttps://www.cursor.comDESCRIPTIONRicky Robinett interviews Ashley Peacock, author of "Serverless Apps on Cloudflare", about the developer platform side of Cloudflare. Ashley explains how Cloudflare has evolved from primarily a security company to a full-fledged developer platform with global deployment capabilities, databases, caching solutions, and AI tools.They discuss the unique aspects of Cloudflare's architecture, including global deployment by default, bindings that simplify resource connections without requiring secrets management, and excellent local development experience.Ashley highlights several Cloudflare products including Workers (serverless functions), D1 (SQLite database), KV (key-value store), R2 (object storage), Durable Objects, and AI offerings like Workers AI and AI Gateway. The conversation covers developer experience, using AI assistants for coding, and the benefits of Cloudflare's approach to simplifying cloud development.RECOMMENDED BOOKSAshley Peacock • Serverless Apps on CloudflareAshley Peacock • Creating Software with Modern Diagramming TechniquesJeroen Mulder • Multi-Cloud Strategy for Cloud ArchitectsCrossing BordersCrossing Borders is a podcast by Neema, a cross border payments platform that...Listen on: Apple Podcasts SpotifyBlueskyTwitterInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

Welcome to episode #1002 of Thinking With Mitch Joel (formerly Six Pixels of Separation). What if code isn't just software, but the culture script of our age shaping what we notice, how we decide and who holds power? That's the provocation at the heart of Sam Arbesman's new book, The Magic Of Code - How Digital Language Created And Connects Our World - And Shapes Our Future, which he uses to reveal how programming moves from the screen into the fabric of everyday life. Sam is Scientist in Residence at Lux Capital and a visiting scholar at Harvard. He connects emerging technologies with human systems and helps founders, leaders and the rest of us make sense of complexity. He is also the author of two other influential books (The Half-Life of Facts and Overcomplicated). In this episode, we get a plain-English tour of why coding now functions as cultural literacy, why “vibe coding” and natural-language tools lower barriers without removing responsibility, and how to think clearly about the trade-offs when AI accelerates creation but also amplifies hidden assumptions. Sam breaks down how to treat algorithms less like oracles and more like instruments, demystifying engagement mechanics on social platforms, highlighting the shrinking shelf life of facts and offering ways to keep agency when tools get smarter and more opaque. These are practical frames for navigating complex systems (and their failure modes), along with a humane case for humility in product and policy and a reminder that the goal isn't more tech for its own sake, but better versions of ourselves using it. If you care about where code, culture and creativity meet… and how to keep your bearings as the ground shifts… this one delivers both the big picture and next steps for smarter, more intentional use of the tools we're all inheriting. Enjoy the conversation... Running time: 56:47. Hello from beautiful Montreal. Listen and subscribe over at Apple Podcasts. Listen and subscribe over at Spotify. Please visit and leave comments on the blog - Thinking With Mitch Joel. Feel free to connect to me directly on LinkedIn. Check out ThinkersOne. Here is my conversation with Sam Arbesman. The Magic Of Code - How Digital Language Created And Connects Our World - And Shapes Our Future. The Half-Life of Facts. Overcomplicated. Lux Capital. Sign up for Sam's newsletter. Follow Sam on LinkedIn. Chapters: (00:00) - Exploring the Role of a Scientist in Residence. (03:08) - The Evolution of Knowledge and Information. (05:50) - The Importance of Coding in Modern Society. (08:54) - Demystifying Coding and Access to Technology. (12:11) - Cultural Shifts in Technology Perception. (15:08) - Understanding the Complexity of Code. (17:58) - Code as the Grammar of Modern Civilization. (20:48) - The Impact of Code on Society. (24:08) - The Future of AI and Coding. (32:58) - The Evolution of Programming. (36:14) - Vibe Coding: The Future of Software Development. (39:44) - Democratizing Software: Customization for Everyone. (43:09) - The Complexity of Technology and Trust. (48:28) - Understanding Complex Systems. (51:58) - Human Limitations in Technology. (54:09) - The Role of Technology in Shaping Humanity.

BONUS: Jochen Issing on Building High-Performing Engineering Teams In this BONUS episode, we explore the fascinating journey of Jochen Issing, an engineering leader who brings unique insights from his background as a handball player and band member to building exceptional software development teams. From sports courts and music stages to engineering leadership, Jochen shares practical wisdom on psychological safety, team dynamics, and creating cultures where the best ideas win. From Sports and Music to Software Leadership "As soon as you complain about each other, you are starting to lose." Jochen's unconventional background as a handball player and band member has profoundly shaped his approach to engineering leadership. Drawing from team sports, he discovered that frustration leads to losing in both athletics and technology work. Great players in great teams optimize for the team's results, not individual glory. This translates directly to software development where great engineers slow down to make the team faster, recognizing that collective success trumps individual achievement. The lesson from the handball court is clear: when team members start blaming each other, they create a losing mindset that becomes self-fulfilling. Breaking the 10X Engineer Myth "It's not your success that makes our success, it's our success that makes your success." The mythology of the 10X engineer remains pervasive in software development, but Jochen challenges this with insights from team dynamics. The "hero culture" in companies often emerges when systems are already broken, requiring someone to step in and save the day. While we celebrate these heroes, we forget to ask the crucial question: how did we end up needing a hero in the first place? True high-performing teams don't require heroic individual efforts because they've built sustainable systems and shared knowledge. The goal isn't to eliminate talented individuals but to ensure that even the most skilled engineers can take time off without the organization grinding to a halt. Creating Psychological Safety Through Vulnerability "When psychological safety is missing, I try to ask ignorant questions - expose myself as being the least experienced person in the room." Building psychological safety requires intentional strategies that go beyond good intentions. Jochen employs a counterintuitive approach: when he senses team members hesitating to speak up, he deliberately asks "ignorant" questions to position himself as the least knowledgeable person in the room. This modeling behavior demonstrates that it's safe to admit uncertainty and ask questions. He also builds a culture of "challenging ourselves" by implementing ritualized dissent - assigning someone the specific job of finding flaws in proposed solutions. This prevents the dangerous harmony that can emerge when teams agree too quickly without proper scrutiny. The Power of the Expectation Sheet "I want people to share with me what might even drive them away from the company." Trust forms the foundation of effective team relationships, but building it requires explicit frameworks. Jochen uses an "expectation sheet" (See a prototype here Google Doc)- a document that formalizes mutual expectations between him and his team members. This tool establishes that he wants open, honest communication about everything, including situations that might drive someone to leave the company. The key principle is that he will never share confidential information or use personal disclosures against team members. This creates a relationship where he serves as both a representative of the company when necessary and a personal advocate for his team members when they need support navigating organizational challenges. Team-Centric Productivity and Collaboration "The team is the unit of productivity and delivery, not the individual." Effective engineering leadership requires balancing individual desires with team outcomes. Jochen emphasizes that while people naturally want to say "I did this," the focus must remain on team impact. This involves creating shared understanding of collective goals while still addressing individual needs and growth aspirations. Practical strategies include using on-call rotations to identify knowledge silos, implementing pair programming and mob programming to reinforce collaborative work patterns, and designing tasks that allow individuals to take ownership while remaining embedded in team efforts. The analogy to band dynamics is apt - when someone brings a song idea to the band, it evolves through collaboration into something different and usually better than the original vision. Building Sustainable High Performance "Great engineers slow down to make the team faster - which is how we get better teams." Sustainable high performance emerges when senior engineers invest in lifting the entire team rather than maximizing their individual output. This means senior staff level engineers focus less on their personal contributions and more on forming "tribes" across teams, coaching junior engineers, and building organizational capability. The measure of success shifts from individual heroics to collective achievement - if problems consistently require the same person to fix them, the team hasn't truly succeeded in building sustainable systems and shared knowledge. Recommended Resources for Further Reading Jochen recommends several foundational books for understanding team dynamics and engineering leadership. "The Culture Code" by Daniel Coyle explores the structure of high-performing teams and debunks myths about command-and-control leadership. "Product Development Flow" by Reinertsen provides the scientific foundation behind agile methodologies and explains what teams are really trying to solve. "The Culture Map" by Erin Meyer offers insights on working with diverse cultures and backgrounds to bring out the best in each team member. "Coaching Agile Teams" by Lyssa Adkins serves as a practical guide for developing coaching skills in technical environments. And our very own Scrum Master Toolbox podcast provides ongoing insights and real-world experiences from practitioners in the field. About Jochen Issing Jochen is an engineering leader who's all about building great teams and better developer experiences. From audio tech and cloud platforms to monorepos and feedback culture, he's done it all. A former bandmate and handball player, Jochen brings heart, trust, and collaboration into everything he builds with his teams. You can connect with Jochen Issing on LinkedIn and connect with Jochen Issing on Twitter.

Thanks Gabriel Augendre for guest co-hosting this episode!Visit cupogo.dev for all the links.

This week, Mazen is joined by Infinite Red teammates Frank Calise and Tyler Williams to unpack everything included in the huge React Native 0.81 release. They cover Android 16 support, precompiled iOS builds, and many other updates! Show NotesReact Native 0.81 Blog ArticleExpo SDK 54 Beta Blog Article Connect With Us!Mazen Chami: @mazenchamiFrank Calise: @frankcaliseTyler Williams: @coolsoftwaredevReact Native Radio: @reactnativerdio This episode is brought to you by Infinite Red!Infinite Red is an expert React Native consultancy located in the USA. With nearly a decade of React Native experience and deep roots in the React Native community (hosts of Chain React and the React Native Newsletter, core React Native contributors, creators of Ignite and Reactotron, and much, much more), Infinite Red is the best choice for helping you build and deploy your next React Native app.

Cursor, the AI code editor, recently integrated with Linear, a project management tool, enabling developers to assign tasks directly to Cursor's background coding agent within Linear. The collaboration felt natural, as Cursor already used Linear internally. Linear's new agent-specific API played a key role in enabling this integration, providing agents like Cursor with context-aware sessions to interact efficiently with the platform.Developers can now offload tasks such as fixing issues, updating documentation, or managing dependencies to the Cursor agent. However, both Linear's Tom Moor and Cursor's Andrew Milich emphasized the importance of giving agents clear, thoughtful input. Simply assigning vague tasks like “@cursor, fix this” isn't effective—developers still need to guide the agent with relevant context, such as links to similar pull requests.Milich and Moor also discussed the growing value and adoption of autonomous agents, and hinted at a future where more companies build agent-specific APIs to support these tools. The full interview is available via podcast or YouTube.Learn more from The New Stack about the latest in AI and development in Cursor AI and Linear:  Install Cursor and Learn Programming With AI HelpUsing Cursor AI as Part of Your Development WorkflowAnti-Agile Project Tracker Linear the Latest to Take on JiraJoin our community of newsletter subscribers to stay on top of the news and at the top of your game. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

This interview was recorded for the GOTO Book Club.http://gotopia.tech/bookclubRead the full transcription of the interview hereSy Brand - Author of "Building a Debugger" and C++ Developer Advocate at MicrosoftTim Misiak - Systems Engineer at Datadog and Co-Founder of AugmendRESOURCESSyhttps://bsky.app/profile/tartanllama.xyzhttps://x.com/tartanllamahttps://github.com/TartanLLamahttps://uk.linkedin.com/in/sy-brand-36520857https://sybrand.inkhttps://blog.tartanllama.xyzTimhttps://bsky.app/profile/timdbg.comhttps://x.com/timmisiakhttps://github.com/timmisiakhttps://www.linkedin.com/in/tim-misiakhttps://www.timdbg.comLinkshttps://dwarfstd.orghttps://lldb.llvm.orghttps://rr-project.orghttps://undo.ioDESCRIPTIONTim Misiak interviews Sy Brand about their book "Building a Debugger". Sy, who has a background in GPU compilers and debuggers, discusses how implementing a debugger offers profound insights into computer systems.The conversation explores the unexpected complexities of debugging fundamentals like stack unwinding and code stepping. They examine how debugging interfaces have evolved and the challenges posed by backward compatibility and language evolution.Sy highlights areas for future advancement in debugging, particularly time travel debugging for non-deterministic issues and better tools for debugging optimized code. Throughout the interview, both experts share fascinating technical details that reveal why debugger implementation serves as an excellent path to deeper understanding of operating systems and hardware.RECOMMENDED BOOKSSy Brand • Building a DebuggerCathy O'Neil • Weapons of Math DestructionCrossing BordersCrossing Borders is a podcast by Neema, a cross border payments platform that...Listen on: Apple Podcasts SpotifyBlueskyTwitterInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

In this episode Shiv is in conversation with Jason Casey, CEO and co-founder of Beyond Identity. Jason talks about his early fascination with technology, his career trajectory, and how he entered cybersecurity. He describes Beyond Identity's mission to eliminate passwords and improve identity verification. Jason shares insights on staying ahead in cybersecurity, touching on topics like AI, supply chain attacks, and trusted computing. He discusses the transition from CTO to CEO, the importance of curiosity and experimentation in both early and mid-career stages, and his personal practices for managing stress and staying grounded.00:25 Jason Casey's Early Fascination with Technology01:22 Journey into Cybersecurity02:23 Understanding the Hacker Mindset03:58 Staying Ahead in Cybersecurity06:57 Fundamentals of AI and Security09:01 Challenges and Innovations in AI Security10:16 Building Secure Systems with AI13:50 The Cost of Real-Time Security15:24 Deterministic vs. Probabilistic Security Controls17:19 The Role of Honeypots in Cybersecurity18:44 Adversarial Tactics and Device Posture21:15 AI in Software Development and Security25:17 Trusted Computing in Aerospace and Defense27:01 Hardware-Based Trusted Computing28:04 Genesis of Beyond Identity29:31 Meeting Jim Clark32:17 Beyond Identity's Mission34:04 Transition from CTO to CEO37:17 Career Tips for Cybersecurity50:06 Personal Practices to Stay Groundedhttps://www.linkedin.com/in/jassoncasey/Jasson Casey currently serves as Chief Executive Officer and Co-Founder at Beyond Identity, where he's built an identity security platform for enterprises to make identity-based attacks impossible.Jasson has 20+ years of experience delivering security and networking products to all markets and customer types, including global enterprises and carriers. He served as CTO at Security Scorecard, Fellow in CyberSecurity with the Center for Strategic and International Studies (CSIS), and as Advisor to IronNet CyberSecurity, a security startup founded by Gen. (Ret) Keith Alexander.Prior to Beyond Identity, Jasson was VP of Engineering at IronNet CyberSecurity and oversaw development of the vendor's revolutionary collective intelligence platform and pioneered new approaches to total network observability, including limitless wire rate packet capture with truly elastic retention abilities.He also brings a long history of innovation advocacy for Software Defined Networks (SDN) through his work founding and leading Flowgrammable, and serving as a member of the Software Leadership Council at the Open Networking Foundation. Previously he held roles in product management, business development and engineering with CenturyTel(CenturyLink), Level3(CenturyLink), and Alcatel(Nokia).Jasson has a BSEE from the University of Texas at Austin and has a Ph.D. in electrical engineering at Texas A&M University.

In this episode of the Investor Fuel Podcast, host Michelle Kesil speaks with real estate agent Cait Hudson about her journey in the real estate industry and the development of her software platform, Nest Hub. Cait shares her experiences as an agent, the challenges she faced, and the innovative solutions she created to improve communication between realtors and buyers. The conversation covers the importance of video marketing, lessons learned in real estate, and the unique features of Nest Hub that aim to streamline the buying process. Cait emphasizes the significance of building relationships and investing in oneself to succeed in the industry.   Professional Real Estate Investors - How we can help you: Investor Fuel Mastermind:  Learn more about the Investor Fuel Mastermind, including 100% deal financing, massive discounts from vendors and sponsors you're already using, our world class community of over 150 members, and SO much more here: http://www.investorfuel.com/apply   Investor Machine Marketing Partnership:  Are you looking for consistent, high quality lead generation? Investor Machine is America's #1 lead generation service professional investors. Investor Machine provides true ‘white glove' support to help you build the perfect marketing plan, then we'll execute it for you…talking and working together on an ongoing basis to help you hit YOUR goals! Learn more here: http://www.investormachine.com   Coaching with Mike Hambright:  Interested in 1 on 1 coaching with Mike Hambright? Mike coaches entrepreneurs looking to level up, build coaching or service based businesses (Mike runs multiple 7 and 8 figure a year businesses), building a coaching program and more. Learn more here: https://investorfuel.com/coachingwithmike   Attend a Vacation/Mastermind Retreat with Mike Hambright: Interested in joining a “mini-mastermind” with Mike and his private clients on an upcoming “Retreat”, either at locations like Cabo San Lucas, Napa, Park City ski trip, Yellowstone, or even at Mike's East Texas “Big H Ranch”? Learn more here: http://www.investorfuel.com/retreat   Property Insurance: Join the largest and most investor friendly property insurance provider in 2 minutes. Free to join, and insure all your flips and rentals within minutes! There is NO easier insurance provider on the planet (turn insurance on or off in 1 minute without talking to anyone!), and there's no 15-30% agent mark up through this platform!  Register here: https://myinvestorinsurance.com/   New Real Estate Investors - How we can work together: Investor Fuel Club (Coaching and Deal Partner Community): Looking to kickstart your real estate investing career? Join our one of a kind Coaching Community, Investor Fuel Club, where you'll get trained by some of the best real estate investors in America, and partner with them on deals! You don't need $ for deals…we'll partner with you and hold your hand along the way! Learn More here: http://www.investorfuel.com/club   —--------------------

The increasing use of AI in software development has led to significant changes in the industry, with 62% of developers now utilizing AI tools. While this has enhanced productivity, it has also resulted in greater code complexity and a decline in code quality. Recent findings from the 2025 GitClear AI Code Quality Research report reveal alarming trends: as AI usage rises, so does the duplication of code, leading to more time spent on refactoring rather than creating new code. This shift indicates a troubling pattern where the ability to manage and simplify complex systems is becoming more critical than simply writing new code. In this discussion, we will explore these challenges and the importance of maintaining high code quality in an AI-driven environment.The landscape of software development has notably transformed in 2024, with 62% of developers now leveraging AI in their workflows. While this integration has significantly boosted productivity, it has also raised concerns regarding code quality and complexity. The discussion reflects on findings from the recent 2025 GitClear AI Code Quality Research report, which analyzed over 211 million lines of code and revealed a troubling trend: as AI usage increases, so does the complexity of software systems. Developers are now dedicating more time to refactoring existing code rather than creating new features. This shift highlights a critical issue in the industry: as AI generates more code, it often leads to duplication and violates the fundamental principle of not repeating oneself. Consequently, the reliance on AI tools may inadvertently increase maintenance challenges and bug vulnerability, requiring developers to adapt their roles and focus on system-level understanding and refactoring expertise to ensure sustainable software development practices.Takeaways: In 2024, 62% of professional developers are using AI in their development process, significantly impacting productivity. The increased use of AI has led to more complex code and larger codebases, affecting overall code quality. Developers are now spending more time refactoring existing code rather than writing new features, which alters their workflow. The 2025 GitClear report shows a troubling rise in code duplication as AI-generated code becomes more common. AI coding tools struggle to understand the full context of projects, leading to increased code duplication and complexity. To address these challenges, organizations must focus on long-term maintainability, including reducing duplication and improving test coverage. Links referenced in this episode:softwarearchitectureinsights.com2025 GitClear AI Code Quality Research Report

Shawn Dsouza: The Database Migration Disaster— Why Software Development Teams Need Psychological Safety 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. Shawn worked with a skilled team migrating a database from local to cloud-based systems, supported by a strong Product Owner. Despite surface-level success in ceremonies, he noticed the team avoided discussing difficult topics. After three months of seemingly smooth progress, they delivered to pre-production only to discover 140 critical issues. The root cause? Unspoken disagreements and tensions that festered beneath polite ceremony facades. The situation deteriorated to the point where a senior engineer quit, teaching Shawn that pausing to address underlying issues doesn't cost time—it builds sustainability. In this segment, we refer to the episodes with Mahesh Jade, a previous guest on the Scrum Master Toolbox podcast. Featured Book of the Week: The Advice Trap by Michael Bungay Stanier Shawn discovered this transformative book when he realized he was talking too much in team meetings despite wanting to add value. The Advice Trap revealed how his instinct to give advice, though well-intentioned, was actually self-defeating. The book taught him to stay curious longer and ask better questions rather than rushing to provide solutions. As Shawn puts it, "The minute you think you have the answer you stop listening"—a lesson that fundamentally changed his coaching approach and helped him become more effective with his teams. Self-reflection Question: When working with teams, do you find yourself jumping to advice-giving mode, or do you stay curious long enough to truly understand the underlying challenges? [The Scrum Master Toolbox Podcast Recommends]

In this episode of Building Better Developers with AI, hosts Rob Broadhead and Michael Meloche revisit an earlier conversation—this time through the lens of AI—to explore how constructive communication in software development creates healthier teams and better code. By analyzing their original “Advocating vs. Arguing” discussion, they uncover new ways to transform conflict into collaboration. “The goal is never to win. The goal is to find the best solution.” – Rob Broadhead What Constructive Communication Really Means Rob draws a clear line between two mindsets: Constructive communication invites evidence, empathy, and openness. Defensive arguing focuses on winning, often shutting down valuable ideas. This subtle difference determines whether a team works together to solve problems or gets stuck in endless debates. Why Constructive Communication Improves Software Development Software projects depend on diverse skills and experiences. When team members communicate constructively: Blind spots shrink. Different perspectives uncover hidden issues. Technical debt decreases. Shared understanding prevents costly rework. Client trust grows. Positive dialogue strengthens long-term relationships. Rob highlights how even an outsider's insight—like a .NET developer's idea on a Python project—can spark innovative solutions. Practical Steps to Encourage Constructive Communication Michael offers proven techniques to keep discussions positive and productive: Ask clarifying questions. Instead of “That won't work,” try “How do you see that working in this context?” Restate what you heard. Confirm understanding before you respond. Stay curious. Open-ended questions invite deeper exploration. “No is a conversation killer. Replace it with ‘Let's consider that.'” – Michael Meloche Spotting When Communication Turns Unproductive Arguments often start subtly. Watch for these warning signs: Absolutes such as “always” or “never.” Interrupting or talking over teammates. Ego-driven choices that ignore user needs or project goals. Rob recommends slowing the pace when tempers rise—pause the meeting, schedule a follow-up, or ask everyone to write down their thoughts before reconvening. Agile Practices Support Constructive Communication Rob and Michael agree that Agile's built-in rituals—backlog refinement, iterative feedback, and sprint reviews—naturally encourage constructive communication in software development. If a team frequently argues, it may be skipping these essential steps. Michael also suggests a weekly “water-cooler” session where team members share new ideas or lessons learned. These informal gatherings nurture creativity and trust. Leadership Sets the Tone Managers and leads can reinforce constructive habits by: Checking in with teammates who seem defensive or frustrated. Offering mentoring or personal support when tension surfaces. Encouraging team traditions—from inside jokes to shared hobbies—that build rapport. Rob observes that the best teams always share a unique bond, whether it's dad jokes or a favorite game, which helps them weather stressful moments. Reader Challenge: Practice Constructive Communication This Week Your Mission: Over the next seven days, pick one team interaction—a stand-up, code review, or planning meeting—and intentionally practice constructive communication in software development. Steps to Try: Listen First. Before offering your idea, restate someone else's point to confirm understanding. Replace “No” with Curiosity. When you disagree, ask an open question like “How do you see that working with our current sprint goals?” Log the Outcome. After the meeting, jot down what changed: Did the discussion stay more positive? Did new solutions surface? Share your results with your team—or even comment on the blog post—to inspire others. Challenge yourself: Can you turn at least one potential argument into a moment of advocacy this week? Key Takeaway: Build a Culture of Constructive Communication This episode underscores that constructive communication in software development is more than a soft skill—it's a project-saver. By listening first, asking better questions, and validating every voice, teams can replace conflict with collaboration and move projects forward with confidence. “Choosing one approach together is better than arguing endlessly about the perfect one.” – Rob Broadhead Whether you're leading a sprint, conducting a code review, or gathering requirements, focusing on constructive communication ensures that every idea is heard—and the best solutions rise to the top. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources Honest Communication Is Critical For Consultants When To Vent (never) as part of Consulting Communication Use Written Communication To Improve Your Standing And Career Communication Noise vs. Content The Developer Journey Videos – With Bonus Content Building Better Developers With AI Podcast Videos – With Bonus Content

This interview was recorded for the GOTO Book Club.http://gotopia.tech/bookclubRead the full transcription of the interview hereSteve Pereira - Co-Author of "Flow Engineering" & Principal Consultant at Visible Flow ConsultingAndrew Davis - Co-Author of "Flow Engineering" & Founder at Institute for Transformational LeadershipRESOURCESStevehttps://x.com/steveelsewherehttps://github.com/stevepereirahttps://www.linkedin.com/in/devopstohttps://stevepereira.caAndrewhttps://x.com/andrewdavis_iohttps://github.com/abd3https://www.linkedin.com/in/andrewdavis-iohttps://www.andrewdavis.ioLinkshttps://flowcollective.orgDESCRIPTIONFlow Engineering co-authors Steve Pereira and Andrew Davis discuss their approach to improving workflow visibility in software development and knowledge work. They explore how value stream mapping can be adapted for modern digital work environments, where the work is largely invisible compared to manufacturing settings.The authors explain their five-map framework designed to help teams establish clarity, improve collaboration, and enhance productivity despite busy schedules and constant firefighting. They emphasize the importance of visual collaboration to create shared mental models and the continuing relevance of these practices in an AI-driven future.RECOMMENDED BOOKSSteve Pereira & Andrew Davis • Flow EngineeringAndrew Davis • Mastering Salesforce DevOpsSusanne Kaiser • Adaptive Systems With Domain-Driven Design, Wardley Mapping & Team TopologiesCharles Humble • Professional Skills for Software EngineersSimon Wardley • Wardley Mapping, The KnowledgeSimon Wardley • Wardley MapsCrossing BordersCrossing Borders is a podcast by Neema, a cross border payments platform that...Listen on: Apple Podcasts SpotifyBlueskyTwitterInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

Go 1.25.1 and Go 1.24.7 are released

Bret Taylor is the CEO of Sierra and Chairman of the Board of OpenAI. He previously served as co-CEO of Salesforce. I sat down with Bret to explore how the AI revolution compares to previous platform shifts and what it means for both startups and incumbents navigating this transition. (00:00) Introduction and Recent Milestone (00:38) AI Market and Historical Comparisons (02:30) Competitive Landscape and Business Models (06:02) Outcome-Based Pricing and Value Creation (13:52) Technological Shifts and Business Transitions (26:32) Adoption Challenges and Forward Deployed Engineering (37:21) Early Investment in Snowflake and Cloud Strategy (38:02) Enterprise Software Market Dynamics (38:38) AI Agents and Implementation Costs (41:06) Democratization of Software Development (43:35) The Future of Software Companies and AI Agents (49:36) Consumer Behavior and AI Agents (58:56) The Role of AI in Customer Experience (01:01:25) Career Advice in the Age of AI Executive Producer: Rashad Assir Mixing and editing: Justin Hrabovsky Check out Unsupervised Learning, Redpoint's AI Podcast: https://www.youtube.com/@UCUl-s_Vp-Kkk_XVyDylNwLA

Chas Jhin, Director of Engineering for Discord, joins our hosts to unpack Discord's adoption of React Native. Chas opens up about Discord's experience adopting React Native, performance challenges, and the New Architecture. Show NotesDiscord's Switch Android to React Native (2022)Supercharging Discord Mobile (2025)Achieving Native iOS performance with React Native (2019) React Native Mornings Connect With Us!Chas Jhin: @chasjhinJamon Holmgren: @jamonholmgrenRobin Heinze: @robinheinzeMazen Chami: @mazenchamiReact Native Radio: @reactnativerdio This episode is brought to you by Infinite Red!Infinite Red is an expert React Native consultancy located in the USA. With nearly a decade of React Native experience and deep roots in the React Native community (hosts of Chain React and the React Native Newsletter, core React Native contributors, creators of Ignite and Reactotron, and much, much more), Infinite Red is the best choice for helping you build and deploy your next React Native app.

This is the Engineering Culture Podcast, from the people behind InfoQ.com and the QCon conferences. In this podcast, Shane Hastie, Lead Editor for Culture & Methods, spoke to Thanos Diacakis about how teams often struggle with software delivery. He proposes a shift in mental models and a four-step framework to systematically improve software development by focusing on bottlenecks, balancing different types of work beyond just feature delivery, and investing 20-30% of effort in improving how the team works. Read a transcript of this interview: http://bit.ly/4gxwKNb Subscribe to the Software Architects' Newsletter for your monthly guide to the essential news and experience from industry peers on emerging patterns and technologies: https://www.infoq.com/software-architects-newsletter Upcoming Events: InfoQ Dev Summit Munich (October 15-16, 2025) Essential insights on critical software development priorities. https://devsummit.infoq.com/conference/munich2025 QCon San Francisco 2025 (November 17-21, 2025) Get practical inspiration and best practices on emerging software trends directly from senior software developers at early adopter companies. https://qconsf.com/ QCon AI New York 2025 (December 16-17, 2025) https://ai.qconferences.com/ QCon London 2026 (March 16-19, 2026) https://qconlondon.com/ The InfoQ Podcasts: Weekly inspiration to drive innovation and build great teams from senior software leaders. Listen to all our podcasts and read interview transcripts: - The InfoQ Podcast https://www.infoq.com/podcasts/ - Engineering Culture Podcast by InfoQ https://www.infoq.com/podcasts/#engineering_culture - Generally AI: https://www.infoq.com/generally-ai-podcast/ Follow InfoQ: - Mastodon: https://techhub.social/@infoq - X: https://x.com/InfoQ?from=@ - LinkedIn: https://www.linkedin.com/company/infoq/ - Facebook: https://www.facebook.com/InfoQdotcom# - Instagram: https://www.instagram.com/infoqdotcom/?hl=en - Youtube: https://www.youtube.com/infoq - Bluesky: https://bsky.app/profile/infoq.com Write for InfoQ: Learn and share the changes and innovations in professional software development. - Join a community of experts. - Increase your visibility. - Grow your career. https://www.infoq.com/write-for-infoq

Join us this week for The Tech Leaders Podcast, where Gareth sits down with Chris Moore, European President at Veeva Systems. Chris talks about the impact AI will have on software development and data security, how technology has transformed the life sciences industry, and the long-term implications of Covid on drug development.On this episode, Chris and Gareth discuss how Chris helped make Veeva Europe more European, the importance of understanding the opportunities and threats associated with new technologies, and why the Y2K bug was a beautiful anti-climax.Timestamps:ICI, Kinesis and PWC (3:40)IBM, EY and living abroad (10:28)Making Veeva Europe more European (17:30)The impact of Covid on drug development (29:05)The evolution of the CIO (33:00)AI: Hopes, fears and the impact on software development and pharma (36:33)Advice for 21-year-old Chris (51:46)https://www.bedigitaluk.com/

In this conversation, Leo interviews Alex Smereczniak, the founder of Franzy, a platform designed to streamline the buying and selling of franchise businesses. Alex discusses the innovative use of AI in his business model, the importance of adapting to market demands, and the significance of building relationships in the industry. He emphasizes the emotional aspect of purchasing a business and shares insights on enhancing client experiences through thoughtful engagement and support. Professional Real Estate Investors - How we can help you: Investor Fuel Mastermind:  Learn more about the Investor Fuel Mastermind, including 100% deal financing, massive discounts from vendors and sponsors you're already using, our world class community of over 150 members, and SO much more here: http://www.investorfuel.com/apply   Investor Machine Marketing Partnership:  Are you looking for consistent, high quality lead generation? Investor Machine is America's #1 lead generation service professional investors. Investor Machine provides true ‘white glove' support to help you build the perfect marketing plan, then we'll execute it for you…talking and working together on an ongoing basis to help you hit YOUR goals! Learn more here: http://www.investormachine.com   Coaching with Mike Hambright:  Interested in 1 on 1 coaching with Mike Hambright? Mike coaches entrepreneurs looking to level up, build coaching or service based businesses (Mike runs multiple 7 and 8 figure a year businesses), building a coaching program and more. Learn more here: https://investorfuel.com/coachingwithmike   Attend a Vacation/Mastermind Retreat with Mike Hambright: Interested in joining a “mini-mastermind” with Mike and his private clients on an upcoming “Retreat”, either at locations like Cabo San Lucas, Napa, Park City ski trip, Yellowstone, or even at Mike's East Texas “Big H Ranch”? Learn more here: http://www.investorfuel.com/retreat   Property Insurance: Join the largest and most investor friendly property insurance provider in 2 minutes. Free to join, and insure all your flips and rentals within minutes! There is NO easier insurance provider on the planet (turn insurance on or off in 1 minute without talking to anyone!), and there's no 15-30% agent mark up through this platform!  Register here: https://myinvestorinsurance.com/   New Real Estate Investors - How we can work together: Investor Fuel Club (Coaching and Deal Partner Community): Looking to kickstart your real estate investing career? Join our one of a kind Coaching Community, Investor Fuel Club, where you'll get trained by some of the best real estate investors in America, and partner with them on deals! You don't need $ for deals…we'll partner with you and hold your hand along the way! Learn More here: http://www.investorfuel.com/club   —--------------------

Today, we're joined by Mats Persson, CEO of Umbraco, provider of the world's leading open-source CMS platform. We talk about:The impacts of AI in developing and managing contentWhy content management systems will always surviveThe pluses and minuses of open source and AI helping write codeRisks of being too enthusiastic about your own opportunity & productThe challenges of GEO (Generative Engine Optimization), considering there's not one standard system

In this episode of the Business of Laravel podcast, Matt Stauffer sits down with Patrick O'Meara and Stephen Quayle, co-founders of Maintainly, a CMMS (computerized maintenance management system) company built on Laravel. They dive into the evolution of Maintainly, the challenges of building and scaling software, and the unique role Laravel plays in their operations.The conversation explores how industry expertise, thoughtful hiring, and a strong remote culture have shaped their company. Patrick and Stephen also share the personal influences behind their journey and their vision for the future of Maintainly.Matt Stauffer TwitterTighten WebsiteMaintainly WebsiteSteven Quayle on LinkedIn Patrick O'Meara TwitterPatrick O'Meara on BlueSkyPatrick O'Meara on GitHubPatrick O'Meara on LinkedInNever Write Another Loop Again by Adam WathanHow to Win Friends and Influence People by Dale CarnegieGood to Great by Jim CollinsEditing and transcription sponsored by Tighten.

AI Insights: Anthropic's Settlement, Coding Realities, and Tesla's Robot Flop In this episode of #Trending, host Jim Love discusses the possibility of having a live studio audience for the popular AI Weekend Show, Project Synapse. Key stories include Anthropic's $1.5 billion copyright settlement over unauthorized use of authors' books to train AI, a poll showing senior developers often rely on AI-generated code, and Broadcom's admission of selling VMware shelfware. The episode also highlights the underwhelming demo of Tesla's Optimist robot and the debate over an AI-generated threatening voicemail involving an Ontario municipal counselor. 00:00 Introduction and Audience Invitation 00:22 Top News Stories 02:11 AI in Software Development 04:53 Broadcom's VMware Shelfware Issue 06:45 Tesla's Robot Servant Demo 09:10 AI-Generated Threat Voicemail 10:46 Conclusion and Audience Invitation Reminder

CTO Series: Toni Sallanmaa on Scaling Engineering Teams and Aligning Tech with Business Goals In this BONUS episode, we explore the journey of scaling technology teams and maintaining alignment between engineering and business objectives with Toni Sallanmaa, CTO at Funidata. Toni shares invaluable insights from leading the development of Sisu, a cutting-edge student information system serving over 100,000 Finnish university users, and discusses practical strategies for growing engineering organizations while preserving company culture. The Genesis of Leadership in Technology "I understood what I was really responsible for. I'm interested in the business we are running—the business adds meaning to the work." Toni's approach to technology leadership was fundamentally shaped by a pivotal moment early in his career when he first gained influence over system development and technology choices. After working with large-scale systems for 20 years, this moment of responsibility revelation transformed his perspective from purely technical to business-focused. He emphasizes that infinite curiosity drives success in tech businesses, and understanding the business context gives meaningful purpose to technical work. Bridging the Gap Between Tech and Product "Don't separate Tech from Product. We established a common language between product and technology people." One of Toni's most significant insights centers on eliminating the traditional divide between technology and product teams. As Funidata grew from a small startup to a 70-person organization, the challenges of maintaining alignment became apparent. Their solution involved several key practices: Teaching developers the language of the product domain  Banning confusing technical terms that create communication barriers Workshopping product language to ensure clarity Keeping entity names deliberately vague until true understanding emerges This approach draws heavily from Domain Driven Design principles, creating a unified vocabulary that enables seamless collaboration. Collaborative Planning and Transparency "We use transparency as a collaboration technique. Every team sees what's being proposed as a goal for the next quarter." Funidata implements a unique "marketplace of goals" approach during their quarterly big room planning sessions. Rather than using scaled agile frameworks, they focus on transparency and collaborative goal-setting. Teams present their high-level quarterly plans to each other, creating visibility across the organization. Product owners are embedded within teams, keeping communication distances short and ensuring alignment between technical execution and business objectives. Future-Forward Roadmapping "We talk about the higher level ideas regularly, but let them bubble up from the community. We hold internal hackathons." Toni's approach to roadmapping balances strategic vision with grassroots innovation. They maintain an internal technology roadmap that addresses emerging trends like AI, while allowing ideas to organically emerge from the engineering community. Internal hackathons serve as catalysts for innovation, providing structured opportunities for teams to explore new technologies and approaches that might inform future roadmap decisions. Scaling Challenges and Cultural Preservation "The biggest challenge is not technology, it was the rapid scaling of technology teams. When you scale up, keep the culture in mind." The most significant challenge Toni faced wasn't technical but organizational—rapidly scaling teams while preserving company culture. Growing from 10 to 50 people required evolving processes, from establishing internal forums for architectural discussions to implementing continuous integration flows. The key was identifying pain points proactively and maintaining open discussions with team members throughout the scaling process. Strengthening company culture became essential to successful growth. AI's Impact on Software Development "Productivity is on the rise. We see opportunities like generating test data, but we have strict requirements for cybersecurity, which puts pressure on code quality." Toni views AI's impact on software development with cautious optimism. While productivity gains are evident, particularly in areas like test data generation, the stringent cybersecurity requirements in their domain mean that AI hasn't yet significantly improved code quality where it matters most. The technology shows promise, but implementation must be carefully considered within the context of security and quality requirements. Measuring Engineering Success "We use DORA and SPACE framework. We measure how much of our work is KTLO (Keep The Lights On) and how much is elective development." Funidata employs both DORA and SPACE frameworks to measure engineering organization success. From SPACE, they particularly focus on measuring software team wellbeing, while also tracking the balance between "Keep The Lights On" (KTLO) work and elective development. Using JIRA connected to a data warehouse, they mine extensive data that serves both leadership decision-making and team improvement efforts, ensuring metrics benefit everyone in the organization. Influential Leadership Resources "The organizational books have been more influential to me than purely technical ones." Toni emphasizes that organizational leadership books have shaped his CTO approach more than technical resources. Two key influences stand out: "Team Topologies" for understanding how to structure and scale engineering teams effectively, and "Radical Candor" for building authentic, productive relationships within the organization. You can find a BONUS episode on Team Topologies with the authors Matthew Skeltton and Manuel Pais. About Toni Sallanmaa Toni leads technology and engineering at Funidata, developing Sisu—a cutting-edge student information system serving over 100,000 Finnish university users. Passionate about agile methodologies, system architecture, and software engineering, Toni specializes in technology management, software lifecycle, OOP, and relational databases to deliver innovative, scalable solutions in higher education tech. You can connect with Toni Sallanmaa on LinkedIn.

Infinite Red's own Mark Rickert joins to discuss the new Ignite 11 "Bison" release and the thoughtful changes that went into it! This latest update removes MobX State Tree as the default state management to give developers more flexibility, streamlines everything to new architecture-only, and includes improved light/dark theming right out of the box. He also shared with our hosts why the name of this release is codenamed "BISON"Show NotesIgnite 11: Bison

In this week'sThe New Stack Agents, Zach Lloyd, founder and CEO of Warp, discussed the launch of Warp Code, the latest evolution of the Warp terminal into a full agentic development environment. Originally launched in 2022 to modernize the terminal, Warp now integrates powerful AI agents to help developers write, debug, and ship code. Key new features include a built-in file editor, project-structuring tools, agent-driven code review, and WARP.md files that guide agent behavior. Recognizing developers' hesitation to trust AI-generated code, Warp emphasizes transparency and control, enabling users to inspect and steer the agent's work in real time through "persistent input" and task list updates. While Warp supports terminal workflows, Lloyd says it's now better viewed as an AI coding platform. Interestingly, the launch announcement was delivered from horseback in a Western-themed ad, reflecting Warp's desire to stand out in a crowded field of conventional tech product rollouts. The quirky “Code on Warp” (C.O.W.) branding captured attention and embodied their unique approach.Learn more from The New Stack about the latest in AI and Warp:Warp Goes Agentic: A Developer Walk-Through of Warp 2.0Developer Review of Warp for Windows, an AI Terminal AppHow AI Can Help You Learn the Art of ProgrammingJoin our community of newsletter subscribers to stay on top of the news and at the top of your game.

Sally and Joël kick off a new season of the Bike Shed by asking the question, what exactly is it that we as developers even do around here? Together they discuss their roles as developers, how their workflows and skills have changed over time, the value of context and experience when evaluating different solutions to a problem, why so much of their work revolves around googling error codes, (https://thoughtbot.com/blog/indiana-jones-and-the-crypt-of-cryptic-error-messages) and giving some advice to aspiring junior developers (https://thoughtbot.com/blog/turning-experience-into-growth). — Thanks to our sponsors for this episode Judoscale - Autoscale the Right Way (https://judoscale.com/bikeshed) (check the link for your free gift!), and Scout Monitoring (https://www.scoutapm.com/). Your hosts for this episode have been thoughtbot's own Joël Quenneville (https://www.linkedin.com/in/joel-quenneville-96b18b58/) and Sally Hall (https://www.linkedin.com/in/sallyannahall). If you would like to support the show, head over to our GitHub page (https://github.com/sponsors/thoughtbot), or check out our website (https://bikeshed.thoughtbot.com). Got a question or comment about the show? Why not write to our hosts: hosts@bikeshed.fm This has been a thoughtbot (https://thoughtbot.com/) podcast. Stay up to date by following us on social media - YouTube (https://www.youtube.com/@thoughtbot/streams) - LinkedIn (https://www.linkedin.com/company/150727/) - Mastodon (https://thoughtbot.social/@thoughtbot) - BlueSky (https://bsky.app/profile/thoughtbot.com) © 2025 thoughtbot, inc.

Are long code review cycles killing your engineering team's velocity? Learn how top engineering teams are shipping code faster without sacrificing quality.In this episode, Greg Foster, CTO and co-founder of Graphite, discusses the evolution of code review practices, from the fundamentals of pull requests to the future of AI in code review workflows. He shares the secrets behind how the Graphite team became one of the most productive engineering teams by leveraging techniques like small code changes and stacked PRs (pull requests).Key topics discussed:The evolution of code review from bug-hunting to knowledge sharingBest practices for PRs and why small PRs get better feedbackHow stacked PRs eliminate waiting time in development workflowsThe rise of AI in the code review processWhy AI code review works best as an automated CI checkHow Graphite achieves P99 engineering productivityHiring engineers in the age of AI-assisted codingTimestamps:(00:00) Trailer & Intro(02:21) Career Turning Points(05:11) Now is The Golden Time to Be in Software Engineering(09:08) The Evolution of Code Review in Software Development(14:59) The Popularity of Pull Request Workflow(21:01) Pull Request Best Practices(26:17) The Stacked PR and Its Benefits(34:07) How Graphite Ships Code Remarkably Fast(40:03) The Cool Things About AI Code Review(45:23) Graphite's Unique Recipes for Engineering Productivity(50:55) Hiring Engineers in the Age of AI(55:31) 2 Tech Lead Wisdom_____Greg Foster's BioGreg Foster is the CTO and co-founder of Graphite, an a16z and Anthropic-backed company helping teams like Snowflake, Figma, and Perplexity ship faster and scale AI-generated code with confidence. Prior to Graphite, Greg was a dev tools engineer at Airbnb. There, he experienced the impact of robust internal tooling on developer velocity and co-founded Graphite to bring powerful, AI-powered code review to every team. Greg holds a BS in Computer Science from Harvard University.Follow Greg:LinkedIn – linkedin.com/in/gregmfosterX – x.com/gregmfosterEmail – greg@graphite.devGraphite – graphite.devGraphite X – x.com/withgraphiteLike this episode?Show notes & transcript: techleadjournal.dev/episodes/231.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

- Endorsement of Pete Chambers for Texas Governor (0:10) - Chambers' Commitment to Decentralized Medicine and Humanitarian Efforts (1:41) - Importance of Prompt Engineering in AI (4:26) - AI's Role in Software Development and Prompt Engineering Techniques (5:53) - Prediction of a Major Robotics Hoax (19:27) - Comparison of Mainstream Deodorants and Health Ranger Store Deodorant (28:54) - Health Benefits of Purple Okra and Anthocyanins (40:02) - RFK Jr's Investigation into Psychiatric Medications and School Shootings (42:53) - Texas' Role in the Future of the United States (51:09) - Nutritional Tips for Enjoying Barbecue (55:42) - Energy Consumption and Water Usage by Data Centers (1:08:35) - Impact of Data Centers on Texas' Power Grid (1:19:53) - Economic and Environmental Concerns (1:20:58) - Water and Land Use Conflicts (1:23:37) - Governor's Role and Citizen-Led Governance (1:26:36) - Border Security and Governor Abbott's Performance (1:27:34) - Health and Human Services Expenditures (1:34:46) - Education and Food Security Initiatives (1:49:40) - Challenges of Political Corruption and Centralization (1:51:09) - Vision for Texas' Future (2:08:42) For more updates, visit: http://www.brighteon.com/channel/hrreport NaturalNews videos would not be possible without you, as always we remain passionately dedicated to our mission of educating people all over the world on the subject of natural healing remedies and personal liberty (food freedom, medical freedom, the freedom of speech, etc.). Together, we're helping create a better world, with more honest food labeling, reduced chemical contamination, the avoidance of toxic heavy metals and vastly increased scientific transparency. ▶️ Every dollar you spend at the Health Ranger Store goes toward helping us achieve important science and content goals for humanity: https://www.healthrangerstore.com/ ▶️ Sign Up For Our Newsletter: https://www.naturalnews.com/Readerregistration.html ▶️ Brighteon: https://www.brighteon.com/channels/hrreport ▶️ Join Our Social Network: https://brighteon.social/@HealthRanger ▶️ Check In Stock Products at: https://PrepWithMike.com

This episode is sponsored by Boldly Go! Need fractional Gophering work? Visit boldlygo.tech.For everything Cup o' Go, incl. swag, Patreon, past episodes, and more, please visit our website.GopherCon 2026 location pollGopherCon IndiaGOMAXPROCSCourse: "Introducing Command Line Applications in Go"SQLite benchmarks ★ Support this podcast on Patreon ★

Today, the Elixir Wizards wrap up Season 14 “Enter the Elixirverse.” Dan, Charles, and Sundi look back at some common themes: Elixir plays well with others, bridges easily to access languages and tools, and remains a powerful technology for data flow, concurrency, and developer experience. We revisit the popular topics of the year, from types and tooling to AI orchestration and reproducible dev environments, and share what we're excited to explore next.   We also invite your questions and takeaways to help shape future seasons and conference conversations. Season 14 doubles as a handy primer for anyone curious about how Elixir integrates across the stack.   Key topics discussed in this episode:   * Lessons from a season of interoperability * Set-theoretic types and what new compiler warnings unlock * AI in practice: LLM orchestration, fallbacks, and real-world use * SDUI and GraphQL patterns for shipping UI across web/iOS/Android * Dataframes in Elixir with Explorer for analytics workflows * Python interoperability (ErlPort, PythonX) and when to reach for it * Reproducible dev environments with Nix and friends * Performance paths: Rustler and Zig for native extensions * Bluetooth & Nerves: Blue Heron and hardware integrations * DevEx upgrades: LiveView, build pipelines, and standard project setup * Observability and ops: Prometheus/Grafana and sensible deployments * Community feedback, conferences, and what's on deck for next season   Links mentioned in this episode: Cars.com S14E06 SDUI at Scale with Elixir https://youtu.be/nloRcgngTk?si=g4Zd4N1s56Ronrtw https://hexdocs.pm/phoenixliveview/Phoenix.LiveView.html https://wordpress.com/ https://elixir-lang.org/ S14E01 Zigler: Zig NIFs for Elixir https://youtu.be/hSAvWxh26TU?si=d55tVuZbNw0KCfT https://ziglang.org/ https://hexdocs.pm/zigler/Zig.html https://github.com/blue-heron/blueheron https://github.com/elixir-explorer/explorer S14E08 Nix for Elixir Apps https://youtu.be/yymUcgy4OAk?si=BRgTlc2VK5bsIhIf https://nixos.org/ https://nix.dev/ S14E07 Set Theoretic Types in Elixir https://youtu.be/qMmEnXcHxL4?si=Ux2lebiwEp3mc0e S14E10 Python in Elixir Apps https://youtu.be/SpVLrrWkRqE?si=ld3oQVXVlWHpo7eV https://www.python.org/ https://hexdocs.pm/pythonx/ https://github.com/Pyrlang/Pyrlang https://github.com/erlport/erlport S14E03 LangChain: LLM Integration for Elixir https://youtu.be/OwFaljL3Ptc?si=A0sDs2dzJ0UoE2PY https://github.com/brainlid/langchain S14E04 Nx & Machine Learning in Elixir https://youtu.be/Ju64kAMLlkw?si=zdVnkBTTLHvIZNBm S14E05 Rustler: Bridging Elixir and Rust https://youtu.be/2RBw7B9OfwE?si=aRVYOyxxW8fTmoRA https://github.com/rusterlium/rustler Season 3: Working with Elixir https://youtube.com/playlist?list=PLTDLmInI9YaDbhMRpGuYpboVNbp1Fl9PD&si=hbe7qt4gRUfrMtpj S14E11 Vibe Coding the LoopedIn Crochet App https://youtu.be/DX0SjmPE92g?si=zCBPjS1huRDIeVeP Season 5: Adopting Elixir  YouTubeLaunchisode and Outlaws Takeover with Chris Keathley, Amos King, and Anna Neyzberg S13E01 Igniter: Elixir Code Generation https://youtu.be/WM9iQlQSF_g?si=e0CAiML2qC2SxmdL Season 8: Elixir in a Polyglot Environment https://youtube.com/playlist?list=PLTDLmInI9YaAPlvMd-RDp6LWFjI67wOGN&si=YCI7WLA8qozD57iw !! We Want to Hear Your Thoughts *!!* Have questions, comments, or topics you'd like us to discuss on the podcast? Share your thoughts with us here: https://forms.gle/Vm7mcYRFDgsqqpDC9

AI in software development sounds like a dream, faster coding, cleaner refactoring, and technical reports that actually make sense to stakeholders. But, what's the bad news in the classic good news/bad news scenario? Poisoned training data, compliance risks, and systems that are brittle and will not scale.  This week on Feds At The Edge, Alex Gromadzki, Assistant Director of Data Science at US GAO, and Steven Toy, Senior Director, Cloud Infrastructure for ICF, unpack the opportunities and pitfalls of generative AI in federal software development. From source-citing AI to data security in the software lifecycle, they reveal why small, testable use cases may be the smartest way forward.   Listen now on your favorite podcast platform to hear how federal leaders can balance innovation with responsibility as AI reshapes the software development life cycle.          

Send us a textIn this thoughtful episode of the Joey Pinz Conversations podcast, Joey sits down with Stan Ivanov, founder and  CTO of ThreatMate, to explore a decades-long journey through software development, entrepreneurship, and personal evolution.

Strong teams and transformed product practices drive growth. In order to drive outcomes using software and build great product teams, you need to drive speed to value and adapt quickly. The problem is, technology teams and business teams are often disjointed and lack clarity around each other's “why.” Unlock the full potential of your product team with Integral's player coaches, experts in lean, human-centered design. Visit integral.io/convergence for a free Product Success Lab workshop to gain clarity and confidence in tackling any product design or engineering challenge. In this first part of a continuing series on the Convergence podcast, Ashok Sivanand and Bailey O'Shea, Head of Product at Integral, explore 9 conversations essential for the success of product teams that are too often forgotten. These conversations are cultivated from the years of experience Ashok and the team at Integral have consulting with some of the best product makers in the world. This discussion is vital for product managers and team leaders, offering an in-depth look at the nuanced dialogues that shape a product's journey from ideation to market execution. Learn about the often-overlooked discussions that can significantly enhance agility, speed up market delivery, and maintain team alignment as your operations scale. Unlock the full potential of your product team with Integral's player coaches, experts in lean, human-centered design. Visit integral.io/convergence for a free Product Access Lab workshop to gain clarity and confidence in tackling any product design or engineering challenge. Inside the episode... Understanding Communication Impact: Ashok and Bailey discuss how insufficient communication can severely affect team dynamics, decelerate processes, and impede agility. Critical Conversations for Product Teams: They highlight the crucial but frequently missed discussions necessary within product teams to prevent bottlenecks and foster a culture of transparency. Methods for Effective Dialogue: They share detailed strategies on facilitating these conversations to ensure comprehensive alignment across roles from engineers to product managers. Practical and Theoretical Insights: The episode offers practical examples and theoretical insights to help listeners understand the application of these conversations in real teams, along with the foundational theories behind their significance. Subscribe to the Convergence podcast wherever you get podcasts including video episodes to get updated on the other crucial conversations that we'll post on YouTube at youtube.com/@convergencefmpodcast Learn something? Give us a 5 star review and like the podcast on YouTube. It's how we grow.   Follow the Pod Linkedin: https://www.linkedin.com/company/convergence-podcast/ X: https://twitter.com/podconvergence Instagram: @podconvergence

Please enjoy this encore of Word Notes. A software development model that relies on a series of sequential steps that flow into each other, like a series of waterfalls.  CyberWire Glossary link: ⁠https://thecyberwire.com/glossary/waterfall-software-development⁠ Audio reference link: “⁠Creating Video Games - Agile Software Development,⁠” by Sara Verrilli, MIT OpenCourseWare, YouTube, 10 December 2015

Please enjoy this encore of Word Notes. A software development model that relies on a series of sequential steps that flow into each other, like a series of waterfalls.  CyberWire Glossary link: ⁠https://thecyberwire.com/glossary/waterfall-software-development⁠ Audio reference link: “⁠Creating Video Games - Agile Software Development,⁠” by Sara Verrilli, MIT OpenCourseWare, YouTube, 10 December 2015 Learn more about your ad choices. Visit megaphone.fm/adchoices

BONUS: The Platform-as-Product Revolution: How to Turn Your Biggest Cost Center Into Your Secret Weapon With Alvaro Lorente In this BONUS episode we explore a topic that's creating a lot of discussion—and sometimes confusion—in the software community: Platform Teams vs DevOps. In this conversation, we dive into Alvaro Lorente's journey from delivery teams to platform leadership, exploring how to treat platforms as products, avoid common pitfalls, and build bridges between engineering and product leadership. The Evolution from DevOps Role to Platform Team "DevOps is a culture, not a role." Alvaro's journey into platform work began when he joined a company where the infrastructure team was left behind and struggling with traditional DevOps approaches. Initially, they had a single DevOps person who became a bottleneck rather than an enabler. This experience highlighted a fundamental misunderstanding that many organizations face—treating DevOps as a job title rather than a cultural shift toward collaboration and shared responsibility. The team experimented with a "DevOps buddy" approach, placing experienced individuals within each delivery team, before eventually consolidating into a dedicated platform team with the clear intention of treating it as a product-focused unit. Platform as a Product: A Scaling Strategy "Platform as a product is a scaling strategy. Look for common problems that you can then solve once, and serve many." The concept of treating platforms as products emerged from recognizing that feature delivery teams have continuity and ongoing needs that a platform team should serve. Rather than solving their own problems first, successful platform teams focus on making other teams' work easier and more comfortable while managing costs effectively. This approach requires identifying common problems across multiple teams and creating solutions that can be implemented once but serve many. The key insight is that platform teams exist to facilitate the delivery of value in a scalable way for other teams, not to pursue their own technical interests. Understanding Your Customer and Validating Value "I want to see platform team members talking to their customers. Understand their pains, and what they struggle with." Effective platform teams operate like any other product team by actively listening to their customer-teams rather than pushing ideas onto them. This means platform team members should regularly engage with their internal customers to understand pain points and struggles. Success requires defining clear KPIs for the platform and focusing on the quality of deliverables including release notes, demos, bug fixing processes, and feature prioritization. The validation comes from observing whether teams willingly adopt platform features rather than being mandated to use them. Building Bridges with Product Leadership "Focus on the key impact and value that the platform team can bring to the company." Making the case for investing product talent in platform teams requires demonstrating concrete business value. This includes quantifying how many incidents are being resolved faster or prevented entirely, and highlighting the money saved through internal platform development versus external solutions. Platform work offers excellent growth opportunities for Product Owners, serving as a training ground for product thinking and stakeholder management. The focus should always be on measurable impact rather than technical complexity. Avoiding Common Platform Team Traps "Don't just start working on what you think is important! Start with the Product process, listen to the client-teams, and help them directly." When standing up a platform team, several critical mistakes can derail success. The most important trap to avoid is immediately diving into what the platform team thinks is important without first understanding customer needs. Platform teams should resist delivery pressure that might compromise quality and never mandate adoption of their features—teams should want to use what the platform provides. Treating the platform as a genuine product with quality standards is essential, and leaders should view the creation of a platform team as the beginning of a change management process rather than just a technical reorganization. Resources and Continuous Learning "One size does NOT fit all!" For teams looking to improve their platform work, Alvaro recommends Camille Fournier's work on platform teams and resources focused on "The value of product thinking in platform teams." The key is to get experiments running within your team and recognize that there's no universal solution—each organization must find its own path based on its unique context and needs. About Alvaro Lorente Currently Director of Engineering at Voxel (an Amadeus company), Alvaro is a software engineer who has grown in the people leadership path, experimenting with everything from product development to startups and open source projects. He embraces the idea of being a jack of all trades, helping wherever needed to drive value and impact. You can connect with Alvaro Lorente on LinkedIn and follow his insights through his Substack newsletter titled Leads Horizons.