POPULARITY
Categories
304 episodes with Elixir
192 episodes with Elixir
102 episodes with Elixir
183 episodes with Elixir
125 episodes with Elixir
57 episodes with Elixir
95 episodes with Elixir
55 episodes with Elixir
43 episodes with Elixir
35 episodes with Elixir
61 episodes with Elixir
21 episodes with Elixir
50 episodes with Elixir
44 episodes with Elixir
16 episodes with Elixir
19 episodes with Elixir
17 episodes with Elixir
32 episodes with Elixir
23 episodes with Elixir
7 episodes with Elixir
14 episodes with Elixir
11 episodes with Elixir
31 episodes with Elixir
9 episodes with Elixir
209 episodes with Elixir
11 episodes with Elixir
9 episodes with Elixir
30 episodes with Elixir
19 episodes with Elixir
17 episodes with Elixir
7 episodes with Elixir
6 episodes with Elixir
16 episodes with Elixir
8 episodes with Elixir
9 episodes with Elixir
12 episodes with Elixir
5 episodes with Elixir
9 episodes with Elixir
15 episodes with Elixir
13 episodes with Elixir
13 episodes with Elixir
6 episodes with Elixir
6 episodes with Elixir
15 episodes with Elixir
11 episodes with Elixir
24 episodes with Elixir
7 episodes with Elixir
3 episodes with Elixir
6 episodes with Elixir
6 episodes with Elixir
6 episodes with Elixir
11 episodes with Elixir
6 episodes with Elixir
13 episodes with Elixir
4 episodes with Elixir
3 episodes with Elixir
5 episodes with Elixir
4 episodes with Elixir
3 episodes with Elixir
3 episodes with Elixir
2 episodes with Elixir
5 episodes with Elixir
4 episodes with Elixir
4 episodes with Elixir
10 episodes with Elixir
9 episodes with Elixir
3 episodes with Elixir
3 episodes with Elixir
4 episodes with Elixir
3 episodes with Elixir
2 episodes with Elixir
3 episodes with Elixir
2 episodes with Elixir
9 episodes with Elixir
11 episodes with Elixir
3 episodes with Elixir
2 episodes with Elixir
2 episodes with Elixir
3 episodes with Elixir
7 episodes with Elixir
7 episodes with Elixir
3 episodes with Elixir
9 episodes with Elixir
2 episodes with Elixir
4 episodes with Elixir
65 episodes with Elixir
3 episodes with Elixir
2 episodes with Elixir
9 episodes with Elixir
2 episodes with Elixir
2 episodes with Elixir
2 episodes with Elixir
3 episodes with Elixir
3 episodes with Elixir
7 episodes with Elixir
3 episodes with Elixir
15 episodes with Elixir
3 episodes with Elixir
3 episodes with Elixir
2 episodes with Elixir
6 episodes with Elixir
2 episodes with Elixir
2 episodes with Elixir
2 episodes with Elixir
5 episodes with Elixir
8 episodes with Elixir
6 episodes with Elixir
3 episodes with Elixir
Welcome to the circus. In this solo episode, Barrett Gruber tracks the escalating hilarity of our current political and legal realities. We pull back the curtain on the resolution of Donald Trump's massive $10 billion lawsuit, mapping out how the negotiations looked less like a legal battle and more like someone "negotiating with himself in the mirror."We break down the math behind a highly symbolic $1.776 billion federal settlement fund and look at the jaw-dropping moment a sci-fi horror plot involving a "resurrection drug" was casually dropped into national headlines. Finally, Barrett brings it back home with a look at the local redistricting chaos and voter suppression tactics keeping South Carolina politics predictably scandalous, finishing with a necessary philosophical plea for collective nonchalance in a fundamentally chaotic world.Key Topics: #PoliticalSatire #TrumpLawsuit #ResurrectionElixir #SouthCarolinaPolitics #VoterSuppression #LegalComedy #CurrentEvents2026The All About Nothing: Check Your Voter RegistrationBarrett Gruber | LinktreeThe All About Nothing: Podcast | LinktreeBlack White Blue in the South | Instagram, Facebook | LinktreeClick here for Episode Show Notes!As always, "The All About Nothing: Podcast" is owned and distributed by BIG Media LLC!Check out our network of fantastic podcasts!Click Here to see available advertising packages!Click Here for information on the "Fair Use Copyright Notice" for this podcast.Mentioned in this episode:ZJZ DesignsCheck out the 4th of July Heart Designs for this Independence Day! Visit zjzdesigns.com!ZJZ DesignsCheck Your Voter RegistrationVisit https://theallaboutnothing.com/voter to check your registration! It takes less than 2 minutes. Do it now!BIG Media Copyright 2026BIG Media LLC
¿Has escuchado hablar de los sueros para tener más energía después de una fiesta? ¿Para ‘desintoxicar' o rejuvenecer? Los vitamin drips se volvieron tendencia en Instagram y TikTok. Pero en las últimas semanas hemos escuchado casos graves por el uso de éstos: 8 muertes, 1 hospitalizado grave y 2 recuperados tras aplicarse sueros vitaminados. Hoy, de la mano del doctor Ismael Axayácatl Juárez Galindo desmenuzamos qué son y por qué se pusieron de moda.
Hosts: Ed Jones (Owner – Nutrition World & The Holistic Navigator) & Clint Powell A variety of topics all related to living a healthy life Presented by: Nutrition World www.nutritionw.com Broadcasting from the Nooga Dentistry Studio www.noogadentistry.com Production of: Whitfield Media Group www.vitalhealthradio.com Title: Interview with Dr. Fleetwood – Diseases of the Drugs and The Disease Reversal Project [0:00:00] Opening, Banter, Events Ed & Clint banter about boxing lessons for Ed's daughter and local restaurants (Hennings, Sweet Basil, Cava). Ed's recent stomach bug and renewed appreciation for feeling well. Ed's Fox News appearance (AI for fitness and sleep). Brief mention of FDA commissioner change and concerns about vaping policy. Announcements: NeuroLens screening at Nutrition World (May 29, 1–3 PM). Sound bath event at the Wellness Corner (May 31, 1 PM). Mention of Tallow House (tallow‑focused restaurant) opening in Cleveland. [0:15:39] Interview with Dr. Christy Fleetwood & Dr. Dearing Dr. Fleetwood's journey: pharmacist → naturopathic doctor after seeing drug‑induced problems and experiencing her own unresolved illness. After less than a decade in pharmacy, she noticed disturbing patterns with drugs (e.g., antihypertensives, statins) and enrolled at Bastyr University to become a naturopathic doctor in the late 80s.. Overview of her book “Diseases of the Drugs” / The Disease Reversal Project (cardio‑metabolic focus: high BP, cholesterol, type 2 diabetes). Emphasis on informed consent and lifestyle‑based disease reversal, not just drug management. Critique of statins, CoQ10 depletion, and over‑lowering cholesterol targets; possible links to dementia, ED, and fertility issues. Dr. Dearing's shift from running drug‑centered clinics to using plant‑based diet and deprescribing in diabetes care. Mention of a practitioner‑only deprescribing guide for diabetes, dyslipidemia, and hypertension. How to get the book: christiefleetwood.com/books [0:39:34] Products, Carnivore Conference, Vitamin D Product highlight: Vita Prima “Nature's Elixir” tallow shampoo used as soap; focus on moisturizing, clean ingredients. Ed's recap of a carnivore / “Meat Stock” conference in Gatlinburg: ~700 attendees; many report life‑changing results from meat‑heavy, low‑carb eating. Ed's stance: prefers high‑protein, healthy‑fat, low‑carb with some healthy carbs; stresses clean, quality meats. Discussion of oxalates (from “Toxic Superfoods” by Sally Norton) and their role in joint and other issues; link to Ed's double hip replacement. Mention of Casey & Calley (Vani) Means and their book “Good Energy”; pushback against medical dogma. Takeaways from Dr. Berg talk on vitamin D: Symptoms of low D (back pain, mood, infections, glaucoma, hair loss, brain fog). Idea of vitamin D resistance and downregulated receptors in chronic illness. [0:55:41] Consumer Wins, Labs, Closing Food Babe (Vani Hari) wins: Aldi banning 44 additives (e.g., BHA, BHT, titanium dioxide) from store brands; “vote with your dollars.” Quick note: intermittent fasting research suggesting possible links to hair loss in some individuals. Side note: Kraft macaroni & cheese formula changes over decades (additives then partial clean‑up). Plug for Be Well Labs and BeginWithLabs.com (advanced bloodwork, IV therapy, especially when acutely ill). Closing appreciation for multi‑generation Nutrition World customers and final sign‑off. The post Radio Show / Podcast – May 17, 2026 first appeared on Vital Health Radio.
In Season 15 episode 3, Charles Suggs sits down with Greg Medland, aka “The Elixir Fixer,” to talk about the current state of hiring and the software jobs market in 2026. Greg shares what he's seeing from both sides of the hiring process as an Elixir-focused recruiter, from shifting company expectations to the growing importance of specialization, communication skills, and real-world product thinking. We discuss how the market has changed since the 2021–2022 hiring boom, why things feel more uncertain today, and how developers are adapting to a slower, more competitive landscape. The conversation also explores how AI is affecting hiring workflows, résumé quality, technical interviews, and even the rise of fraudulent candidates. Greg explains why human relationships and reputation still matter more than ever, especially in smaller ecosystems like Elixir where community connections carry real weight. Along the way, we talk about what junior developers are up against, why senior engineers with domain expertise continue to stand out, and what developers can do to position themselves more effectively in today's market. Greg shares practical advice for building a sustainable career, developing a clear professional identity, and navigating a rapidly changing industry. Topics discussed in this episode: The current state of the Elixir job market Hiring trends and market shifts since 2021–2022 How AI is changing hiring and recruiting workflows Fraudulent candidates and AI-generated résumés Domain expertise vs. generalist engineering skills Product thinking and customer-focused development What companies are looking for in 2026 Junior developer challenges in the current market Why senior specialists remain in demand Networking and relationship-building in tech Open source contributions and visibility in the Elixir community Standing out in a crowded hiring environment Résumé quality and application strategies The role of personal branding for developers Remote work trends and geographic hiring patterns Technical interview expectations and evaluation changes Startup vs. enterprise hiring differences Human connection in an increasingly automated industry Career resilience and long-term positioning Building a sustainable software engineering career Links mentioned: Socially Responsible Recruitment https://sr2rec.com/en/ Greg's LinkedIn https://www.linkedin.com/in/elixirfixer/ Greg's email address: greg@sr2rec.com
What if the pill you believed would save your life was slowly killing you? In the third century, the most powerful ruler in human history, Qin Shi Huang, the first Emperor of China, was secretly drinking mercury. His court alchemists called it the Elixir of Immortality. He called it hope. History calls it the thing that killed him. In this episode of For the Love of History, TK takes you on a journey through humanity's oldest obsession: cheating death. From the mercury-laced elixirs of ancient China to the gold tinctures of 16th-century French courts, to the blood plasma injections and cryonic freezing of today's Silicon Valley billionaires — the methods have changed, but the madness hasn't. In this episode, we cover:
In Season 15 episode 2, Elixir Wizards Sundi Myint and Charles Suggs chat with Micah Cooper to talk about distributed systems, data replication, and what it actually looks like to build these ideas in Elixir. Micah shares his journey from Ruby to Elixir and walks us through Visor, a library he's building based on the Viewstamps replication algorithm. Inspired by systems like TigerBeetle, Visor explores how you can replicate state across nodes using GenServers, giving you fault tolerance and recovery without relying entirely on traditional database patterns. We talk about the difference between distributed systems and data replication, where things tend to get misunderstood, and what changes when you start thinking about state this way. The conversation also touches on event sourcing, tradeoffs in system design, and how Elixir's distributed model makes some of these concepts more approachable than you might expect. Along the way, we talk about building for curiosity, experimenting with new ideas, and how projects like this push the ecosystem forward. Topics discussed in this episode: Building Visor and working with the Viewstamps replication model Replicating GenServer state across nodes Distributed systems vs. data replication Lessons from TigerBeetle and financial system design Event sourcing challenges and tradeoffs Rethinking database-first architectures Snapshotting, recovery, and fault tolerance The role of Elixir's distributed model Experimentation, learning, and building for curiosity Links mentioned: Micah's GitHub https://github.com/mrmicahcooper Micah's GitLab https://gitlab.com/mrmicahcooper The Visor repository: https://gitlab.com/mrmicahcooper/visor Visor Hex Package https://hex.pm/packages/visor Ruby on Rails https://rubyonrails.org/ Phoenix LiveView Framework https://www.phoenixframework.org/ Zig Programming Language https://ziglang.org/ TigerBeetle https://tigerbeetle.com/ TigerBeetle internal docs https://github.com/tigerbeetle/tigerbeetle/tree/main/docs/internals The BEAM https://www.erlang-solutions.com/blog/the-beam-erlangs-virtual-machine/ GenServer https://hexdocs.pm/elixir/GenServer.html Apache Kafka https://github.com/apache/kafka RabbitMQ https://www.rabbitmq.com/ Redpanda https://www.redpanda.com/ SQL https://www.ibm.com/think/topics/structured-query-language Kubernetes https://kubernetes.io/ YAML https://yaml.org/ Nomad Workload Orchestrator https://developer.hashicorp.com/nomad Flutter https://flutter.dev/ Commanded https://hexdocs.pm/commanded/Commanded.html Go Programming Language https://go.dev/ Clojure Programming Language https://clojure.org/ Nebulex https://hexdocs.pm/nebulex/Nebulex.html Mnesia https://www.erlang.org/doc/apps/mnesia/mnesia.html Cachex https://hexdocs.pm/cachex/Cachex.html libgraph https://hexdocs.pm/libgraph/Graph.html Horde https://hexdocs.pm/horde/Horde.Registry.html NocFree split keyboard https://www.nocfree.com/ Micah's LinkedIn https://www.linkedin.com/in/micah-cooper-4a737560/
Sally Lait joins Robby Russell on Maintainable to explore software maintainability through a different lens… not just code quality, but how teams work together over time. Sally is a fractional technology leader and advisor with more than two decades in the industry. You can follow her on LinkedIn or Mastodon. They start with a familiar question: what makes software well maintained? Structure and standards matter, but Sally shifts the focus to signals around the edges… documentation, onboarding speed, knowledge sharing, and especially how confident people feel making changes. That confidence becomes the thread throughout the conversation. Teams with high confidence move faster and adapt more easily. Teams with low confidence hesitate, avoid parts of the system, and struggle to make progress… regardless of what the code looks like. Robby and Sally also dig into why maintenance work often struggles to get traction. It rarely speaks for itself. Leaders need to connect it to outcomes the business already cares about… risk, hiring, delivery speed, and long-term sustainability. Sally references a LeadDev panel she moderated on why maintenance still feels “stuck in 2015”: Why Software Maintenance Is Stuck in 2015. They also discuss modernizing legacy systems and moving away from long-standing in-house software… work that is rarely just technical. It requires trust, clear communication, and navigating the emotional attachment teams have to what they've built. The episode closes with advice for engineers joining older codebases: stay curious, build relationships early, and use onboarding gaps as opportunities to improve things for the next person. Episode Highlights [00:01:02] What Makes Software Maintainable: Technical quality matters, but cultural signals often tell the deeper story. [00:05:45] Why Progress Still Feels Slow: Even with improvements, teams can feel stuck due to perception gaps. [00:07:30] Communicating Small Wins: Lack of visibility into incremental progress impacts morale and confidence. [00:12:40] Influencing Without Manipulating: Maintenance work needs to be framed in business terms. [00:16:00] Technical Debt as a Hiring Problem: Outdated systems affect recruiting and retention. [00:20:22] Modernizing a Siloed System: Unlocking legacy data required both technical and organizational change. [00:26:55] Building Trust for Change: Surprise proposals fail… alignment takes time. [00:32:39] Letting Go of “Our Baby”: Replacing systems involves emotional and cultural dynamics. [00:46:25] Joining an Older Codebase: Practical advice for onboarding and building confidence quickly. Resources Mentioned Sally Lait Sally Lait on LinkedIn Sally Lait on Mastodon Why Software Maintenance Is Stuck in 2015 (LeadDev Panel) Lara Hogan The Murderbot Diaries by Martha Wells Death of the Author by Nnedi Okorafor Sally's Reading & Reviews Site Thanks to Our Sponsors! Your test coverage says 90%, but that might be misleading. Undercover CI looks at your Ruby pull requests and shows you which parts of your changes weren't tested- not just overall coverage, but what changed and what got missed, down to the method level. Visit undercover-ci.com and use code MAINTAINABLE for 15% off your first billing cycle. Free for public repos. Private repos with unlimited users also available. Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and other frameworks. It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications. Keep your coding cool and error-free, one line at a time! Use the code maintainable to get a 10% discount for your first year. Check them out! Subscribe to Maintainable on:Apple PodcastsSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.
In this episode, Dr. David Jockers reveals the powerful benefits of apple cider vinegar, an ancient elixir known for boosting fat burning and enhancing cellular energy. You'll learn how this simple ingredient can help balance blood sugar and support better digestion. Dr. Jockers explains how apple cider vinegar activates the vagus nerve, improving digestion and reducing bloating. It also strengthens the gut microbiome, promoting the growth of healthy bacteria while limiting harmful microbes. Throughout the episode, Dr. Jockers shares practical tips on how to incorporate apple cider vinegar into your daily routine for maximum benefits, from improving energy levels to supporting skin health and reducing cravings. In This Episode: 00:00 Acne Face Wash Recipe 00:26 Podcast Welcome and Coaching 04:18 Apple Cider Vinegar Origins 05:20 Gut and Mitochondria Benefits 09:16 Blood Sugar and Weight Studies 13:33 Topical Uses Acne Warts 15:13 Detox Baths and Dandruff 16:33 Sore Throat and Home Cleaning 17:33 FAQs Dilution and Safety 20:51 Wrap Up and Final Outro If you want to burn belly fat…boost your energy levels…balance blood sugar…or relieve swelling in your legs or feet… Then you need to check out PureHealth Research immediately. This company makes some amazing health-boosting supplements that are manufactured right here in America. They only use natural, non-GMO ingredients that are backed by the latest science and proven to work. And right now, you can save 35% on all of their products with this special subscriber-only offer. Just use your exclusive coupon code JOCKERS at checkout. If you're feeling wired, tired, and depleted, it's time to replenish your electrolytes with Relight from Redmond. Made with Redmond's Real Salt, this clean formula provides essential electrolytes like sodium, potassium, and magnesium without any sugar or artificial ingredients. Perfect for those under stress, fasting, or living an active lifestyle, Relight helps restore hydration, improve energy, and support mental clarity. Visit RedmondLife.com/DrJockers and use code JOCKERS for 15% off today! "Apple cider vinegar helps balance blood sugar, reduces cravings, and supports a healthy gut microbiome by promoting beneficial bacteria." ~ Dr. Jockers Subscribe to the podcast on: Apple Podcast Stitcher Spotify PodBean TuneIn Radio Resources: Visit https://www.purehealthresearch.com/ - Use code DRJOCKERS for 35% Visit RedmondLife.com/DrJockers and use code JOCKERS for 15% off today! Connect with Dr. Jockers: Instagram – https://www.instagram.com/drjockers/ Facebook – https://www.facebook.com/DrDavidJockers YouTube – https://www.youtube.com/user/djockers Website – https://drjockers.com/ If you are interested in being a guest on the show, we would love to hear from you! Please contact us here! - https://drjockers.com/join-us-dr-jockers-functional-nutrition-podcast/
Neste episódio especial de Dia do Trabalho, refletimos sobre o trabalho feminino de uma forma sensível, histórica e acolhedora.Mais do que falar sobre mercado de trabalho, este episódio é um convite para reconhecer todas as formas de trabalho que fazem parte da vida das mulheres — visíveis ou invisíveis, tradicionais ou modernos.Uma homenagem àquelas que constroem, cuidam, criam, transformam… cada uma à sua maneira.✨ Porque hoje, mais do que nunca, temos a possibilidade de escolher o caminho que faz sentido para o nosso coração.
In the Elixir Wizards season 15 premiere, host Charles Suggs is joined by Holden Oullette, Senior Security Software Engineer at Netflix and maintainer of Sobelow, to talk about how security is evolving in the Elixir ecosystem. We discuss how certain features of the Elixir programming language (like functional patterns and server-side rendering) provide natural immunity against some common vulnerabilities, and what that means as the language continues to grow. Holden shares how tools like Sobelow are adapting and how new technologies like LLMs and Elixir's type system may help to strengthen security practices. We cover supply chain risks, ecosystem-level responsibility and reputation management, and how initiatives like AEGIS are prepping the community for more widespread adoption. We wrap with practical tips for teams to be more security-minded throughout the software development lifecycle without slowing everything down. Key topics discussed in this episode: How Elixir's design influences secure-by-default development Security tradeoffs between server-side and client-heavy architecture Supply chain risks and what the ecosystem is doing to prepare Static analysis with tools like Sobelow and AST-based pattern matching Where LLMs fit into modern security workflows The role of Elixir's upcoming type system in improving tooling Securing CI/CD pipelines and production environments Balancing development speed with security requirements Dependency management and vulnerability monitoring The AEGIS Initiative and ecosystem-wide security efforts Links mentioned: Holden's GitHub https://github.com/houllette Elixir Programming Language https://elixir-lang.org/ Security-focused static analysis for the Phoenix Framework https://github.com/nccgroup/sobelow Code Security for Builders https://semgrep.dev/ Erlang Ecosystems Foundation https://erlef.org/ Phoenix Framework https://www.phoenixframework.org/ WebSockets https://hexdocs.pm/phoenix_live_view/Phoenix.LiveView.Socket.html https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API Open Worldwide Application Security Project https://owasp.org/ https://github.com/elixir-ecto/ecto Log4j Vulnerability https://www.ncsc.gov.uk/information/log4j-vulnerability-what-everyone-needs-to-know React2Shell Vulnerability https://www.finra.org/guidance/guidance/cybersecurity-advisory-react2shell The Heartbleed Bug https://www.heartbleed.com/ Elixir Type System https://hexdocs.pm/elixir/main/gradual-set-theoretic-types.html Holden Oullette “Securing the Future: A Roadmap to Making Elixir the Safest Language” ElixirConf 2024 https://youtu.be/gpvKxS6sY8Y Aegis Initiative: Supply Chain Security & Compliance Initiative https://security.erlef.org/aegis/ OIDC Tokens https://openid.net/ Anthropic's Claude Mythos & Cybersecurity https://red.anthropic.com/2026/mythos-preview/ Igniter Code Generation Framework https://github.com/ash-project/igniter https://smartlogic.io/podcast/elixir-wizards/s13-e01-igniter-code-generation-zach-daniel/ Secure-by-default open source software https://www.chainguard.dev/ https://www.docker.com/ https://github.com/dependabot https://docs.aws.amazon.com/apigatewayv2/latest/api-reference/apis-apiid-models.html https://nixos.org/ https://smartlogic.io/podcast/elixir-wizards/s14-e08-nix-for-elixir-apps/ https://fedoraproject.org/ https://kubernetes.io/ https://netflix.github.io/chaosmonkey/ https://netflixtechblog.com/all?topic=chaos-monkeySpecial Guest: Holden Oullette.
Andy shares a recap from his trip to New Club Golf Society's Spring Meeting at Sweetens Cove. He and Dasa discuss the golf course, competition, community, and what makes Sweetens Cove such a special place.
O que é, afinal, o quiet luxury?Neste episódio do Afrodite Podcast, exploramos a estética do luxo silencioso — uma tendência que vai além da moda e revela comportamentos, símbolos e até mudanças econômicas.Em tempos de possível instabilidade financeira, o consumo se transforma: menos ostentação, mais discrição. Mas será que isso representa simplicidade… ou apenas uma nova forma de status?Uma reflexão sobre elegância, identidade, consumo consciente e o verdadeiro significado de luxo.✨ Um episódio para quem deseja viver com mais intenção — dentro e fora do que veste.
Today's episode made free by Elixir Uptown!We're live from Eliseo's bar in Downtown Dallas with Friday Mike Sirois! Cowboys draft talk, some baseball Blake, and Dan's old intern, High School Mike, drops by to explain the bear problem in Japan (00:00) - Open: Live from Elixir Uptown (16:21) - Sports: Cowboys don't follow consensus in drafts (27:21) - Baseball Blake: prospect signings (41:10) - Beyond the Clip: Clavicular walks out of 60 Minutes (01:26:40) - News: Man defends girlfriend with his car (01:45:26) - VM birthdays/Today in History with Heart Attack Man (02:15:07) - Closing Remarks: Eliseo and High School Mike ★ Support this podcast on Patreon ★
Software maintenance is often framed as a technical problem. Refactoring code, fixing bugs, or upgrading dependencies. In this conversation, Robby Russell talks with Rein Henrichs about a different lens, one centered on understanding. Rein is a Principal Software Engineer at Procore, where he works within a large, long-lived system used across the construction industry. Rather than focusing on tooling, Rein emphasizes that well-maintained software is software that makes sense to the people maintaining it. To explain this, Rein introduces the idea of the line of representation, drawing on the work of Richard Cook. Engineers do not interact directly with systems. They rely on representations such as logs, dashboards, and code. These are approximations, not reality, echoing ideas from Plato's Allegory of the Cave. When those representations break down, teams lose shared understanding, what Rein describes as “common ground.” This often shows up as weak signals. Subtle indicators that something is not quite right. They are easy to ignore, but over time they lead to confusion and slower decision-making. Incidents make this especially visible. Rein explains how teams build alignment under pressure, highlighting that the role of an incident commander is coordination, not control. Clear communication matters as much as technical correctness. The conversation also explores how large systems behave in practice. They rarely fail completely. Instead, they degrade in multiple ways at once. While SLOs can help teams respond to customer-facing issues, they do not capture internal clarity or alignment. Rein references W. Edwards Deming to highlight a common trap. Not everything that matters can be measured. High-performing teams often rely on judgment, experience, and shared context. Toward the end, Rein connects these ideas to The Field Guide to Understanding Human Error by Sidney Dekker, challenging the idea that incidents are simply caused by mistakes. Instead, they emerge from the same behaviors that usually lead to success, just under different conditions. For teams working in complex systems, the takeaway is straightforward. Maintaining software depends on maintaining understanding. Links & Resources Procore Rein Henrichs on LinkedIn Concepts & References How Complex Systems Fail – Richard Cook The Field Guide to Understanding Human Error – Sidney Dekker W. Edwards Deming Gerald Weinberg – Secrets of Consulting Referenced in this Conversation Kent Beck: You're Ignoring Optionality and Paying for It Charity Majors: Deploys Are Just the Beginning Heidi Helfand: The Art and Wisdom of Changing Teams Thanks to Our Sponsor! Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and other frameworks. It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications. Keep your coding cool and error-free, one line at a time! Use the code maintainable to get a 10% discount for your first year. Check them out! Subscribe to Maintainable on:Apple PodcastsSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.
We're proud to release this ahead of Ryan's keynote at AIE Europe. Hit the bell, get notified when it is live! Attendees: come prepped for Ryan's AMA with Vibhu after.Move over, context engineering. Now it's time for Harness engineering and the age of the token billionaires.Ryan Lopopolo of OpenAI is leading that charge, recently publishing a lengthy essay on Harness Eng that has become the talk of the town:In it, Ryan peeled back the curtains on how the recently announced OpenAI Frontier team have become OpenAI's top Codex users, running a >1m LOC codebase with 0 human written code and, crucially for the Dark Factory fans, no human REVIEWED code before merge. Ryan is admirably evangelical about this, calling it borderline “negligent” if you aren't using >1B tokens a day (roughly $2-3k/day in token spend based on market rates and caching assumptions):Over the past five months, they ran an extreme experiment: building and shipping an internal beta product with zero manually written code. Through the experiment, they adopted a different model of engineering work: when the agent failed, instead of prompting it better or to “try harder,” the team would look at “what capability, context, or structure is missing?”The result was Symphony, “a ghost library” and reference Elixir implementation (by Alex Kotliarskyi) that sets up a massive system of Codex agents all extensively prompted with the specificity of a proper PRD spec, but without full implementation:The future starts taking shape as one where coding agents stop being copilots and start becoming real teammates anyone can use and Codex is doubling down on that mission with their Superbowl messaging of “you can just build things”.Across Codex, internal observability stacks, and the multi-agent orchestration system his team calls Symphony, Ryan has been pushing what happens when you optimize an entire codebase, workflow, and organization around agent legibility instead of human habit.We sat down with Ryan to dig into how OpenAI's internal teams actually use Codex, why the real bottleneck in AI-native software development is now human attention rather than tokens, how fast build loops, observability, specs, and skills let agents operate autonomously, why software increasingly needs to be written for the model as much as for the engineer, and how Frontier points toward a future where agents can safely do economically valuable work across the enterprise.We discuss:* Ryan's background from Snowflake, Brex, Stripe, and Citadel to OpenAI Frontier Product Exploration, where he works on new product development for deploying agents safely at enterprise scale* The origin of “harness engineering” and the constraint that kicked off the whole experiment: Ryan deliberately refused to write code himself so the agent had to do the job end to end* Building an internal product over five months with zero lines of human-written code, more than a million lines in the repo, and thousands of PRs across multiple Codex model generations* Why early Codex was painfully slow at first, and how the team learned to decompose tasks, build better primitives, and gradually turn the agent into a much faster engineer than any individual human* The obsession with fast build times: why one minute became the upper bound for the inner loop, and how the team repeatedly retooled the build system to keep agents productive* Why humans became the bottleneck, and how Ryan's team shifted from reviewing code directly to building systems, observability, and context that let agents review, fix, and merge work autonomously* Skills, docs, tests, markdown trackers, and quality scores as ways of encoding engineering taste and non-functional requirements directly into context the agent can use* The shift from predefined scaffolds to reasoning-model-led workflows, where the harness becomes the box and the model chooses how to proceed* Symphony, OpenAI's internal Elixir-based orchestration layer for spinning up, supervising, reworking, and coordinating large numbers of coding agents across tickets and repos* Why code is increasingly disposable, why worktrees and merge conflicts matter less when agents can resolve them, and what it really means to fully delegate the PR lifecycle* “Ghost libraries”, spec-driven software, and the idea that a coding agent can reproduce complex systems from a high-fidelity specification rather than shared source code* The broader future of Frontier: safely deploying observable, governable agents into enterprises, and building the collaboration, security, and control layers needed for real-world agentic workRyan Lopopolo* X: https://x.com/_lopopolo* Linkedin: https://www.linkedin.com/in/ryanlopopolo/* Website: https://hyperbo.la/contact/Timestamps00:00:00 Introduction: Harness Engineering and OpenAI Frontier00:02:20 Ryan's background and the “no human-written code” experiment00:08:48 Humans as the bottleneck: systems thinking, observability, and agent workflows00:12:24 Skills, scaffolds, and encoding engineering taste into context00:17:17 What humans still do, what agents already own, and why software must be agent-legible00:24:27 Delegating the PR lifecycle: worktrees, merge conflicts, and non-functional requirements00:31:57 Spec-driven software, “ghost libraries,” and the path to Symphony00:35:20 Symphony: orchestrating large numbers of coding agents00:43:42 Skill distillation, self-improving workflows, and team-wide learning00:50:04 CLI design, policy layers, and building token-efficient tools for agents00:59:43 What current models still struggle with: zero-to-one products and gnarly refactors01:02:05 Frontier's vision for enterprise AI deployment01:08:15 Culture, humor, and teaching agents how the company works01:12:29 Harness vs. training, Codex model progress, and “you can just do things”01:15:09 Bellevue, hiring, and OpenAI's expansion beyond San FranciscoTranscriptRyan Lopopolo: I do think that there is an interesting space to explore here with Codex, the harness, as part of building AI products, right? There's a ton of momentum around getting the models to be good at coding. We've seen big leaps in like the task complexity with each incremental model release where if you can figure out how to collapse a product that you're trying to.Build a user journey that you're trying to solve into code. It's pretty natural to use the Codex Harness to solve that problem for you. It's done all the wiring and lets you just communicate in prompts. To let the model cook, you have to step back, right? Like you need to take a systems thinking mindset to things and constantly be asking, where is the Asian making mistakes?Where am I spending my time? How can I not spend that time going forward? And then build confidence in the automation that I'm putting in place. So I have solved this part of the SDLC.swyx: [00:01:00] All right.[00:01:03] Meet Ryan swyx: We're in the studio with Ryan from OpenAI. Welcome.Ryan Lopopolo: Hi,swyx: Thanks for visiting San Francisco and thanks for spending some time with us.Ryan Lopopolo: Yeah, thank you. I'm super excited to be here.swyx: You wrote a blockbuster article on harness engineering. It's probably going to be the defining piece of this emerging discipline, huh?Ryan Lopopolo: Thank you. It is it's been fun to feel like we've defined the discourse in some sense.swyx: Let's contextualize a little bit, this first podcast you've ever done. Yes. And thank you for spending with us. What is, where is this coming from? What team are you in all that jazz?Ryan Lopopolo: Sure, sure.Ryan Lopopolo: I work on Frontier Product Exploration, new product development in the space of OpenAI Frontier, which is our enterprise platform for deploying agents safely at scale, with good governance in any business. And. The role of VMI team has been to figure out novel ways to deploy our models into package and products that we can sell as solutions to enterprises.swyx: And you have a background, I'll just squeeze it in there. Snowflake, brick, [00:02:00] stripe, citadel.Ryan Lopopolo: Yes. Yes. Same. Any kind of customerswyx: entire life. Yes. The exact kind of customer that you want to,Vibhu: so I'll say, I was actually, I didn't expect the background when I looked at your Twitter, I'm seeing the opposite.Stuff like this. So you've got the mindset of like full send AI, coding stuff about slop, like buckling in your laptop on your Waymo's. Yes. And then I look at your profile, I'm like, oh, you're just like, you're in the other end too. Oh, perfect. Makes perfect.Ryan Lopopolo: I it's quite fun to be AI maximalist if you're gonna live that persona.Open eye is the place to do it. And it'sswyx: token is what you say.Ryan Lopopolo: Yeah. Certainly helps that we have no rate limits internally. And I can go, like you said, full send at this stay.swyx: Yeah. Yeah. So the Frontier, and you're a special team within O Frontier.Ryan Lopopolo: We had been given some space to cook, which has been super, super exciting.[00:02:47] Zero Code ExperimentRyan Lopopolo: And this is why I started with kind of a out there constraint to not write any of the code myself. I was figuring if we're trying to make agents that can be deployed into end to enterprises, they should be [00:03:00] able to do all the things that I do. And having worked with these coding models, these coding harnesses over 6, 7, 8 months, I do feel like the models are there enough, the harnesses are there enough where they're isomorphic to me in capability and the ability to do the job.So starting with this constraint of I can't write the code meant that the only way I could do my job was to get the agent to do my job.Vibhu: And like a, just a bit of background before that. This is basically the article. So what you guys did is five months of working on an internal tool, zero lines of code over a mi, a million lines of code in the total code base.You say it was cenex, more like it was cenex faster than you would've. If you had done it by end. SoRyan Lopopolo: yeah, thatVibhu: was the mindset going into this, right?Ryan Lopopolo: That's right.[00:03:46] Model Upgrades LessonsRyan Lopopolo: Started with some of the very first versions of Codex CLI, with the Codex Mini model, which was obviously much less capable than the ones we have today.Which was also a very good constraint, right? Quite a visceral feeling to ask the [00:04:00] model to build you a product feature. And it just not being able to assemble the pieces together.Which kind of defined one of the mindsets we had for going into this, which is whenever the model just cannot, you always pop open at the task, double click into it, and build smaller building blocks that then you can reassemble into the broader objective.And it was quite painful to do this. Honestly, the first month and a half was. 10 times slower than I would be. But because we paid that cost, we ended up getting to something much more productive than any one engineer could be because we built the tools, the assembly station for the agent to do the whole thing.[00:04:43] Model Generations, Build Systems & Background ShellsRyan Lopopolo: But yeah, so onward to G BT 5, 5, 1, 5, 2, 5, 3, 5 4. To go through all these model generations and see their kind of corks and different working styles also meant we had to adapt the code base to change things up when the model was revved. [00:05:00] One interesting thing here is five two, the Codex harness at the time did not have background shells in it, which means we were able to rely on blocking scripts to perform long horizon work.But with five, three and background shells, it became less patient, less willing to block. So we had to retool the entire build system to complete in under a minute and. This is not a thing I would expect to be able to do in a code base where people have opinions. But because the only goal was to make the Asian productive over the course of a week, we went from a bespoke make file build to Basil, to turbo to nx and just left it there because builds were fast at that point.swyx: Interesting. Talk more about Turbo TenX. That's interesting ‘cause that's the other direction that other people have been doing.Ryan Lopopolo: Ultimately I have. Not a lot of experience with actual frontend repo architecture.swyx: You're talking that Jessica built the sky. So I'm like, I know the NX team. I know Turbo from Jared [00:06:00] Palmer.And I'm like, yeah, that's an interesting comparison.[00:06:02] One Minute Build LoopRyan Lopopolo: The hill we were climbing right, was make it fast.swyx: Is there a micro front end involved? Is it how how complex reactRyan Lopopolo: electron base single app sort of thingswyx: And must be under a minute. That's an interesting limitation. I'm actually not super familiar with the background shelf stuff.Probably was talked about in the fight three release.Ryan Lopopolo: BA basically means that codex is able to spawn commands in the background and then go continue to work while it waits for them to finish. So it can spawn an expensive build and then continue reviewing the code, for example.swyx: Yeah.Ryan Lopopolo: And this helps it be more time efficient for the user invoking the harness.swyx: And I guess and just to really nail this, like what does one minute matter? Like why not five, okay, good. We want no. WeRyan Lopopolo: want the inner loop to be as fast as possible. Okay. One minute was just a nice round number and we were able to hit it.swyx: And if it doesn't complete, it kills it or some something,Ryan Lopopolo: No.We just take that as a signal that we need to stop what we're doing, double click, decompose a build graph a bit to get us to high back under so that we [00:07:00] can able the agent continue to operate.swyx: It's almost like you're, it's like a ratchet. It's like you're forcing build time discipline, because if you don't, it'll just grow and grow.That's right. And you mentioned that my current, like the software I work on currently is at 12 minutes. It sucks.Ryan Lopopolo: This has been my experience with platform teams in the past, where you have an envelope of acceptable build times and you let it go up to breach and then you spend two, three weeks to bring it back down to the lower end of the average low bed stop.But because tokens are so cheap Yeah. And we're so insanely parallel with the model, we can just constantly be gardening this thing to make sure that we maintain these in variants, which means. There's way less dispersion in the code and the SDLC, which means we can simplify in a way and rely on a lot more in variance as we write the software.[00:07:45] Observability, Traces & Local Dev StackVibhu: Lovely.[00:07:46] Humans Are BottleneckVibhu: You mentioned in your article, like humans became the bottleneck, right? You kicked off as a team of three people. You're putting out a million line of code, like 1500 prs, basically. What's the mindset there? So as much as code is disposable, you're doing a lot of review. A lot [00:08:00] of the article talks about how you wanna rephrase everything is prompting everything, is what the agent can't see.It's kind of garbage, right? You shouldn't have it in there. So what's like the high level of how you went about building it, and then how you address okay, humans are just PR review. Like how is human in the loop for this?Ryan Lopopolo: We've moved beyond even the humans reviewing the code as well.[00:08:19] Human Review, PR Automation & Agent Code ReviewRyan Lopopolo: Most of the human review is post merge at this point.But post, post merge, that's not even reviewed. That's justswyx: Oh, let's just make ourselves happy by YouRyan Lopopolo: haven't used fundamentally. The model is trivially paralyzable, right? As many GPUs and tokens as I am willing to spend, I can have capacity to work with my hood base.The only fundamentally scarce thing is the synchronous human attention of my team. There's only so many hours in the day we have to eat lunch. I would like to sleep, although it's quite difficult to, stop poking the machine because it makes me want to feed it. You have to step back, right?Like you need to take a systems thinking mindset to things and [00:09:00] constantly be asking where is the agent making mistakes? Where am I spending my time? How can I not spend that time going forward? And then build confidence in the automation that I'm putting in place. So I have solved this part of the SDLC, and usually what that has looked like is like we started needing to pay very close attention to the code because the agent did not have the right building blocks to produce.Modular software that decomposed appropriately that was reliable and observable and actually accrued a working front end in these things, right?[00:09:35] Observability First SetupRyan Lopopolo: So in order to not spend all of our time sitting in front of a terminal at most, doing one or two things at a time, invested in giving the model that observability, which is that that graph in the post here.swyx: Yeah. Let's walk through this traces and which existed firstRyan Lopopolo: we started with just the app and the whole rest of it. From vector through to all these login metrics, APIs was, I dunno, half an [00:10:00] afternoon of my time. We have intentionally chosen very high level fast developer tools. There's a ton of great stuff out there now.We use me a bunch, which makes it trivial to pull down all these go written Victoria Stack binaries in our local development. Tiny little bit of python glue to spin all these up. And off you go. One neat thing here is we have tried to invert things as much as possible, which is instead of setting up an environment to spawn the coding agent into, instead we spawn the coding agent, like that's the entry point.It's just Codex. And then we give Codex via skills and scripts the ability to boot the stack if it chooses to, and then tell it how to set some end variables. So the app and local Devrel points at this stack that it has chosen to spin up. And this I think is like the fundamental difference between reasoning models and the four ones and four ohs of the past, where these models could not think so you had to put them in [00:11:00] boxes with a predefined set of state transitions.Whereas here we have the model, the harness be the whole box. And give it a bunch of options for how to proceed with enough context for it to make intelligent choices. SoVibhu: sales, so like a lot of that is around scaffolding, right? Yes. Previous agents, you would define a scaffold. It would operate in that.Lube, try again. That's pivoted off from when we've had reasoning models. They're seeming to perform better when you don't have a scaffold, right? That's right.[00:11:28] Docs Skills GuardrailsVibhu: And you go into like niches here too, like your SPEC MD and like having a very short agent MG Agent md.swyx: Yes. Yes.Vibhu: Yeah. So you even lay out what it is here, but I likeswyx: the table contents.Vibhu: Yeah.swyx: Like stuff like this, it really helps guide people because everyone's trying to do this.Ryan Lopopolo: This structure also makes it super cheap to put new content into the repository to steer both the humans and the agents.swyx: You, you reinvented skills, right?Vibhu: One big agents andswyx: skills from first princip holdsRyan Lopopolo: all skills did not exist when we started doing this.Vibhu: You have a short [00:12:00] one 100 line overall table of contents and then you have little skills, right? Core beliefs, MD tech tracker. Yeah. Yeah. The scale is overRyan Lopopolo: The tech jet tracker and the quality score are pretty interesting because this is basically a tiny little scaffold, like a markdown table, which is a hook for Codex to review all the business logic that we have defined in the app, assess how it matches all these documented guardrails and propose follow up work for itself.Before beads and all these ticketing systems, we were just tracking follow up work as notes in a markdown file, which, we could spa an agent on Aron to burn down. There's this really neat thing that like the models fundamentally crave text. So a lot of what we have done here is figure out ways to inject textswyx: intoRyan Lopopolo: the system right when we get a page, because we're missing a timeout, for example.I can just add Codex in Slack on that page and say, I'm gonna fix this by adding a timeout. Please update our reliability documentation. To require that all network calls have [00:13:00] timeouts. So I have not only made a point in time fix, but also like durably encoded this process knowledge around what good looks like.swyx: Yeah.Ryan Lopopolo: And we give that to the root coding agent as it goes and does the thing. But you can also use that to distill tests out of, or a code review agent, which is pointed at the same things to narrow the acceptable universe of the code that's produced.swyx: I think one of the concerns I have with that kind of stuff is you think you're making the right call by making, it's persisted for all time across everything.Yes. But then you didn't think about the exceptions that you need to make, right? And that you have to roll it back.Vibhu: Part of it isswyx: also sometimes it can follow your s instructions too.Vibhu: It's somewhat a skill, right? So it determines when it uses the tools, right? Like it's not like it'll run outta every call.It'll determine when it wants to check quality score, right?Ryan Lopopolo: Yeah. And we do in the prompts we give these agents, allow them to push back,[00:13:51] Agent Code Review RulesRyan Lopopolo: When we first started adding code review agents to the pr, it would be Codex, CLI. Locally writes the change, pushes up a PR on [00:14:00] those PR synchronizations of review agent fires.It posts a comment. We instruct Codex that it has to at least acknowledge and respond to that feedback. And initially the Codex driving the code author was willing to be bullied by the PR reviewer, which meant you could end up in a situation where things were not converging. So yeah, we had to,swyx: he's just a thrash.Ryan Lopopolo: We had to add more optionality to the prompts on both of these things, right? The reviewer agents were instructed to bias toward merging the thing to not surface anything greater than a P two in priority. We didn't really define P two, but we gave it, youswyx: did define P two.Ryan Lopopolo: We gave it a framework within which to score its outputswyx: and then greater than P zero is worse, right?Yes. P two is very good.Ryan Lopopolo: P zero is you will mute the code place ifswyx: you merch thisRyan Lopopolo: thing, right?swyx: Yeah.Ryan Lopopolo: But also on the code authoring agent side, we also gave it the flexibility to either defer or push back against review feedback, right? This happens all the time, right? Like I happen to notice something and leave a code review, [00:15:00] which.Could blow up the scope by a factor of two. I usually don't mean for that to be addressed Exactly. In the moment. It's more of an FYI file it to the backlog, pick it up in the next fix it week sort of thing. And without the context that this is permissible, the coding agents are gonna bias toward what they do, which is following instructions.swyx: Yeah.[00:15:19] Autonomous Merging Flowswyx: I do wanted to check in on a couple things, right? Sure. All the coding review agent, it can merge autonomously. I think that's something that a lot of people aren't comfortable with. And you have a list here of how much agents do they do Product code and tests, CI configuration and release tooling, internal Devrel tools, documentation eval, harness review, comments, scripts that manage the repository itself, production dashboard definition files, like everything.Yes. And so they're just all churning at the same time, is there like a record that, that any human on the team pulls to stop everythingRyan Lopopolo: Because we are building a native application here. We're not doing continuous deploy. So there's still a human in the loop for cutting the release branch.I see. We require a blessed [00:16:00] human approved smoke test of the app before we promote it to distribution, these sort of things.swyx: So you're working on the app, you're not building like infrastructure where you have like nines of reliability, that kinda stuff?Ryan Lopopolo: That's correct. That's correct. Okay. And also like full recognition here that all of this activity took in a completely greenfield repository.There's. Should be no script that this applies generally toswyx: this is a production thing, you're gonna shipRyan Lopopolo: toswyx: customers. Of course. Yeah, of course. So this is realVibhu: And like one of the things there is, you mentioned you started this as a repo from scratch. The onboarding first month or so was pretty, it was like working backwards, right?Yeah. And then you had to work with the system and now you're at that point where you know, you're very autonomous. I'm curious like, okay, so what, how human in the loop is it? So what are the bottlenecks that you wish you could still automate? And part of that is also like, where do you see the model trajectory improving and offloading more human in the loop?We just got 5.4. It's a really good,Ryan Lopopolo: fantastic model, by the way.Vibhu: Yeah. Yeah. It's the first one that's merged. Top tier coding. So it's codex level coding and reasoning. So general reasoning both in one model. SoRyan Lopopolo: andVibhu: computer [00:17:00] use vision.Ryan Lopopolo: Now we now with five four, I can just have Codex write the blog post, whereas for this one I had to balance between chat.swyx: Oh, I need to, I might be out of a job. Oh my God.Ryan Lopopolo: Oh,swyx: I know. You just gave me an idea for a completely AI newsletter that five four could do. Yeah, I get it Now.Ryan Lopopolo: This sort of thing is just one example of closing the loop, right? Like the dashboard thing you mentioned. We have Codex authoring the Js ON, for the Grafana dashboards and publishing them and also responding to the pages, which means when it gets the page, it knows exactly which dashboards are defined and what alerts.What alert was triggered by which exact log in the code base. ‘cause all of this stuff is collated together.swyx: It has to own everything.Yes. Yeah. Yeah.Ryan Lopopolo: And it means that if we have an outage that did not result in a page. It has the existing set of dashboards available to it. It has the existing set of metrics and logs and can figure out where the gaps in the dashboard are or [00:18:00] in the underlying metrics and fix them in one go.In the same way, you would have a full stack engineer be able to drive a feature from the backend all the way to the front end.Vibhu: So it, it seems like a lot of the work you guys had to do was you as a small team are fully working for a way that the model wants the software to be written. It's like less human legible for better. Code legibility, agent legibility. How do you think that affects broader teams? So one at OpenAI, do liaison, like this is how software should be written. Like I can imagine, say you join a new team with this methodology, this mindset there's ways that, teams do code review, teams write code, like teams are structured and a lot of it is for human legibility.So should we all swap? Like how does this play back one broader into OpenAI and then like broader into the software engineering, right? Is it like teams that pick this up will it's pretty drastic, right? You have to make a pretty big switch. Should they just full send Yeah.Ryan Lopopolo: The mindset is very much that I'm removed from the process, right? I can't really have deep code level opinions about [00:19:00] things. It's as if I'm. Group tech leading a 500 person organization.Vibhu: Yeah.Ryan Lopopolo: Like it's not appropriate for me to be in the weeds on every pr. This is why that post merge code review thing is like a good analog here, right?Like I have some representative sample of the code as it is written, and I have to use that to infer what the teams are struggling with, where they could use help, where they're already moving quickly and I can pivot my focus elsewhere.Vibhu: Yeah.Ryan Lopopolo: So I don't really have too many opinions around the code as it is written.I do, however, have a command based class, which is used to have repeatable chunks of business logic that comes with tracing and metrics and observability for free. And the thing to focus on is not how that business logic is structured, but that it uses this primitive ‘cause I know that's gonna give leverage by default.Vibhu: Yeah.Ryan Lopopolo: Yeah, back to that sort of systems stinking,Vibhu: and you have part of that in your blog post, enforcing architecture and ta taste how you set boundaries for what's used. There's also a section on redefining [00:20:00] engineering and stuff, but yeah, it's just, it's interesting to hear,Ryan Lopopolo: and as the models have gotten better, they have gotten better at proposing these abstractions to unblock themselves, which again, lets me move higher and higher up the stack to look deeper into the future on what ultimately blocked the team from shipping.swyx: Yeah. You mentioned so you, this is primarily a, it is like a 1 million line of code base electron app. But it manages its own services as well, so it's like a backend for front end type thing.Ryan Lopopolo: We do have a backend in there, but that's hosted in the cloud.Yeah. This sort of structure is actually within the separate main and render processesWithin theswyx: electric.That's just how electronic works.Ryan Lopopolo: Yeah, of course. So have also treated like. MVC style decomposition with the same level of rigor, which has been very fun.swyx: I have a fun pun. This is a tangent, NVC is model view controller. Any sort of full stack web Devrel knows that.But my AI native version of this is Model view Claw, the clause the harness.Ryan Lopopolo: That's right. That's right. I do think that there is an interesting space to [00:21:00] explore here with Codex, the harness as part of building AI products, right? There's a ton of momentum around getting the models to be good at coding.We've seen big leaps in like the task complexity with each incremental model release where if you can figure out how to collapse a product that you're trying to build, a user journey that you're trying to solve into code, it's pretty natural to use the Codex Harness to solve that problem for you. It's done all the wiring and lets you just communicate and prompts to let the model cook.Yeah. It's been very fun. And there's also a very engineering legible way of increasing capabil. It's fantastic, right? Yeah. Just give you, just give the model scripts, the same scripts you would already build for yourself.swyx: Yeah.Yeah. So for listeners, this is Ryan saying that software engineering or coding against will eat knowledge work like the non-coding parts that you would normally think.Oh, you have to build a separate agent for it. No, start a coding agent and go out from there. Which open Claw has like it's pie Underhood.Ryan Lopopolo: [00:22:00] Yes.Vibhu: Basically define your task in code. Everything is a codingswyx: agent by the way. Since I brought it up, it's probably the only place we bring it up. Is any open claw usage from you?Any?Ryan Lopopolo: No. No. Not for me. I don't have any spare Mac Minis rattling around my house.swyx: You can afford it? No. I just, I'm curious if it's changed anything in opening eye yet, but it's probably early days. And then the other, the other thing I, I wanna pull on here is like you mentioned ticketing systems and you mentioned prs and I'm wondering if both those things have to go away or be reinvented for this kind of coding.So the git itself and is like very hostile to multi-agent.Ryan Lopopolo: Yeah. We make very heavy use of work trees.swyx: But like even then, like I just did a, dropped a podcast yesterday with Cursors saying, and they said they're getting rid of work trees ‘cause it still has too many merge conflicts.It's still un too un unintuitive. But go ahead.Ryan Lopopolo: The models are really great at resolving merge conflicts. Yeah. And to get to a state where I'm not synchronously in the loop in my terminal, I almost don't care that there are mergeswyx: with disposable.[00:23:00] Yeah.Ryan Lopopolo: We invoke a dollar land skill and that coaches codex to push the PR Wait for human and agent reviewers Wait for CI to be green.Fix the flakes if there are any merged upstream. If the PR comes into conflict, wait for everything to pass. Put it in the merge queue. Deal with flakes until it's in Maine. End. This is what it means to delegate fully, right? This is in a, very large model re probably a significant tax on humans to get PRS merged, but the agent is more than capable of doing this and I really don't have to think about it other than keep my laptop open.swyx: Yeah. I used to be much more of a control freak, but now I'm like, yeah, actually you could do a better job of this than me. Yeah. With the right context. Yes.[00:23:47] Encoding Requirementsswyx: Anything else in harness in general? Just this piece, I just wanna make sure we,Ryan Lopopolo: I think one thing that I maybe didn't make super clear in the article that I heard on Twitter as an interesting, that's respond [00:24:00]swyx: to them.What's the chatter and then what's your response?Ryan Lopopolo: Ultimately, all the things that we have encoded in docs and tests and review agents and all these things are ways to put all the non-functional requirements of building high scale, high quality, reliable software into a space that prompt injects the agent.We either write it down as docs, we add links where the error messages tell how to do the right thing. So the whole meta of the thing is to basically tease out of the heads of all the engineers on my team, what they think good looks like, what they would do by default, or what they would coach a new hire on the team to do to get things to merch.And that's why we pay attention to all the mistakes, mistakes that the agent makes, right? This is code being written that is misaligned with some as yet not written down, non-functional requirement.swyx: Sorry, what? Did the online people misunderstand orRyan Lopopolo: No,swyx: whatyouRyan Lopopolo: responded to? Somebody just literally said that.I was like, oh yeah,swyx: okay,Ryan Lopopolo: This is the [00:25:00] thing. This is what I've been doing. Oh, youswyx: agree? Yeah. I see. Interesting.Ryan Lopopolo: One other neat thing, which I did totally did not expect is folks were just. Taking the link to the article and giving it to pi or Codex and say, make my repo this,Vibhu: you achi a whole recursion.Ryan Lopopolo: And it was wildly effective. Really? It was wildly effective. NoVibhu: way. It just actually is something I tried with five, four yesterday. I didn't have time. Last time I was like out speaking of something, and this is one of my things, I was like, okay, I have this article. Can we just scaffold out what it would be like to run this?And I, I did it first as that and then I was like, okay, let me take another little side repo and say okay, if I was to fully automate this like this because I haven't written a line of code, it'sRyan Lopopolo: like over full, setVibhu: it right. The side thing I'm doing of voice. TTS I'm just like, slobbing out, whatever.It's nothing production. I'm like, how would I make this like this? And it's actually like a really good way. It's like a good way to learn what could be changed, what could be like, it's just a good analyzing, right? You give it all the codes, you give it all the context, you give it the article and it walks you through it very well.That's right. That's right.[00:25:57] Inlining Dependencies[00:25:57] Dependencies Going Away & Brett Taylor's Responseswyx: I guess one more thing before we go to Symphony is I wanted to cover [00:26:00] Brett Taylor's response. We had him on the show. He is your chairman, which is wild. Yeah. That he's reading your articles as well and like getting engaged in it. He says software dependencies are going away.Basically they can just be like vendored. Yes. Response.Ryan Lopopolo: Aswyx: hundred percent. A hundred percent agree. You still pro qr, you still pay Datadog. You still pay Temporal. Thank you.Ryan Lopopolo: Yep. The level of complexity of the dependencies that we can internalize is, I would say low, medium right now. Just based on model capability.What does the,swyx: what is medium?Ryan Lopopolo: I would say like a. A couple thousand line dependency is a thing that we could in-house No problem. Call in an afternoon of time. One neat thing about it is like probably most of that code you don't even need. Like by in-house and abstraction, you can strip away all the generic parts of it and only focus on what you need to enable the specific thing.Yes. You're building,swyx: I've been calling this the end of b******t plugins.Ryan Lopopolo: Yeah.swyx: Because there's so much when I published an open source thing, I want to accept everything, be liberal. I want to accept, this is post's law, but that means there's so much bloat. Yes. There's so much overhead.Ryan Lopopolo: One other neat thing about [00:27:00] this too is when we deploy Codex Security on the repo, it is able to deeply review and change. The internalized dependencies in a much lower friction way than it would be to like, push patches upstream, wait for them to be released, pull them down, make sure that's compatible with all the transitive I have in my repo and things like that.So it's also much lower friction to internalize some of these things if code is free. ‘cause the tokens are cheap sort of thing.swyx: Yeah. Yeah. I think like the only argument I have against this is basically scale testing, which obviously the larger pieces of software like Linux, MySQL, he calls up even the Datadog and Temporals and then maybe security testing where Yes.Classically, I think, is it linis tos, it said security open source is the best disinfectant.Ryan Lopopolo: Many eyes.swyx: Many eyes. And if inline your dependencies and code them up, you're gonna have to relearn mistakes from other people that Yep.Ryan Lopopolo: Yep. And to internalize that dependency, you're back to zero and you have to start.Reassembling all those bits and pieces to Yeah. Have [00:28:00] high confidence in the code as it is written. Yeah.Vibhu: Even part of the first intro of this, you basically mentioned like everything was written by codex, including internal tooling, right? So internal tooling, like when you're visualizing what's going on it's writing it for itself.swyx: Yeah. I'm built internal tools way I now, and like I just show them off and they're like, how long did you spend? And I didn't spend any time. I just prompted it,Ryan Lopopolo: very funny story here.swyx: Yeah, go ahead.Ryan Lopopolo: We had deployed our app to the first dozen users internally had some performance issues, so we asked them to export a trace for us get a tar ball, gave it to our on-call engineer, and he did a fantastic job of working with Codex to build this beautiful local Devrel tool, next JS app, the drag and drop the tar ball in, and it visualizes the entire trace.It's fantastic. Took an afternoon, but none of this was necessary. Because you could just spin up codex and give it the tar ball and ask the same thing and get the response immediately. So in a way, optimizing for human [00:29:00] legibility of that debugging process was wrong. It kept him in the loop unnecessarily when instead he could have just like Codex cooked for five minutes and gotten this same.swyx: Yeah, you verify your instincts here of this is how we used to do it. Or this is how I would have used to solve it.Ryan Lopopolo: Yeah. In this local observability stack. Like sure, you can de deploy Yeager to visualize the traces, but I wouldn't expect to be looking at the traces in the first place because I'm not gonna write the code to fix them.swyx: Yeah. So basically there needs to be like this kind of house stack and owning the whole loop. I think that is very well established. And it sounds like you might be like sharing more about that in the future, right?Ryan Lopopolo: Yeah. I think we're excited to do[00:29:36] Ghost Libraries Specs[00:29:36] Ghost Libraries & Distributing Software as SpecsRyan Lopopolo: We're gonna talk about Symphony in a little bit, but like the way we distribute it as a spec, which I think folks are calling Ghost Libraries on Twitter.This is like a such a cool name. It does mean it becomes much cheaper to share software with the world, right? You define a spec, how you could build your own specifying as much as is required for a coding agent to reassemble it [00:30:00] locally. The flow here is very cool. Like we have taken. All the scaffolding that has existed in our proprietary repo spun up a new one.Ask Codex with our repo as a reference. Write the spec. We tell it. Spin up a team ox spawn a disconnected codex to implement the spec. Wait for it to be done. Spawn another codex and another team ox to review the spec com or review the implementation compared to upstream and update the spec so it diverges less.And then you just loop over and over Ralph style until you get a spec that is with high fidelity able to reproduce the system as it is. It's fantastic.Vibhu: And you're basically, you're not really adding any of your human bias in there, right? That's correct. A lot of times people write a spec and be like, okay, I think it should be done this way, and you'll riff on something.And it's no, the agent could have just handled it like you're still scaffolding in a sense, right? I want it done this way. It can determine its spec better.swyx: That's right. That's right. Part of me it, I'm, I've been working a lot on evals recently, and part of me is wondering if [00:31:00] an agent can produce a spec that it cannot solve.Is it always capable of things that he can imagine or can you imagine things that it is impossible to do?Ryan Lopopolo: I think with Symphony, we, there's like this there's this axis where you have things that are easier, hard, or established or new, right? And I think things that are hard and new is still something that the models need humans.Yeah. Drive.swyx: Yeah. Yeah.Ryan Lopopolo: But I think those other quadrants are largely salt. Given the right scaffold and the right thing that's gonna drive the agent to completion,swyx: it's crazy that it solved,Ryan Lopopolo: but it means that the humans, the ones with limited time and attention get to work on the hardest stuff, like the problems where it's pure white space out in front. Or like the deepest refactorings where you don't know what the proper shape of the interfaces are. And this is where I wanna spend my time. ‘cause it lets me set up for the next level of scale.swyx: Yeah. Yeah. Amazing. Let's introduce Symphony.I think we've been mentioning it every now and then. Elixir. Interesting option.Ryan Lopopolo: Yeah.swyx: Yeah. I'm not,Ryan Lopopolo: again, like the [00:32:00] elixir manifestation here is just a derivative. Is it a modelswyx: chosen? Yeah.Ryan Lopopolo: Yeah. Yeah. And it chose that because the process supervision and the gen servers are super amenable to the type of process orchestration that we're doing here.You are essentially spinning up little Damons for every task that is in execution and driving it to completion, which. Means the mall gets a ton of stuff for free by using Elixir and the Beam.swyx: I had to go do a crash course in Beam and Elixir, and I think most people are not operating at that scale of concurrency where you need that.But it is a good mental model for Resum ability and all those things. And these are things I care about. But tell me the story, the origin story of Symphony. What do you use it for? Is this, how did it form maybe any abandoned paths that you didn't take?[00:32:46] Terminal Free Orchestration[00:32:46] Symphony: Removing Humans from the LoopRyan Lopopolo: At the end of December we were at about three and a half PRS per engineer per day.This was before five two came out in the beginning of January. Everyone gets back from holiday with five two and no other work [00:33:00] on the repository. We were up in the five to 10 PRS per day per engineer. And I don't know about y'all, but like it's very taxing to constantly be switching like that. Like I was pretty tapped out at the end of the day, again, where are the humans spending their time? They're spending their time context switching between all these active tmox pains to drive the agent forward.swyx: Yeah. No way. Yeah.Ryan Lopopolo: So let's again, build something to remove ourselves from the loop. And this is what frantic sprinted adapt here to find a way to remove the need for the human to sit in front of their terminal.So a lot of experimentation with Devrel boxes and, automatically spinning up agents, like it seems like a fantastic end state here, where my life is beach. I open live twice a day and say yes no to these things. Yeah. And this is again, a super, super interesting framing for how the work is done.Because I become more latency and sensitive. I have [00:34:00] way less attachment to the code as it is written. Like I've had close to zero investment in the actual authorship experience. So if it's garbage. I can just throw it away and not care too much about it. In Symphony, there's this like rework state where once the PR is proposed and it's escalated to the human for review, it should be a cheap review.It is either mergeable or it is not. And if it's not, you move it to rework. The elixir service will completely trash the entire work tree NPR and start it again from scratch. Okay. And this is that opportunity again to say, why was it trash right? What did the agent do that wasswyx: bad. Yeah.Ryan Lopopolo: Fix that before moving the ticket toswyx: endRyan Lopopolo: of progress again.swyx: Yeah. Why is this not in codex app? I guess this, you guys are ahead of Codex app,Ryan Lopopolo: yeah, so the way the team has been working is basically to be as AI pilled as possible and spread ahead. And a lot of the things we have worked on have fallen out [00:35:00] into a lot of the products that we have.Like we were in deep consultation with the Codex team to. Have the Codex app be a thing that exists, right? To have skills be a thing that Codex is able to use. So we didn't have to roll our own to put automations into the product. So all of our automatic refactoring agents didn't have to be these hand rolled control loops.It has been really fantastic to be, in a way, un anchored to the product development of Frontier and Codex and just very quickly try to figure out what works and then later find the scalable thing that can be deployed widely. It's been a very fun way to operate. It's certainly chaotic. I have lost track very often of what the actual state of the code looks like.‘cause I'm not in the loop. There was. One point where we had wired playwright directly up to the Electron app. With MCPM CCPs, I'm pretty bearish on because the harness forcibly injects all those tokens in the [00:36:00] context, and I don't really get a say over it. They mess with auto compaction. The agent can forget how to use the tool.There's probably only what three calls in playwright that I actually ever want to use. So I pay the cost for a ton of things. Somebody vibed a local Damon that boots playwright and exposes a tiny little shim CLI to drive it. And I had zero idea that this had occurred because to me, I run Codex and it's able to, it's oh, it's better.Yeah. Like no knowledge of this at all. Uhhuh.[00:36:30] Multi Human ChaosRyan Lopopolo: So we have had like in human space to spend a lot of time doing synchronous knowledge sharing. We have a daily standup that's 45 minutes long because we almost have to. Fan out the understanding of the current state.swyx: Yeah, I was gonna say this is good for a single human multi-agent, but multi human, multi-agent is a whole like po like explosion of stuff.Ryan Lopopolo: Yeah. And that this is fundamentally why we have such a rigid, like 10,000 [00:37:00] engineer level architecture in the app because we have to find ways to carve up the space so people are not trampling on each other.swyx: Sorry, I don't get the 10,000 thing. Did I miss that?Ryan Lopopolo: The structure of the repository is like 500 NPM packages.It's like architecture to the excess for what you would consider, I think normal for a seven person team. But if every person is actually like 10 to 50. Then the like numbers on being super, super deep into decomposition and sharding and like proper interface boundaries make a lot more sense.swyx: Yeah. To me, that's why I talked about Microfund ends and I, an anex is from that world, but Cool. It is just coming back to, to, to this I dunno if you have other, thoughts on. Orchestrating so much work coin going through this. Is this enough? Is this like any aha moments?Vibhu: It'll be interesting to see like where, okay, so right now you pick linear as your issue tracker, right?swyx: Or it's like a is it actually linear? This is actually linear.[00:37:55] Linear vs Slack WorkflowVibhu: Oh, that's linear. It's linear.swyx: Oh I never looked atVibhu: video. The demo video I had to download to [00:38:00] run.swyx: So I, because I'm a Slack maxie, but Yeah, linear. Linear is also really good. Yes,Ryan Lopopolo: we do make a good use of Slack. We we fire off codex to do all these lotion, elasticity, fix ups, the things that like sync that knowledge into the repository.It's super cheap. Yeah.swyx: Yeah.Ryan Lopopolo: Just do it in Codex.swyx: My biggest plug is OpenAI needs to build Slack. You need to own Slack. Build yours. Turn this into Slack.Ryan Lopopolo: I did read about it. Youswyx: did?Ryan Lopopolo: Yeah.[00:38:25] Collaboration Tools for AgentsRyan Lopopolo: I would say that if we think that we want these agents to do economically valuable work, which is like this is the mission, right?We want AI to be deployed widely, to do economically valuable work, then we need to find ways for them to naturally collaborate with humans, which means collaboration tooling, I think, is an interesting space to explore.swyx: Yeah, totally. Yeah. GitHub, slack, linear.Vibhu: Yeah, that was my thing. Okay, where do we see right now Codex has started Codex Model, then CLI, now there's an app, app can let me shoot off multiple Codex is in parallel, but there's no great team collaboration for Codex.And it [00:39:00] seems like your team had some say into what comes out, right? So you talked to ‘em, codex kind of was a thing. From there, if you guys are on the bound, what stuff that like, you might not focus on, but what do you expect other people to be building, right? So people that are like five x 50 Xing.Should you build stuff that's like very niche for your workflow, for your team? Should it be more general so other people can adopt? Is there a niche there? ‘Cause part of it is just okay, is everything just internal tooling? Do we have everything our own way? Like the way our team operates has our own ways that we like to communicate or is there a broader way to do it?Is it something like a issue tracker? Just thoughts if you wanna riff on that.[00:39:35] Standardizing Skills and CodeRyan Lopopolo: I think TBD we have not figured this out in a general way. I do think that there is leverage to be had in making the code and the processes as much the same as possible. If you think that code is context, code is prompts, it's better from the agent behavior perspective to be able to look in a package in directory X, Y, Z, and it not to have to page so [00:40:00] deeply into directory if you C, because they have the same structure, use the same language, they have the same patterns internally.And that same like leverage comes from aligning on a single set of skills that you're pouring every engineer's taste into to make sure that the agent is effective. So like in our code base, we have, I think, six skills. That's it. And if some part of the software development loop is not being covered, our first attempt is to encode it in one of the existing setup skills, which means that we can change the agent behavior.Yeah. More cheaply than changing the human driver behavior.swyx: Yeah.[00:40:39] Self Improvement via Logsswyx: Have you ever, have you experimented with agents changing their own behavior?Ryan Lopopolo: We do.swyx: Yeah. Or parent agent changing a subagents, behavior or something like that.Ryan Lopopolo: We have some bits for skill distillation. So for example, there's one neat thing you can do with Codex, which is just point it at its own session logs to ask it to tell you how you can use [00:41:00] the tool pedal better.swyx: It's like introspectionRyan Lopopolo: or ask it to do things. I useVibhu: this session better. What skills should Iswyx: high? I like the modification of, you can do, just do things to you can just ask agent to do things.Ryan Lopopolo: Yeah. You can just codex things. This is like a, this is like a silly emoji that we have, right? You can just codex things, you can just prompt things.It's really glorious future we live in, but okay, you can do that one-on-one. But we're actually slurping these up for the entire team into blob storage and. Running agent loops over them every day to figure out where as a team can we do better and how do we reflect that back into the repositories?Yes, though everybody benefits from everybody else's behavior for free. Same for like PR comments, right? These are all feedback. That means the code as written, deviated from what was good, a PR comment, a failed build. These are all signals that mean at some point the agent was missing context. We gotta figure out how toswyx: Yeah.Ryan Lopopolo: Slurp it up and put it back in the reboot.swyx: By the way, I do this exactly right. I used to, when I use cloud code for [00:42:00] knowledge work, cloud cowork is like a nice product, right? Yes. In I think you would agree. I always have it tell me what do I do better next time? And that's the meta programming reflection thing.So I almost think like you have six reflection extraction levels in symphony and almost like the zero of layer. So the six levels are PO policy, configuration, coordination, execution, integration, observability. We've talked about a couple of these, but the zero layer is like the, okay, are we working well?Can we improve how we work? Yes. Can I modify my own workflow without MD or something? I don't know.Ryan Lopopolo: Yeah, of course. Yeah, of course you can. Like this thing is also able to cut its own tickets ‘cause we give it full access.Yeah. Make it a ticket to have it cut. Tickets you can.Put in the ticket that you expect it to file as on follow up work,swyx: like Yeah. Self-modifying. Yeah.Ryan Lopopolo: Yeah.[00:42:44] Tool Access and CLI FirstRyan Lopopolo: Put, don't put the agent in a box. Give the agent full accessibility over it. Domain.swyx: I had a mental reaction when you said don't put the agent in a box. So I think you should put it in a box. Like it's just that you're giving the box everything it needs.Ryan Lopopolo: Yeah. Context and tools.swyx: But we're like, as developers, we're used to calling [00:43:00] out to different systems, but here you use the open source things like the Prometheus, whatever, and you run it locally so that you can have the full loop. I assume.Ryan Lopopolo: Yep.Vibhu: I think likeRyan Lopopolo: another, you wanna minimize cloud, cloud dependencies.Vibhu: You also want to make sure that you think about what the agent has access to. What does it see? Does it go back into the loop, like from the most basic sense of you let it see its own like calls, traces it can determine where it went wrong. But are you feeding that back in? So you know, just the most basic level of you wanna see exactly what's input output, like does the agent have access to.What is being outputted, right? It can self-improve a lot of these things. It's allRyan Lopopolo: text, right? My job is to figure out ways to funnel text from one agent to the other.swyx: It's so strange like way back at the start of this whole AI wave Andre was like, English is the hottest day programming language.It's here, it's just Yeah. The feature as well.Vibhu: A lot of, okay. Like a lot of software, a lot of stuff. There's a gui, it's made for the human. We're seeing the evolution of CLI for everything, right? All tools have CLIs. Your agents can use [00:44:00] them well, do we get good vision? Do we get good little sandboxes?Like right now? It's a really effective way, right? Models love to use tools. They love the best. They love to read through text. So slap a CLI let it go loose. That works for everything.Ryan Lopopolo: It does. Yeah. Yeah.[00:44:14] UI Perception and RasterizingRyan Lopopolo: We've also been adapting nont, textual things to that shape in order to improve model behavior in some ways, right?We want the agent to be able to see the UI agents do not perceive visually in the same way that we do. They don't see a red box, they see red box button, right? They see these things in latent space. So if we want, Hey, yeah, I do. We haveswyx: a ding if that goes off every time. Alien spaceRyan Lopopolo: ding.Anyway if we wanna actually make it see the layout, it's almost easier to rasterize that image to ask EOR and feed it in to the agent. Ha. And there's no reason you can't do both, right? To like further refine how the model perceives the object it's [00:45:00] manipulating.swyx: Cool. Could we, you wanna talk about a couple more of these layers that might bear more introspection or that you have personal passion for?[00:45:07] Coordination Layer with ElixirRyan Lopopolo: I will say that the coordination layer here was a really tricky piece to get right.swyx: Let's do it. Yep. I'm all about that. And this is Temporal core.Ryan Lopopolo: This is where when we turn the spec into Elixir, where like the model takes a shortcut, right? Like it's oh, I have all these primitives that I can make use of in this lovely runtime that has native process supervision.Which is I think, a neat way to have taken the spec and made it more choices achievable by making choices that naturally mapswyx: Yeah.Ryan Lopopolo: To the domain, right? In the same way that like you would prefer to have a TypeScript model repo if you are doing full stack web development, right? Because the ability to share types across the front end and backend reduces a lot of complexity.And becauseswyx: that's what graph kill used to be.Ryan Lopopolo: That's right. Andswyx: I don't know if it's still alive, butRyan Lopopolo: [00:46:00] no humans in the loop here. So like my own personal ability to write or not write elixir. Doesn't really have to bias us away from using the right tool for the job. It is just wild.swyx: Love it. I love it.Yeah. I wonder if any languages struggle more than others because of this? I feel like everyone has their own abstractions. That would make sense. But maybe it might be slower, it might be more faulty where like you'd have to just kick the server every now and then. I, I don't know. I think observability layer is really well understood.Integration layer, CP is dead. I think all these just like a really interesting hierarchy to travel up and down. It's common language for people working on the system to understandRyan Lopopolo: The policy stuff is really cool, right? Yeah. You don't really have to build a bunch of code to make sure the system wait for the, to passswyx: it's institutional knowledge.Ryan Lopopolo: Yeah. You just give it the G-H-C-L-I with some text that say CI has to pass. It makes the maintenance of these systems a lot easier.[00:46:57] Agent Friendly CLI Outputswyx: Do you think that CLI maintainers need to be [00:47:00] do anything special for agents or just as is? It's good because like I don't think when people made the G GitHub, CLI, they anticipated this happening.Ryan Lopopolo: That's correct. The GH CLI is fantastic. It's great super industry.swyx: Everyone go try GH repo create GH pull and then pull request number, right? GH HPR, like 1 53, whatever. And then it like pullsRyan Lopopolo: basically my only interaction with the GitHub web UI at this point is GH PR view dash web.Exactly. Glanceswyx: at the diffRyan Lopopolo: and be like Sure thing. Send it. Yeah. But the CLI are nice ‘cause they're super token efficient and they can be made more token efficient really easily. Like I'm sure you all have seen like I go to build Kite or Jenkins and I could just get this massive wall of build output.And in order to unblock the humans, your developer productivity team is almost certainly gonna write some code that parses the actual exception out of the build logs and sticks it in a sticky note at the top of the page. And you basically [00:48:00] want CLI to be structured in a similar way, right? You're gonna want to patch dash silent to prettier because the agent doesn't care that every file was already formatted.Just wants to know it's either formatted or not. So it can then go run a right command. Similarly, like in our PNPM distributed script runner, when we had one, when you do dash recursive, like it produces a absolute mountain of text. But all of that is for passing. Test suites. So we ended up wrapping all of this in another scriptswyx: to suppress the,Ryan Lopopolo: which you can vibe the channel only output the failing parts of the tests.swyx: You make a pipe errors versus the standard, standard out. I don't know. Okay. Whatever. Too much thinking have to do that. The CII used to maintain SCLI for my company and yeah, this is like core, very core to my heart. But you're vibing my job.Ryan Lopopolo: That's right.swyx: Cool. Any other things?This is a long spec. [00:49:00] I appreciate that. It's got a lot of strong opinions in here. Any other things that we should highlight? I think obviously you can spend the whole day going through some of these, but I do think that some of these have a lot of care or some of this you might wanna tell people, Hey, take this, but, make it your own.[00:49:15] Blueprint Spec and GuardrailsRyan Lopopolo: Fundamentally, software is made more flexible when it's able to adapt to the environment in which it is deployed, which means that things like linear or GitHub even are specified within the spec, but not required pieces of it. There's like a more platonic ideal of the thing that you could swap in like Jira or Bitbucket, for example.But being able to tightly specify things like the ID formats or how the Ralph Loop works for the individual agents. Basically means you can get up and running with a fully specified system quickly that you then evolve later on. I think we never intended for this to be a static spec that you can [00:50:00] never change.It's more like a blueprint to get something worth a starting point up and running.swyx: Yeah.Ryan Lopopolo: For you then to vibe later to your heart's content,swyx: you have like code and scripts in here where it's oh, I think this is a really good prompt. It's just a very long prompt.Ryan Lopopolo: Fundamentally, the agents are good at following instructions, so give them instructions.And it will, improve the reliability of the result. We, much like the way we use Symphony, we don't want folks to have to monitor the agent as it is vibing the system into existence. So being very opinionatedVery strict around what these success criteria are means that our deployment success rate goes up. Yeah. It means we don't have to get tickets on this thing.Vibhu: Think it all goes back to that like code to disposable, right? Like early on when you had CLI or you'd kick off a Codex run, it would take two hours. You would wanna monitor okay, I'm in the workflow of just using one.I don't want it to go down the wrong path. I'll cut it off and, just shoot off four, like that was my favorite thing of the Codex app, right? Yeah. Just Forex it like, [00:51:00] it's okay. One of them will probably be right, one of them might be better. Stop overthinking it. Like my first example was probably like deep research.When you put out deep research and I'd ask it something like, I asked it something about LLM, it thought it was legal something and spent an hour, came back with a report completely off the rails. And I was like, okay, I gotta monitor this thing a bit. No don't monitor it. Just you want to build it so it's that it, it goes the right way.And you don't wanna, you don't wanna sit there and babysit, right? You don't want to babysit your agentsRyan Lopopolo: with that deep research query that you made. Looking at the bad result, you probably figured out you needed to tweak your prompt Yeah. A bit, right? That's that guardrail that you fed back into the code base for the task, your prompt to further align the agent's execution.Same sort of concept supply there too.swyx: When you talk, how are the customers feelingRyan Lopopolo: for Symphony? I think we have none, right? This is a thing we have put out into theswyx: world. Symphony's internal, right? As long as you are happy, you are the customer. That'
Software doesn't become hard to maintain only because the code is messy. It often becomes hard to maintain because the reasoning behind it disappears. In this episode of Maintainable, Robby Russell talks with Russ Olsen about trade-offs, legacy systems, and why maintainability depends on context more than dogma. Russ brings decades of experience across very different kinds of systems, each with its own definition of what “maintainable” actually means. A central theme is that software must be understandable to the people maintaining it. Teams tend to document implementation details well, but often fail to capture system-level intent and the trade-offs behind major decisions. Russ makes the case for preserving that thinking, including the alternatives that were rejected, so future maintainers don't have to rediscover it the hard way. The conversation also touches on Russ's book Eloquent Ruby, Second Edition. Rather than teaching syntax, the book focuses on how Ruby is actually used in practice and why common patterns exist. That leads into a discussion about where elegance improves maintainability, and where it turns into unnecessary cleverness. From there, the episode shifts into the realities of working in legacy systems. Russ explains how teams develop pessimism over time, often accepting flawed assumptions about how their systems behave. In some cases, major issues turn out to be far simpler than expected. The challenge is that teams stop looking. Robby and Russ also discuss the value of fresh perspective. New engineers or outside contributors can surface assumptions that longtime maintainers overlook. Russ suggests finding “pinch points” in a system as a practical way to understand behavior without needing to fully untangle everything at once. Later, the conversation explores developer quality of life. Long build and deploy cycles create daily friction that teams often underestimate. These slow feedback loops quietly degrade productivity and morale over time. The episode also tackles rewrites. Russ warns that teams frequently underestimate how much knowledge is embedded in existing systems. Code that looks questionable may reflect constraints no one documented. In practice, most successful rewrites happen incrementally, not all at once. The conversation wraps with a reminder that software development is fundamentally a social process. Russ argues that engineers undervalue storytelling, even though it's one of the most effective ways to connect technical work to real human outcomes. Episode Highlights [00:00:40] Defining maintainability: Why context matters more than a universal standard [00:02:01] Beyond code comments: Documenting system intent and trade-offs [00:08:14] Who Eloquent Ruby is for: Understanding how Ruby is used in practice [00:16:21] Elegance vs. cleverness: Where maintainability starts to erode [00:23:18] Legacy pessimism: Why teams stop questioning assumptions [00:29:25] Pinch points: A practical way to understand complex systems [00:32:05] Developer experience: The hidden cost of slow feedback loops [00:38:26] Rewrites: Why they fail and what teams overlook [00:44:00] Storytelling: Connecting technical work to real-world impact Resources Mentioned Russ Olsen on LinkedIn Eloquent Ruby, Second Edition Getting Clojure Zen and the Art of Motorcycle Maintenance A History of Western Philosophy Thanks to Our Sponsor! Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and other frameworks. It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications. Keep your coding cool and error-free, one line at a time! Use the code maintainable to get a 10% discount for your first year. Check them out! Subscribe to Maintainable on:Apple PodcastsSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.
En este episodio de Road to CTO, nos sentamos con Ilya Zayats, CTO de Factorial, para desgranar cómo la inteligencia artificial está redefiniendo el rol del ingeniero y del líder tecnológico.Ilya nos explica su filosofía de "comprimir el stack" para reducir la distancia entre el problema del cliente y la solución técnica. Hablamos sobre su trayectoria desde sus inicios en startups en 2010 hasta liderar a más de 200 ingenieros , por qué decidieron volver a Ruby on Rails tras probar Elixir, y cómo herramientas como Lovable y v0 están permitiendo que incluso perfiles no técnicos shipeen código a producción.Support the show
Myself and Chris chat about the movies, documentaries & TV shows that have kept us entertained over the last couple of months. This episodes 'Double Dip' movies are The Elixir & Until Dawn. Thanks for listening, and any recommendations to friends or social media shares are much appreciated.
Doctor and special correspondent Avir Mitra takes Executive Editor Soren Wheeler, plus a live studio audience, on a journey from the operating room to inside the body to the farm to the sewers and back again—searching for answers to an alarming threat to humanity's existence as we know it: antibiotic resistance in bacteria. This live show, performed in New York City and also in Little Rock, Arkansas, is part of a series we're doing with Avir that we are calling “Viscera.” Each event is a conversation that takes the audience on a journey into a quirk or question or mystery inside of us, and gives them a visceral experience of the viscera within us. The previous installment of the series was called “The Elixir of Life.” (https://radiolab.org/podcast/the-elixir-of-life)Special thanks to all of Little Rock Public Radio (especially Grace Zafasi and Jonathan Seaborn), Thomas Patterson, The Greene Space staff, CALS Ron Robinson Theater, Tom Philpott, Stephen Roach, Kate Shaw, Alex Wong, Maryn McKenna, and Kerri McClimen.If you are a patients or a doctor, and you are interested in phage therapy, please contact IPATH@ucsd.edu EPISODE CREDITS: Reported by - Avir Mitra Produced by - Jessica Yung Sound design contributed by - Jeremy Bloom and Jessica Yung Fact-checking by -Natalie Middleton EPISODE CITATIONS: Videos - Check out the video from the Viscera live show (and a bonus Q&A with Bruce Stewart-Brown and Steffanie Strathdee) on Radiolab's YouTube (https://zpr.io/3BK9MqJYVKQA). A deep dive (https://zpr.io/WNQNfgiNvKeZ) on bacteriophages with Avir Mitra and Steffanie Strathdee, also on Radiolab's Youtube.. Books - The Perfect Predator (https://theperfectpredator.com/) by Dr. Steffanie Strathdee's telling of her battle against a killer superbug. Plucked (https://zpr.io/PudGMEuzgU9X) by Maryn Mckenna a detailed accounting of chicken farming's practice of using antibiotics. Signup for our newsletter!! It includes short essays, recommendations, and details about other ways to interact with the show. Sign up (https://radiolab.org/newsletter)! Radiolab is supported by listeners like you. Support Radiolab by becoming a member of The Lab (https://members.radiolab.org/) today. Follow our show on Instagram, Twitter and Facebook @radiolab, and share your thoughts with us by emailing radiolab@wnyc.org.Leadership support for Radiolab's science programming is provided by the Simons Foundation and the John Templeton Foundation. Foundational support for Radiolab was provided by the Alfred P. Sloan Foundation.
Long-lived software systems rarely stay tidy. Over time they accumulate decisions, workarounds, and layers of history that can make even simple changes feel risky. For engineers responsible for maintaining those systems, the challenge often becomes less about writing new code and more about understanding what already exists. In this episode of Maintainable, Robby Russell speaks with Joel Oliveira, Engineering Manager at ezCater, about what helps software remain understandable and adaptable as it evolves. Joel starts with a principle that often gets overlooked: predictability. When patterns are consistent and code is organized in familiar ways, engineers can navigate a codebase with confidence. Frameworks like Ruby on Rails reinforce this by encouraging shared conventions, making it easier for developers to orient themselves when working in a new application. The conversation also explores how common metrics can be misleading. Test coverage is often treated as a proxy for quality, but Joel explains that it can create a false sense of confidence. Instead, he values testing most as a thinking tool. Practices like test-driven development can help engineers clarify interfaces and better understand the problem before committing to an implementation. Joel also shares a story from ezCater about replacing an aging image-cropping service that had become difficult to maintain and required frequent restarts due to a memory leak. Rather than patch the system again, the team introduced ImageProxy, an open source image processing tool created by Evil Martians. Because the image URLs flowed through a single object in their GraphQL layer, the team could introduce an adapter and gradually route traffic to the new service using feature flags. This allowed them to migrate safely and incrementally instead of relying on a risky “big bang” change. Robby and Joel also discuss how engineers' perspectives shift over time. Early in a career it is easy to look at legacy code and label it as bad. Joel now sees older systems as layers of decisions shaped by real constraints. Approaching them with empathy makes it easier to improve them thoughtfully. The episode closes with advice for engineers maintaining complex systems: frame problems as opportunities. By documenting impact and proposing incremental improvements, teams can steadily move their software toward a healthier future. Maintainable software rarely comes from one heroic refactor. More often, it's the result of many small improvements made by teams who understand their systems and care about how they evolve. Episode Highlights 00:02:18 – Predictability as a Maintainability Feature Joel explains why predictable patterns and conventions make large codebases easier to navigate. 00:07:41 – When Test Coverage Misleads Why high coverage can give a false sense of quality. 00:12:05 – Consulting vs. Product Engineering How switching environments shaped Joel's approach to code. 00:16:32 – Replacing a Legacy Image Service ezCater's migration away from a failing Node-based image service. 00:21:14 – Migrating with Adapters and Feature Flags How the team gradually moved traffic to ImageProxy. 00:26:03 – Developing Empathy for Legacy Code Why older systems deserve understanding, not blame. 00:30:47 – The Shift to Engineering Management Joel reflects on moving from IC work to leading teams. 00:34:52 – Advice for Improving Complex Systems Small, consistent improvements matter more than big rewrites. Thanks to Our Sponsor! Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and other frameworks. It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications. Keep your coding cool and error-free, one line at a time! Use the code maintainable to get a 10% discount for your first year. Check them out! Links / References Joel Oliveira — LinkedIn Joel Oliveira — Website Joel Oliveira — Mastodon (@jayroh) ezCater ImageProxy Subscribe to Maintainable on:Apple PodcastsSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.
This is the sixty-seventh and final episode in the Crypto Hipster's Curtain Calls Series, which includes 3–4-minute clips from Seasons 6-8. This compilation draws upon my conversations with:Haden Patrick, Director of Business Operations @ Cordial Systems (6/5/2024, Season 7)Karan Bharadwaj, CEO @ Arithmic (7/3/2024, Season 7)Tim Wang, COO @ Elixir (6/9/2024, Season 7)Michael O'Rourke, CEO and co-founder @ Pocket Network (9/2/2023, Season 6)
En este nuevo episodio de Road to CTO, nos sumergimos en una de las trayectorias más inusuales y honestas del ecosistema tecnológico actual junto a David Vrensk, CTO de Ealyx, antes co-founder y CTO en SeQura.Lejos de seguir una carrera lineal, David nos cuenta por qué decidió ejecutar un "downgrade" voluntario, dejando la dirección para volver a las trincheras como ingeniero de software, priorizando la inspiración del proyecto por encima de cualquier título jerárquico.En el plano técnico, analizamos el dilema de 2013 entre la madurez de Ruby y el potencial de Elixir, además de descubrir por qué los LLMs modernos tienen una "relación especial" con la estructura de Rails. David no se guarda nada y comparte su mayor cura de humildad: una migración de base de datos que terminó reenviando miles de SMS a usuarios de hace cuatro años, recordándonos que en sectores críticos como el FinTech, el respeto por el sistema y el "developer happiness" son más importantes que el ego del directivo.Support the show
Ever feel like your life is a series of trials you didn't sign up for? This week, we're stepping out of the rooms and into the "Ordinary World" of Joseph Campbell's Hero's Journey. We break down why your struggle with addiction isn't just a series of mistakes, it's the "Call to Adventure" you were initially too afraid to answer. We explore how the "Abyss" of active addiction mirrors the darkest part of the mythic cycle, and more importantly, how the 12 Steps provide the exact roadmap needed to return home with the "Elixir" of sobriety. Whether you're currently facing your "Road of Trials" or you're a "Mentor" helping others through their own, this episode explores how viewing your recovery through the lens of a classic epic can turn your greatest shame into your greatest strength.
Cardiologist and Medical Director, Dr. Kereiakes discusses Elixir Medical's Bioadaptor Device for heart patients. Elixir's Bioadaptor device will save millions of heart disease patients over the next few decades. Unlike stents, the novel scaffolding design of this med-tech device affords a heart patient's arteries a chance to recover to the tune of 90% back to its original form. By comparison, those who receive stents, need more stents to thwart future blockages caused by the primary stent application. In ten years, the survival rate for those with a stent is generally not optimistic.
Welcome to Lunacy; where we discern the sacred from the insane and admit that whether we like it or not, we are all profoundly affected by the cycles of the moon.Today on LUNACY, I interview my good friend Mica Balabuch. He's an Alchemist. Not metaphorically, actually. We delve into the history of Alchemy from Egypt, and possibly Atlantis, and the deep, dark, beautiful truth about this ancient art.Of particular interest are discussions about the Philosopher's Stone and the Elixir of Life. Both of which have a great deal of lore about them. Here we talk about the reality of these things as perfected matter. Is it real? So it seems. This is a profoundly interesting episode in terms of investigating an art that is perhaps the initial science, that is still being used and explored today. Perhaps it's time to bring it into the light. ***********************I'm Geoff Eido. Join me each week for interviews and insights intended to shine a light on the darkness, like the full moon in the forest.*****************Explore our other video content here on YouTube, where you'll find more insights into Keys To Self Mastery, along with relevant social media links.YouTube:  / @geoffeido3155 website: www.geoffeido.comSoundCloud:  / geoff-eido Spotify: https://open.spotify.c...Bandcamp: https://geoffeido.band...Instagram: @geoffeido Facebook:  / geoffeido info@geoffeido.comGeoff Eido. Join me each week for interviews and insights intended to shine a light on the darkness, like the full moon in the forest.Support the show
Elixir Aircraft's Cyril Champenois talks about the two-seat, low-wing aircraft using Carbon Oneshot technology derived from competition sailing that helps simplify structures to produce safer, more economical, and more versatile aircraft. Plus, stick around for the latest general aviation news discussion on see-and-avoid technology that may affect pilots, GAO recommendations for the drone industry, and more.
Manuel Carballal nos cuenta sus experiencias con plantas de poder y cómo sintió y vivió visiones, algo similar a lo que ha descubierto un equipo multidisciplinar recreando la receta del elixir mágico de Eulises en la antigua Grecia. Un elixir que usaban las sacerdotisas para contactar con los ancestros de las personas que las visitaban.
This episode covers: Cardiology This Week: A concise summary of recent studies Atrial septal defects in adults Conservative and invasive management of chronic coronary syndromes Milestones: 4S trial Host: Rick Grobbee Guests: JP Carpenter, Annemien van den Bosch, Rasha Al-Lamee, Roxana Mehran Want to watch the episode? Go to: https://esc365.escardio.org/event/2552 Want to watch the extended interview on Atrial septal defects in adults, go to: https://esc365.escardio.org/event/2552?resource=interview Disclaimer: ESC TV Today is supported by Novartis through an independent funding. The programme has not been influenced in any way by its funding partner. This programme is intended for health care professionals only and is to be used for educational purposes. The European Society of Cardiology (ESC) does not aim to promote medicinal products nor devices. Any views or opinions expressed are the presenters' own and do not reflect the views of the ESC. All declarations of interest are listed at the end of the episode. The ESC is not liable for any translated content of this video. The English language always prevails. Declarations of interests: Stephan Achenbach, Yasmina Bououdina, Rick Grobbee, Nicolle Kraenkel and Annemien van den Bosch have declared to have no potential conflicts of interest to report. Carlos Aguiar has declared to have potential conflicts of interest to report: personal fees for consultancy and/or speaker fees from Abbott, AbbVie, Alnylam, Amgen, AstraZeneca, Bayer, BiAL, Boehringer-Ingelheim, Daiichi-Sankyo, Ferrer, Gilead, GSK, Lilly, Novartis, Pfizer, Sanofi, Servier, Takeda, Tecnimede. Rasha Al-Lamee has declared to have potential conflicts of interest to report:speaker's fees for Menarini pharmaceuticals, Abbott, Philips, Medtronic, Servier, Shockwave, Elixir. Advisory board: Janssen Pharmaceuticals, Abbott, Philips, Shockwave, CathWorks, Elixir, Astrazeneca. Consulting Fees: Menarini pharmaceuticals, Abbott, Philips, Shockwave, Elixir, IsomAB, VahatiCor, SpectraWave, AstraZeneca, Cathworks, Janssen Pharmaceuticals. John-Paul Carpenter has declared to have potential conflicts of interest to report: stockholder MyCardium AI. Davide Capodanno has declared to have potential conflicts of interest to report: Abbott Vascular, Bristol Myers Squibb, Daiichi Sankyo, Edwards Lifesciences, Novo Nordisk, Sanofi Aventis, Terumo. Konstantinos Koskinas has declared to have potential conflicts of interest to report: honoraria from MSD, Daiichi Sankyo, Sanofi. Felix Mahfoud has declared to have potential conflicts of interest to report: research grants from Deutsche Forschungsgemeinschaft (SFB TRR219), Deutsche Gesellschaft für Kardiologie (DGK), Deutsche Herzstiftung, Ablative Solutions, ReCor Medical. Consulting fees, payment honoraria lectures, presentations, speaker, support travel costs: Ablative Solutions, Astra-Zeneca, Novartis, Inari, Recor Medical, Medtronic, Philips, Merck. Roxana Mehran has declared to have potential conflicts of interest to report: institutional research payments from Abbott, Alleviant Medical, Chiesi, Concept Medical, Cordis, CPC Clinical Research, Daiichi Sankyo, Duke, Faraday Pharmaceuticals, Idorsia Pharmaceuticals, Janssen, MedAlliance, Medtronic, NewAmsterdam Pharma, Novartis, Novo Nordisk Inc., Population Health Research Institute (PHRI), Protembis GmbH, Radcliffe, RM Global Bioaccess Fund Management, Sanofi US Services, Inc. ; personal fees from: None ; Equity
Bridget, Caitlin, and Hilda wrap up their coverage of "Between Two Kings," book 2 in Lindsay Straube's Split or Swallow series. Now, they've always said this story was outrageous and unexpected -- and nothing is more unexpected than that ending. And apparently, the third book is a prequel and NOT a follow up to book 2! So ... how did you all feel about that ending, because you know our fave book besties are going to give you their thoughts. Join our Patreon for exclusive behind-the-scenes content and let's be friends!Instagram > @Booktokmademe_podTikTok > @BooktokMadeMe
Get-Fit Guy's Quick and Dirty Tips to Slim Down and Shape Up
670. Is bone broth good for you? It is on a continuing upward popularity trend, so what's the deal? This episode originally aired in March 2024.Get-Fit Guy is hosted by Kevin Don. Find a full transcript here. Have a fitness question? Email Kevin at getfitguy@quickanddirtytips.com.Find Get-Fit Guy on Facebook and Twitter, or subscribe to the newsletter for more fitness tips.Get-Fit Guy is a part of Quick and Dirty Tips.Links:https://www.quickanddirtytips.comhttps://www.facebook.com/GetFitGuyhttps://twitter.com/GetFitGuy Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
Bridget, Caitlin, and Hilda are back with part 1 of "Between Two Kings" book 2 in Lindsay Straube's Split or Swallow series. And if you read book 1 (or listened to the episode) then you know how outrageous this series is, and this book does NOT disappoint. Like we're sure there's a plot we're supposed to care about, but the basilisks have entered mating season which means Tem is indulging her basilisk nature. Anyways, listen now for thoughts on part 1. Join our Patreon for exclusive behind-the-scenes content and let's be friends!Instagram > @Booktokmademe_podTikTok > @BooktokMadeMe
Strength training is more and more looking like the closest thing we have to an elixir of youth. But how do you get started building muscle when you're over 60? And if you're already bitten by the iron bug, are there any changes you should make or be aware of past that age? In this episode, we try to answer all of your questions on the topic (see the timestamps below) to leave no stone unturned. Timestamps: 05:00 - The benefits of strength training for people over 60. 09:15 - Intro to building muscle after 60: sarcopenia, lower hormone levels, and blunted signals for muscle growth. 15:00 - Common questions and objections: it's too late to start, it's dangerous, and joints hurt. 22:30 - The effects of menopause: is it game over? 28:40 - What actually changes in your body after 60? 30:20 - How do you keep your connective tissue strong and healthy so it doesn't become a bottleneck? 31:30 - Do you need longer recovery time after heavy workouts when you're over 60? Would it be better to split your training into shorter, more frequent workouts? 33:40 - How to strength train when over 60. 38:30 - Are higher rep-ranges safer? 41:00 - Should we reduce or increase training volume and/or frequency as we age? 42:00 - Choosing the right training program. 44:20 - Eating for muscle, strength, and health: metabolism, macronutrients, and supplements. 52:00 - Will nonsteroidal anti-inflammatory drugs (NSAIDs) impair muscle growth? 55:45 - Managing joint pain. 01:00:00 - Specific advice for women getting back into lifting after 60. 01:00:45 - For how long can people with impressive physiques maintain their muscle and strength as they age? 01:05:00 - What are the most impactful recovery methods? Most of these questions came in through our Subreddit. You should join the conversation over there, if you haven't already! *** Do you like what you hear so far? Please leave a five-star review in your podcast player. And hit that follow button! You can also follow us on Instagram. You'll find Daniel at @strengthdan, and Philip at @philipwildenstam. Become a part of our Reddit community here. *** This podcast is brought to you by Styrkelabbet AB, Sweden. To support us, download the world's best gym workout tracker app StrengthLog here. It's completely ad-free and the most generous fitness app on the market, giving you access to unlimited workout logging, lots of workouts and training programs, and much, much more even if you stay a free user for life. If you want a t-shirt with "Train hard, eat well, die anyway", check out our shop here.
The air in Wizzlethorp the Wizard's tower usually smells like magic, but today it smells like... burnt broccoli?
If you're in the mood for romance, comedy, and music that'll be stuck in your head for days, this one's for you.Toledo Opera is bringing the feel-good favorite The Elixir of Love to the Valentine Theatre on February 13 and 15, 2026, and it's packed with charm, heart, and plenty of laughs.This classic comedy by Gaetano Donizetti follows a lovable underdog who's convinced the only way to win true love is with the help of a not-so-mystical “love potion.” Spoiler alert: things don't go exactly as planned , and that's where the fun really starts.Conducted by J. Ernest Green, this production blends gorgeous music with playful storytelling, making it a perfect pick whether you're an opera regular or just opera-curious.Grab a date, grab a friend, or just grab a seat — this is one night at the theater guaranteed to leave you smiling. Tickets: https://tolo-internet.choicecrm.net/dist/#/events
DownloadWelcome to one of the most anticipated episodes of every year, our top 10 horror movies from 2025. 2025 turned out to be a decent year for horror and the crew tackles their own personal lists of top 10. The show starts with GregaMortis and Doctor Shock Dave Becker being joined with Anthony RRRRR from MRAC and Head Long Into Monsters Podcast as well as Justin Beahm from Reverend Entertainment. After they give their top 10 films GregaMortis is joined by the Twisted Temptress and Bill Van Veghel as they give their top 10 films from the year. Lastly you will hear from the listeners who called in with their lists. With almost 7 hours of recording time we hope you will enjoy the show. We would love to hear from you on who's list you feel lines up with your lists more. 1-804-569-5682.Be sure to grab your favorite snacks and beverages and grab those pens and papers or tablets so you can write down the films you need to see. HELP KEEP HORROR ALIVE!!TOP 10 LISTSANTHONY RRRR1. WEAPONS2. BRING HER BACK3. THE MONKEY4. SINNERS5. JIMMY & STIGGS6. RATS7. THE UGLY STEPSISTER8. V/H/S/ HALLOWEEN9. THE SHROUDS10. COMPANIONDAVE1. THE LONG WALK2. STRANGE HARVEST3. SINNERS4. BRING HER BACK5. DANGEROUS ANIMALS6. WEAPONS7. THE SURRENDER8. THE ELIXIR9. TOGETHER10. FRANKENSTEINJUSTIN BEAHM1. FRANKENSTEIN2. SILENT NIGHT DEADLY NIGHT3. BLACK PHONE 24. THE MONKEY5. THE UGLY STEPSISTER6. STRANGER THINGS SEASON 57. WELCOME TO DERRY8. THE LONG WALK9. MONSTER THE ED GEIN STORY10. WOLFMANGREG1. WEAPONS2. FINAL DESTINATION : BLOODLINES3. COMPANION4. JIMMY & STIGGS5. HEART EYES6. SILENT NIGHT DEADLY NIGHT7. CANNIBAL MUKBANG8. INFLUENCERS9. DEATH OF A UNICORN10. DANGEROUS ANIMALSPEARL1. WEAPONS2. GOOD BOY3. HOUSEMAID4. COMPANION / INFLUENCERS5. FINAL DESTINATION : BLOODLINES6. THE LONG WALK7. MARSHMALLOW8. VICIOUS9. JIMMY & STIGGS10. DANGEROUS ANINALS / BEASTS OF WARBILL1. DANGEROUS ANIMALS2. WOLFMAN3. YOUR HOST4. TOGETHER5. MARSHMALLOW6. THE ELIXIR7. TAKE OUT8. V/H/S HALLOWEEN9. CANNIBAL MUKBANG10. SCARED SHITLESSGUEST LINKSANTHONY RMRAC PODCASTHEAD LONG INTO MONSTERS PODCASTWEBSITEJUSTIN BEAHMWEBSITELOTC Links :Land Of The Creeps InstagramGregaMortisFacebookTwitterLand Of The Creeps Group PageLand Of The Creeps Fan PageJay Of The Dead's New Horror Movie PodcastYoutubeInstagramEmailLetterboxdDr. ShockDVD Infatuation TwitterDVD Infatuation WebsiteFacebookHorror Movie PodcastJay Of The Dead's New Horror Movies PodcastYouTube ChannelLetterboxdDVD Infatuation PodcastThe Illustrated Fan PodcastBill Van Veghel LinkFacebookLetterboxdMusic,Movies,Sports & Stuff PodcastFacebook Music Movies Sports & StuffTwisted Temptress LinkLetterboxdLOTC Hotline Number1-804-569-56821-804-569-LOTCLOTC Intro is provided by Andy Ussery, Below are links to his social mediaEmail:FacebookTwitterOutro music provided by Greg Whitaker Below is Greg's Twitter accountTwitterFacebook
Maintaining software over time rarely fails because of one bad decision. It fails because teams stop getting clear signals… and start guessing.In this episode, Robby talks with Lucas Roesler, Managing Partner and CTO at Contiamo. Lucas joins from Berlin to unpack what maintainability looks like in practice when you are dealing with real constraints… limited context, missing documentation, and systems that resist understanding.A big through-line is feedback. Lucas argues that long-lived systems become easier to change when they provide fast, trustworthy signals about what they are doing. That can look like tests that validate assumptions, tooling that makes runtime behavior visible, and a habit of designing for observability instead of treating it as a bolt-on.The conversation also gets concrete. Lucas shares a modernization effort built on a decade-old tangle of database logic… views, triggers, stored procedures, and materializations… created by a single engineer who was no longer around. With little documentation to lean on, the team had to build their own approach to “reading” the system and mapping dependencies before they could safely change anything.If you maintain software that has outlived its original authors, this is a grounded look at what helps teams move from uncertainty to confidence… without heroics, and without rewriting for sport.Episode Highlights[00:00:46] What well-maintained software has in common: Robby asks Lucas what traits show up in systems that hold together over time.[00:03:25] Readability at runtime: Lucas connects maintainability to observability and understanding what a system actually did.[00:16:08] Writing the system down as code: Infrastructure, CI/CD, and processes as code to reduce guesswork and improve reproducibility.[00:17:42] How client engagements work in practice: How Lucas' team collaborates with internal engineering teams and hands work off.[00:25:21] The “rat's nest” modernization story: Untangling a legacy data system with years of database logic and missing context.[00:29:40] Making data work testable: Why testability matters even when the “code” is SQL and pipelines.[00:34:59] Pivot back to feedback loops: Robby steers into why logs, metrics, and tracing shape better decision-making.[00:35:20] Why teams avoid metrics and tracing: The organizational friction of adding “one more component.”[00:42:59] Local observability with Grafana: Using visual feedback to spot waterfalls, sequential work, and hidden coupling.[00:50:00] Non-technical book recommendations: What Lucas reads and recommends outside of software.Links & ReferencesGuest and CompanyLucas Roesler: https://lucasroesler.com/Contiamo: https://contiamo.com/SocialMastodon: https://floss.social/@theaxerBluesky: https://bsky.app/profile/theaxer.bsky.socialBooks MentionedThe Wheel of Time (Robert Jordan): https://en.wikipedia.org/wiki/The_Wheel_of_TimeAccelerando (Charles Stross): https://en.wikipedia.org/wiki/AccelerandoCharles Stross: https://en.wikipedia.org/wiki/Charles_StrossThanks to Our Sponsor!Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and other frameworks.It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications.Keep your coding cool and error-free, one line at a time! Use the code maintainable to get a 10% discount for your first year. Check them out! Subscribe to Maintainable on:Apple PodcastsSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.
Alan interviews Curtis Breville. Curtis' aha invention idea came when his daughter's friend suffered after eating spicy hot sauce. Curtis gave him crushed hops from a brewing jar and the pain was gone. Curtis invented a cooling mouth spray that prevents pain from spicy foods. Today he sells his Dr. B's Elixir everywhere. Make sure to subscribe to the podcast at Apple Podcasts, or wherever you get your podcasts, so you won't miss a single episode. Website: www.DrBsElixir.com
Top 3…uh…6!: One Battle After Another, This Is Spinal Tap II: The End Continues, Left-Handed Girl, Adolescence s1, The Elixir, Once Upon A Dance Time: Peach Boy Jimmy is back with some more great recommendations for you to check out! Check them out if you haven't. And if you have, let us know what you thought.
There's a specific kind of frustration that shows up for high-capacity leaders. You know what you want. You've thought it through. You've made the decision consciously. And yet… you still hesitate. You still circle the same choice. You still feel slower than you “should” be. In this episode, I name what's actually happening and it's not procrastination, fear, or self-sabotage. It's something I call identity lag. Identity lag happens when your life starts moving faster than your nervous system can comfortably integrate. Your mind may be clear, but your body is still catching up to who you're becoming. In this conversation, I share: Why feeling “stuck” is often a sign of integration, not failure How high-capacity leaders experience identity lag more intensely The difference between intuition and nervous system stress Why clarity isn't always the missing piece — and what actually is How shifting from self-monitoring to leadership and contribution can unlock movement again I also share personal stories from my own life — moments when everything was aligned on paper, yet my nervous system reacted with hesitation and fatigue right before stepping into something meaningful. If you've ever told yourself: “I should be past this by now” “Why does this feel harder than it should?” “What's wrong with me?” This episode is here to gently take the pressure off. Nothing is wrong with you. You're not behind. Your system may simply be integrating a new level of responsibility, visibility, or truth. And that deserves support — not force. Resources Mentioned:
Rewrites are seductive. Clean slates promise clarity, speed, and “doing it right this time.” In practice, they're often late, over budget, and quietly demoralizing.In this episode of Maintainable, Robby sits down with Brittany Ellich, a Senior Software Engineer at GitHub, to talk about a different path. One rooted in stewardship, readability, and resisting the urge to start over.Brittany's career began with a long string of rebuild projects. Over time, she noticed a pattern. The estimates were wrong. Feature development stalled. Teams burned energy reaching parity with systems they'd already had. That experience pushed her toward a strong belief: if software is in production and serving users, it's usually worth maintaining.[00:00:57] What well-maintained software actually looks likeFor Brittany, readability is the first signal. If code can't be understood, it can't be changed safely. Maintenance begins with making systems approachable for the next person.[00:01:42] Rethinking technical debtShe explains how her understanding of technical debt has evolved. Rather than a fixed category of work, it's often anything that doesn't map directly to new features. Bugs, reliability issues, and long-term risks frequently get lumped together, making prioritization harder than it needs to be.[00:05:49] Why AI changes the maintenance equationBrittany describes how coding agents have made it easier to tackle small, previously ignored maintenance tasks. Instead of waiting for debt to accumulate into massive projects, teams can chip away incrementally. (Related: GitHub Copilot and the Copilot coding agent workflow she's explored.)[00:07:16] Context from GitHub's billing systemsWorking on metered billing at GitHub means correctness and reliability matter more than flash. Billing should be boring. When it's not, customers notice quickly.[00:11:43] Navigating a multi-era codebaseGitHub's original Rails codebase is still in active use. Brittany relies heavily on Git blame and old pull requests to understand why decisions were made, treating them as a form of living documentation.[00:25:27] Treating coding agents like teammatesRather than delegating massive changes, Brittany assigns agents small, well-scoped tasks. She approaches them the same way she would a new engineer: clear instructions, limited scope, and careful review.[00:36:00] Structuring the day to avoid cognitive overloadShe breaks agent interaction into focused windows, checking in a few times a day instead of constantly monitoring progress. This keeps deep work intact while still moving maintenance forward.[00:40:24] Low-risk ways to experimentImproving test coverage and generating repository instructions are safe entry points. These changes add value without risking production behavior.[00:54:10] Navigating team resistance and ethicsBrittany acknowledges skepticism around AI and encourages teams to start with existing backlog problems rather than selling AI as a feature factory.[00:57:57] Books, habits, and staying balancedOutside of software, Brittany recommends Atomic Habits by James Clear, sharing how small routines help her stay focused.The takeaway is clear. AI doesn't replace engineering judgment. Used thoughtfully, it can support the unglamorous work that keeps software alive.Good software doesn't need a rewrite.It needs caretakers.References MentionedGitHub – Brittany's current role and the primary environment discussedGitHub Universe – Where Brittany presented her coding agent workflowAtomic Habits by James Clear – Brittany's recommended book outside of techOvercommitted - Podcast Brittany co-hostsThe Balanced Engineer Newsletter – Brittany's monthly newsletter on engineering, leadership, and balanceBrittany Ellich's website – Central hub for her writing and linksGitHub Copilot – The AI tooling discussed throughout the episodeHow the GitHub billing team uses the coding agent in GitHub Copilot to continuously burn down technical debt – GitHub blog post referencedThanks to Our Sponsor!Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and other frameworks.It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications.Keep your coding cool and error-free, one line at a time! Use the code maintainable to get a 10% discount for your first year. Check them out! Subscribe to Maintainable on:Apple PodcastsSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.
Sometimes the exact thing you want - more leadership, more impact, a bigger decision, a new season - can make you feel anxious, exhausted, frozen, or unusually triggered. That doesn't mean you're failing. It often means you're in identity lag and your nervous system is activated. In this episode, I break down why growth can feel heavy even when you're ready, how to tell the difference between intuition and stress responses, and what to do so you can keep moving without self-betrayal. In this episode, you'll learn: Why “I feel scared, so it's not aligned” is often a misread What identity lag is (and why it can make you tired) The difference between fear, avoidance, and a stress response Why strategy works when identity is stable (and backfires when it's not) The 3 supports that create real identity integration: regulation mirroring spacious, embodied decisions If growth is making you tired, edgy, emotional, or frozen—nothing is wrong with you. Your body is prioritizing safety during change. And with the right support, you can stabilize into who you're becoming. Work with me (in the right size of support) Intuitive Leader Retreat (March 3–5, 2026 | Lincoln City, Oregon) A small, embodied container for nervous system regulation, identity integration, and real-time mirroring. ➡️ https://www.brendawinkle.com/retreat2026 The Elixir ($77 on-demand) 14 short, powerful tools (3–6 minutes each) for real-time emotional + nervous system regulation. ➡️ https://www.brendawinkle.com/elixir Ongoing community: The Spiritual CEO membership Weekly support to lead your life + business with steadiness, ethics, and connection. ➡️ https://www.skool.com/thespiritualceo/about Free: Download the Energy Audit ➡️ https://www.brendawinkle.com/audit Keywords: nervous system regulation, identity shift, identity lag, somatic coaching, emotional regulation, freeze response, overthinking, people pleasing, intuitive leadership, spiritual entrepreneur, embodied decision making
Identity isn't something you “figure out.” It's something you shift into. In this episode, Brenda breaks down four practical ways identity actually changes - not through mindset hacks or pressure, but through embodiment, nervous system safety, and self-trust. If you've done the training, earned the credentials, and still feel like you're negotiating with yourself to move forward… this episode will land. You'll learn why identity shifts can feel so destabilizing, how child parts and protector parts quietly shape your decisions, and what actually helps you step into the version of yourself you already know is emerging. In this episode, we explore: Why identity change can feel threatening to the nervous system The concept of secondary gain (what you may be unconsciously protecting) How clothing, roles, and self-permission reinforce identity Child parts vs. protector parts -and how they impact confidence and visibility Why you don't need one income stream to be “legitimate” How turning the spotlight outward makes identity shifts easier What internal safety has to do with decision-making Why over-consuming information can stall momentum Ways to go deeper: The Elixir – 14 on-demand somatic tools for emotional regulation https://www.brendawinkle.com/elixir Intuitive Leader Retreat (March 3–5, 2026 | Oregon Coast) https://www.brendawinkle.com/retreat2026 Spiritual CEO Membership https://www.skool.com/thespiritualceo/about Free Clarity Guide – discern next steps and mentorship alignment Free Energy Audit: brendawinkle.com/audit Keywords: Brenda Winkle, Your Yes Filled Life, podcast, leadership guide, psychic medium, somatic coach, identity transformation, shifting identity, personal growth, coaching, entrepreneurial identity, secondary gain, self-inquiry, physical appearance, clothing, identity fluidity, multiple roles, income streams, Internal Family Systems, child parts, protector parts, emotional healing, nervous system regulation, somatic coaching, Intuitive Leader Retreat, spiritual entrepreneurs, self-acceptance, internal dialogue, self-compassion, identity integration, authentic self, emotional regulation, Spiritual CEO membership, personal narrative, psychological insights, mindset shift, overcoming barriers, coaching industry perceptions, self-worth, community recognition, professional identity, self-discovery, personal narrative, listener engagement, podcast growth, self-empowerment, compassionate engagement.
Thinking harder won't get you unstuck. In this episode of Your Yes Filled Life, Brenda Winkle—energetic leadership guide, psychic medium, and somatic coach—explores the truth most people miss: your identity is what drives your decisions, capacity, and outcomes. This episode meets you in the moments when things feel heavy, unclear, or overwhelming and brings you back into your body so you can access the version of you who already knows what's true. Through real-time somatic practices, identity reflection, and grounded leadership insight, you'll learn how nervous system safety - not more information - is the foundation for aligned action. We also name what's happening in the world right now. Because “protect your energy” can become spiritual bypassing when it's used to avoid integrity, values, and responsibility. You don't have to be loud. You do get to be honest about who you are. In this episode, you'll learn: Why identity - not strategy - drives results How fight, flight, freeze, and fawn impact decision-making Simple somatic practices to regulate your nervous system fast Why embodiment can feel unfamiliar (and how to return safely) How outdated identities quietly keep you stuck What integrity-based leadership looks like in uncertain times Experiential practices included: Nervous system down-regulation through breath and bilateral stimulation Body-based awareness practices you can return to anytime Resources mentioned: The Elixir - 14 short, on-demand somatic resets (3–6 minutes each) to interrupt overwhelm and support clean decisions https://www.brendawinkle.com/elixir The Intuitive Leader Retreat - A 3-day oceanfront retreat for intuitive leaders
Happy new year! It's 2026 and time for another exciting edition of your favorite Zombie Movie Podcast, the one and only Dead Man Still Walking, featuring your favorite zombie expert (and ours), Dr. Walking Dead (Kyle William Bishop)! In this 58th edition of DMSW, the good doctor brings you a double feature of brand-new international zombie flicks! Here in Episode 175 of Jay of the Dead's New Horror Movies, Dr. Kyle William Bishop reviews The Elixir (2025) and The Silence After (2025). "The Elixir" is an Indonesian zombie horror film, co-written and directed by Kimo Stamboel, about a family whose plan to profit from a healing tonic spirals into catastrophe, triggering a horrific wave of undead in their rural community. And "The Silence After," directed by Stockton Miller, depicts a Caribbean island which unravels into chaos when a disputed drug trial ignites social unrest and a strange contagion which transforms ordinary residents into feral, undead beings. This is a great episode! Join Dr. Bishop!
Navigate the energy of January 2026 with a deep dive into the 3 core energetic themes: Centering, Receiving Outside Help, and the Elixir of Self-Challenge. Move beyond the 'hustle' illusion and learn how to align with your internal rhythm, activate your heart chakra, and collaborate with divine guidance for a powerful start to the new year. Discover why 2026 is the year of reclaiming your personal authority and living from the inside out. Sign-Up for Amanda’s January Workshop! This Frequency Field Inner Circle Experience includes: January Astro–Numerology PDF Guide + Worksheet (downloadable) A comprehensive roadmap for the month: numerology themes, key transits, New + Full Moon focus points, and prompts to help you track your signal and make aligned choices. Companion Voice Memo (audio) A guided walkthrough of January—astrologically, numerologically, and energetically—so you can listen and re-listen whenever you need clarity, orientation, or recalibration. Live Workshop on Zoom + Replay Access through March 31, 2026 Attend live if you’d like, or use the replay—either way, this is a practical and energetic container to help you step into 2026 with a clean signal and real momentum. Host: Amanda Rieger Green YouTube: @soul_pathology Instagram: @soulpathology Website: SoulPathology.com Email: Podcast@soulsessions.meFollow Amanda on Instagram: https://www.instagram.com/soulpathology/See omnystudio.com/listener for privacy information.
In this episode, Stewart Alsop sits down with Joe Wilkinson of Artisan Growth Strategies to talk through how vibe coding is changing who gets to build software, why functional programming and immutability may be better suited for AI-written code, and how tools like LLMs are reshaping learning, work, and curiosity itself. The conversation ranges from Joe's experience living in China and his perspective on Chinese AI labs like DeepSeek, Kimi, Minimax, and GLM, to mesh networks, Raspberry Pi–powered infrastructure, decentralization, and what sovereignty might mean in a world where intelligence is increasingly distributed. They also explore hallucinations, AlphaGo's Move 37, and why creative “wrongness” may be essential for real breakthroughs, along with the tension between centralized power and open access to advanced technology. You can find more about Joe's work at https://artisangrowthstrategies.com and follow him on X at https://x.com/artisangrowth.Check out this GPT we trained on the conversationTimestamps00:00 – Vibe coding as a new learning unlock, China experience, information overload, and AI-powered ingestion systems05:00 – Learning to code late, Exercism, syntax friction, AI as a real-time coding partner10:00 – Functional programming, Elixir, immutability, and why AI struggles with mutable state15:00 – Coding metaphors, “spooky action at a distance,” and making software AI-readable20:00 – Raspberry Pi, personal servers, mesh networks, and peer-to-peer infrastructure25:00 – Curiosity as activation energy, tech literacy gaps, and AI-enabled problem solving30:00 – Knowledge work superpowers, decentralization, and small groups reshaping systems35:00 – Open source vs open weights, Chinese AI labs, data ingestion, and competitive dynamics40:00 – Power, safety, and why broad access to AI beats centralized control45:00 – Hallucinations, AlphaGo's Move 37, creativity, and logical consistency in AI50:00 – Provenance, epistemology, ontologies, and risks of closed-loop science55:00 – Centralization vs decentralization, sovereign countries, and post-global-order shifts01:00:00 – U.S.–China dynamics, war skepticism, pragmatism, and cautious optimism about the futureKey InsightsVibe coding fundamentally lowers the barrier to entry for technical creation by shifting the focus from syntax mastery to intent, structure, and iteration. Instead of learning code the traditional way and hitting constant friction, AI lets people learn by doing, correcting mistakes in real time, and gradually building mental models of how systems work, which changes who gets to participate in software creation.Functional programming and immutability may be better aligned with AI-written code than object-oriented paradigms because they reduce hidden state and unintended side effects. By making data flows explicit and preventing “spooky action at a distance,” immutable systems are easier for both humans and AI to reason about, debug, and extend, especially as code becomes increasingly machine-authored.AI is compressing the entire learning stack, from software to physical reality, enabling people to move fluidly between abstract knowledge and hands-on problem solving. Whether fixing hardware, setting up servers, or understanding networks, the combination of curiosity and AI assistance turns complex systems into navigable terrain rather than expert-only domains.Decentralized infrastructure like mesh networks and personal servers becomes viable when cognitive overhead drops. What once required extreme dedication or specialist knowledge can now be done by small groups, meaning that relatively few motivated individuals can meaningfully change communication, resilience, and local autonomy without waiting for institutions to act.Chinese AI labs are likely underestimated because they operate with different constraints, incentives, and cultural inputs. Their openness to alternative training methods, massive data ingestion, and open-weight strategies creates competitive pressure that limits monopolistic control by Western labs and gives users real leverage through choice.Hallucinations and “mistakes” are not purely failures but potential sources of creative breakthroughs, similar to AlphaGo's Move 37. If AI systems are overly constrained to consensus truth or authority-approved outputs, they risk losing the capacity for novel insight, suggesting that future progress depends on balancing correctness with exploratory freedom.The next phase of decentralization may begin with sovereign countries before sovereign individuals, as AI enables smaller nations to reason from first principles in areas like medicine, regulation, and science. Rather than a collapse into chaos, this points toward a more pluralistic world where power, knowledge, and decision-making are distributed across many competing systems instead of centralized authorities.
Welcome back Heal Squad, to Part 2 of our powerful conversation with Siggi Clavien, Founder & CEO of The Liver Clinic. Today Maria and Siggi chat how your liver truly works inside the ecosystem of your body, and why it might be the hidden source behind so many chronic conditions. Siggi also dives into surprising emotional clues too, like why people who get angry or stressed easily may be more prone to liver disease, and he explains why so many people are misdiagnosed. FYI, fatty liver disease rarely shows up on standard blood tests, which means millions are walking around with symptoms but no answers. But the hope? Siggi shares which scans actually detect liver issues early (and which ones don't), a key wellness practice that boosts liver repair, and a nutritional hack to support regeneration. If you're ready to understand your body's quietest signals, take empowered action, and support the organ that keeps everything else running, this is for you! HEALERS & HEAL-LINERS: Your liver is the body's ULTIMATE organizer: If the brain is the computer, the liver is the coordinator, distributing vitamins, minerals, hormones, and nutrients. Best Liver Support: Sweating (sauna, exercise, dry brushing), eating clean fats, and reducing chemical exposures are essential to support liver healing. Early detection is everything: Fatty liver disease can drive chronic illness by progressing to more severe liver damage like cirrhosis and liver cancer. It is also linked to other chronic conditions such as diabetes, obesity, high blood pressure, and heart disease. A fatty liver does not appear on standard blood tests. FibroScan is the gold standard for picking up fat and fibrosis before things get serious. HEAL SQUAD SOCIALS IG: https://www.instagram.com/healsquad/ TikTok: https://www.tiktok.com/@healsquadxmaria HEAL SQUAD RESOURCES: Heal Squad Website:https://www.healsquad.com/ Heal Squad x Patreon: https://www.patreon.com/HealSquad/membership Maria Menounos Website: https://www.mariamenounos.com My Curated Macy's Page: Shop My Macy's Storefront EMR-Tek Red Light: https://emr-tek.com/discount/Maria30 for 30% off Airbnb: https://www.airbnb.com/maria Thrive Causemetics: https://thrivecausemetics.com/healsquad Get 20% OFF with this link! Briotech: https://shopbriotech.com/ Use Code: HEALSQUAD for 20% off GUEST RESOURCES: Instagram: https://www.instagram.com/siggiclavien The Liver Clinic: https://theliverclinic.com/ De-Liver-ance Elixir: https://us.loveyourliver.com/ ABOUT MARIA MENOUNOS: Emmy Award-winning journalist, TV personality, actress, 2x NYT best-selling author, former pro-wrestler and brain tumor survivor, Maria Menounos' passion is to see others heal and to get better in all areas of life. ABOUT HEAL SQUAD x MARIA MENOUNOS: A daily digital talk-show that brings you the world's leading healers, experts, and celebrities to share groundbreaking secrets and tips to getting better in all areas of life. DISCLAIMER: This Podcast and all related content (published or distributed by or on behalf of Maria Menounos or http://Mariamenounos.com and http://healsquad.com) is for informational purposes only and may include information that is general in nature and that is not specific to you. Any information or opinions provided by guest experts or hosts featured within website or on Company's Podcast are their own; not those of Maria Menounos or the Company. Accordingly, Maria Menounos and the Company cannot be responsible for any results or consequences or actions you may take based on such information or opinions. This podcast is presented for exploratory purposes only. Published content is not intended to be used for preventing, diagnosing, or treating a specific illness. If you have, or suspect you may have, a health-care emergency, please contact a qualified health care professional for treatment.
Hey, Heal Squad! Today we're diving into the organ almost nobody thinks about… yet it quietly controls your energy, your metabolism, your sleep, your skin...everything. And it might just be the key to your deepest healing. We're joined by Siggi Clavien, Founder & CEO of The Liver Clinic, who has dedicated his life to stopping the alarming rise in liver disease. Ready for this? Over 40% of the population now has fatty liver disease and more than 70% of those cases have nothing to do with alcohol. Yep! The real culprits are hiding in your everyday life, and Siggi drops two shockers you absolutely won't see coming. But here's the hope: Your liver regenerates itself every three years. Meaning you have the power to rebuild it stronger than ever, and today, Siggi shows us what we can do to begin learning more about our livers and the very first signs your liver is struggling (think: brain fog, poor sleep, stubborn weight you can't lose) and how those subtle clues might actually be your body's earliest SOS. Can't wait for everyone to take action and give their livers the love they deserve. HEALERS & HEAL-LINERS: Alarming Rise in Liver Disease: Liver disease is up 400% and over 70% of cases are non-alcohol–related, despite assumptions that drinking is the main cause. Causes are now connected to chemical overload, like micro plastics, pesticides, medications & artificial sweeteners. Early Signs & Silent Progression: First signs are subtle: brain fog, sleep disruptions, weight gain, and mitochondrial dysregulation (especially for women). Sleep, Repair & Liver Overload: The liver performs major repair work during sleep. Alcohol dramatically worsens sleep because it forces the liver into overtime. HEAL SQUAD SOCIALS IG: https://www.instagram.com/healsquad/ TikTok: https://www.tiktok.com/@healsquadxmaria HEAL SQUAD RESOURCES: Heal Squad Website:https://www.healsquad.com/ Heal Squad x Patreon: https://www.patreon.com/HealSquad/membership Maria Menounos Website: https://www.mariamenounos.com My Curated Macy's Page: Shop My Macy's Storefront EMR-Tek Red Light: https://emr-tek.com/discount/Maria30 for 30% off Airbnb: https://www.airbnb.com/maria Thrive Causemetics: https://thrivecausemetics.com/healsquad Get 20% OFF with this link! Briotech: https://shopbriotech.com/ Use Code: HEALSQUAD for 20% off GUEST RESOURCES: Instagram: https://www.instagram.com/siggiclavien The Liver Clinic: https://theliverclinic.com/ De-Liver-ance Elixir: https://us.loveyourliver.com/ ABOUT MARIA MENOUNOS: Emmy Award-winning journalist, TV personality, actress, 2x NYT best-selling author, former pro-wrestler and brain tumor survivor, Maria Menounos' passion is to see others heal and to get better in all areas of life. ABOUT HEAL SQUAD x MARIA MENOUNOS: A daily digital talk-show that brings you the world's leading healers, experts, and celebrities to share groundbreaking secrets and tips to getting better in all areas of life. DISCLAIMER: This Podcast and all related content (published or distributed by or on behalf of Maria Menounos or http://Mariamenounos.com and http://healsquad.com) is for informational purposes only and may include information that is general in nature and that is not specific to you. Any information or opinions provided by guest experts or hosts featured within website or on Company's Podcast are their own; not those of Maria Menounos or the Company. Accordingly, Maria Menounos and the Company cannot be responsible for any results or consequences or actions you may take based on such information or opinions. This podcast is presented for exploratory purposes only. Published content is not intended to be used for preventing, diagnosing, or treating a specific illness. If you have, or suspect you may have, a health-care emergency, please contact a qualified health care professional for treatment.
Geoff, Gavin and Andrew talk about most useless fact, xXx, Vin Diesel, last words, paintball, Bingo, good bad dog movies, The Dog Who Saved Christmas, Jones Crayola, The Little Things, Poppi, biotics, fruit eating, apple emoji, annoying your parents, multiverse, The Elixir, better movies, copper, fajitas, weird tech, the state of your pikachu, Pokemon, trading, Geoff cards, collectibles, a claw machine, Disco Fever, and Vancouver Goldeneyes. Sponsored by Factor. Thanks Factor! Go to FACTORMEALS.com/REGULATION50OFF and use code REGULATION50OFF to get 50% off your first box plus Free Breakfast for 1 Year. Offer only valid for new Factor customers with code and qualifying auto-renewing subscription purchase. Support us directly at https://www.patreon.com/TheRegulationPod Stay up to date, get exclusive supplemental content, and connect with other Regulation Listeners. Learn more about your ad choices. Visit megaphone.fm/adchoices
© 2020-2026 Ivy Podcast Discovery LLC
