Podcasts about Continuous integration

Is demarcation stunting your business? In this episode, Squirrel tells us about how his 500-year-old house restoration reminded him of dealing with team members whose strict adherence to demarcation i.e. “That's not my job!” led to mistakes, poor communication and lack of problem-solving - and why un-demarcation is the best route forward. SHOW LINKS: Links: - Demarcation: https://www.fordtransition.org.uk/stories/trade-unions-at-ford/demarcation - Psychological safety: https://en.wikipedia.org/wiki/Psychological_safety - Seven Habits book: https://en.wikipedia.org/wiki/The_7_Habits_of_Highly_Effective_People -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

The search for ultimate truth has no place in an effective business! In this episode, Jeffrey and Squirrel explain how to detect when your team are stuck in the “rightness” trap and how to move from abstract debate to scientific experiments that help you discover what actually works. SHOW LINKS: Links: - Less Wrong: https://www.lesswrong.com/ - Less Online: https://less.online/ - Abor Summer Camp: https://www.arborsummer.camp/ - Manifest: https://manifest.is/ - Driftwood hiring episode: https://soundcloud.com/troubleshootingagile/driftwood-vs-planks-agile-team-roles-and-skills - Socratic Dialogues: https://dn790004.ca.archive.org/0/items/PlatoDialogues/Plato_dialogues.pdf -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

With so many great reader emails recently Jeffrey and I haven't got around to discussing CitCon on the podcast yet! This week we do just that, with Jeffrey's reflections from discussions on the evolving role of AI in coding including Steve Yegge's new article which revisits whether the ‘death' of the junior developer will ultimately be a ‘revenge.' Links: - Steve Yegge article: https://sourcegraph.com/blog/revenge-of-the-junior-developer - Jevon's Paradox: https://en.wikipedia.org/wiki/Jevons_paradox -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

Do ‘Experts Have It Easy'? In this episode, Squirrel and Jeffrey discuss how experts and novices can overcome the empathy gap with rapid feedback, and breaking down complex problems into smaller steps to facilitate understanding. SHOW LINKS: Links: - Boyd Kane's article: https://boydkane.com/essays/experts - Gladwell, Blink: https://en.wikipedia.org/wiki/Blink:_The_Power_of_Thinking_Without_Thinking - Shuhari: https://en.wikipedia.org/wiki/Shuhari - Terence Tao on finding gaps in proofs: https://mathstodon.xyz/@tao/111287749336059662 -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

Dangerous Dilettantes vs. Toyota Way EngineeringCore ThesisThe influx of AI-powered automation tools creates dangerous dilettantes - practitioners who know just enough to be harmful. The Toyota Production System (TPS) principles provide a battle-tested framework for integrating automation while maintaining engineering discipline.Historical ContextToyota Way formalized ~2001DevOps principles derive from TPSCoincided with post-dotcom crash startupsDecades of manufacturing automation parallels modern AI-based automationDangerous Dilettante IndicatorsPromises magical automation without understanding systemsFocuses on short-term productivity gains over long-term stabilityCreates interfaces that hide defects rather than surfacing themLacks understanding of production engineering fundamentalsPrioritizes feature velocity over deterministic behaviorToyota Way Implementation for AI-Enhanced Development1. Long-Term Philosophy Over Short-Term Gains// Anti-pattern: Brittle automation scriptlet quick_fix = agent.generate_solution(problem, { optimize_for: "immediate_completion", validation: false});// TPS approach: Sustainable system designlet sustainable_solution = engineering_system .with_agent_augmentation(agent) .design_solution(problem, { time_horizon_years: 2, observability: true, test_coverage_threshold: 0.85, validate_against_principles: true });Build systems that remain maintainable across yearsEstablish deterministic validation criteria before implementationOptimize for total cost of ownership, not just initial development2. Create Continuous Process Flow to Surface ProblemsImplement CI pipelines that surface defects immediately:Static analysis validationType checking (prefer strong type systems)Property-based testingIntegration testsPerformance regression detectionBuild flow:make lint → make typecheck → make test → make integration → make benchmarkFail fast at each stageForce errors to surface early rather than be hidden by automationAgent-assisted development must enhance visibility, not obscure it3. Pull Systems to Prevent OverproductionMinimize code surface area - only implement what's neededPrefer refactoring to adding new abstractionsUse agents to eliminate boilerplate, not to generate speculative features// Prefer minimal implementationsfunction processData(data: T[]): Result { // Use an agent to generate only the exact transformation needed // Not to create a general-purpose framework}4. Level Workload (Heijunka)Establish consistent development velocityAvoid burst patterns that hide technical debtUse agents consistently for small tasks rather than large sporadic generations5. Build Quality In (Jidoka)Automate failure detection, not just productionAny failed test/lint/check = full system haltEvery team member empowered to "pull the andon cord" (stop integration)AI-assisted code must pass same quality gates as human codeQuality gates should be more rigorous with automation, not less6. Standardized Tasks and ProcessesUniform build system interfaces across projectsConsistent command patterns:make formatmake lintmake testmake deployStandardized ways to integrate AI assistanceDocumented patterns for human verification of generated code7. Visual Controls to Expose ProblemsDashboards for code coverageComplexity metricsDependency trackingPerformance telemetryUse agents to improve these visualizations, not bypass them8. Reliable, Thoroughly-Tested TechnologyPrefer languages with strong safety guarantees (Rust, OCaml, TypeScript over JS)Use static analysis tools (clippy, eslint)Property-based testing over example-based#[test]fn property_based_validation() { proptest!(|(input: Vec)| { let result = process(&input); // Must hold for all inputs assert!(result.is_valid_state()); });}9. Grow Leaders Who Understand the WorkEngineers must understand what agents produceNo black-box implementationsLeaders establish a culture of comprehension, not just completion10. Develop Exceptional TeamsUse AI to amplify team capabilities, not replace expertiseAgents as team members with defined responsibilitiesCross-training to understand all parts of the system11. Respect Extended Network (Suppliers)Consistent interfaces between systemsWell-documented APIsVersion guaranteesExplicit dependencies12. Go and See (Genchi Genbutsu)Debug the actual system, not the abstractionTrace problematic code pathsVerify agent-generated code in contextSet up comprehensive observability// Instrument code to make the invisible visiblefunc ProcessRequest(ctx context.Context, req *Request) (*Response, error) { start := time.Now() defer metrics.RecordLatency("request_processing", time.Since(start)) // Log entry point logger.WithField("request_id", req.ID).Info("Starting request processing") // Processing with tracing points // ... // Verify exit conditions if err != nil { metrics.IncrementCounter("processing_errors", 1) logger.WithError(err).Error("Request processing failed") } return resp, err}13. Make Decisions Slowly by ConsensusMulti-stage validation for significant architectural changesAutomated analysis paired with human reviewDesign documents that trace requirements to implementation14. Kaizen (Continuous Improvement)Automate common patterns that emergeRegular retrospectives on agent usageContinuous refinement of prompts and integration patternsTechnical Implementation PatternsAI Agent Integrationinterface AgentIntegration { // Bounded scope generateComponent(spec: ComponentSpec): Promise; // Surface problems validateGeneration(code: string): Promise; // Continuous improvement registerFeedback(generation: string, feedback: Feedback): void;}Safety Control SystemsRate limitingProgressive exposureSafety boundariesFallback mechanismsManual oversight thresholdsExample: CI Pipeline with Agent Integration# ci-pipeline.ymlstages: - lint - test - integrate - deploylint: script: - make format-check - make lint # Agent-assisted code must pass same checks - make ai-validation test: script: - make unit-test - make property-test - make coverage-report # Coverage thresholds enforced - make coverage-validation# ...ConclusionAgents provide useful automation when bounded by rigorous engineering practices. The Toyota Way principles offer proven methodology for integrating automation without sacrificing quality. The difference between a dangerous dilettante and an engineer isn't knowledge of the latest tools, but understanding of fundamental principles that ensure reliable, maintainable systems.

What is the true meaning of accountability? In this episode, Squirrel and Jeffrey share a real-life story that illustrates how it's often misunderstood. Listen now to learn why it's not about blame or punishment, but about 'rendering an account' - in other words, sharing reasoning and decisions transparently. SHOW LINKS: Links: - Previous episode on accountability: https://itrevolution.com/articles/accountability-leaders-are-accountable-too/ -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

What can perverse incentives teach us about software development? Join Squirrel and Jeffrey for a discussion on the importance of personal responsibility and the potential benefits of 'blameful' postmortems in driving accountability and improvement within organisations, in this episode of Troubleshooting Agile. SHOW LINKS: Links: - Tal's article: https://talyarkoni.org/blog/2018/10/02/no-its-not-the-incentives-its-you/ - Blameless Postmortems: https://openpracticelibrary.com/practice/blameless-postmortem/ - Perverse Incentives: https://en.wikipedia.org/wiki/Perverse_incentive -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

At Arm, open source is the default approach, with proprietary software requiring justification, says Andrew Wafaa, fellow and senior director of software communities. Speaking at KubeCon + CloudNativeCon Europe, Wafaa emphasized Arm's decade-long commitment to open source, highlighting its investment in key projects like the Linux kernel, GCC, and LLVM. This investment is strategic, ensuring strong support for Arm's architecture through vital tools and system software.Wafaa also challenged the hype around GPUs in AI, asserting that CPUs—especially those enhanced with Arm's Scalable Matrix Extension (SME2) and Scalable Vector Extension (SVE2)—are often more suitable for inference workloads. CPUs offer greater flexibility, and Arm's innovations aim to reduce dependency on expensive GPU fleets.On the AI framework front, Wafaa pointed to PyTorch as the emerging hub, likening its ecosystem-building potential to Kubernetes. As a PyTorch Foundation board member, he sees PyTorch becoming the central open source platform in AI development, with broad community and industry backing.Learn more from The New Stack about the latest insights about Arm: Edge Wars Heat Up as Arm Aims to Outflank Intel, Qualcomm Arm: See a Demo About Migrating a x86-Based App to ARM64Join our community of newsletter subscribers to stay on top of the news and at the top of your game. 

Is topgrading a controversial topic? It seems so. In this episode, Jeffrey and Squirrel revisit the theme of topgrading in recruitment, featured just two episodes ago. Join as they discuss a listener's experience, the necessity for some structure in interviews and the benefits of learning from candidates' past experiences through stories. SHOW LINKS: - Topgrading: https://en.wikipedia.org/wiki/Topgrading - Topgrading episode link: https://soundcloud.com/troubleshootingagile/threats-and-topgrading-in-executive-hiring - Shu ha ri: https://en.wikipedia.org/wiki/Shuhari - Squirrel's interviewing event: https://squirrelsquadron.com/events/2025/04-10-interviews - TDD for People: https://itrevolution.com/articles/test-driven-development-for-people/ -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

(03:59) Brought to you by Swimm.io.⁠⁠⁠⁠Start modernizing your mainframe faster with Swimm.Understand the what, why, and how of your mainframe code.Use AI to uncover critical code insights for seamless migration, refactoring, or system replacement.Stop fearing Friday and late-night deployments!Discover how the most painful part of software development—deploying to production—can become routine, safe, and even boring.In this episode, I sit down with Valentina Servile (ThoughtWorks lead developer and author of “Continuous Deployment”) to discuss the principles, practices, and mindset shift required to achieve true Continuous Deployment.Key topics discussed:The key differences between Continuous Integration, Continuous Delivery, and Continuous DeploymentWhy “if it hurts, do it more often” is the secret to safer, faster releasesApplying Lean principles like one-piece flow and reducing batch size for higher quality and speedThe importance of removing the final manual deployment gate and automating everythingEssential minimum practices: robust automated testing, feature flags, static analysis, and zero-downtime deploymentsSeparating deployment from release with feature flags and expand/contract patternsOvercoming challenges in regulated industries, technical hurdles, and third-party integrationsThe critical mindset shift: treating production as a first-class citizen and embracing “shift left” for quality and securityCautions and advice on using AI tools in a continuous deployment workflowTune in to level up your software delivery and learn how to make deployments so routine that you'll never dread another release.  Timestamps:(02:00) Career Turning Points(06:05) Tips for Juniors Starting Their Careers(08:00) Continuous Deployment Book(10:16) Definitions of CI, CD, Continuous Deployment(15:42) If It Hurts, Do It More Often(19:18) Why Remove The Final Manual Gate to Production(24:56) Common Challenges in Adopting Continuous Deployment(30:02) Minimum Practices for Continuous Deployment(35:17) Hiding Work-in-Progress(38:46) The Difference Between Deployment vs Release(41:40) Slicing the Work(45:10) Coordinating Changes Between Systems & Third Parties(47:58) The Importance of Backward Compatibility(50:05) The Required Mindset Shift(53:16) AI Caution in Continuous Deployment(55:35) 3 Tech Lead Wisdom_____Valentina Servile's BioValentina Servile is a full-stack software craftswoman and Lead Software Developer at Thoughtworks.She has worked with over a dozen companies in 5 different countries, ranging from start-up to enterprise scale. Her work has been focused on clean code, distributed systems and microservices, CI/CD practices, and evolutionary architectures in a variety of tech stacks. As a technical lead, she also coordinates delivery, and ensures a shared vision around ways of working and technical health in her cross-functional teams.Valentina is passionate about creating an engineering baseline of clean code, testing and automation as the the most fundamental enabler of Agile, Lean and DevOps principles.Follow Valentina:LinkedIn – linkedin.com/in/valentina-servileBluesky – @valentinaservile.bsky.social

I speak with Kyle from Depot.dev, which promise to speed up your your Docker image builds and GitHub Actions workflows. Depot easily integrates with your existing CI provider and dev workflows to save hours of build time.Learn something new with a book or course from ManningStart today with learning something new or up-skilling, get 30% of ANYTHING at manning.com by visiting go.chrischinchilla.com/manning For show notes and an interactive transcript, visit chrischinchilla.com/podcast/To reach out and say hello, visit chrischinchilla.com/contact/To support the show for ad-free listening and extra content, visit chrischinchilla.com/support/

Is shielding your team a sign of good leadership? On this episode, Jeffrey has been riled up by an episode of the podcast, Cortex, and wants to make a case against shielding, which he believes keeps teams disconnected from the reality of business conditions and leads to suboptimal results. SHOW LINKS: - Cortex podcast: https://podcasts.apple.com/us/podcast/cortex/id1001591696 - Dale Carnegie book: https://en.wikipedia.org/wiki/How_to_Win_Friends_and_Influence_People -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

The episode discusses the concept of Minimum Viable Continuous Delivery (Minimum CD), which represents a counter-movement to heavyweight frameworks like SAFe. The hosts explore how Minimum CD provides a set of essential practices for successfully building software-based products without unnecessary complexity. The approach focuses on core principles rather than rigid frameworks, making it particularly relevant for embedded systems development.The discussion covers the fundamental requirements for continuous delivery, including automated testing, pipeline-driven deployments, and trunk-based development. The hosts emphasize that while these practices may seem challenging for embedded systems, they become increasingly important as devices become more sophisticated and connected.A key theme throughout the episode is the importance of building trust in the development process through automation, consistent practices, and cultural commitment. The hosts stress that while some practices may seem difficult to implement in embedded systems, the more challenging they are, the more valuable they become when successfully implemented.Timestamps and Topics:00:00:00 - Introduction and overview of Minimum CD00:02:00 - Discussion of Minimum CD as counter-movement to complex frameworks00:03:45 - Continuous Integration fundamentals00:15:35 - Pipeline as the only way to deploy00:27:00 - Production-like test environments00:29:45 - Rollback capabilities for connected devices00:32:25 - Configuration deployment with artifacts00:34:50 - Trunk-based development principles00:39:30 - Automated testing requirements00:41:10 - Maintaining delivered work integrity00:45:55 - Wrap-up and closing thoughtsShownotes:Link to minimumcd.org: https://minimumcd.org/ Reference to Brian Finster as instigator of Minimum CD Reference to Raymond Chen's blog about Windows backward compatibility Reference to previous episode on trunk-based development Reference to interviews with Philip Johnston from Embedded Artistry Reference to interview with Francois from Mend Fault Link to Agile Embedded Slack group You can find Jeff at https://jeffgable.com.You can find Luca at https://luca.engineer.Want to join the agile Embedded Slack? Click here

Is the use of threats to repel dishonest people a good idea? On this episode of Troubleshooting Agile, Squirrel and Jeffrey talk about the “threat of reference check” and whether the benefits of reducing dishonesty outweigh the drawbacks of damaging trust. Get in touch to tell us what you think. SHOW LINKS: - Domain-Driven Design: en.wikipedia.org/wiki/Domain-driven_design - Big Book of Concepts: mitpress.mit.edu/books/big-book-concepts - Specification by Example: gojko.net/books/specification-by-example/ - Walking Skeleton: wiki.c2.com/?WalkingSkeleton -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

It's time to talk about commitment! Not engagement, which is insufficient to produce effective results. In this episode - a repost of a previous conversation - Squirrel and Jeffrey offer specific tools for effective commitments and tell a story about a company that created a pile of bones instead of a Walking Skeleton. You'll hear lots of references to “the book.” That's our book - Agile Conversations!! You can learn more about that here: https://agileconversations.com/agile-conversation-book/ SHOW LINKS: - Domain-Driven Design: en.wikipedia.org/wiki/Domain-driven_design - Big Book of Concepts: mitpress.mit.edu/books/big-book-concepts - Specification by Example: gojko.net/books/specification-by-example/ - Walking Skeleton: wiki.c2.com/?WalkingSkeleton -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

In this episode of Technical Tips, Tommy shares 10 expert tips to keep your CI pipeline fast and efficient. Learn how to improve performance, reduce errors, and ship quality software faster!Like this episode? Be sure to leave a ⭐️⭐️⭐️⭐️⭐️ review on the podcast player of your choice and share it with your friends.

What if complaining could be a good thing? In this episode, Squirrel and Jeffrey discuss the benefits of ‘positive complaining' and how it can be used to strengthen relationships and offer valuable insights into what matters to the person complaining. Links: Trust Conversation (TDD for People): https://itrevolution.com/articles/test-driven-development-for-people/ Co-conspirators episode: https://soundcloud.com/troubleshootingagile/co-conspirators-and-citcon Squirrel Squadron: https://squirrelsquadron.com/ -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

If you're using Sinek's “why, what and how” framework for team collaboration, what do you do when it turns out you're lacking two out of the three?! In this episode, Squirrel and Jeffrey talk about their own experience of this, the concept of leaky abstractions, and the importance of shared problem ownership. Links: - Simon Sinek: https://simonsinek.com/books/start-with-why/ - Somebody Else's Problem Field: https://hitchhikers.fandom.com/wiki/Somebody_Else%27s_Problem_Field - Previous episode about Walking Skeletons - Ep125: Commitment Engagement is Not Enough: https://soundcloud.com/troubleshootingagile/commitment-engagement-is-not-enough - Previous episode about Cycle Time - Ep249: Estimates: A Productive Argument, Part I https://soundcloud.com/troubleshootingagile/reporting-estimates -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

Global Agile Summit Preview: Implementing Agile Practices for Data and Analytics Teams with Henrik Reich In this BONUS Global Agile Summit preview episode, we dive into the world of Agile methodologies specifically tailored for data and analytics teams. Henrik Reich, Principal Architect at twoday Data & AI Denmark, shares his expertise on how data teams can adapt Agile principles to their unique needs, the challenges they face, and practical tips for successful implementation. The Evolution of Data Teams "Data and analytics work is moving more and more to be like software development." The landscape of data work is rapidly changing. Henrik explains how data teams are increasingly adopting software development practices, yet there remains a significant knowledge gap in effectively using certain tools. This transition creates both opportunities and challenges for organizations looking to implement Agile methodologies in their data teams. Henrik emphasizes that as data projects become more complex, the need for structured yet flexible approaches becomes critical. Dynamic Teams in the Data and Analytics World "When we do sprint planning, we have to assess who is available. Not always the same people are available." Henrik introduces the concept of "dynamic teams," particularly relevant in consulting environments. Unlike traditional Agile teams with consistent membership, data teams often work with fluctuating resources. This requires a unique approach to sprint planning and task assignment. Henrik describes how this dynamic structure affects team coordination, knowledge sharing, and project continuity, offering practical strategies for maintaining momentum despite changing team composition. Customizing Agile for Data and Analytics Teams "In data and analytics, tools have ignored agile practices for a long time." Henrik emphasizes that Agile isn't a one-size-fits-all solution, especially for data teams. He outlines the unique challenges these teams face: Team members have varying expectations based on their backgrounds Experienced data professionals sometimes skip quality practices Traditional data tools weren't designed with Agile methodologies in mind When adapting Agile for data teams, Henrik recommends focusing on three key areas: People and their expertise Technology selection Architecture decisions The overarching goal remains consistent: "How can we deliver as quickly as possible, and keep the good mood of the team?" Implementing CI/CD in Data Projects "Our first approach is to make CI/CD available in the teams." Continuous Integration and Continuous Deployment (CI/CD) practices are essential but often challenging to implement in data teams. Henrik shares how his organization creates "Accelerators" - tools and practices that enable teams to adopt CI/CD effectively. These accelerators address both technological requirements and new ways of working. Through practical examples, he demonstrates how teams can overcome common obstacles, such as version control challenges specific to data projects. In this segment, we refer to the book How to Succeed with Agile Business Intelligence by Raphael Branger. Practical Tips for Agile Adoption "Start small. Don't ditch scrum, take it as an inspiration." For data teams looking to adopt Agile practices, Henrik offers pragmatic advice: Begin with small, manageable changes Use established frameworks like Scrum as inspiration rather than rigid rules Practice new methodologies together as a team to build collective understanding Adapt processes based on team feedback and project requirements This approach allows data teams to embrace Agile principles while accounting for their unique characteristics and constraints. The Product Owner Challenge "CxOs are the biggest users of these systems." A common challenge in data teams is the emergence of "accidental product owners" - individuals who find themselves in product ownership roles without clear preparation. Henrik explains why this happens and offers solutions: Clearly identify who owns the project from the outset Consider implementing a "Proxy PO" role between executives and Agile data teams Recognize the importance of having the right stakeholder engagement for requirements gathering and feedback Henrik also highlights the diversity within data teams, noting there are typically "people who code for living, and people who live for coding." This diversity presents both challenges and opportunities for Agile implementation. Fostering Creativity in Structured Environments "Use sprint goals to motivate a team, and help everyone contribute." Data work often requires creative problem-solving - something that can seem at odds with structured Agile frameworks. Henrik discusses how to balance these seemingly conflicting needs by: Recognizing individual strengths within the team Organizing work to leverage these diverse abilities Using sprint goals to provide direction while allowing flexibility in approach This balanced approach helps maintain the benefits of Agile structure while creating space for the creative work essential to solving complex data problems. About Henrik Reich Henrik is a Principal Architect and developer in the R&D Department at twoday Data & AI Denmark. With deep expertise in OLTP and OLAP, he is a strong advocate of Agile development, automation, and continuous learning. He enjoys biking, music, technical blogging, and speaking at events on data and AI topics. You can link with Henrik Reich on LinkedIn and follow Henrik Reich's blog.

Should you start a Guild?In this episode, Squirrel and Jeffrey discuss examples of adverse possession, including listener Marcel-Jan's experience of starting a Python guild within his team, and how you can take similar proactive steps to help build a more engaging and dynamic community of practice. Links: Co-conspirators episode: https://soundcloud.com/troubleshootingagile/co-conspirators-and-citcon Adverse possession: https://www.linkedin.com/posts/dsquirrel_squirrel-squadron-events-activity-7015965093418934272-1qZf/ -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

What does it mean to be a co-conspirator? On the run up to CitCon Auckland 2025, join Squirrel and Jeffrey as they reflect on the event they first met, its history and how ‘co-conspirators' have been pivotal in their careers and client work. Links: - CITCON ANZ 2025: https://citconf.com/auckland2025/ - Chris Matts Communities of Practise: https://theitriskmanager.com/2015/04/19/communities-of-need-community-of-solutions/ -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

Join us for a fascinating episode where we explore the development of SaturnCI—a new and user-friendly Continuous Integration tool that arose from frustrations with existing solutions like CircleCI and GitHub Actions. Our guest, Jason Sweat, shares his passion for creating a platform that not only simplifies the user experience but actively incorporates feedback from early adopters. Through candid conversations, Jason recounts his journey as a content creator in the Ruby community, and how it inspired him to address the shortcomings he observed in CI tools.We delve into the technical challenges faced as SaturnCI grows, particularly those relating to user scalability as it onboarded new customers. Jason offers valuable insights into his tech stack choices while drawing attention to the importance of creating streamlined interfaces that cater to developers' needs. The conversation shifts to the foundation of community through his upcoming Sin City Ruby conference, showcasing the efforts made to facilitate connection among participants and ensure each attendee leaves with new friendships and knowledge.Toward the end of our episode, we touch upon Jason's unique approach to outreach through his snail mail newsletter, where he shares insights and stories beyond technology. This creative endeavor highlights how stepping away from screens can cultivate a deeper connection with the audience. With an inviting conversational tone and enriching discussions, this episode is packed with valuable insights for anyone interested in CI tools, community-building, and finding the courage to innovate within your space. Be sure to subscribe and share your thoughts with us!Send us some love.HoneybadgerHoneybadger is an application health monitoring tool built by developers for developers.HoneybadgerHoneybadger is an application health monitoring tool built by developers for developers.Disclaimer: This post contains affiliate links. If you make a purchase, I may receive a commission at no extra cost to you.Support the showReady to start your own podcast?This show is hosted on Buzzsprout and it's awesome, not to mention a Ruby on Rails application. Let Buzzsprout know we sent you and you'll get a $20 Amazon gift card if you sign up for a paid plan, and it helps support our show.

What does it mean to be a flexible leader? In part two of this two-part episode of Troubleshooting Agile, we welcome back Kevin Eikenberry to talk about ‘flexors,' approaches to leadership that can help leaders and team adapt more effectively, and develop a mindset of experimentation. Links: - Kevin Eikenberry: http://kevineikenberry.com and http://kevineikenberry.com/gift - Flexible Leadership https://kevineikenberry.com/flexible - Betterism: https://thectoclub.com/news/lies-your-tech-team-tells-you/ -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

What does it mean to be a flexible leader? In this episode of Troubleshooting Agile, we welcome Kevin Eikenberry to talk about complex vs complicated situations, how to experiment rather than sticking to rigid policies, and his new book ‘Flexible Leadership' Links: - Kevin Eikenberry: http://kevineikenberry.com and http://kevineikenberry.com/gift - Flexible Leadership https://kevineikenberry.com/flexible - Cynefin: https://en.wikipedia.org/wiki/Cynefin_framework - Naive Realism: https://en.wikipedia.org/wiki/Na%C3%AFve_realism -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

How do you manage your CI/CD pipeline resources? Richard chats with Eliza Tarasila about Managed DevOps Pools in Azure DevOps. Eliza tells the story of discovering that teams were using Azure DevOps internally at Microsoft but would need to build their tooling to stand up the resources for testing and deployment. Managed DevOps Pools became the standard way to specify resources like virtual machines and assign them to projects so that they would start up automatically. The resources in the pool can be custom resources in Azure or even on-premises servers! And, more importantly, you don't need to care and feed for the infrastructure used in the pipelines, Azure DevOps will do it for you.LinksAzure DevOpsCreate and Manage PoolsManaged DevOps Pool Origin StoryAzure DevOps PricingAzure Spot Virtual MachinesManaged DevOps Pools DocumentationRecorded January 6, 2025

Is trust the ability to predict someone's actions? And can it apply to organisations as well as individuals? Join your hosts, Squirrel and Jeffrey, as they tackle the importance of delivering consistent results to foster trust, on this episode of Troubleshooting Agile. Links: - TDD for People, a method for building trust: https://itrevolution.com/articles/trust-and-test-driven-development-for-people/ - Stock picking scam: https://ask.metafilter.com/216295/Is-this-famous-investment-scam-real-or-fiction - Agile Conversations: https://agileconversations.com/agile-conversation-book/ -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

What are the challenges when it comes to implementing Toyota Kata at scale? In this episode of Troubleshooting agile, Jeffrey talks about how they're using the Improvement and Coaching Katas to foster better structured learning and accountability across multiple teams. Links: - Toyota Kata: https://en.wikipedia.org/wiki/Toyota_Kata - Shu, Ha, Ri: https://en.wikipedia.org/wiki/Shuhari - Previous episode - Toya Toyota Kata A-Z: https://soundcloud.com/troubleshootingagile/toyota-kata-a-z -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

In this episode, we delve into the next step in the developer journey: implementation. We explore how to work within different team sizes and structures, including individual projects, small teams, and large teams. This guide will cover essential strategies for maximizing efficiency in various software development environments.   Maximizing Efficiency as an Individual Developer When you're the sole developer on a project, whether it's a side hustle, a proof of concept for your boss, or a personal endeavor, it's crucial to establish strong habits and practices. Here are some tips to help you maximize efficiency: Commit Code Regularly: Develop the habit of committing code frequently. This not only helps you keep track of changes but also makes it easier to roll back if something goes wrong. Comment Your Code: Clear comments can save you and others a lot of time when revisiting the code. It's a small step that pays off in the long run. Create Reproducible Builds: Establish a reproducible build process to avoid manual errors. Tools like Ant scripts can automate building, testing, and deploying, saving time and reducing mistakes. By focusing on these practices, you can enhance your development process, making it more efficient and less error-prone. Maximizing Efficiency in Small Teams Working in a small team requires a different approach compared to working solo. Communication becomes key, and each member often has to wear multiple hats. Here are strategies to ensure efficiency in small teams: Effective Communication Tools: Utilize instant messaging tools like Slack or Microsoft Teams. These platforms facilitate real-time communication, helping to keep everyone on the same page. Defined Roles but Flexible Collaboration: Flexibility is crucial when each member might have a specific role, such as front-end or back-end development. Small teams often need to adapt quickly to changes and new requirements. Synchronous Schedules: Ensure that team members' working hours overlap as much as possible. This synchronization helps in quick decision-making and problem-solving. By maintaining clear communication and flexible roles, small teams can navigate the dynamic landscape of software development efficiently. Maximizing Efficiency in Large Teams Large teams introduce more complexity, with defined roles and more formal structures. Efficiency in such environments hinges on ownership and robust processes. Here's how to maximize efficiency in large teams: Clear Ownership: Each project component or feature should have an owner. This person is responsible for making decisions and ensuring that the feature meets its requirements. Regular Meetings and Updates: Daily stand-ups, sprint planning, and retrospective meetings help keep the team aligned. They ensure that any blockers are quickly addressed and everyone is aware of their tasks. Comprehensive Documentation and Testing: In larger teams, having detailed documentation and a strong focus on testing (unit tests, integration tests, etc.) is vital. This helps maintain the quality and understanding of the project as it grows. Ownership and structured processes are key to handling the complexities of large teams, ensuring that everyone is aligned and working efficiently towards common goals. General Tips for Maximizing Efficiency in Software Development Regardless of the team size, some universal strategies can help maximize efficiency across the board: Agile Methodology: Implementing agile practices, such as sprints and regular feedback loops, helps organizations adapt to changes and deliver incremental value. Continuous Integration and Deployment (CI/CD): Automate the build, testing, and deployment processes to catch issues early and release updates faster. Scope Management: Avoid scope creep by clearly defining and agreeing on requirements before starting a project. Any new features should be evaluated and planned for future iterations. These practices help in creating a streamlined development process, reducing delays, and improving the overall quality of the software. Final Thoughts Maximizing efficiency in software development requires adapting to the team size and the project environment. Whether you're working solo, in a small team, or as part of a large team, the key lies in good communication, clear ownership, and robust processes. By implementing these strategies, you can navigate the complexities of software development and deliver high-quality products efficiently. 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 Embrace Feedback for Better Teams Using Offshore Teams and Resources – Interview With Tanika De Souza Moving To Mobile Teams and Building Them – Sebastian Schieke The Developer Journey Videos – With Bonus Content Behind the Scenes Podcast Video – With Bonus Content

Why can't I apply for a driving license at 3 AM? Join Squirrel and Jeffrey in discussion on the history and challenges of modernising legacy systems and how delivering incremental improvements can "strangle" the pitfalls of a full rewrite, in this episode of Troubleshooting Agile. Links: - Dafydd Vaughan on DVLA batch systems: https://dafyddvaughan.uk/blog/2025/why-some-dvla-digital-services-dont-work-at-night/ - Joel Spolsky on not rewriting: https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/ -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

Does asking for the “dumbest” solutions stimulate the most creative ideas? Join Squirrel and Jeffrey as they answer two listener questions on the theme of boosting creativity, including why you might wear a funny hat to your team warm-up, in this week's episode of Troubleshooting Agile. Links: - Core Protocols Checkin: https://thecoreprotocols.org/protocols/checkin - Dave Snowden on Changing Clothes: https://medium.com/@brixen/dave-snowden-how-leaders-change-culture-though-small-actions-766cd2bf5128 - Niko Niko chart: https://www.agilealliance.org/glossary/niko-niko/ -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

CTO Series: How Open Strategy and Agile Practices Drive Success at NorthCode With Ismo Aro   In this BONUS episode, we sit down with Ismo Aro, CTO and partner at NorthCode, to delve into the transformative power of Open Strategy in the tech world. Ismo shares his journey from corporate roles at Nokia and Ericsson to becoming a full-time entrepreneur, and he unpacks how his approach to leadership evolved with the rise of agile methodologies, test automation, and cloud transformation. This episode is packed with actionable insights for anyone looking to modernize their company's strategy and foster a culture of transparency and co-ownership. Pivotal Career Moments: From Waterfall to Agile Mindset   “When I joined the agile pilot team, it felt like discovering the way software development should always be done—release early, get feedback fast, and improve continuously.”   Ismo reflects on his early days at Nokia, where he began as a test engineer in a traditional waterfall environment. He describes how the shift to agile methodologies transformed the way teams communicated and collaborated. When he joined a pilot project for Scrum, he realized the value of fast feedback loops and early releases. This experience laid the foundation for his future focus on continuous integration and test automation.   Key Takeaway: Adopting agile frameworks can improve workflows by shortening feedback loops and promoting direct communication. The Essence of Open Strategy “Open Strategy means involving everyone in shaping the direction of the company—not just receiving updates but truly co-creating the future.”   At NorthCode, Open Strategy is a cornerstone of their operations. Ismo explains how they empower employees by making strategy-building a transparent and collaborative process. The company's structure includes a parent company and subsidiaries where employees are also co-owners. Revenue-sharing ensures that when the business succeeds, everyone benefits directly.   Key Elements of Open Strategy: Transparency: Strategy is made visible through a kanban board and KPIs accessible to all. Ownership: Subsidiary team members can own up to 80% of their company. Profit-sharing: 80% of client revenue goes to the subsidiary, and dividends are shared annually.   “By aligning incentives and opening up the strategy process, you create a culture where employees don't just work for you—they work with you.” How Open Strategy Unfolds Annually “We make ideas visible and let them evolve until they're ready for execution.”   Ismo outlines the company's approach to strategy using a high-level roadmap and clear metrics to track progress. The focus is on organic growth through subsidiaries, with a benchmark of starting a new subsidiary once a team reaches 20 people. The company also uses “business spikes”—short, low-cost experiments to test new ideas.   Practical Tip: A business spike allows you to explore an idea quickly without committing significant resources, making it easier to pivot when necessary. Navigating Challenges in Open Strategy “Some people want to co-create, while others prefer to focus on their work—and both are valid.”   Ismo acknowledges that not everyone in the organization is equally interested in strategic discussions, and that's okay. Open Strategy doesn't require everyone to participate equally—it provides opportunities for involvement at different levels. The key is fostering an environment where insights and information flow freely from the ground up, rather than top-down mandates.   Key Insight: Open Strategy thrives when participation is voluntary and inclusive, rather than forced. Measuring Success: KPIs and Transparency “We believe in showing our utilization rates openly because our people have a stake in the results.”   To measure success, NorthCode tracks KPIs such as revenue, profit, and utilization rates. Unlike traditional consulting companies that keep these metrics private, NorthCode shares them openly to build trust and foster a sense of ownership. Monthly meetings focus on tactical updates, while strategic sessions aim to inspire employees to contribute ideas for the company's future.   Fun Practice: The “nightmare competitor” exercise encourages the team to imagine an ideal competitor and then adopt some of their hypothetical best practices into NorthCode's strategy.   “When people can see the metrics that matter, they're more motivated to take ownership of their impact.” Inspiration from Open Strategy and Business Agility “We take concepts from corporate books and tailor them to fit our context as a growing, agile company.” Ismo cites two key books that shaped his thinking: Open Strategy and The 6 Enablers of Business Agility. However, he emphasizes the importance of adapting corporate-level concepts to suit smaller, more agile organizations. He believes that while agile is mainstream in software development, many companies remain rigid in their overall strategy.   Recommended Reads: Open Strategy: Mastering Disruption from Outside the C-Suite by Stadler et al. The 6 Enablers of Business Agility by Harbott   Key Reflection: Ismo's approach underscores the importance of agility not just in software but in company operations and strategy-making.   Final Tip: Embrace modern tools like Large Language Models (LLMs) to streamline workflows—but remember, they enhance your work, not replace it.   About Ismo Aro Ismo Aro is the CTO and partner at NorthCode, specializing in software development and workflow modernization. With experience at Nokia and Ericsson, he has held various roles, from test engineer to entrepreneur. Ismo co-founded NorthCode after selling a previous company and also served as Chairman of the Robot Framework Foundation, contributing to the growth of the widely used open-source test automation framework.   You can link with Ismo Aro on LinkedIn.

Balancing psychological safety and high standards is crucial for high performance in your tech team. Join Squirrel and Jefferey for a discussion on this, plus the misconceptions around perks and productivity, in this week's episode of Troubleshooting Agile LINKS - Safety vs standards article: https://www.leadingsapiens.com/psychological-safety-vs-high-standards/ - Challenge article: https://www.nobelcoaching.com/tag/challenge/ - Flow book: https://www.goodreads.com/book/show/66354.Flow - Brian Marick: http://www.exampler.com/ease-and-joy.html -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

Can you drive change in your organisation by accelerating crises? In this episode, Squirrel and Jeffrey discuss Deming's philosophy and explore how visibility and awareness of issues can bring about necessary change. LINKS - Deming: https://en.wikipedia.org/wiki/W._Edwards_Deming - Panel discussion: https://www.youtube.com/watch?v=bu7JMAQggfo - Information radiators: https://www.agilealliance.org/glossary/information-radiators/ -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

In this new Technical Tips episode, Tommy explores Continuous Integration, Deployment, and Delivery—three practices with the same goal: making software development faster and more reliable. Tune in as he explains the key differences and clears up the confusion!Listen to the full episode or read the transcript on the Semaphore blog.Like this episode? Be sure to leave a ⭐️⭐️⭐️⭐️⭐️ review on the podcast player of your choice and share it with your friends.

Is your plan to avoid conflict making things worse? In this episode, Squirrel and Jeffrey discuss the Paul and Ted Case Study, the concept of 'easing in,' and what leaders should do instead, on this episode of Troubleshooting Agile. LINKS - Eight Behaviors for Smarter Teams: https://www.csu.edu.au/__data/assets/pdf_file/0008/917018/Eight-Behaviors-for-Smarter-Teams-2.pdf -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

Do you document and analyse failure? In this episode, Squirrel and Jeffrey draw inspiration from Donald Knuth's detailed study of his own software mistakes to give you the lowdown on learning from past mistakes, including meaningful postmortems and retrospectives. -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

What do you do when you inherit a 20 year old codebase? In this episode, Squirrel and Jeffrey look at an extreme example of legacy software and discuss why it's important to understand past contexts as well as address modern discrepancies. Links: - Brian's Archaeology Tips: https://www.linkedin.com/pulse/10-tips-software-archeologists-brian-reich-n0ase - Ask Why, But Never Answer: https://blog.jbrains.ca/permalink/ask-why-but-never-answer - Macintosh's Backward Capacitor: https://www.downtowndougbrown.com/2024/11/the-capacitor-that-apple-soldered-incorrectly-at-the-factory/ -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

How do you make sure that critical information is preserved over time? Tune in to learn about “reverse smuggling,” lost TV shows, outdated video game formats, and Ron Landley's Petrochemical archaeology, in this week's episode of Troubleshooting Agile. Links: - Grant's article; - Petrochemical archaeology from Ron Landley: https://landley.net/history/mirror/institutional_memory.html - Dr. Who archaeology: https://en.wikipedia.org/wiki/Doctor_Who_missing_episodes -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

Scott and Wes dive into the State of Frontend 2024 Survey, breaking down the latest trends, tools, and frameworks shaping the developer ecosystem. Tune in as they react to hot takes on frameworks, state management, hosting, and what's next for frontend devs! Show Notes 00:00 Welcome to Syntax! 00:53 Brought to you by Sentry.io. 01:15 About the survey. Follow along! State of Frontend Survey 02:10 Frameworks. 06:15 Rendering frameworks. 07:35 State management. 09:14 Other libraries. Just: Dependency-free Utilities. 13:34 Data. Syntax Episode 453. Syntax Episode 833. 16:39 Hosting. AWS Amplify. 19:51 Continuous Integration. 21:30 Micro-frontends. 23:25 Package Managers. pnpm Link Workspace Packages. Corepack. 28:35 JS Runtimes. 29:47 Typescript. 33:13 Browser Technologies. 35:05 What is app property? 38:20 Progressive Web Apps. 40:11 Styling tools. 43:17 Testing. 45:39 Code editors. 49:02 Build tools. 49:17 Linting tools. 50:26 Operating systems. 51:17 The future trends. 54:14 Sick Picks + Shameless Plugs. Sick Picks Scott: Candle Warmer. Wes: Flighty iOS App. Shameless Plugs Scott: Syntax on Bluesky Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

Can extreme constraints help you think of radically different solutions? In this week's episode, Jeffrey and Squirrel explore what happens when you point a figurative gun at your team, inspired by Grant Slatton's provocative article 'Algorithms We Develop Software By' Links: - Grant's article; https://grantslatton.com/software-pathfinding#algorithms-we-develop-software-by - Thinking, Fast and Slow: https://en.wikipedia.org/wiki/Thinking,_Fast_and_Slow - Toyota Kata: https://en.wikipedia.org/wiki/Toyota_Kata - Independence Day: https://www.linkedin.com/pulse/three-incendiary-questions-douglas-squirrel-seqre/ - Feature thinning: https://agileconversations.com/blog/ford-not-ferrari-feature-thinning-and-roi/ - Oblique Strategies cards: https://en.wikipedia.org/wiki/Oblique_Strategies -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

Would you delete your unfinished work to ensure a fresh start? On this week's episode, Jeffrey and Squirrel discuss whether using deletion as a tool can provide focus and improvement, with help from Grant Slatton's provocative article 'Algorithms We Develop Software By' Links: - Grant's article; https://grantslatton.com/software-pathfinding#algorithms-we-develop-software-by - Thinking, Fast and Slow: https://en.wikipedia.org/wiki/Thinking,_Fast_and_Slow - Toyota Kata: https://en.wikipedia.org/wiki/Toyota_Kata - Independence Day: https://www.linkedin.com/pulse/three-incendiary-questions-douglas-squirrel-seqre/ - Feature thinning: https://agileconversations.com/blog/ford-not-ferrari-feature-thinning-and-roi/ - Oblique Strategies cards: https://en.wikipedia.org/wiki/Oblique_Strategies -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

Discussing Modern Development Techniques in Embedded SystemsIn this episode of the Agile Embedded Podcast, hosts Jeff Gable and Luca Ingianni play buzzword bingo, discussing various modern development techniques, tools, and methodologies in the context of embedded systems. They explore the relevance and applicability of terms like microservices, serverless, Kubernetes, Docker, continuous integration, continuous delivery, continuous deployment, A/B testing, API-first design, behavior-driven development, and modern languages such as Rust and C++. They also touch upon the use of AI in development and deployment processes, along with debugging, observability, monitoring, and simulation tools like Memfault, Mender, and Renode. The conversation seeks to provide insights and opinions on which of these techniques and tools are worth investigating or applying to embedded projects.00:00 Introduction to the Agile Embedded Podcast00:06 Exploring Modern Development Buzzwords01:26 Web Technologies in Embedded Systems05:28 Diving into Docker for Embedded Development07:49 Understanding Immutable Infrastructure13:32 Continuous Integration, Delivery, and Deployment19:53 A/B Testing in IoT Devices23:06 API First Design in Embedded Systems26:08 Modern Languages: The Case for Rust27:54 Exploring Rust in Embedded Systems28:37 Challenges with Modern C Programming30:10 Embedded Linux and Language Flexibility32:27 Model-Based Development with Simulink33:53 Modern Tooling for Embedded Systems40:25 AI in Embedded Systems44:05 AI-Assisted Development47:36 Conclusion and Contact Information You can find Jeff at https://jeffgable.com.You can find Luca at https://luca.engineer.Want to join the agile Embedded Slack? Click here

Do you or your team show resistance to change? There are some common ingrained habits that can affect your ability to learn. Find out how difficult conversations, pair programming, and test-driven development can help you create new habits to foster meaningful transformation, in this episode of Troubleshooting Agile. Links: - Toyota Kata: https://en.wikipedia.org/wiki/Toyota_Kata - Karate Kid: https://en.wikipedia.org/wiki/The_Karate_Kid - Shu Ha Ri: https://en.wikipedia.org/wiki/Shuhari - Wardley mapping: https://en.wikipedia.org/wiki/Wardley_map -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

Do you avoid making uncertain predictions in favour of task lists to ensure success? If a fear of being wrong means you can't embrace uncertainty and learn from mistakes then you're missing out on the natural discomfort of learning. Find out more about how to combat this in this episode of Troubleshooting Agile Links: - Toyota Kata: https://en.wikipedia.org/wiki/Toyota_Kata - Recent Kata episode: https://soundcloud.com/troubleshootingagile/toyota-kata-a-z - Thinking, Fast and Slow: https://en.wikipedia.org/wiki/Thinking,_Fast_and_Slow - Kathryn Schulz on being wrong: https://www.ted.com/talks/kathryn_schulz_on_being_wrong -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

When deception overshadows disappointment, severe ethical breaches can occur. Join your hosts, Squirrel and Jeffrey to discover how clear, honest communication can make sure you're not dealing with the next Volkswagen emissions scandal, on this episode of Troubleshooting Agile. Links: - Goal displacement: https://www.oxfordreference.com/display/10.1093/acref/9780191843273.001.0001/acref-9780191843273-e-122 - Passive voice: https://en.wikipedia.org/wiki/Passive_voice - Normalisation of Deviance: https://en.wikipedia.org/wiki/Normalization_of_deviance - Volkswagen emissions scandal: https://en.wikipedia.org/wiki/Volkswagen_emissions_scandal -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

To kick off Elixir Wizards Season 13, The Creator's Lab, we're joined by Zach Daniel, the creator of Igniter and the Ash framework. Zach joins hosts Owen Bickford and Charles Suggs to discuss the mechanics and aspirations of his latest brainchild, Igniter—a code generation and project patching framework designed to revolutionize the Elixir development experience. Igniter isn't just about generating code; it's about generating smarter code. By leveraging tools like Sourcerer and Rewrite, Igniter allows developers to modify source code and batch updates by directly interacting with Elixir's AST instead of regex patching. This approach streamlines new project setup and package installations and enhances overall workflow. They also discuss the strategic implications of Igniter for the broader Elixir community. Zach hopes Igniter will foster a more interconnected and efficient ecosystem that attracts new developers to Elixir and caters to the evolving needs of seasoned Elixir engineers. Topics discussed in this episode: Advanced package installation and code generation improve the developer experience Scripting and staging techniques streamline project updates Innovative methods for smoother installation processes in Elixir packages High-level tools apply direct patches to source code Progressive feature additions simplify the mix phx.new experience Chaining installers and composing tasks for more efficient project setup Continuous improvement in developer experiences to boost Elixir adoption Encourage listeners to collaborate by sharing code generation patterns Introduction of a new mix task aimed at removing the "unless" keyword in preparation for Elixir 1.18 You can learn more in the upcoming book "Building Web Applications with Ash Framework" by Zach and Rebecca Links mentioned: https://smartlogic.io/ https://alembic.com.au/blog/igniter-rethinking-code-generation-with-project-patching https://hexdocs.pm/igniter/readme.html https://github.com/ash-project/igniter https://www.zachdaniel.dev/p/serialization-is-the-secret https://www.zachdaniel.dev/p/welcome-to-my-substack https://ash-hq.org/ https://hexdocs.pm/sourceror/readme.html https://smartlogic.io/podcast/elixir-wizards/s10-e09-hugo-lucas-future-of-elixir-community/ https://github.com/hrzndhrn/rewrite https://github.com/zachdaniel https://github.com/liveshowy/webauthn_components https://hexdocs.pm/elixir/Regex.html https://github.com/msaraiva/vscode-surface https://github.com/swoosh/swoosh https://github.com/erlef/oidcc https://alembic.com.au/ https://www.zachdaniel.dev/ Special Guest: Zach Daniel.

Challenging the iron triangle in software development - balancing quality, time and scope. In this episode, Squirrel and Jeffrey discuss Andy Giese's recent provocative article 'How to Make Product Give a Shit About Your Architecture Proposal.' Join us to learn how you can use ‘feature thinning' and joint design to promote collaborative approaches in situations like this. Links: - Andy G's article: https://gieseanw.wordpress.com/2024/10/09/how-to-make-product-give-a-shit-about-your-architecture-proposal/ - Getting To Yes, on interests and positions: https://en.wikipedia.org/wiki/Getting_to_Yes -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

Brendan Irvine-Broque, Director of Product at CloudFlare, about the latest updates to CloudFlare Workers, including persistent logging, service bindings, and the cutting-edge Hyperdrive. Discover how these innovations are shaping the future of web development and deployment. Links https://x.com/irvinebroque https://workers.cloudflare.com https://www.linkedin.com/in/brendanirvinebroque https://blog.cloudflare.com/author/brendan-irvine-broque We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Let us know by sending an email to our producer, Emily, at emily.kochanekketner@logrocket.com (mailto:emily.kochanekketner@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understand where your users are struggling by trying it for free at [LogRocket.com]. Try LogRocket for free today.(https://logrocket.com/signup/?pdr) Special Guest: Brendan Irvine-Broque.

Boost team results by measuring carefully and using consistent methods to move toward your goal–with “scientific thinking” “the Improvement Kata” and “the Coaching Kata”. In this bumper episode, Squirrel and Jeffrey discuss quality and delivery the Toyota Way. Links: - Toyota Kata: https://public.websites.umich.edu/~jmondisa/TK/Homepage.html - Gemba: en.wikipedia.org/wiki/Gemba Other relevant episodes: - Episode 214 - Get Your Reps In: https://soundcloud.com/troubleshootingagile/get-your-reps-in -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

Your elaborate spreadsheet that prioritises features isn't rigorous mathematical analysis and should be a conversation starter not a definitive guide. Find out how to avoid ‘Mathiness' with Squirrel and Jeffrey in the latest from Troubleshooting Agile. Links: - Mathiness article: https://www.votito.com/methods/mathiness -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/