Podcasts about Scaffolding

Founder of Upshift, Shawn Yeager, joined me on Ditching Hourly to talk about how AI is killing the billable hour and what professional services firms can do about it. Jonathan and Shawn dig into judgment versus execution, what firms should commercialize after AI, why cost-cutting is only the first move, and how agent workflows change what small and midsize firms can do.00:00 - Introduction01:54 - AI and the billable hour03:56 - The judgment sandwich05:19 - Strategy, execution, and hidden value09:06 - Client conversations about AI pressure13:26 - Validating AI output15:29 - Judgment, marketing, and cost of being wrong17:07 - AI transformation and commercialization20:08 - The hard parts big firms still need humans for22:20 - Cost recovery versus new offerings25:35 - Agents as extra employees26:40 - Interns versus chiefs of staff28:44 - Scaffolding agent workflows30:12 - From chatbots to delegated workflows37:00 - AI adoption inside firms42:01 - Closing remarksShawn Yeager runs Upshift, a firm focused on helping professional services firms understand what they sell after AI. His career has focused on emerging technology and getting it to market, including work on Microsoft's first browser team, the SaaS/cloud wave, mobile, Bitcoin, and AI. His background is in computer science, and his work has included sales, marketing, partnerships, consulting, Accenture, early-stage startups, and his own ventures. Learn more at upshiftco.com. (00:00) - Introduction (01:54) - AI and the billable hour (03:56) - The judgment sandwich (05:19) - Strategy, execution, and hidden value (09:06) - Client conversations about AI pressure (13:26) - Validating AI output (15:29) - Judgment, marketing, and cost of being wrong (17:07) - AI transformation and commercialization (20:08) - The hard parts big firms still need humans for (22:20) - Cost recovery versus new offerings (25:35) - Agents as extra employees (26:40) - Interns versus chiefs of staff (28:44) - Scaffolding agent workflows (30:12) - From chatbots to delegated workflows (37:00) - AI adoption inside firms (42:01) - Closing remarks ----Do you have questions about how to improve your business? Things like:Value pricing your work instead of billing for your time?Positioning yourself as the go-to person in your space?Productizing your services so you never have to have another awkward sales call or spend hours writing another custom proposal?Book a one-on-one coaching call with me and get answers to these questions and others in the time it takes to get ready for work in the morning.Best of all, you're covered by my 100% satisfaction guarantee. If at the end of the call, you don't feel like it was worth it, just say the word, and I'll refund your purchase in full.To book your one-on-one coaching call, go to: https://jonathanstark.com/callI hope to see you there!

Hey Team! When I moved into my neighborhood, most of the houses weren't built.  So I got to see over the course of a few years, a lot of the work that went into putting those houses up, all the day-to-day progress that always kept happening, and how every step seemed to set them up for the next step. Now, nobody expects a brick wall to just materialize out of midair on pure willpower or a house to get completely built with no effort. yet when it comes to managing our daily routines, that's exactly what we try to do. We expect our internal motivation to keep us on track despite our own track record, and then we get frustrated when they fall flat. In this episode, we're taking a look at why our attempts to build traditional habits often doesn't work with ADHD, and why it isn't a moral failure or a lack of trying. We're going to explore the critical mechanics of external scaffolding versus internal habits, digging into how we can stop burning through our limited supply of daily executive function and start building physical infrastructure that does the heavy lifting for us If you'd life to follow along on the show notes page you can find that at HackingYourADHD.com/298 YouTube: https://tinyurl.com/y835cnrk Patreon: https://www.patreon.com/HackingYourADHD This Episode's Top Tips Traditional habits rely on an internal dopamine reward to lock them onto autopilot. Because ADHD reward chemistry is wildly inconsistent, that "autopilot" switch rarely flips. Instead, we want to work on designing our environment through systems to help make our intentions inevitable. Passive reminders are entirely too easy for an ADHD brain to ignore. Instead, use design psychology to create physical roadblocks that force conscious awareness. Putting your clean laundry basket directly on the couch cushion where you want to sit forces your brain to actively negotiate with the task before you can proceed. Human brains naturally drift toward the path of least resistance. Take advantage of this by manipulating that friction. Lower the friction for positive intentions by creating one-step solutions, like a dedicated key basket by the front door, or crank up the friction for distractions by doing things putting your phone completely out of reach so you can't just pick it up without thinking about it. Your physical environment is never neutral; it is actively directing your behavior right now, whether you designed it or not, which means relying on willpower is a losing game. Treat environmental design as a handoff between two versions of you: let your "Good Brain Day" self build a physical world that protects and supports your "Bad Brain Day" self.  

Welcome back to the Law School Toolbox podcast! Today, we explain the neuroscience behind our RAMP bar study tool -- which we introduced in a recent episode. We discuss the limitation of working memory, which makes it essential to move legal rules into long-term memory through spaced repetition and scaffolding.  In this episode we discuss: The research and science behind our RAMP bar study tool Scaffolding and why we use three learning tiers Studying through spaced repetition RAMP study mode features and confidence calibration How much information can our working memory hold? Resources: https://barexamtoolbox.com/ramp (https://barexamtoolbox.com/ramp) Podcast Episode 369: Using Spaced Repetition for Your Law School and Bar Exam Studies (w/Gabriel Teninbaum) (https://lawschooltoolbox.com/podcast-episode-369-using-spaced-repetition-for-your-law-school-and-bar-exam-studies-w-gabriel-teninbaum/) Podcast Episode 554: How We're Thinking About NextGen Prep Differently (Plus, Try Our New Tool for Free) (https://lawschooltoolbox.com/podcast-episode-554-how-were-thinking-about-nextgen-prep-differently-plus-try-our-new-tool-for-free/) Download the Transcript  (https://lawschooltoolbox.com/episode-557-this-is-how-your-brain-actually-learns-the-brain-science-behind-our-ramp-tool/) If you enjoy the podcast, we'd love a nice review and/or rating on Apple Podcasts (https://itunes.apple.com/us/podcast/law-school-toolbox-podcast/id1027603976) or your favorite listening app. And feel free to reach out to us directly. You can always reach us via the contact form on the Law School Toolbox website (http://lawschooltoolbox.com/contact). If you're concerned about the bar exam, check out our sister site, the Bar Exam Toolbox (http://barexamtoolbox.com/). You can also sign up for our weekly podcast newsletter (https://lawschooltoolbox.com/get-law-school-podcast-updates/) to make sure you never miss an episode! Thanks for listening! Alison & Lee

Raymundo talked about the celebrities he ran into at Kane Brown's bar opening last night. Trace tells us about the worst injury of his life he suffered after falling 12 feet from scaffolding. He doesn't spare us all the gruesome details. He also reflects on his 30th anniversary of his debut album and his biggest hits that surprisingly weren't no. 1 songs. He also gives Bobby his best advice on being a girl dad because he has 5 daughters. Lunchbox says listeners need to stop sending him body parts in the mail.See omnystudio.com/listener for privacy information.

Oriol Vinyals, VP of Research at Google DeepMind and co-lead of the Gemini program, joins Jacob the day after Google I/O to unpack the research underpinning Google's latest announcements and where frontier AI is heading. The conversation moves from world models (why Google has uniquely bet on them as a path to AGI, what the "GPT moment" for video and images would look like, and how they connect to robotics and simulation) to agents (the Spark release, why the system and model need to be optimized jointly, and why scaffolding will eventually be written by models themselves). Oriol gets into the mechanics of memory in models, drawing on his cognitive neuroscience background to argue that file-system-style non-parametric memory is more practical than baking memory into weights at serving scale. He shares his views on the limits of RL today (LLMs are data-limited in a way that game-playing RL never was), why training on narrow domains like math and code generalizes surprisingly well, and what a true "Move 37" moment for science or ML research would look like. Throughout, he reflects on the unique advantages of being inside Google (TPU co-design, end-to-end revenue stability, the merger of Brain and DeepMind), the trade-offs between focus and exploration in research orgs, and why he believes AGI in some meaningful sense may already be here, even if the goalposts keep moving.   (0:00) Intro  (1:36) Why World Models  (4:21) The GPT Moment for Video  (7:51) What Makes Omni a World Model  (10:04) World Models & Robotics  (12:37) Evaluating Physics in AI  (14:51) Consumer Agents & Spark  (18:39) Scaffolding & the Bitter Lesson  (22:06) Memory & Continual Learning  (26:54) Research Bets Inside Big Labs  (32:30) Post-Training RL is Greenfield  (35:57) What Real Intelligence Looks Like  (39:11) RL Generalization  (43:00) Advice for Founders  (46:40) Can AI Truly Innovate?  (49:48) Recursive Self-Improvement  (52:14) Quickfire With your host: @jacobeffron - Managing Director at Redpoint

Logan Kilpatrick and Tulsee Doshi of Google DeepMind join for a first-ever in-person episode recorded just days before Google I/O, covering headline launches like Gemini 3.5 Flash, the Omni video generation model, and the new Gemini Spark agentic product. The conversation digs into Google's strategic decision to lead with cost-adjusted efficiency over raw capability, how DeepMind now ships a full agent harness rather than bare models, and technical questions around context window limits and knowledge cutoffs. They also explore how the team thinks about model psychology, AI welfare, and recursive self-improvement. Sponsors: Brave Search API: Brave Search API gives AI agents a fast, independent search index for research, RAG pipelines, images, places, and fewer hallucinations. Get $5 in free credits at https://brave.com/search/api/?mtm_campaign=q2-26-cognitive-revolution Sequence: Sequence handles the full revenue workflow for complex pricing, from quoting and metering to invoicing, revenue recognition, and collections. Book a public demo at https://sequencehq.com and use code COGNISM in the source field to save 20% off year one Roboflow: Roboflow is an end-to-end visual AI platform that lets you turn raw ideas into fully deployed applications in just hours, powering breakthroughs like Blueprint Pro's floor-plan understanding tool. Read the full Blueprint Pro story and see how over a million engineers are building the next wave of visual AI at https://roboflow.com Claude: Claude by Anthropic is an AI collaborator that understands your workflow and helps you tackle research, writing, coding, and organization with deep context. Get started with Claude and explore Claude Pro at https://claude.ai/tcr

Summer can feel terrifying when you're parenting a struggling teen or young adult. The routines disappear. Structure falls away. And suddenly you're left wondering how to support your child without slipping into control, conflict, or constant anxiety.And if your teen is coming home from treatment? The pressure can feel even heavier.Today, I sit down with Hilary Moses to talk about what parents often misunderstand about summer break, especially when supporting a struggling teen during summer break after treatment. Because summer isn't just “time off.” For many families, it's a major transition period filled with fear, guilt, uncertainty, and a loss of structure.We talk about the difference between healthy structure and control, why parents often panic when they see old behaviors resurface, and how to create support systems that actually help your teen build resilience instead of dependence.Hilary also shares practical ways parents can approach screens, friends, boredom, jobs, driving, boundaries, and expectations during the summer months without falling into exhausting power struggles.Most importantly, this episode is a reminder that you don't have to create a perfect summer. You're not trying to raise a perfectly compliant child. You are helping a young person slowly learn how to navigate real life with support, structure, and connection.In this episode on supporting your teen's transition home from treatment during summer break, we discuss:Why summer break can feel so destabilizing for struggling teens and familiesThe hidden challenges of bringing a teen home from treatment during summerHow to create healthy summer structure without micromanaging your teen or young adult childSupporting your child with jobs, responsibilities, and independenceWhat parents often misunderstand about motivation and accountabilityHow to approach “red flag” friendships with more nuanceWhy isolation and loneliness are major risks during summer breakHow fear pushes parents back into controlling patternsWhat healthy boundaries and expectations actually look like at homeWhy parents need resilience just as much as their kids doMore about Hilary MosesHilary Moses, MSW, LCSW, is a widely-esteemed therapist and parent coach who, throughout her career as a wilderness clinician and program clinical director was among the most highly regarded in the field. Hilary is a national public speaker and presenter, has written and developed parenting and transition curricula, facilitated hundreds of workshops and family seminars, and was an adjunct professor for the Masters in Social Work program at Arizona State University's Watts College of Public Service and Community Solutions. Hilary co-authored, “H.O.M.E: Strategies for Making home a SUCCESS during and after Treatment”.Looking for support?

As the Iran ceasefire is likely collapsing, signs that high officials are ready to flee the country. Intel reveals some Iranians are heading to Russia. The latest on Pres. Trump's pressure to end the war, Iran's refusal to accept terms, and a counter-proposal wanting the US to pay for all of Iran's damages? Commentary and perspective on this and trash-talkin' all of Tuesday morning's biggest stories

Welcome back to the Bar Exam Toolbox podcast! Today, we explain the neuroscience behind our RAMP study tool -- which we introduced in our last episode. We discuss the limitation of working memory, which makes it essential to move legal rules into long-term memory through spaced repetition and scaffolding.  In this episode, we discuss: The research and science behind our RAMP study tool Scaffolding and why we use three learning tiers Studying through spaced repetition RAMP study mode features and confidence calibration How much information can our working memory hold? Resources: https://barexamtoolbox.com/ramp (https://barexamtoolbox.com/ramp) Podcast Episode 191: Quick Tips – Using Spaced Repetition to Memorize (https://barexamtoolbox.com/podcast-episode-191-quick-tips-using-spaced-repetition-to-memorize/) Podcast Episode 348: How We're Thinking About NextGen Prep Differently (Plus, Try Our New Tool for Free) (https://barexamtoolbox.com/podcast-episode-348-how-were-thinking-about-nextgen-prep-differently-plus-try-our-new-tool-for-free/) Download the Transcript (https://barexamtoolbox.com/episode-349-this-is-how-your-brain-actually-learns-the-brain-science-behind-our-ramp-tool/) If you enjoy the podcast, we'd love a nice review and/or rating on  Apple Podcasts (https://itunes.apple.com/us/podcast/bar-exam-toolbox-podcast-pass-bar-exam-less-stress/id1370651486) or your favorite listening app. And feel free to reach out to us directly. You can always reach us via the contact form on the Bar Exam Toolbox website (https://barexamtoolbox.com/contact-us/). Finally, if you don't want to miss anything, you can sign up for podcast updates (https://barexamtoolbox.com/get-bar-exam-toolbox-podcast-updates/)! Thanks for listening! Alison & Lee

Scaffolding in the operating room: baby steps or giant leaps? Our study explores how surgical educators negotiate supervision and support as procedures unfold. #SurgicalEducation #MedEd Read the accompanying article here: https://doi.org/10.1111/medu.70074

Beth Barnes and David Rein on the one graph that ate the AI timelines discourse, and why the two people who built it are the most careful about how you read it.**SPONSOR**Prolific - Quality data. From real people. For faster breakthroughs.https://www.prolific.com/?utm_source=mlstInterview: https://youtu.be/cnxZZTl1tkk---Beth Barnes and David Rein from METR on the one graph that ate the AI timelines discourse, and why the people who built it are the most careful about how it gets read.Beth founded METR after leaving OpenAI alignment. David is first author on GPQA and co-author on HCAST and the METR Time Horizons paper. Together they built the measurement Daniel Kokotajlo called the single most important piece of evidence on AI timelines: the log-linear line of "how long a task a frontier model can complete at 50% reliability" vs release date.The conversation opens on reward hacking. Current models can articulate in chat why a behaviour is undesired and then execute it anyway as agents. From there: construct validity, Melanie Mitchell's four-problem taxonomy, and the ARC-AGI 1-to-2 collapse as a worked example of adversarially-selected benchmarks regressing once labs target them. Beth's counter: METR deliberately does not adversarially select. David's: models do not have to do the right thing for the right reasons.Methodology, then specification — David's compiler analogy, Beth on four-month tasks as expensive to evaluate rather than unspecifiable. Then the SWE-bench reality check, the METR finding that half of passing PRs would not be merged, and Beth's horses-versus-bank-tellers analogy for the labour market.The close: monitorability, the coin-spinning boat, two-year recursive self-improvement, and Beth's line that "overhyped now" and "big deal later" are not correlated claims.---TIMESTAMPS:00:00:00 Intro00:02:06 Sponsor break: Prolific human-feedback infrastructure00:02:33 Welcome and the scalable oversight motivation00:06:02 Construct validity, benchmark pathologies and the Chollet worry00:15:45 Time Horizons: human time, HCAST tasks and the 50% logistic00:24:50 Is human difficulty really one variable?00:33:05 Agent harness evolution and the inference-compute dividend00:40:00 Scaffolding bells, token budgets and the credit-assignment problem00:44:15 Look at the damn graph: regularisation bug and reliability nuance00:50:00 Why 50%? Reliability, reward hacking and pizza-party transcripts00:55:20 Extrapolation risk and straight lines on graphs00:59:25 Software engineering as a specification acquisition problem01:07:40 Compilers also made ugly code: vibe-coding quality and Claude on METR Slack01:15:15 Strongest defensible claim, Carlini's compiler swarm and AI 202701:23:45 SWE-bench merge rates, the bank-teller analogy and horses01:31:45 Scheming, alignment faking and the mentalistic vocabulary problem01:40:45 Reward hacking, monitorability and chain-of-thought faithfulness01:45:25 Recursive self-improvement, knowledge vs intelligence and closingReScript: https://app.rescript.info/public/share/de3bb40cc02ee39fdf36e2c60366eb4d(PDF, refs, transcript etc)

Title:

Are you tired of the corporate grind but terrified to leave the "security" of a full-time salary? You aren't alone. In this high-impact archive episode of Connected Leadership Bytes, Andy Lopata sits down with Matt Crabtree—the man who meets CEOs and shows them how to successfully jump ship. Matt shares the raw, honest truth about his transition from a senior role at Barclays to building a multi-million-pound consultancy. Forget what you think you know about "entrepreneurial risk." Matt argues that having 18 clients is actually safer than having one boss who can make you redundant on a whim. We examine the "unemployable" mindset, why you don't need a massive network to start, and the exact "If I did, would you?" conversation that validates your business idea before you even resign. If you've ever dreamed of being your own boss but felt held back by fear, this is the blueprint you need to move from full-time to fulfilled. Stop being a "minister without portfolio" and start building a legacy on your own terms. What You Will Learn From This Episode The "If I Did, Would You?" Script: The specific conversation you must have with 20 people to determine if your idea is a goldmine or a "lunatic" move. The "Non-Job" Catalyst: How a six-month stint as a "minister without portfolio" at a major bank became the ultimate laboratory for self-employment. The "Unemployable" Badge of Honor: Why making yourself impossible to hire by anyone else is actually the ultimate career liberation. Scaffolding vs. Sabotage: Why internal corporate mentors often have an "axe to grind" and where to find the unvarnished truth instead. Actionable Insights Conduct the "Sunday Paper" Test: Pay attention to which section of the news you read first. If you aren't naturally obsessed with the business pages and organisational drama, consultancy isn't for you. You must be a "geek for business" to thrive outside the corporate structure. Inventory Your "Hardcore Seven": You don't need a gigantic network to start. Identify the seven "founder customers" or core contacts who would vouch for your reputation. Focus on the quality of these relationships and the "ripple effect" of their referrals rather than trying to meet thousands of strangers. Establish a Financial and Relational Runway: Don't leap without a "war chest." Ensure you have a financial cushion (6–12 months of expenses) to avoid the "smell of desperation." Combine this with an 18-month pre-launch plan to ensure your first invoice is ready to be sent before your final day in the office. SELECTED LINKS FROM THE EPISODE Connect with Andy Lopata: Website | Instagram | LinkedIn | X/Twitter | YouTube Connect with Matt Crabtree: Website |LinkedIn | The Financial Times Guide to Mentoring Episode 142 Featuring Matt Crabtree

Ido Genosar is the CEO and Founder of Verobotics, the pioneering robotics solution for building façade maintenance, inspection, and upkeep. Prior to this, he led innovation at Aluminium Construction, Israel's biggest façade constructor. His diverse background in building exteriors, technology and global business development is at the core of his mission to solve deep-rooted inefficiencies with breakthrough innovation.(00:50) - “Miracle” Robotics(02:50) - What the Façade Robot Does(03:11) - Humanoids vs. Task-Specific Robots(04:28) - Why Robotics Demos Fail in the Real World(06:05) - VC Lens on Robotics(09:13) - Funding & Adoption Reality(12:48) - Façades as a Data Blind Spot(15:11) - Construction Signoff & Compliance(16:00) - Unions, Scaffolding & Safety(18:07) - New Data-driven Decisions(20:52) - Where's the Long-Term Value (29:33) - Humans in the Loop(31:48) - Best-Fit Buildings Today(33:03) - Robots in 5 to 10 Years(36:43) - Collaboration Superpower: Sir James Dyson, Leonardo Torres

Rigor doesn't mean more work, and it doesn't mean figuring it out on your own without support. It should mean achievement at a level just outside of a student's ability to do things unaided. Just like temporary building support structures, scaffolds for learners are designed to provide access to rigorous learning for all. We want our learners to have what they need to experience productive struggle at a higher level of challenge. James Fester describes strategies to create that support. Read James' article, "How to Scaffold Learning and Maintain Rigor" here.  Visit the National Park Classroom website here. Visit James' website and get in contact here. Subscribe to the Steve Barkley Ponders Out Loud podcast on iTunes or visit BarkleyPD.com to find new episodes!  

How can we put our emerging knowledge around forest systems into practice? In this episode, renowned forest ecologist Suzanne Simard returns to the podcast to talk about her latest book, When the Forest Breathes, and her decades-long Mother Tree Project, which integrates Western science and Traditional Ecological Knowledge to reshape our forest harvesting methods in ways that protect the integrity of both their ecosystems and our climate futures. As she shares her team's landmark findings on what Mother Trees are telling us about generational resilience, Suzanne challenges us to begin working with the intelligence of the forest. Read the transcript. Photo by Bill Heath

In Season 11 Episode 7 of Learning Can't Wait, Brandon Cardet-Hernandez, CEO and founder of Medley Learning, shares his journey from multilingual learner to educator, school leader, and edtech founder. He describes how early classroom experiences and the impact of a teacher who provided personalized language scaffolds shaped his commitment to equity and access. Brandon discusses the persistent gaps facing multilingual learners, the challenge of providing real-time, differentiated language supports, and how Medley leverages technology to bridge the research-to-reality gap—empowering teachers and students without lowering rigor. He emphasizes that belonging, high expectations, and intentional scaffolding are essential for student success, and urges educators not to use AI as a shortcut for reducing rigor, but as a tool for advancing achievement and inclusion.

Jon Spike on Games as Creative ConstraintIn this episode of Experience Points, Jon Spike explores how creative constraint drives innovation in game design and learning. A former K–12 English teacher now working at University of Wisconsin–Whitewater, Jon shares how classroom experimentation led him to design tabletop educational games through GamestormEDU. He highlights Gamestormers, which uses a five-card structure to scaffold storytelling while preserving player agency, and Doomscroll, where players step into the role of social media algorithms to unpack persuasive design. Jon emphasizes that educational games must first succeed as enjoyable experiences. Through thoughtful playtesting and adaptable design, he argues that strong constraints don't limit creativity—they focus and elevate it.If you liked this episode please consider commenting, sharing, and subscribing.Subscribing is absolutely free and ensures that you'll get the next episode of Experience Points delivered directly to you.I'd also love it if you took some time to rate the show!I live to lift others with learning.  So, if you found this episode useful, consider sharing it with someone who could benefit.Also make sure to visit University XP online at www.universityxp.comUniversity XP is also on Twitter @University_XP and on Facebook and LinkedIn as University XPAlso, feel free to email me anytime at dave@universityxp.comGame on!Get the full transcript and references for this episode here: https://www.universityxp.com/podcast/162GBLV_2026_Registration_Pre-Roll GBLV_2026_Registration_Post-RollSupport the show

Suna Hall is an ADHD and neurodiversity coach who works with neurodivergent teens, adults, and parents. Today she's breaking down what neurodivergence actually means—ADHD, autism, dyslexia, and more—and how coaching differs from therapy. Coaching is future-focused and finite: where you are now, where you want to be, what's getting in the way, and building skills to close that gap. Executive function is the logistics part of your brain—task initiation, completion, planning, working memory. For neurodivergent people, these struggles aren't just annoying, they're exhausting. You're expending huge energy to hold information that neurotypical brains process easily. To meet diagnostic criteria, you're struggling to the point where life becomes extremely hard, not just inconvenient. Kids notice they're different from peers. Late-diagnosed adults always knew something was off but didn't know what. The late-diagnosed women demographic is massive right now. Girls were missed because boys manifested ADHD physically while girls internalized it. Hormonal shifts—motherhood especially—ramp up symptoms. New mothers are getting diagnosed because their sensory world shifts, the mental load explodes, and they can't white-knuckle it anymore. They've been told they're dramatic their whole lives, but actually they were coping until they weren't. One mom screams into the freezer during hot flashes. Another realizes heat is her sensory breaking point. The advice: track when explosions happen, take yourself away before it escalates, shore up your capacity, and talk to your peers. Say "I wanted to throttle my child today" and hear "me too." Connect with Suna Hall: Instagram: https://www.instagram.com/nd.coach.suna/ Facebook: https://www.facebook.com/suna.hall/ Linkedin: https://za.linkedin.com/in/neurodiversity-coach-suna Coaching circles starting 2026 Follow Carly on: Website: https://onthecouchwithcarly.com/ YouTube: https://www.youtube.com/channel/UCfBi56xQookfRGL3zvWVzCg Instagram: https://www.instagram.com/onthecouchwithcarly/?hl=en Facebook: https://www.facebook.com/onthecouchwithcarly/ TikTok: https://www.tiktok.com/@onthecouchwithcarly Apple Podcasts: https://podcasts.apple.com/za/podcast/on-the-couch-with-carly/id1497585376 Spotify: https://open.spotify.com/show/3t7A2FMnISQ2fz9D5p0Xuw

Claude Cowork came out of an accident.Felix and the Anthropic team noticed something interesting with Claude Code: many users were using it primarily for all kinds of messy knowledge work instead of coding. Even technical builders would use it for lots of non-technical work.Even more shocking, Claude cowork wrote itself. With a team of humans simply orchestrating multiple claude code instances, the tool was ready after a brief week and a half.This isn't Felix's first rodeo with impactful and playful desktop apps. He's helped ship the Slack desktop app and is a core maintainer of Electron the open-source software framework used for building cross-platform desktop applications, even putting Windows 95 into an Electron app that runs on macOS, Windows, and Linux.In this episode, Felix joins us to unpack why execution has suddenly become cheap enough that teams can “just build all the candidates” and why the real frontier in AI products is no longer better chat, but trusted task execution.He also shares why Anthropic is betting on local-first agent workflows, why skills may matter more than most people realize, and how the hardest questions ahead are about autonomy, safety, portability, and the changing shape of knowledge work itself.We discuss* Felix's path: Slack desktop app, Electron, Windows 95 in JavaScript, and now building Claude Cowork at Anthropic* What Claude Cowork actually is: a more user-friendly, VM-based version of Claude Code designed to bring agentic workflows to non-terminal-native users* Why “user-friendly” does not mean “less powerful”: Cowork as a superset product, much like how VS Code initially looked simpler than Visual Studio but became more hackable and extensible* Anthropic's prototype-first culture: why Cowork was built in 10 days using many pre-existing internal pieces, and how internal prototypes shaped the final product* Why execution is getting cheap: the shift from long memos, specs, and debate toward rapidly building multiple candidates and choosing based on reality instead of theory* The local debate: why Felix thinks Silicon Valley is undervaluing the local computer, and why putting Claude “where you work” is often more powerful* Why Claude gets its own computer: the VM as both a safety boundary and a capability unlock, letting Claude install tools, run scripts, and work more independently without constant approval* Safety through sandboxing: why “approve every command” is not a real long-term UX, and how virtual machines create a middle ground between uselessly safe and dangerously autonomous* How Cowork differs from Claude Code: coding evals vs. knowledge-work evals, different system-prompt tradeoffs, longer planning horizons, and heavier use of planning and clarification tools* Why skills matter: simple markdown-based instructions as a lightweight abstraction layer for reusable workflows, personalized automation, and portable agent behavior* Skills vs. MCPs: why Felix is increasingly interested in file-based, text-native interfaces that tell the model what to do, rather than forcing everything through rigid tool schemas* The portability problem: why personal skills should move across agent products, and the unresolved tension between public reusable workflows and private user-specific context* Real use cases already happening today: uploading videos, organizing files, handling taxes, managing calendars, debugging internal crashes, analyzing finances, and automating repetitive browser workflows* Why AI products should work with your existing stack: Anthropic's bias toward integrating with Chrome, Office, and existing workflows instead of rebuilding every app from scratch* Computer use one year later: how much better it has gotten, why vision plus browser context is such a superpower, and why letting Claude see the thing it is working on changes everything* Why many “AI verticals” may get compressed: specialized wrappers may matter in the short term, but better general models and stronger primitives could absorb a lot of narrow use cases* The future of junior work: Felix's concerns about entry-level roles, labor-market disruption, and whether AI can compress early-career learning into denser simulated experience* Why Waterloo grads stand out: internships, shipping experience, and learning how real teams build products versus purely theoretical academic preparation* The agentic future of the desktop: what it means for Claude to have its own computer, whether AI should act on your machine or a remote one, and how intimacy with personal data changes the product design space* Why Electron still mattered: shipping Chromium as a controlled rendering stack, the limits of OS-native webviews, and why browser engines remain one of the great software abstractions* Anthropic's Labs mentality: wild internal experiments, half-broken future-looking prototypes, and the broader effort to move users from asking questions to delegating increasingly long and valuable tasks* Why the endgame is not just more capability, but more independence: teaching users to trust AI with bigger scopes of work, for longer durations, with fewer interventionsFelix Rieseberg* X: https://x.com/felixrieseberg* LinkedIn: https://www.linkedin.com/in/felixrieseberg* Website: https://felixrieseberg.com/Anthropic* Website: http://anthropic.comFull Video PodTimestamps00:00 — Cheap execution and building all the candidates00:44 — Intro in the new Kernel studio02:47 — What Claude Cowork is04:18 — Why user-friendly can be more powerful05:33 — How Anthropic built Cowork07:09 — Prototype-first product development08:00 — Why local computers still matter09:20 — Skills, primitives, and platform leverage12:13 — Cowork's architecture: VM + Chrome + system prompt15:38 — Felix's own bug-fixing Cowork workflows17:38 — Local-first agents20:16 — Evals, planning, and knowledge-work optimization23:14 — What Anthropic means by evals24:21 — Scaffolding, tools, and why skills matter27:44 — Demo: YouTube uploads and self-generated skills31:03 — Calendar automation and cleaning your desktop34:47 — Browser context and why DOM access matters37:47 — Skills portability and plugins44:36 — Which AI categories survive?46:19 — Junior jobs, simulated work, and labor disruption52:00 — Gradual takeoff vs big-bang takeoff53:42 — Finance, taxes, and enterprise verticals56:24 — Vision and the improvement in computer use57:31 — Why Claude writes its own scripts58:06 — Should Claude have its own computer?1:01:26 — Windows 95 in JavaScript1:03:19 — VM tradeoffs and sandbox design1:07:23 — Approval fatigue and safe delegation1:11:18 — The future of Cowork1:12:27 — What comes next for agentic knowledge work1:15:13 — Electron, Chromium, and desktop software lessons1:22:16 — Multiplayer agents and coworker-to-coworker workflows1:26:05 — Anthropic Labs and closing thoughtsTranscriptAlessio: Hey everyone. Welcome to the Latent Space Podcast, our first one in the new studio. This is Alessio, founder of Kernel Labs, and I'm joined by swyx, editor of Latent Space.swyx: Yeah, so nice to be here. Thanks to, uh, TJ, Alessio, Allen helping to set everything up. It looks beautiful. We even have the logo outside.Yeah, kind.Felix: It's like really nice, right? When you walk in here as a guest, you're like, ah, this is a serious production. You're like, feel it immediately.swyx: Yeah. Felix, you've been, you're, you're currently a product manager of Cowork or,Felix: uh, really Technicswyx: Eng. Yeah. The, the identities are kind of vague member technical staff.Felix: I know member staff is like, the official title will carry around forever.swyx: Yeah. I basically kind of wanted, like we've been. Kinda obsessed. I, I've been using it a lot, even for managing latent space. Like, uh, cowork helps me upload videos and like title things and like edit and everything. It's, it's like really amazing.Alessio: Cool. He said multiple times Cowork has said gi in the group track.swyx: Yeah, yeah, yeah. So, so we have a second, uh, we have a second channel, uh, for latent space tv. Uh, and I, uh, and uh, we basically, this is our Discord meetup. Um, and I I, we have like Claude Coworks, it might be a GI, I don't know if we, we have, uh, uploaded it yet, but one of the sessions was like a, like a Claude cowork thing.Felix: I, you have to see, I would love to see it. Like, I'm so curious, like one of the most fun parts of my job is like constantly see the weird things people use Cowork for because it's obviously like very hard for us to actually design for specific use cases we do. But like every single person who's like most amazed is usually amazed about a thing that I didn't even expect cowork would be good at.Um, we have a new designer and it's one of the first small tasks. I was like, Hey, we need like a new emoji for cowork for our internal stock. It's like a pretty small thing. I like, can you please do it? And he drew an SVG and just gave it to coworker was like, can you animate this emoji? And now it has like this beautiful loopy animation.Um, and I mean, I think obviously this goes down to like, it turns out you can do more things with code than you expected, but it, it's like that kind of stuff that is really fun to me. So, long story short, I would love to see like, the kind of things you're doing.swyx: I'll pull it up. I'll pull it up.Felix: Yeah. Yeah.swyx: Uh, but before we get into it, I, I think always wanna start with like a top level. What is Claude Cowork for people who haven't heard of it? Haven't tried it out.Felix: Okay. Uh, real quick, Claude Cowork is a user friendly version of Claude Code. So the way it basically works is we have Claude Code and for us, fairly impressive agent harness that over December we noticed more and more people are using either, even though they're not technical, they, they're not at home in the terminal or they are at home in the terminal, but they started using Claude Code for non-coding workloads, right?Like managing expenses or like filling out receipts or organizing a knowledge base. Like there was a big obsidian moment that a lot of people liked and we wanted to capitalize on that, but also bring, bring this capability to people who are not terminal native and who might not know how to like brew and store something.So cowork is Claude Code running in original machine with a little bit of padding, a little bit more guardrails, making it a little safer and a little bit more convenient for people who don't wanna first open up the terminal when they go to work.swyx: It's interesting, uh, that is kind of. Pitch that way as a more user friendly thing because I always feel like it, it, to me, I I treat it as like why I'm familiar with Claude Code.Like we, we did a Claude Code episode Yeah. A year ago. But this one is like even more power user tools ‘cause it, uh, it kind of integrates much better with like clotting Chrome and, uh, in all the, all the other tooling. But like, maybe, maybe that's like a perception thing, right? LikeFelix: No, honestly, I don't think you're wrong.This is like a, a thing I've been thinking a lot about for like the last two weeks. So,swyx: but when they say user friendly, it's like, oh, it's the dumb down version. But no, actually this is the superset.Felix: Yeah. Like, I think a similar thing happened, A similar thing happened to me about 10 years ago, like maybe 12 years ago when I was at Microsoft and we started working on, on Electron and like browser-based technologies and cross-platform stuff.And one of the first use cases was Visual Studio Code, which used to be a website. And the initial narrative was, or Visual Studio Code is, is like a more user-friendly version of Visual Studio. But in a similar vein, I think there was some voices saying, oh, this is. For serious developers, like, we're not gonna use this.Right? For like anything. And I think in the end what happened is people have different stories about why Visual Studio Code became such a big thing. But my personal, my personal belief is that the Hackability and the extendability has like played a pretty big role, right? You can hook in Visual Studio Code that like almost any workload, it's so easy to hack on, so easy to put extensions for it.And I think cowork might be hitting a similar thing where it's very easy to extend and it's very easy to bring into your workflows. Uh, so the convenience I think is a bit of a, it's obviously the thing we strive for as developers, but I think the way people find value in it then is by probably mapping it onto whatever they actually have to do in their job.Alessio: So end of last year, you see the spike of like non-technical usage and clock code. What's the design process to say we should make clock code work? Because I mean, you built it in only 10 days. Um, I'm sure there was some discussion before on whether it's easier to use mean. You know, like making, making like a desktop GUI is obviously one way to do it, but like there's a lot of nuance in the product.Like maybe talk people through what was like the trigger of like, we should build a separate thing. We should not build like a different plot code thing. And then maybe some of the more interesting design decisions that maybe you didn't take.Felix: Yeah, I think philanthropic, we've been thinking about ways to move people who are comfortable with using Claude to answer questions and bring more of the power of like this thing to now like, execute tasks for you.I can like solve problems for you can like build things for you. How do we bring that capability to people who are currently mostly comfortable with like a like question answer paradigm within the chat. And we've had a lot of prototypes around that. Just going back as far as like easily a year and a half.Like we had a lot of people working on that. Um, and internally philanthropic is a very prototype demo, first culture. We have a lot of like internal prototypes that don't reach the public. What Cowork actually became is like we sort of picked the right pieces out of the many prototypes that we had.Right. And that's, that's maybe also like, I think an important qualifier whenever people mention this like 10 day number. I do think it's important to me to mention that within Double Scratch there was like a lot of stuff already happening, right? Like, and I think it's important for people to remember that when you build a website, you use React, you use like a bunch of other things.And this is like a similar scenario with like a lot of pieces we already had. Um, and in terms of decision path, I think we live in like an interesting new world where execution is actually quite cheap.swyx: Mm-hmm.Felix: So maybe, maybe what you would do That's so crazy. The year. I know it's wild.swyx: You should be, ideas are cheap.Execution is the hard part. IFelix: know. And like the, we, we used to live in this world maybe where you would take a product manager and the product manager would go to a number of potential customers and in this like very low bandwidth way, would try to. Try to like tease out what are the problems they're having, what are they willing to buy?Um, and then maybe what can you build to like drive out that need and then you go back and you like draft a spec and you think about it and then like you make a design and you execute it. We internally philanthropic app, not pretty much closer to the point where we're like, don't even write a memo, just like build, like let's build all the candidates very quickly.Let's just build all of them and then pick the best ones. I think the, the decision that is most impactful both for the product as well for the users right now is like the way we put value on your local computer. I think that's a big decision point a lot of people have thought about. Should this thing, whatever it is, should it ultimately run into computer or should it run in the cloud?‘cause they're big trade offs, right?Alessio: I guess like if we solve auth, it would be easy to do in the cloud. But I think like the fact that I can just download any file from anywhere and then put it and cowork there, it's like a big unlock. Um, I mean it's interesting you mentioned reusing certain pieces. I think this is something I've been thinking about even with Claude Code, right?The price of like writing code is going to zero, blah, blah, blah. But it actually seems like the value of having some sort of platform substrate is like increasing because as you build these new things, you can kind of plug them together.Felix: Yeah.Alessio: So I almost feel like when people are saying, oh, the value of a lot of software is gonna zero because you can recreate it, to me it's almost like the opposite.It's like having an existing platform to build on top of. It's like even more valuable because you can kind of bolt things on.Felix: Yeah.Alessio: You have obviously mcps, you have skills, you have like obviously the models, which is a big part. All these things kind of come together. Do you feel like that's a valid way to think about it, where people should invest even more in kind of like primitives.To rebuild on or are you like recreating a lot of it each time because like things change and it's easier to rewrite than reuse?Felix: You know, I think, I think you're right. I think you're right that the holistic platform is really useful. And this is maybe a whole like a somewhat contrarian view to a lot of people in ai.I actually don't think that the future is going to be hyper personalized software down to the point where everyone is running their own version. Like, I actually think it's going to be quite hard for all of us to have our own internal chat tool and like, if I wanna talk to you, likeswyx: howFelix: is that gonna work, right?In the, in the context of cowork and how we build it, I think it's a bit of a combination. Like what the, the execution that gets cheap is not necessarily rebuilding all the primitives. I think our priori, there's also not a lot of value in it. So for instance, my team did not think about rebuilding clock code.We're like very much started with the. The core thesis of this should be Claude Code.Mm-hmm.Felix: And then we'll like build things on top of it. The part of the execution that gets a little cheaper is like, how do you take all of these Lego pieces and put them together in a way that makes sense for users?It's like actually valuable. You have so many different approaches now in terms of what kind of, what kind of things do you actually elevate to a primitive, do you strongly believe that all your products should be built by just combining primitive that the public also has available? Do you keep some things internal?Um, and I think that's still evolving, but I think what's probably gonna go away is like, I'm not sure if it's gonna fully go away, but I'm gonna say, I think for me personally, I will probably no longer try to come up with a really good product without testing up with people. This is not a new concept, but wherever you used to have to make costly decisions around, do we pick technology A or technology B, or do we like, um, build it this way, build it the other way.I really strongly believe now you just build all of them and try them out with a small focus group and then whatever, whatever is better is what you go with. Right. And that, that is probably quite different even from how we maybe worked a year ago. Right. Like, I think, I think this happened very recently.Alessio: Yeah. I started building something in on Electron since you're here. Coincidence. Uh, but then Electron and like SQL Light are like, there's like some issues that like between development and like, uh, building anyway. And I was like, let's just rebuild the whole thing in Swift and just recreated the whole thing in Swift.And it's like, I. It's done.swyx: You know, I didn't take any effort. I, I, I don't even know Swift.Alessio: Yeah, exactly. I was like, I'm the, I'm not reviewing it anyway, whatever. You can write in whatever language you pick, but the important stuff that I did was not write the electron bindings. Yeah. It was like the logic of what happens in the app, you know, and then the model is like, yeah, I can just recreate the same thing as withswyx: Yeah.I, I think you still want, especially for people who are doing like high performance software or like very complex software, uh, you still want like, some view of the architecture. Uh, but you can use markdown for that,Felix: right? Yeah.swyx: Uh, you don't actually have to read the code again. I, I'm still like on a sort of like a definitional thing.Um, can we build a good mental model of Claude Cowork? Um, this is what I have, right? Like you you said it's like fundamentally cloud co. We don't wanna touch it. There's the cloud app, there's clouding Chrome. I think you guys do something different in planning, but, uh, I've been talking with Tariq who is on the cloud co team, and you guys are, he's like, no, we just exposed planning.Maybe we can clarify like, what are the major pieces. That people should be aware. It goes into cowork, like,Felix: okay, I think you basically have them. So really, um, you can, you can take planning more or less out. I think there's a few things that are really valuable in cowork. Um, the virtual machine is probably the most powerful thing.So we currently run like a, we currently run like a lightweight VM and we put clocked out into the vm and we do that for, for, um, a number of reasons. Safety and security is a big one, but even if you, even if you ignore for a second safety and security and you're just like, okay, Yolo, I want this thing to do whatever.It is quite powerful to give Claus on computer that is like generally a good idea. And in terms of architecture and UX and everything else that we've been working on, philanthropic, it often is quite useful for you to like anthropomorphize, um, clot aggressively and just be like, this is a person. What will you do if you give a, if you had a person, right?Yeah. And the analogy I've given my dad this morning who is still like quite insistent on using chat even for like coding things, is if you were a developer and your employer told you that you don't need a computer, they're just gonna like, send you emails with a code and you send emails with code back like that, maybe work for Patrick Miles in the back, but that it's not very effective.Um, so what we can do with the VM is because it's a, it's a Linux system, Claude Code has more or less free reign to install whatever needs to install. It can install Python, it can install no js. We do have strict network ingress and egress controls. So you can still, as, as a user in like plain human language, make it clear to, to the entire system what you're okay with and what you're not okay with.But at no point do we have to ask a real person, like a, like a person who might be in marketing or a lawyer. I'd have to go to a lawyer and be like, are you okay with me installing Homebrew?Alessio: Yeah, yeah.Felix: Right. Because the implications of the question and the answer are complex and nuanced and like, not, not easy to reason about.This gives us a lot of distraction that makes Cloud very powerful. Now then around it, we, we do probably have a number of things that also keeps growing almost every single week that you're probably noticing that make cowork maybe better for certain tasks than just cloud. Cloud on its own. Yeah. But most of those actually live in the system prompt.They're about like, what can we infer about the work that you do? What can we, what can we intru in the system prompt to make that more effective? It's of course the like very tight integration with Cloud and Chrome. You're noticing that a lot of people, especially as the models get better, a lot of people throw up their hands when it comes to MCP connectors in this area.I'm not gonna, I'm not gonna go through like 25 M CCP connectors, click off everywhere and then like half of them don't let me do the things anyway. So Cloud and Chrome is quite powerful because we can just talk to the cloud and Chrome sub agent and that will just do things for you.swyx: Yeah, so, so one example right in MCPI, honestly, I think that the state of MCP is kind of, kind of.Really hard to integrate. Um, I need to, I needed to add, uh, Figma MCP to the coding agent that I use.Felix: Yeah.swyx: Uh, and, but I didn't wanna read the docs, so I just had caught to it. And it's, it's great at reading docs and the same, same way I had to set up like a Google Cloud, um, account for some project I was working on and get some API keys somewhere.And Google Cloud is famously super hard to navigate, so I just didn't wanna deal with any of it. I just used Claude CoworkFelix: within the first week of developing on Core. This happened very, very quickly. Um, I caught myself by starting to use cowork for coding tasks, which is not ostensibly what we built it for, right?We don't need to. But I found myself, um, I found myself like on our internal, internal tool that we have for, to collect crashes and just like debugging information and I found myself sort like picking out the ones that I think we can easily fix versus the ones that might be like kernel corruption or something else on the operating system.And I found myself sort of picking these out and then just telling Clark, go fix this bug. I was like, what am I doing here? Go one level up, tell a cowork, I want you to go to all these crash tools. I want you to find all the bugs that you think are fixable and not like an operating system crash. And then I want you to tell another cloud to like fix all of that.Um, and that's, that's, that's sort of another cloud,swyx: just so it can spin up another instance or,Felix: uh, it, currently what I do is, um, and this is a bit of a hack, but I tell it to use clockwork remote to which website itself? Yeah, that's interesting. So you basically take, if you, if you imagine like a dashboard with like 20 bucks, you, this is remote control or clock or remote, or, sorry, I just wanted to confirm what, the way I'm using it is.I have cowork running and I'm telling cowork, here's where I normally go every morning to find the latest bugs. Go read the entire bug list, separate out which ones are fixable, which ones are, are fixable, and then for the fixable ones, four is this almost loop. For each bug, write a markdown file with a prompt.And then for each markdown v, that is a prompt. Start of a cloud set. So natively Claude Code hasswyx: this concept of subagents. Mm-hmm. And this is basically a subagent, but you're not using the subagent functionality.Felix: I'm not using the subagent functionality. And the reason I'm not is because I'm firing that off as a Claude Code remoteswyx: task.Felix: Yes. That's kind of nice. ‘cause then I can just fire it off. I can go to my next meeting and in Claude Code remote. Now the work is happening.swyx: Mm-hmm. Yeah. You, you see like you're already starting to use the cloud over your local machine. And I think this is one of those things where like. Shouldn't just everything just be cloud first, right?Felix: Ah, this is such a good group. I'm like solely bad about this. I have so many thoughts about that. Okay. So I generally believe that Silicon Valley overall is undervaluing the local computer. And my default argument for that is always how come we're all using MacBooks and not like an iPad or a Chromebook?Um, that there is like still value in, in having a local machine. And now when I think about Clot, it's this entity that is supposed to be very useful to you, like it tremendously useful to you. I think that entity needs to have access to all the same tools you have access to. Otherwise it's gonna be hamstrung in like all these complex ways.And there's, there's sort of two approaches we could take. We could say, okay, we're gonna like one by one chip away at everything that is at your computer and move it into the cloud. That's, that's one way to do it. Um, and I think other products have taken that path. I personally, this is a very personal opinion, but I personally, for the amount of tools that I use.Just don't have the patience to give another tool like permissions to every single thing and keep those permissions up to date. The second thing that I'm still grappling with, and I don't have a good answer for anyone just yet, but the second thing I'm still grappling with is what does it look like for someone to slurp up your entire work and put that in the cloud?Like if I, just as an example, like if you could click a button and it just clone your entire computer into the cloud, is that something that you would want? I'm not totally convinced yet that all everyone will. Mm-hmm. And that is sort of like upstream of all the technical issues we're gonna have. ‘cause like in general, I think the world is not ready for this kind of stuff.Like, I'll give you one quick example that would probably be very easy for us. So as a desktop app, we in theory with your permission, can do a lot of things on your computer, including reading your Chrome cookies. If we really want to do right, we could take your Chrome cookies, you would have to decrypt them for us.We could put those on the cloud if we really felt like it. Pretty easy solution. That would be super cool. We could just be like, oh, we can do all your tasks in the cloud now. Um, a lot of websites, thanks, include it. If, if they see the same authentication from like two different locations, we'll just lock down your account and now you have to go to the branch and be like, okay, I, I'm here with my passport.You actually know that. Wow. Yeah. As tired as well are of the term agent for the age agent future, I think there's a lot of stuff that sort of slowly needs to catch up and until that's the case, the way I, as someone's working on clock and make Cloud most effective is to like put it where you are working.swyx: Anything else? I thought with our mental model, so like, basically like, uh, part of me also just want, like the more I understand how it works, the more I can use it to its full potential. Right?Felix: Yeah.swyx: And so what I'm get hearing from you is you told me to delete the planning thing. You're not doing anything special on, on the, that's only exclusive to Qua cowork.Felix: We have some tricks for this sort of like change week over week. We eval cowork maybe against different use cases than he would evil clock code, right? If you think about it this way. Okay, so like clock code is our eval clock cowork. Yeah. So clock code is like quite optimized for coding tasks and we mostly value it whether or not we're getting better or worse depending on how good it is at like a typical suite job.And Clark Cowork on the other hand, we evaluate more against typical knowledge work, the kind of stuff he would find in finance or in like maybe a, like in like a legal office. Um, my personal use case is always like managing my things, like managing my personal mortgage or something like that, right? Or like wealth planning for me and my family.Those are the kinds of use cases we eval, clock cowork on. And what you might be picking up on is like the subtle changes we make to the system. Prompt what we put in the system, prompt how we steer, clot with the tools we give it. Um, like either it'd be better in one or the other direction and whether there's a trade off, try us exist a lot.CLO code will be better of a code and Claude Cowork will be better. For non-coding tasks, will those gaps still exist in the next three generations of models? It's like a little unclear to me though.swyx: Yeah,Felix: because right now these like hyper optimizations we make, I'm not sure for how long they're still be relevant.swyx: I think what I was referring to was also, it, it just, uh, it qualitatively felt different when I probably, it's just all prompting and I'm reading too much into it, but like the, the fact that it comes out with like a nine step plan, I can edit the plan and give feedback and, and, and see it execute the plan.Yeah. It felt more long range than in Claude Code, but maybe that already existed in Claude Code and you just build a nicer UI for it.Felix: It's kind of both. Um, like if the Clark Code people who build the planning functionalities would city, they probably say yes, we have all of those things in Clark code and they do.Um, I think people tend to give cowork. Tasks that are maybe of longer time horizon, I thought isswyx: so long. Yeah.Felix: That's like one thing, right? It's just like that the, the chunk of work tends to be maybe a little bigger. And then the second thing is that because the work, when it gets longer, it gets a little bit more ambiguous.We do tell co-work to make heavy use of the planning tool or to make heavy use of the ask user question tool, right? We do want it to come up with like. Different scenarios of, okay, tease out what the user actually wants. Don't go off to work for like four hours and then come back with the wrong thing.And you're probably picking up on that.swyx: Yeah.Felix: Um, I wish I could tell you I like built this magical thing and it's like, there's some secret sauce,swyx: but No, no, no. I mean, it's, it's just clarity is good that, you know, engineers just want to know. Yeah. They can, they can plan around it. And then I think also for me, um, I am realizing I have to switch to my, my other machine because this is a new machine that doesn't have my session.But, uh, yeah, the, the, the planning is really important for, for me to like approve or like to see whether it's like, it's right. The ask is, the question is so beautifully presented. I mean, it also, it also available in like cursor and, and in Claude Code. But like, I, I think like it's so nice to see that it, like it's kind of for me like to understand that it gets me, it gets what I want to do.Felix: Yeah.swyx: Yeah.Felix: It probably very hardswyx: just on the topical evals. Mm-hmm. When you say eval, I think people are very vague about what it means. Is it just like vibe testing or do you have like automated programmatic evals of Claude Cowork?Felix: When we say eval, uh, what we really mean is that we essentially take the entire transcript, including all the tools that clot has available ultimately to it, and we then measure what are the outputs, depending on what we tweak, right?So we do run that a lot. We use that in training. Um, we use that in, in like, if you sort of separate out post training from like the scaffolding around it. Cowork sort of exists in the scaffolding space, but obviously we also train on it a little bit. Um, so when we say eval, we mean given the certain transcript, what do the outputs look like?Including the file outputs as well as like the actual token outputs, like the ones that you see in the chat window.Alessio: I'm curious, um, how much of the failure modes are the model intelligence versus like the usage of the end tool to put the intelligence in? Like the well planning is like a good example, right?It's like one thing is to come up with a plan. The other thing is like make a nice spreadsheet. Yeah. That kind of runs you through the plan. Like how have you seen that? Well,Felix: the thing that I grapple with a lot is that whatever scaffolding you come up with, I think we still have a bit of sort of like model overhang where the model is dramatically more capable than right.Users end up using it for. And I think part of that is that we're just not getting the model all the tools to do all the things that's theory capable of, right? There's like one thing, um, however, whenever you do build the scaffolding, I'm sort of wondering at what point, at what point will that scaffolding go away and like how much you invest in figuring out what the right scaffolding is.It's kind of up to, it's a little bit of a bet. And one thing that I as an NJ quite enjoy is that like working in philanthropic and working at a frontier lab, I maybe have a little bit more insight into what's coming, coming down the chute in terms of like, what's the next model, what is the model capable of?What is good at, what is it bad at? And I'm, I'm increasingly wondering, is the right thing for us to like really invest too much in sort of these like scaffolding corrections where the model might otherwise not misbehave, but just not do the thing that you want?Alessio: Yeah.Felix: Or is it to just like give it as many capabilities as possible, try to make those safe so there's the worst case scenarios, likeno status might be otherwise.And then just simply wait a second for the next model drop. I'm personally, currently more leaning into the ladder. I think we're gonna see a lot of like applications and companies that do very impressive things with ai that in the short term might seem very effective ‘cause they're very specialized to individual use cases.But I think once models get better generalization and get better at like those specific use cases without being super guided on those, I'm not sure how long that's gonna stick around. And you can kind of, kind of already see this in like skills and NCP servers, right? Mm-hmm. We've, we've already seen sort of this like slow shift from MCP service to skills.And like, maybe a good example is Barry who made skills. He was initially hacking on something that honestly looked a lot, looked, looked a lot like what Cowork does today. It was sort of thinking about what if cowork, but for like people who don't wanna build code. Mm-hmm. And, um, he too did that as a prototype inside the desktop app.One of the first use cases we thought of were, okay, what, what are like coding like use cases that could really benefit from graphical interfaces and like from being a little separated from the actual underlying code. And everyone comes with the same answers. Data analysis,Alessio: right?Felix: Yeah. Or saying how many users do we have today?How many, like, it's always data analysis. And I think the thing that ultimately led to skills is that we wanted to connect this little prototype to our data warehouse and. The team very quickly discovered that like instead of building a custom tool for the thing to talk our data warehouse, they just like meet and embarked on follow like mm-hmm.Dear Claude, if you want to get data, here's the end point. Here's what the API looks like. You'll figure it out.swyx: Ah.Felix: And then it be hand over control. Yeah, yeah. Also just like maybe go one step up in the layer of abstractions, right. Just, yeah. Instead of, instead of telling the thing, here's ACL I, please call the CLI, or here's an MCP.Please call this ECT shape. Just like this is the end point. If you wanna know something, if you post here, maybe you can do post sql. It's gonna be okay. And that ended up being so effective that they started trying the same pattern of like just giving the model a markdown file that describes whatever it needs to do.That the whole thing eventually became skills and we're like. We should package this up. This is a good idea.swyx: Yeah. Um, we've had Barry Mahesh, uh, on, on our conference and uh, he's uh, definitely got a good idea there.Felix: Yeah.swyx: I wanted to show you the, how I've been using Claude Cowork.Felix: Uh, this is was my favorite part.swyx: This is this. So this is like me, uh, this is how we run the Discord. Uh, we literally, uh, at first I didn't trust Cloud Core. This was my very first usage.Felix: Okay.swyx: Right. So then I was like, okay, I will just try to manually download from Zoom all my recordings and upload it to YouTube. Yeah. Because this is a very laborious process.I got a click, click, click YouTube, um, isn't super user friendly. Uh, and it just did it. And then I was like, actually, you know, even the download from Zoom part, I should also. Put into Claude Cowork, and then I did it right. Here's a bunch of, and it starts compacting here, and it, and it, it starts to even be able to do things like look through the individual frames of the video to name the video so I can upload it auto automatically.Oh, that is, and this replaces my job as a YouTuber. We will forever appreciate your creative Yes. You know, and so that's great. Uh, but then by the way, it compacts and makes, makes like a new thing, right? So I, I don't, I don't have the initial, initial thing, but then I asked it to make its own skills so that it, so that something that's repetitive and one-off and human guided becomes more automated and I can use the skills independently and reuse them.Uh, and it obviously you can write skills and that goes into context and skills at the bottom here, which is, which is so nice. Um, so I have all these skills that, that I now sort of do on a weekly basis. Uh, I know you've released scheduled Coworks, which I haven't done yet, butFelix: course I should try them. I, I think this is like so wonderful and fun for me to see because.One thing that is very fun for me about skills in particular is that they're so easy to make. Like anyone can make a skill, like a text message, could be a skill, and they can be so hyper personalized to you. And this is like sort of the subtraction layer, right? Like, um, I, I'm just guessing, but I assume, heck, you are very good at your job.You're probably given this thing some guidance about how to do it, right? I,swyx: I just said, wrap everything up into, into a skill, right?Felix: Yeah.swyx: And then, uh, and then I was like, actually, sometimes I might need to break, uh, things apart because some parts fail or some parts might be needed in individually. So I told it to split one skill into three skills.So it's like a skill splitting thing, and then there's like a parent skill that just orchestrates all of them if I want to use that. You know, like, um, I think that's, that's like really good. Uh, and, and, uh, there's, there's one more part, which is the, uh, Google Chrome thing that I told you about.Felix: Yeah.swyx: Where I'm like, okay, you know, what's better than uploading, using Claude Coworks to YouTube?Like actually. Looking at the docs to like programmatically upload to YouTube and then putting that in a skill. And I've never done that before. I don't want to deal with Google Cloud. Yeah. So Claude Cowork does it for me.Felix: That is really cool.swyx: So, so I, I just, I don't care. I just, like, I do a thing. I don't, it doesn't really matter.Felix: That is really cool. And then you've, I assume paired the skill just with the script that it's built.swyx: Yeah, no, I just update, update the skills.Felix: Oh, that is beautiful. Yeah. That's wonderful.swyx: It's kind of like a skill, like, uh, uh, basically I think like the way that people ease into Claude Cowork is like take a knowledge work task that you would normally be clicking around for and then, uh, try to turn, turn that, and then you do the, okay, well what if you went further?Okay. And then when, if you went further, when, if you, and it sort of expand the scope of cowork as you gain trust with it and, and also teach it how to replace you.Felix: Yeah. It's like a little bit like playing factorial, but for your own life. Uh, like you say, you start really small.swyx: Yeah.Felix: You start automating something really tiny and like.Once it clicks, you keep adding onto this like automation empire. Just like make your life easier and easier. My favorite skill has been, um, every single morning Kohlberg starts looking at my calendar and make sure that there's conflicts because people tend to schedule a lot of meetings, sometimes last minute, sometimes miss it soft and painful.And a lot of products have existed like that A lot. I've written in the custom prompt there. I haven't made it a skill, um, honestly should.swyx: Yeah.Felix: But I've given it like pretty clear instructions about okay, here are some people, if they book over other meetings, I'm probably gonna go to their meeting. Like if Dario schedules a meeting.swyx: Right.Felix: Not try to reschedule down. Right. Um, and I think there's some other rules in there about like what kind of meetings I care more about what kind of meetings I care less about. What is okay to like, maybe pun like when I want to be, when I want to be working, when I don't want to be working. And it's those really small things that I can think kind of click with people.Right. When we launch co-work, I think one of the US races that went most viral on Twitter. X was clean up your desktop, which is stuff, because silly, that's such a smart thing, right? Like you don't need to model to clean up your desktop. Not really. Um,swyx: like this, like clean up my desktop.Felix: Yeah, exactly. Yeah.swyx: I need to, I need to choose my desktop, right? I guess give it access to my desktop.Felix: Yeah.swyx: Okay. Uh, okay. This is very scary. Oh, we'll do it.Alessio: I did, I did it with my downloads folder. It was like, you have so many term sheets and there's like eight copies of your rental lease for your office. I was like, all right.Like, don't yell at me.Felix: It's like, it's not such a small task. And then like, I, I would never go out there and normally otherwise and tell people I've pulled a product. It can organize your folder. Right. Um, because it feels small. But I think to your point like,swyx: oh, here's, here's the, here's the ask user questions.Felix: Yeah.swyx: Uh,Felix: beautiful. Right. Elite obvious junk. You probably shouldn't click that.Alessio: No.Felix: If he's not done right.swyx: As long as it's reversible, I don'tAlessio: make up blend to,swyx: yeah. Uh, yeah. No, I, I have a, I have a typical, everything is super messy folder. So, yes. I think this, this is super helpful. So this is a pretty simple task.Mm-hmm. But I've, okay, here it is. Right. Here's the progress. I don't see this in, that's why I'm like, this gotta be something different than, uh, than Claude Code, because I'm like, weFelix: do. Yeah. That's, we do system prompt that. We're like, all right. We want you to think about like, this task Yeah. Methodology.Yeah.swyx: And then I can, I can, I can do like little suggestions for, for, for these things. It's beautiful. Look at this. I, I can, I can like say like, oh, don't do that. Don't do this. It's amazing.Felix: I'm so happy. You like it. Um, I mean, the other way around, like we're part of the Clark core team, if you would like this in Clark COVID.swyx: Yeah. Yeah. Yeah. Uh, so, so yeah, I mean, uh, this is really good. Obviously I, I'm like kind of raving about it. Uh, you know, I have other things like sign up for pg e so if you can do phone calls for me, that'd be great. Um, I, I do, peopleFelix: have done that. Obviously you can't do that natively, but people have done that with like, various other providers.swyx: Yeah. Uh, and then this is like signing up for the Figma MCP. Um, I, I really am trying to do like everything, um, data analysis as well. I do think, um, oh, design to code, uh, very, very good. Right? So like, here's a Figma file, take it. And then this is where like a lot of other tasks is like knowledge work, like replace my manual clicking, but this is no, I would normally use Claude Code or uh, Claude Code for this, but because I perceive that you have better Chrome integrationFelix: mm-hmm.swyx: I, I think you can actually do a better job of this. And I, this, this is one shot at my, uh, conference website.Felix: That's pretty cool. Like at some point I would love to like, hear how you feel about code. In the desktop apps, which is like I never use, which is the, the same team. Same team.swyx: So I use the call code in terminal, which I, I perceive to be the default way of cloud coding.Felix: So one thing this has,swyx: sorry, I'm just like, I'm notFelix: here, I'm not here. All products. Can I talk about other stuff? Like I, I'm not sure if people out there wanna like hear me advertise my stuff for like an hour. Please do that. Um, this thing is like a builtin browser, which is a thing a lot of products have said.Yeah, it's a builtin browser. And I think giving cloud eyes into like what you're actually working on makes it so much more effective. And that's probably what you've seen in cohort because it can see Chrome, it can like debug the dom, it can like see things. Um, that does make it more powerful.swyx: Yeah. So, so I think, uh, my mental model was kind broken.‘cause I only use this cowork because I thought it had a, a browser thing in it. But I understand that the Claude Code app. The app version of Claude Code does have a built-in browser. I've seen, I've seen this preview thing.Felix: Yeah.swyx: I just, I've never used it.Felix: But in the end, in the end, you sort of have it by hard.Yeah. You basically get the same thing. Right? Like the, the, the additional skill that you're describing is chart is better if we can see what it's working on. Right. That's, that's sort of like the summary here and like whether it's using your Chromeswyx: Yeah.Felix: Or it's just like making up its own little like browser.It doesn't really make a big difference because either way it's gonna see what it's working on and that just makes it much better. And then you don't have to run QA for your cloud.swyx: Why doesn't it pick up my existing Claude Code sessions? ‘cause I, I mean, obviously I've used Claude Code, but Excellent question.Um, don't have a good answer other than like, we're honest. Just haven't Yeah. This is what the Open AI team does. Okay. Uh, cool. I I I don't have other, like, I, I just, I, I do wanna expand people's minds and also maybe show people if they haven't really done it, but like, I, I think it's very interesting how I sometimes use this more than I use, I mean, I use dia, right?Yeah. Um, I, and I use, uh, I've used like all the other agentic browsers and philanthropic didn't have to build an agentic browser because you just had Claude Cowork and that's enough.Felix: Yeah. I also think like maybe integrating with number of excellent browsers out there, it's like currently on my personal priority list, a little higher than like trying to rebuild a browser from scratch.Yeah. You know, never say never, but I think going back to this idea of like, we wanna plug this into an entire existing workflow, I think our goal is actually to not replace any of the applications we have in your computer. But instead of like, work really well within a new workflow,Alessio: make the new one. Yeah.Are, it seems that nowadays, especially on the browser, most of the innovation is like user ergonomics. It's not really like the underlying browser engine. So I feel like to call it, it doesn't really matter if it's like the, uh, or Chrome or Alice, whatever.Felix: Yeah. We wanna, we wanna meet you wherever you are.Which is like, like obviously I would say that, but it's also just generally true because I don't wanna shrink my potential user base artificially by saying, okay, like, I'm gonna start building for the people who are willing to switch browsers.Alessio: Right.Felix: That's such a, like, you know, like many lawsuits have been filed over who gets to review the browser and like a lot of money has switched hands over the question of like, which browser is default and which search engine is default within the browser.Um, I just wanna build for, yeah, I wanna build for swyx essentially. Like, I wanna, I wanna, I wanna build for people who have a number of annoying tasks that they feel like. Maybe clock could do it. Could do it for them.Alessio: Yeah. What do you think about skills portability? I think there's been one thing, I use another thing called zo, which is kinda like a cloud computer plus agent.And I have a skill to add visitors to the office. Yeah. So whenever somebody has to come in after hours, they need to check in downstairs. Um, but I wanna like text the thing, so it doesn't really work in, in cowork, but now that skill is in the zone harness and it's not in my cowork thing. And then if I make a change, it's gotta, I gotta sync them.How do you see that going? Like I see memory as like. Cloud personal, kinda like, I don't necessarily want my memories to be cross thing.Felix: Yeah.Alessio: But I do want my skills to be cross agent that I use. I think with MTPs, people do the same thing. It's like, oh, Mt. P Gateway. Mt P registry. I don't really know if that's like a business.So I'm curious like if you've had any thoughts in the area.Felix: I think for me, this is sort of where I go back to the really basic primitives for our skills are file-based instead of like this complicated thing that exists inside a place somewhere that is like super proprietary. I'm really leaning into the idea of like, it's all just files and vultures, and that makes it very portable on its own.Right. We do have skills as part of this container format, which was just called plugins.Alessio: Mm-hmm.Felix: And plugins are available both for Claude Code and Claude Code work the same format, and you can install plugins. This works in cowork today. You can basically say, I'm gonna add a whole, like just a GitHub repo as a.Skills marketplace or like a plugin marketplace. And that's how we're doing portability. I think we have a lot of room left to grow in. How do we make it easy for people to know that they can write skills? How do we make it easy for them to just like, share a skill with you? Because obviously all the words I just said, right?Like I'm losing most of the knowledge worker base out there, right. And start by saying, oh, you can connect to GitHub repo. It's not exactly how most people will end up working in like a general knowledge worker space. Um, but I think there's something there. And another thing that's there that I think has not really been properly explored is the, the, the combination of which part of the skill is very portable and then which part of the skill is like very personal to you.Right. And I think that's something we haven't really solved as an industry. Hmm.swyx: It's like, which, how you wanna introduce more structure to the skill or have always have like. Public skill, private skill, you know, pair. Yeah, yeah. Kind of. I think there'sFelix: like a, like the easiest way to do this, which is we do like use string interpolation or something.Right, right. Yeah, yeah. Insert username here, insert like phone number, insert, like known folder, locations, that kind of stuff. Um, that's probably clunky. That's why we haven't built it. Um, but I do think someone is going to come up with like an interesting way to keep everything we like about skills. The portability is just a file, it's just marked down.It's just text, honestly. Right. Like a text file words. The complete lack of structure, which means you don't need any kind of tutorial to write a skill. Just like explain it to Claude the way he would explain it to me and Claude will probably get it before I work. Mm-hmm. Right? You're just like, for booking a flight, tell Claude how to book a flight the same way we tell him somewhere.I just started working here today. But combine that with a very like, personal thing. Um, maybe we'll stick with a booking a flight example. I don't actually think. AI should be booking flights. I think the tools we have is yes.swyx: Yeah. Finally, somebody says it. It's the default demo that everyone's making.Felix: I'mswyx: like, I even against like booking demos, it is not a good showcase.Felix: Yeah. I'm like, I just wanna book my flight myself. But, um, I think there's a lot of things that have a personal and a non-personal component and that's maybe why people reach for flight booking because some things are very universal. Yeah. Super flight is usually better, right? Like few people try to book the most expensive flight.And then some things are quite personal about like what times you prefer, which seat you prefer, which airports you prefer. Combining that and like a skill format that is actually portable, compatible, easy to understand for people. I think that would be very exciting. We just haven't figured it out yet.Alessio: Yeah, I think the text part every, I think everybody by now has some sort of like cloud file thing. Either Dropbox, Google Drive, whatever. So it feels like in a way it should basically like sim link. My skills into all my agent harnesses. Yeah. Just keep those ing like we have internally this like valuable tokens repo, which is like all the commands sub agents.It's good. Uh, and then I build like a TUI where you can start it and be like, you know, install this command and this three sub agents into this agent in this folder and just copy paste this. It doesn't do anything. It literally cp the file into that. But I feel like there should be something similar where like whenever I go into a new thing, it's like, hey, here's like the link to exactly the cloud folder and just bring down these skills into this.Yeah. Like today it doesn't quite work like that. Like if I install a new agent, I cannot, I have to like copy paste all the skills and I don't even know where they are.Felix: Yeah.Alessio: That's like the big problem. It's like where do I find them?Felix: Yeah.Alessio: Um, so I'm curious like in the future like that, that almost feels like my personal productivity thing will be my skills.Felix: Yeah.Alessio: Is not really the product that I use. Everybody has access to the same product. But today there's, that just looks like copy pasting ME files, IFelix: think so many things I, I really like thinking about agents and LLMs just as like another coworker. So many attempts have made to build documentation companies that are like, oh, we're gonna solve oil documentation problems.Um, I myself, like spend a little bit of time working in notion, right? I'm like deeply familiar with the concept of let's get everyone on the same page. Mm-hmm. Right? And what you're basically saying here is you want all your agents to be on the same page about your preferences, about the skills, about the way they ought to work and like how they ought to execute.And I'm not sure what the right thing is going to be if it's going to be some, some company that can say, all right, we're as an independent body, we're not trying to like, push into any particular product. It's our job to be like the skill authority, and we provide, I don't know, we're gonna be the Dropbox of skills and we can just sim link us into all the products we want to use.I'm not sure that's gonna be viable business, but as, as an idea, it would be cool.Alessio: Yeah. Yeah. I think so many things are just going away as businesses. It's like, how am I supposed to do it? I'm not even asking somebody to make a product about it. Like yeah. I wanna personally know. And there's things like you said, it's like you almost wanna skill and then interpolate it between personal and work.So if I'm booking a fly for work, it's different than I'm booking a flight personally.Felix: Yeah.Alessio: In some ways, yeah. But like a lot of the scaffolding is the same, you know? Cool.Felix: I mean, as an engineer I will tell you like, you know, technic a person to technic a person. I will just be like siblings.Alessio: Well that's what, that's what I do.We call that MD and agents that MD's just the same how sim length. And so it is like, that works, but it feels like, yeah, I don't know. MaybeFelix: you can always go one, you can always tell cowork problem and then cowork will solve it for you. Just make the siblings. That's like one way to do it.Alessio: That's true.That's true. All right. Everything is called cowork.Felix: Uh, potentially spicy. Question for both of you.swyx: Uh, which of these industries will go away?Alessio: Okay, so what Felix was saying before is interesting. There's busy like. The short term pressure of like, we need to turn these tokens into valuable things, which is I should build the last mile product that harness the model.And then there's the question of like, long term, which ones are gonna still be valuable? And I think you're kind of seeing this today with like, uh, you know, the coding space in a way is kind of like everybody's moving up and up in stack because you need more than just turning tokens into code. I think search, like enterprise search is kind of saying the same thing.Like with G Clean and like all these different companies is like, at the end of the day, if Cowork is the one doing all the work, the search itself is like such a small part that like, I don't know if I'm really gonna pay that much money just to do search. It's almost like everything is like a cowork vertical.So like how much can cowork first party support?swyx: Mm-hmm.Alessio: And how much can it not? I think for a lot of these things, the planning thing that you were showing do Which one? The planning. The planning.swyx: Okay. Yeah. Yeah.Alessio: That's one thing where like most of the value that these agents provide is like they're better at planning for specific tasks.Yeah. And have better tools for it.swyx: Yeah.Alessio: But I think the models are now moving in that direction and they have the right harnesses and they're on your computer. So for me it's almost like if for the end customer trusts your startup to be the provider of that task result, then I think that works. This is, uh, something that, this is a shortswyx: spike that we're, we're working on.Uh, yeah.Felix: I think, look, I'll, I'll, I'll tell you this, like I don't think I'm the best person to like actually estimate which industry is going to be hit the hardest. But I do think that at philanthropic as a group of people, we're deeply worried about the impact. That the tools are going to have on the labor market, especially for like junior employees that, because I think, I think it's only honest to say that when we talk about automating a lot away, a lot of the work that we personally find annoying that we maybe think's not the best use of our time.In a lot of industries, that kind of work would've been given to a junior entry level employee. Yeah. Right. And I think it's, it's only, it's only right to be really worried about that and like worry what that's going to do in particular to people like enter the shop market.Alessio: Mm-hmm. I have a solution for that.Which you make them, you create simulative jobs for them.Felix: Okay.Alessio: So this is, this is like half joke, half true. So if you think about software engineering, when you're like a junior engineer, you work like 1, 2, 3 years. And in those three years there's like maybe like a handful of moments where like you really learn something.And then a bunch of other days where like you're not really progressing.Felix: Yeah.Alessio: I think now we can use AI and these models to actually like shortcut these careers and almost like simulate the early years of your work and like just make them like super dense and like these learnings, it's like, hey, we're working on this feature, which is like a distributed system and you need to learn this thing that might take three months at a company.And so you take three months here, it's like we're just simulating the whole thing. It's actually not a real thing. And in one week we kind of speed run through the whole thing and you kind of learn your lesson from there. And we kind of repeat that in like one year. You basically get like three years worth of like projects and experience.Yeah. I think it's harder for like things like sales or for things like, you know, marketing because you don't really have a way to get the feedback loop. But I think a lot of it, it sounds kind of silly, it's like you're making the new effect job, but it's almost like you go to college, right? People pay to learn how to do it, and this might feel similar where it's like, hey, we have the.Jane Street Simulator is like, you wanna come work at Jane Street? We'll just put you in the simulator for like three months.Felix: Wow.Alessio: And you'll come out of it. It's like, you know, I'm ready.Felix: So there, there is an aspect here. I'm not an expert enough to like actually know what, what is going to happen to marketing or legal or finance, right?Like, I don't work in those jobs and I, I don't think I should talk about them, but I am an engineer and I think I have a pretty good idea of what engineering is like. And I think one thing we're sort of seeing is that as a company and also as, as the public, we're like deeply worried about entry level, but we're also seeing more senior engineers accelerate it.If like they're more productive. They, they actually increase the value they provide. And the thing that I'm thinking about a lot is the fact that even before all of this happened, um, I've always had a lot of respect for the University of Waterloo and the, the new grads that have joined my teams as from coming from the University of Waterloo always felt like.More ready than new grads will like literally spend their entire time at the university regardless of how good, but never actually had to work inside an environment where you have to ship things that eventually will be used by users. And I'm, I'm, I'm German. I like initially went to German University and I think the, the, the like information systems programs, there tend to be very theoretical, right?Like I often give people the example of like trying

Regulation starts with you, not your child. In this conversation, I talk with Lisa Candera, single mom of a now-adult son with autism, profound OCD, and anxiety, about what it actually means to "regulate yourself first." Lisa shares how a long stretch of crisis during the pandemic pushed her to the edge and forced her to find ways to stay grounded in the middle of 911 calls, hospitalizations, and daily meltdowns. We unpack what regulation looks like in real life—pausing instead of rushing in, counting a three-out-of-ten success rate as a huge win, and getting honest about the stories that drive our reactions, especially the "I am failing my child" soundtrack. Lisa talks about turning her parked car into a "car office" for safety and space, setting clear boundaries around aggression, and shifting from lecturing in the moment to making a plan when everyone is calmer. We also talk about raising teens with big emotions and neurodivergent brains. Lisa names the pressure parents feel to foster independence, the fear of "enabling," and the reality that a fifteen-year-old with autism may not be developmentally fifteen. Together we explore scaffolding, praising effort and emerging skills, and holding a both-and: your child is struggling, and you deserve support and compassion too. Key Takeaways Regulation starts with you, not your child. Lisa describes regulation as moving from constantly losing your temper to feeling more grounded and able to respond. You don't have to be calm all the time—small shifts in your reactions can dramatically change the dynamic. A three-out-of-ten success rate is already a big deal. Instead of expecting yourself to get it right every time, Lisa suggests aiming for three regulated responses out of ten. Those moments might happen within minutes, and they still count. Pausing interrupts the automatic pattern. The urge to fix or lecture right away is strong. Even a brief pause can interrupt the usual pattern between you and your child and give you space to choose something different. Your triggers are about you, not just your child's behavior. Lisa discovered that many of her reactions were driven by fear and the belief that she was failing her son. Naming those stories helped her respond with more flexibility and compassion. You can change the dance by changing your part. Parents and kids often fall into predictable interaction patterns. When Lisa shifted how she responded—sometimes leaving the apartment instead of engaging—the pattern changed. Boundaries can include creative safety plans. During COVID, Lisa's plan sometimes involved leaving the apartment and sitting in her car when her son became aggressive. She reframed it as a temporary strategy rather than a failure. Thoughts like "this is an emergency" can escalate things. Parents' nervous systems often interpret big emotions as danger. Expanding your tolerance for discomfort can help you respond to what's actually happening. Scaffolding is not the same as enabling. Developmental level and anxiety matter. Sometimes making a task easier is what allows progress in other areas. Notice and name what your child does well. Highlighting everyday successes helps children internalize the belief that they can do hard things. You are not the baseline for how everyone else should be. Letting go of "I am the standard" creates more room for difference and helps you relate to your child as the person they are. About Lisa Candera Lisa Candera is a single mom of a teen with severe autism and OCD, an attorney, ADHD-er, and the autism mom coach behind The Autism Mom Coach. She helps parents of autistic children learn to regulate themselves first so they can show up for their kids with more calm, compassion, and confidence. Lisa hosts The Autism Mom Podcast, contributes to Autism Parenting Magazine, and presents on parental self-care, emotional regulation, and meltdown de-escalation strategies. About Your Host, Gabriele Nicolet I'm Gabriele Nicolet, toddler whisperer, speech therapist, parenting life coach, and host of Complicated Kids. Each week, I share practical, relationship-based strategies for raising kids with big feelings, big needs, and beautifully different brains. My goal is to help families move from surviving to thriving by building connection, confidence, and clarity at home. Complicated Kids Resources and Links

Struggling with social skills practice that actually feels natural? This week on the podcast, we're diving deep into practical, respectful ways to support our neurodivergent kiddos as they navigate friendships and social situations—without the cringe! From conversation entry points (aka scripts that don't turn our kids into social robots!) to playful, low-stakes role-playing at home, Colleen shares hands-on strategies to boost confidence and make socializing just a little easier for everyone involved. If "Just be yourself!" doesn't cut it in your house, you're not alone. Listen to this episode and help your kids build real-world connections, one conversation at a time. Key Takeaways: Scripts as Scaffolding, Not Life Sentences: Social scripts aren't rigid lines for kids to memorize forever. Instead, they serve as supportive "training wheels" to help neurodivergent kids enter, maintain, and exit conversations more naturally—reducing anxiety and offering footholds toward authentic communication. Practice Through Playful, Low-Stakes Moments: Avoid pressuring your child with public corrections or high-stakes rehearsal before social events. Instead, incorporate side-by-side role play, movie-pause coaching, and micro-practicing to gently build and reinforce social skills without making kids feel evaluated. Measure Progress by Initiative, Not Perfection: Success isn't about perfect eye contact or flawless conversation. Celebrate when your child initiates conversations, adapts their scripts into their own words, or asks to socialize again. These signs mean scripts are becoming real-world skills! Parenting and homeschooling neurodivergent kids is tough—but you're already doing amazing work just by showing up, learning, and supporting your child's unique journey. Links and Resources from Today's Episode Thank you to our sponsors: CTC Math – Flexible, affordable math for the whole family! Curiosity Post – A Snail Mail Club for kids – Real mail; Real life! The Learner's Lab – Online community for families homeschooling gifted/2e & neurodivergent kiddos! The Lab: An Online Community for Families Homeschooling Neurodivergent Kiddos The Homeschool Advantage: A Child-Focused Approach to Raising Lifelong Learners Raising Resilient Sons: A Boy Mom's Guide to Building a Strong, Confident, and Emotionally Intelligent Family The Anxiety Toolkit Sensory Strategy Toolkit | Quick Regulation Activities for Home Affirmation Cards for Anxious Kids Nurturing Neurodivergent Friendships: Practical Tips for Parents and Kids RLL #42: What It's Like to be Homeschooled with Best Friends Molly and Ella Teaching Kids About Being a Good Friend with Help From Great Books and Netflix Teaching Kids to Befriend Others 5 Tips for Helping Gifted Children Make Friends Navigating Sensory Overload: Actionable Strategies for Kids in Loud Environments The Not-So Friendly Friend: How to Set Boundaries for Healthy Friendships Social Skills Activities for Kids Growing Friendships: A Kids' Guide to Making and Keeping Friends Have You Filled a Bucket Today?: A Guide to Daily Happiness for Kids One Big Heart: A Celebration of Being More Alike than Different Life Skills for Kids: Unlocking a World of Possibilities through Friendship, Decision-Making, Cooking, Achieving a Success Mindset, Time-Management, Budgeting, and More  Empathy Workbook for Kids: 50 Activities to Learn About Kindness, Compassion, and Other People's Feelings  

On today's poddy, who's your throat goat? Follow The Big Show on Instagram Subscribe to the podcast now on iHeartRadio, YouTube, or wherever you get your podcasts!Featuring Jason Hoyte, Mike Minogue, and Keyzie, "The Big Show" drive you home weekdays from 4pm on Radio Hauraki.Providing a hilarious escape from reality for those ‘backbone’ New Zealanders with plenty of laughs and out-the-gate yarns.Download the full podcast here:iHeartRadioAppleSpotify Follow The Big Show on InstagramSee omnystudio.com/listener for privacy information.

In this third installment of Claude Sessions, Danny is joined by Subash from Not A Square, who helps e-commerce brands scaling past seven figures implement AI without scaling headcount. Subash walks through real client case studies -- including a TikTok brand that boosted its customer satisfaction score from 4.2 to 4.5 in four weeks using a customer support agent built in Claude. Danny then breaks down OpenClaw, the open-source personal AI agent that exploded in popularity, explains why he chose not to use it despite the temptation, and reveals Claude Flow -- his custom operating system built inside Claude Code with 11 engines, 300+ features, and a persistent memory layer powered by ChromaDB. The episode drives home one core message: document your operations first, pick one platform, go deep, and stop chasing every new tool. Key Topics Documenting operations before automation -- Why you cannot automate what is not documented TikTok customer support case study -- Building an AI agent that raised satisfaction scores in four weeks OpenClaw overview and security risks -- What it does, why it blew up, and why Danny built his own alternative Claude Flow -- Danny's custom operating system inside Claude Code with persistent memory The amnesia loop -- How context loss between sessions kills productivity and how ChromaDB solves it Pixel-less environment -- The shift from structured prompts to contextual AI interaction Go deep on one platform -- Why chasing multiple AI tools guarantees you build nothing Timestamps [00:00] Introduction -- Claude Sessions Week 3, delayed from the road [01:03] Subash introduces himself and Not A Square [02:01] Overview of three client projects and the problem founders face [04:30] Why operational truth is the moat in AI commerce [06:48] Three pillars: reduce costs, better governance, scale without headcount [07:30] TikTok case study -- customer support agent boosting store score from 4.2 to 4.5 [09:04] OpenClaw -- history, capabilities, and the security nightmare [15:30] Six core capabilities of OpenClaw (local-first, universal messaging, persistent memory, browser automation, system access, self-extending skills) [18:00] Why OpenClaw matters -- moving from dumb LLMs to personal AI agents [20:00] Security trade-offs -- 1.5M API keys exposed, malware in skills, Cisco tests [22:00] Claude Flow -- Danny's 11-engine operating system built inside Claude Code [24:26] The amnesia loop -- how sessions lose context and how ChromaDB fixes it [28:19] Why Claude MD, agents, and skills are not enough without hooks and triggers [32:40] Go deep on one platform -- stop chasing every new tool [35:35] Subash on helping sellers adopt Claude Code fundamentals (Claude MD, skills) [39:51] Wrap-up and contact info Key Takeaways Document before you automate -- If your business operations live in the founder's head and not on paper, any AI tool will amplify the chaos rather than fix it. Operational truth is the moat -- Clean inventory, accurate catalogs, honest cashflow reporting. Get these right before touching AI. One AI agent moved the needle -- A single customer support agent on TikTok raised a brand's satisfaction score from 4.2 to 4.5 in four weeks, directly improving store visibility. Persistent memory changes everything -- ChromaDB captures decisions, patterns, and project context across sessions so Claude compounds in usefulness over time (zero entries in session one, 1,700+ by session 25). Scaffolding beats raw building -- Danny's Claude Flow system means a project that took five days six months ago now takes 40 minutes. The investment in infrastructure pays exponential returns. OpenClaw is proof of concept, not production-ready -- Broad permissions, prompt injection vulnerabilities, exposed API keys. Wait for the open-source community to patch the holes before diving in. Pick one platform and go all the way in -- Chasing multiple AI tools means you learn none of them deeply and build nothing of value.

What do Gustav Eiffel and dynamic, tactile, temporal cueing have in common? Scaffolding, vision, and the courage to aim higher than anyone else. In this episode, I break down why Dynamic, Tactile, Temporal Cueing (DTTC) is not just for childhood apraxia of speech. It is a practical, high-impact framework that can upgrade how you treat: • Speech sound disorders • Language delays • Literacy skills • Fluency • AAC users • Autism and complex communication needs If you want maximal gains in minimal time, this episode is your blueprint. After standing beneath the Eiffel Tower and speaking at a packed state conference, one message hit me hard: the higher you aim, the bigger the cascade. When you treat at a complex level with the right scaffolds, earlier developing skills often come along for the ride. Inside this episode, we unpack: • Why fewer targets with higher reps build automaticity faster • How simultaneous production jump starts planning and reduces breakdowns • Why slowing time increases accuracy across speech, language, fluency, and AAC navigation • How to use most to least prompting without letting the tower fall • Why errorless learning and the 80 percent sweet spot matter • How multimodal cueing accelerates learning for every child • Why you build automaticity first and generalize later This is not business-as-usual therapy. This is challenge point therapy. This is how you stop grinding and start seeing real progress. Join SIS and get the complex targets done for you If you want powerful complex speech and language targets ready to pull into sessions immediately, join SIS Membership today. You will get access to high impact therapy materials designed to help you scaffold fast progress across speech, language, literacy, and AAC, without reinventing the wheel every week. Join here and get started today: https://www.kellyvess.com/sis Roll up your sleeves. Make the world better, one child at a time. With you in this,

How do experienced operators approach the most technically demanding aspects of Distal Venous Arterialization (DVA)? In this episode of BackTable, host Dr. Sabeen Dhand sits down with Dr. Kumar Madassery for a detailed discussion of procedural strategy, technical decision-making, and real-world troubleshooting in DVA. --- SYNPOSIS Dr. Madassery walks through his approach from pre-procedure planning to final scaffolding. The conversation begins with imaging review, patient selection, and anesthesia considerations, emphasizing how preparation influences technical success. They then examine venous mapping and access strategy, with specific attention to femoral and tibial disease patterns and how these anatomic variables shape crossing techniques.This episode also covers wire and catheter selection, techniques for creating the arteriovenous anastomosis, balloon sizing, valve management, and stent scaffolding. Throughout, Dr. Madassery shares practical solutions to common access challenges and highlights decision points that can determine procedural durability. The discussion closes with reflections on clinical management, operator fatigue, and the value of professional networks when navigating complex limb salvage cases. --- TIMESTAMPS 00:00 - Introduction03:08 - Pre-Procedure Imaging and Setup05:01 - Venous Access and Mapping07:27 - Anesthesia and Patient Preparation12:29 - Femoral and Tibial Disease Considerations23:17 - Crossing Techniques and Tools27:16 - Venous Access Challenges and Solutions35:54 - Creating the Anastomosis37:03 - Balloon Sizing and Scaffolding Techniques38:26 - Navigating Venous Access Challenges39:56 - Wire and Catheter Strategies42:08 - Dealing with Valves and Anastomosis44:16 - Proximal vs. Distal DVA Approaches47:01 - Scaffolding and Stent Techniques50:06 - Clinical Management and Case Fatigue01:01:10 - Networking and Seeking Advice01:05:41 - Concluding Thoughts and Future Directions

On this episode of Mind the Gap, Tom Sherrington and Emma Turner are joined by Alex Fairlamb and Rachel Ball, co-authors of The Scaffolding Effect, to explore what scaffolding really is (and isn't) and why it has become such a pivotal idea in the move from “differentiation” to adaptive teaching. They discuss the research roots of the term, the practical reality of “knowing–doing,” and the central challenge that scaffolds must be temporary - designed to be removed through gradual release and guided by sharp checks for understanding. The conversation digs into common pitfalls (from “impermeable skins” of apparent progress to students becoming dependent on writing frames), debates the role of formulaic writing structures, and shows how scaffolding looks different across subjects and phases, including strategies involving reading, writing, retrieval practice, explanations, practical subjects, even homework. Packed with concrete examples and implementation-minded advice, this is a highly usable episode for teachers and leaders who want to support pupils towards real independence.Alex Fairlamb is a Trust T&L Network Lead and Senior Leader in charge of Teaching and Learning and CPD, based in the North East. She is a Chartered Teacher of History, a Specialist Leader in Education and an Evidence Lead in Education. Alex is a proud member of the Historical Association Secondary Committee and the Schools North East Steering Board. Alex is a History teacher and former Lead Practitioner of History and Teaching and Learning, with a strong commitment to ensuring that curriculums are diverse. She is an author and textbook writer, and recently completed her PhD focusing on Equality and Equity within education. Check out her website at https://alexfairlamb.com/Rachel Ball is Professional Development Specialist at Steplab. She is a former Assistant Principal in charge of teaching and learning and CPD, and passionate history teacher with 22 years experience. She is also a Fellow of the Chartered College of Teachers and an international speaker at schools and conferences including ResearchEd National Conference. Rachel is co-editor of What is History Teaching, Now? (2023) and co-author of The Scaffolding Effect (2025). Find Rachel's blog at theeducationalimposters.wordpress.comTom Sherrington has worked in schools as a teacher and leader for 30 years and is now a consultant specialising in teacher development and curriculum & assessment planning. He regularly contributes to conferences and CPD sessions locally and nationally and is busy working in schools and colleges across the UK and around the world. Follow Tom on X ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠@teacherhead⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Emma Turner FCCT is a school improvement advisor, education consultant, trainer and author. She has almost three decades of primary teaching, headship and leadership experience across the sector, working and leading in both MATs and LAs. She works nationally and internationally on school improvement including at single school level and at scale. She has a particular interest in research informed practice in the primary phase, early career development, and CPD design. Follow Emma on X ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠@emma_turner75⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠This podcast is sponsored by Teaching WalkThrus and produced in association with Haringey Education Partnership. Find out more at ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://walkthrus.co.uk/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ and ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://haringeyeducationpartnership.co.uk/⁠

In this episode of RattlerGator Report, JB White opens with the cultural fallout from the Super Bowl halftime show, breaking down the ratings collapse, media backlash, and what he sees as a widening disconnect between institutional messaging and the American public. He examines the reaction cycle, the outrage economy, and why legacy platforms continue to miscalculate cultural momentum. The conversation then expands into global finance and geopolitical positioning, including IMF leverage, Treasury maneuvering, tariff strategy, tech infrastructure, and what JB frames as a long-built strategic “scaffolding” taking shape. He connects Bitcoin volatility, UK censorship developments, and shifting power centers into a broader narrative of structural realignment, arguing that recent moves across finance, media, and governance point to coordinated counterpressure against entrenched global systems.

Temple Dedication  Alabang Philippines Temple – #213 January 18, 2026 – presided by David Bednar (Husband of Susan) The dress stole the show Dedicatory Prayer 15 Stakes and 1 District assigned to temple district Second Manila Metro Area Temple, a third is planned in Northern Manila 4th temple of 14 temples planned in the Philippines Second to last temple announced by President Monson dedicated (last is below) Temple Open House Begins Harare Zimbabwe Temple Temple Media day on January 19th  President of Zimbabwe tours the temple Open House Through February 7th  Interior Photos Released Design features: the flame lily, aloe ballii, Yoruba bologi, African lettuce, terracotta gazania, aspilia mossambicensis and wentzel's sugarbush. Temple Groundbreakings  João Pessoa Brazil Temple January 24th, presided by Joni L. Koch  Jacksonville Florida Temple January 24th, presided by Massimo De Feo Temple Site Locations Announced Kahului Arizona Temple 7.6 acre site: Maui Lani Parkway, Kahului, Hawaii Next to existing meetinghouse Single Story, 19,000 sq. ft. building Renovations continue in Kona, No site announced in Honolulu.  Flagstaff Arizona Temple 10.43 Acre Site: southwest corner of Butler Ave. and South Fourth St., in Flagstaff Single Story, 18,850 sq. ft. building Puerto Montt Chile Temple 5.8 Acre Site: Avenida Chamiza, in eastern Puerto Montt Single Story, 18,500 sq. ft. building Construction Update Tarawa Kiribati Temple Modules installed on foundation  Heber Valley Utah Temple Utah Supreme Court will allow temple construction to continue  Church is assuming the risk of tearing down progress if they lose an appeal Plaintiff failed to prove irreparable harm, only inconvenience Salt Lake Temple Removal of scaffolding begins and will continue until mid-March Featured video from the B1M engineering youtube channel Original Moroni Trumpet on display at BYU HBLL Communications director gives a lecture at BYU Proposal to close North Temple and West Temple and parts of South Temple to vehicles adjacent to the temple during the extent of the open house Reportably, the church would need to pay $2.3M to lease the roads. Interesting Does temple construction boost property values? No discernable effect… The post Behind all that Scaffolding is…. Temple Ticker 1014 appeared first on The Cultural Hall Podcast.

Mary-Ellen Fimbel on Game Design Principles for EducationThis episode of Experience Points features game designer and educator Mary-Ellen Fimbel, who shares how game design principles can transform classroom learning. She discusses “teaching like a game dev,” using storytelling, interactivity, and even puppets as playful avatars to deliver authentic feedback and spark curiosity. Mary-Ellen explains how honoring student questions, modeling inquiry, and scaffolding problem-solving builds confidence and creativity. She also explores project-based learning through student-created games and her classroom approach to metacognitive self-assessment. Educators, designers, and anyone interested in games-based learning will find practical strategies to make learning more engaging, dynamic, and meaningful.If you liked this episode please consider commenting, sharing, and subscribing.Subscribing is absolutely free and ensures that you'll get the next episode of Experience Points delivered directly to you.I'd also love it if you took some time to rate the show!I live to lift others with learning.  So, if you found this episode useful, consider sharing it with someone who could benefit.Also make sure to visit University XP online at www.universityxp.comUniversity XP is also on Twitter @University_XP and on Facebook and LinkedIn as University XPAlso, feel free to email me anytime at dave@universityxp.comGame on!Get the full transcript and references for this episode here: https://www.universityxp.com/podcast/157Support the show

Deacon Dave and Layperson Lisa discuss the progress of their new building's scaffolding and draw parallels between building scaffolding and growing spiritually (0:00-0:35). They highlight that both require hard work, multiple components, and community (0:41-3:08).Here are the key takeaways from their discussion:Spiritual Growth as Scaffolding (0:49-1:21): Just as scaffolding needs many pieces (metal, wood) to build higher, spiritual life requires various elements like virtues, different forms of prayer (Mass, silence, Divine Mercy Chaplet, rosaries), and continuous effort to "go higher."Hard Work in Virtue (1:54-2:34): They emphasize that spiritual growth is hard work. Using St. Francis de Sales as an example, who took 12 years to overcome anger and cultivate meekness, they illustrate that God provides opportunities for growth, which often involve significant effort.Importance of Community (2:34-3:08): The hosts stress that community is crucial for progress. They note that the scaffolding work went much faster when more people were helping, likening it to spiritual life where community support can accelerate growth and prevent isolation.Faith and Trust in God (5:11-6:26): They discuss how growing in virtue and holiness strengthens faith and dependency on God, which helps in calming life's storms. Lisa mentions St. Thérèse and her confidence in God through faith, hope, and love, emphasizing that God wants us to rise from mistakes with His help rather than self-condemn.Avoiding Self-Criticism (6:28-7:15): They advise against beating oneself up over mistakes, identifying it as a form of pride that shifts focus away from God. Instead, they encourage learning from errors and allowing God to use those experiences for positive change.

In this episode, we dive deep into the evolving relationship between human creativity and artificial intelligence. Inspired by Ada Lovelace's early vision of creative machines, we explore how the boundaries between expertise and common sense have been reshaped by modern AI, from expert systems to today's generative models. We sit down with pioneers and practitioners—Vasant Dhar, a longtime AI researcher and author of Thinking With Machines; Christopher Mims, technology journalist and author of How To AI; and the creators of Tachi AI, Aden Bahadori and Brett Granstaff—to discover how AI is shifting not only what we make but how we make it.We unpack the promise and the pitfalls of treating AI as a true thinking partner, not just a tool for automation. Our guests share practical strategies for using AI to augment creative work, streamline tedious tasks, and enhance idea generation—while emphasizing the necessity of human framing, expertise, and judgment. Whether you're a leader, designer, marketer, or filmmaker, we reveal why using AI thoughtfully is the real competitive edge in creative fields and business.Five Key Learnings:AI's Compounding Edge: Utilizing AI consistently and benchmarking progress gives creatives and teams a multiplying advantage—not by replacing human originality, but by amplifying it through incremental improvements.Framing Questions Matter: The ability to ask the right, nuanced questions remains fundamentally human, and is essential when using AI as a partner in ideation, research, and strategy.Context and Expertise Are Critical: Experts benefit most from AI—leveraging their knowledge to dig deeper, validate outputs, and push beyond generic solutions, while ensuring originality in their work.AI as Scaffolding, Not a Substitute: The greatest value of AI today is in reducing friction and clearing time for creativity—whether it's summarizing information, managing knowledge, or prepping film edits—so humans can focus on what matters.Human-Centric, Supportive AI: Tools like Tachi AI demonstrate that supporting creativity is more transformative than automating it; AI as infrastructure enables faster iteration and more creative decision-making, not just higher productivity.Get full interviews and bonus content for free! Just join the list at DailyCreativePlus.com.Mentioned in this episode:To listen to the full interviews from today's episode, as well as receive bonus content and deep dive insights from the episode, visit DailyCreativePlus.com and join Daily Creative+.The Brave Habit is available nowMy new book will help you make bravery a habit in your life, your leadership, and your work. Discover how to develop the two qualities that lead to brave action: Optimistic Vision and Agency. Buy The Brave Habit wherever books are sold, or learn more at TheBraveHabit.com.

If you rely on complex scaffolding to build AI agents you aren't scaling you are coping. Thibault Sottiaux from OpenAI's Codex team joins us to explain why they are ruthlessly removing the harness to solve for true agentic autonomy. We discuss the bitter lesson of vertical integration, why scalable primitives beat clever tricks, and how the rise of the super bus factor is reshaping engineering careers.LinearB: Measure the impact of GitHub Copilot and CursorFollow the show:Subscribe to our Substack Follow us on LinkedInSubscribe to our YouTube ChannelLeave us a ReviewFollow the hosts:Follow AndrewFollow BenFollow DanFollow today's guest:OpenAI Codex: Learn more about the models powering tools like GitHub Copilot.Codex Open Source Repo: The lightweight coding agent that runs in your terminal (check out the Rust migration mentioned in the episode).Agent Skills Open Standard: The open standard and catalog for giving agents new capabilities.The Bitter Lesson: Richard Sutton's essay on why compute-centric methods win in AI.Follow Tibo on X @thsottiaux | GitHubOFFERS Start Free Trial: Get started with LinearB's AI productivity platform for free. Book a Demo: Learn how you can ship faster, improve DevEx, and lead with confidence in the AI era. LEARN ABOUT LINEARB AI Code Reviews: Automate reviews to catch bugs, security risks, and performance issues before they hit production. AI & Productivity Insights: Go beyond DORA with AI-powered recommendations and dashboards to measure and improve performance. AI-Powered Workflow Automations: Use AI-generated PR descriptions, smart routing, and other automations to reduce developer toil. MCP Server: Interact with your engineering data using natural language to build custom reports and get answers on the fly.

Grandp Bill Focus: The 12th House "Bridge" & The 11th House "Scaffolding"The Theme: The Invisible Work. This is the house of the subconscious, secrets, and spiritual closure.The Pluto Factor: Pluto is now a permanent resident here. For you, this means a deep "soul-cleanse." You are letting go of old identities and "karmic loops" from the last 15 years.Interview Insight: Ask Tam about the "Quiet Before the Storm." In the Almanac, how does she recommend we handle the exhaustion that often comes when the 12th House is this active?Keywords: Closure, Intuition, Sanctuary, Restoration, Subconscious.The Theme: The Tribe & The Blueprint. This house rules your social circles, fans, and long-term "Hopes and Wishes."The Action: While the 12th house is dreaming, the 11th house (Capricorn) is demanding structure.The Jan 9 Peak: The Sun meets Mars here. This is your "Business of Being Pisces" moment. It's about finding the right people to help launch your 2026 vision.Keywords: Alliances, Networking, Long-term Goals, Community, Scaffolding.The Tension: You may feel pulled between wanting to go into a "Pisces Cave" (12th House) and needing to show up for your community (11th House).The Goal: Use the first 15 days of January to finalize the "who" (11th House) so you can spend February focusing on the "why" (12th House).Janet's Note: Since Janet generated your chart, remind Tam that your "Social House" (11th) is currently the anchor keeping your "Spiritual House" (12th) from drifting off into space.Jan 9: Sun/Mars Conjunction (The "Green Light" for your 11th House community projects).Jan 18: New Moon in Capricorn (A reset for your long-term dreams).Jan 26: Neptune (Your ruler) enters Aries (A massive shift in how you value yourself).1. The 12th House (Aquarius Stellium: Jan 4–11)2. The 11th House (Capricorn Conjunction: Jan 1–15)3. The "Bridge" Dynamics (Now through March)

You still using AI to..... write emails?

In episode 551 of 'Coffee with Butterscotch,' the brothers talk about why flailing is not a failure mode, it's the strategy. They unpack how progress in game development, marketing, and life often comes from trying lots of things without knowing which will work, then slowing down as signals start to appear. It's a look at uncertainty, experimentation, and why nobody really knows the answer, but everyone figures out a small piece by doing.Support How Many Dudes!Official Website: https://www.bscotch.net/games/how-many-dudesTrailer Teaser: https://www.youtube.com/watch?v=IgQM1SceEpISteam Wishlist: https://store.steampowered.com/app/3934270/How_Many_Dudes00:00 Cold Open00:25 Introduction and Welcome02:41 Navigating YouTube and Game Development Insights05:40 The Indie Game Developer Experience08:43 Flailing Towards Success: The Random Walk11:43 Exploring New Strategies and Marketing Approaches14:37 The Importance of Experimentation in Game Development17:43 R&D and the Value of Unpredictability20:40 Closing Thoughts on Research and Development21:38 The ROI of Science in Game Development22:17 Designing Game Mechanics: Chaos vs. Structure23:36 Iterative Design: Balancing Planning and Flexibility24:55 Class Systems and Game Evolution27:28 High-Level Planning vs. Low-Level Details30:18 Scaffolding for Game Development34:38 The Challenge of Crafting Systems36:33 Navigating Constraints in Game Design40:13 The Importance of User Feedback42:41 The Role of Humor in Game DevelopmentTo stay up to date with all of our buttery goodness subscribe to the podcast on Apple podcasts (apple.co/1LxNEnk) or wherever you get your audio goodness. If you want to get more involved in the Butterscotch community, hop into our DISCORD server at discord.gg/bscotch and say hello! Submit questions at https://www.bscotch.net/podcast, disclose all of your secrets to podcast@bscotch.net, and send letters, gifts, and tasty treats to https://bit.ly/bscotchmailbox. Finally, if you'd like to support the show and buy some coffee FOR Butterscotch, head over to https://moneygrab.bscotch.net. ★ Support this podcast ★

Lords: * Hallie * Peter * https://www.paschaefer.com/ Topics: * Do you know where all your things are? * How education doesn't melt * Bebop Bytes Back * Augustus Gloop by Roald Dahl * https://allpoetry.com/-Augustus-Gloop...- Microtopics: * The Directrix of Cybernetic Security. * Unity licensing from Unity as Unity. * Fantasy Book of the Month. (FBOM) * Part zombie, part ghost. * Accidentally GenMoing your WriMo. * A house with a bunch of your things in it, and they're everywhere. * Knowing someone who knows how to find things and knowing someone who knows where things are. * Knowing where to put something because it's where you first thought to look for it. * A person who itches when they see somebody not using a switch statement. * Having been gradually removing yourself from social media since back when Twitter was Twitter. * Back when you could get out of a chair without grunting. * Getting the whooping cough and coughing your disc out. (And you're in your twenties.) * Whether your dad named you after the murderous robot in 2001. * Seeing your students cheating poorly and teaching them how to do it well. * Scaffolding it pedagogically. * Big boat: hard turn. * How do we get education to exhibit swarm behavior? * A brand new exciting way to be bummed. * Education by Panopticon. * LLMs exposing how much of people's jobs and education are bullshit busywork. * When does the salt jump? * Putting together the 50s and then putting together the tens and then putting together the fours. * The simplest shallowest version of active listening that exists. * Doritos hacking the learning loop. * Continually finding new opiates of the masses. * Typing hex opcodes into the Beboputer. * An effective educational tool that has never been less appealing to the youth it's targeted at. * Steve Jobs coming out of his grave and slitting your throat if you install a programming tool on your iPhone. * Making the sun wink and realizing that this is the rest of your life. * Deescalating your LLM partner when it has an anxiety attack. * Your Socratic Oxford Don persona. * The Life Cycle of Software Objects. * There is a mistake, and it is being overcome. * Steps you can take to avoid Godzilla coming back and nature reclaiming the earth. * A poem written by a beloved children's author who absolutely loathes fat people. * Whether the terrible children in Charlie and the Chocolate Factory are all based on people that Roald Dahl knew. * SwitchBitch, Roald Dahl's famous Typescript library. * Making sure your weirdness is a kindness. * Roald Dahl: boy did he do the stuff. * Penning The Twits in an effort to "do something against beards." * Why Stephen King? * The Dollar Babies. * Whether Stephen King is still on MySpace. * Walking down the road and hearing Stephen King yelling at cloud. * The Dave Barry game jam. * Going into the sewer and solving puzzle platformer problems. * Group hug vs. forming a blob. * Tube Hippo is back! * The game engine sorting hat. * Coming out of character to talk about Inform 7. * The year that you fucked around with interactive fiction but never shipped anything. * Presuming that interactive fiction has continued to be great even after you stopped playing. * Choosing Twine over Inform 7 because of your absolutely enormous forelimbs. * LLMs as an extremely fancy Tarot deck.

In this episode, I speak with Robin Couture-Matte about his work "Task-based Language Teaching and High-immersive Virtual Reality: An Investigation of Children's Use of Scaffolding" 

This episode features Dianne Na Penn, a senior product leader at Anthropic, discussing the launch of Claude Opus 4.5 and the evolution of frontier AI models. The conversation explores how Anthropic approaches model development—balancing ambitious capability roadmaps with user feedback, making strategic bets on areas like agentic coding and computer use while deliberately avoiding others like image generation. Dianne shares insights on the shifting nature of AI evaluation (moving beyond saturated benchmarks like SWE-bench toward more open-ended measures), the evolution of scaffolding from "training wheels" to intelligence amplifiers, and why she believes we're closer to transformative long-running AI than most people think. She also discusses Anthropic's distinctive culture of authenticity, the under appreciated benefits of model alignment for producing independent-thinking AI, and why the real bottleneck to AI agents isn't model capability anymore but product innovation. (0:00) Intro(0:57) Starting the Work on Opus 4.5(2:04) Model Capabilities and Surprises(5:59) Computer Use and Practical Applications(7:21) Pricing and Positioning(10:02) Customer Feedback and Early Access(16:44) The Reality of Enterprise Agents(18:47) Future of AI and Long-Running Intelligence(28:06) Anthropic's Culture and Decision Making(30:31) Key Decisions and Fun Moments(33:45) Quickfire With your co-hosts: @jacobeffron - Partner at Redpoint, Former PM Flatiron Health @patrickachase - Partner at Redpoint, Former ML Engineer LinkedIn @ericabrescia - Former COO Github, Founder Bitnami (acq'd by VMWare) @jordan_segall - Partner at Redpoint

The blaze that engulfed seven high-rise residential buildings in Hong Kong's Tai Po district was the deadliest the city has seen in over 70 years. At least 156 people have died, 30 are still missing, while 15 have been arrested for alleged manslaughter. Grief has overwhelmed the city and fuelled an uncontrollable anger towards those in power.Today - almost a week after the fire - we ask how the tragedy unfolded, why Hong Kong is still enraged and what it tells us about the city that once prided itself on transparency and democracy.Joining Matt Frei from Hong Kong are Tom Grundy, founder and editor of the local media Hong Kong Free Press, and Selina Cheng, chair of the Hong Kong Journalists Association.

Autonomy-Supportive Parenting with Dr. Emily Edlynn, PhD In this episode of the Helping Families Be Happy Podcast, host Christopher Robbins interviews Dr. Emily Edlynn, a licensed clinical psychologist and author of "Autonomy-Supportive Parenting." Dr. Edlynn explains how autonomy-supportive parenting, based on self-determination theory, nurtures three fundamental human needs: autonomy, competence, and relatedness. She discusses how modern parenting culture's intensive approach often leads to controlling behaviors that undermine children's development, and provides practical strategies for parents to foster independence while reducing parental burnout. The conversation covers real- world applications of these principles, including how to help children solve their own problems and develop financial independence. Episode Highlights 00:00:10: Host Christopher Robbins introduces the podcast and guest Dr. Emily Edlynn, highlighting her credentials as a licensed clinical psychologist and author. 00:02:06: Light-hearted exchange about parenting experience with Christopher mentioning he's a father of nine children. 00:02:50: Dr. Edlynn defines autonomy-supportive parenting as a science-based approach that nurtures three fundamental human needs: autonomy, competence, and relatedness. 00:04:07: Discussion of the three core needs, with Christopher seeking clarification on each component. 00:04:40: Dr. Edlynn explains relatedness as the foundational need involving belonging, connection, and feeling understood and accepted. 00:05:14: Connection made to Daniel Pink's book "Drive" and its relationship to motivation theory. 00:06:17: Christopher acknowledges the challenges of parenting, describing it as sometimes being "a grind." 00:06:28: Dr. Edlynn identifies two primary barriers: overwhelming parental stress (declared a public health crisis) and intensive parenting culture. 00:08:10: Discussion of how control is the antithesis of autonomy-supportive parenting. 00:08:33: Dr. Edlynn explains how parents often do too much for their children, preventing skill development and confidence building. 00:09:36: Christopher relates the advice to leadership principles applicable beyond parenting. 00:10:25: Christopher shares his parenting approach of encouraging children to solve problems independently. 00:10:56: Dr. Edlynn validates Christopher's approach based on its effectiveness. 00:11:34: Humorous exchange about background music making parental advice more appealing. 00:11:48: Christopher asks for key autonomy supportive strategies to implement immediately. 00:11:56: Dr. Edlynn provides specific strategies including expecting more independence and expressing trust in children. 00:13:28: Application of strategies to a real scenario involving a child who needs to become more financially self-reliant. 00:13:47: Dr. Edlynn walks through the process of addressing the financial independence issue collaboratively. 00:15:00: Christopher acknowledges learning new parenting approaches after 33 years of experience. 00:15:38: Discussion of how autonomy supportive parenting relates to good leadership principles. 00:16:19: Exploration of short-term and long-term benefits of autonomy-supportive parenting. 00:16:35: Dr. Edlynn outlines benefits including reduced stress for parents and increased confidence for children. 00:17:25: Christopher reflects on accepting that children will grow up to be themselves, not replicas of their parents. 00:17:54: Dr. Edlynn emphasizes the importance of seeing children for who they truly are. 00:18:01: Acknowledgment that parenting is a marathon, not a sprint. 00:18:15: Important clarification that parents don't need to be autonomy supportive every moment to be effective. 00:19:12: Dr. Edlynn shares her contact information and online presence. 00:19:24: Closing remarks and podcast subscription information. Key Takeaways Autonomy supportive parenting focuses on nurturing three fundamental needs: autonomy, competence, and relatedness. Modern intensive parenting culture often leads to controlling behaviors that undermine children's development. Parents should ask children "What are you thinking?" before offering solutions to encourage problem- solving skills. Expecting more independent behaviors from children reduces parental stress while building children's confidence. Approach children's mistakes with curiosity rather than judgment to maintain connection and facilitate learning. Scaffolding approach works best - implementing changes step by step rather than expecting immediate complete independence. Autonomy-supportive parenting leads to higher self-esteem, better academic achievement, and stronger social relationships in children. Parents don't need to be perfect - creating a general environment of autonomy support is what matters most. Quotable Moments "All of us, regardless of our age or where we live in the world, we thrive when we have these three needs met." "We feel like this anxiety that we have to curate this perfect life for our kids. And so what we end up doing is we do too much for our kids as a way to love them." "I want you to pretend that there's no one here to solve this problem and your life depends on solving this problem. And I bet you can solve it." "We just undermine or underestimate our children. We underestimate what they have to offer and they'll feel that over time." "One of the best things we can do is let go of our image of them and really see them for who they are." "Parenting is not a hundred yard dash. It's a really long ultra marathon." "You do not have to be autonomy supportive every minute of every day to be an autonomy-supportive parent."

If you've ever wrapped up what felt like a perfectly modeled lesson only to see blank stares when your students try it on their own, you're not alone. You know the moment: you've explained, demonstrated, and thought aloud, but when it's their turn, they freeze. The problem often isn't the modeling itself—it's that students need more support between watching and doing. That's where effective scaffolding comes in.In this episode, I break down the four key steps of scaffolding—modeling, approximating, fading away, and independent learning—and share why each one matters. You'll learn how these steps help students internalize new skills rather than just imitate what they see, and how skipping a single phase can lead to confusion or frustration. When we add in those middle scaffolds, we create the structure students need to build true confidence and independence.Ultimately, scaffolding is about slowing down the learning process just enough so that all students have the chance to succeed. When we give them the right amount of support—and remove it at the right time—we set them up for meaningful growth and long-term learning. This episode will help you reflect on your own scaffolding practices and feel confident making small, intentional shifts that lead to big results.Join us in the Stellar Literacy Collective Membership: stellarteacher.com/join!Sign up for my FREE private podcast, the Confident Writer Systems Series, here!Sign up for my FREE Revision Made Easy email series here!Follow me on Instagram @thestellarteachercompany. To check out all of the resources from this episode, head to the show notes: https://www.stellarteacher.com/episode278.

Send us a textThank you for tuning in!  On today's episode, we are taking a look back at some infamous music videos from the 1980s and 1990s that feature warehouses and scaffolding as the setting.  I realize this episode is a bit niche, but I think you will appreciate the focus on some memorable music videos.  This episode is marked as explicit because I quote a few lyrics from Queen Latifah's song UNITY which has some adult language in it.I mentioned my recent guest appearance on an awesome podcast called "Pop Culture Reflections."  You can find this show here.If you love listening to music from the 80s and 90s, as well as podcasts related to pop culture during these fabulous decades, check out the app Q106.5.  There you will find links to my show and many other awesome podcasts, as well as the ability to listen to some tunes from yesteryear :)I also referenced a few of my older episodes on this one:Learn about Madonna's incredible rise to fame here.Learn about Michael Bolton and why he is such an icon here.Support the showVisit: https://www.popcultureretrospective.com/ for all things Pop Culture Retrospective! Follow me on Instagram: https://www.instagram.com/popcultureretrospective/ Follow me on Twitter!: https://twitter.com/PopCultureRetroReview the show! https://www.popcultureretrospective.com/reviews/new/Pop Culture Retrospective Merch!: https://pop-culture-retrospective-pod.myspreadshop.com/allEmail me anytime: amy@popcultureretrospective.com

In this powerful episode of the Equipping ELLs podcast, host Beth Vaucher (formerly Boche), founder of Inspiring Young Learners, dives deep into one of the most pressing challenges facing educators today—supporting newcomer English Language Learners (ELLs) in the classroom. As classrooms across the country see a rising number of newcomer students, many educators feel overwhelmed and unsure where to begin. In Episode 11, Beth shares a step-by-step roadmap to scaffold lessons effectively so newcomers feel supported, engaged, and empowered from day one.This episode goes beyond the basics of welcoming newcomers and focuses on actionable strategies to make instruction accessible, even when students enter with little or no English or native-language literacy. Beth explains why understanding a student's literacy background in their first language (L1) is essential and how it informs your approach to lesson planning. She breaks down five simple, yet powerful scaffolding strategies you can start using this week—from using visuals and QR codes for listening comprehension to incorporating cognates and sentence starters.Drawing from her personal experience teaching abroad in Panama during the pandemic, Beth offers insight into why today's newcomers may have drastically different needs than those from pre-pandemic years. With many having experienced years of interrupted or nonexistent schooling, educators need practical tools more than ever to bridge the gaps in foundational learning.Whether you're a homeroom teacher or an ESL specialist, Beth emphasizes the critical importance of collaboration between both roles to see real progress in your newcomer students. She provides real-life classroom examples, reflective questions, and helpful analogies (like learning about the solar system in a language you don't speak!) to inspire confidence in teachers who may feel underprepared.Tune in to hear how you can blend foundational language instruction with content-area learning, all while making students feel safe and successful. Plus, Beth shares how small, intentional efforts—like slowing your rate of speech or providing picture-supported vocabulary—can make a huge difference in helping newcomers thrive.Finally, Beth invites educators to join the Equipping ELLs membership, where they can access done-for-you lesson plans, coaching, and a community of passionate teachers ready to support each other. If you're looking to grow your confidence and capacity when working with newcomer ELLs, this episode is a must-listen.Links and Resources:⁠⁠⁠Join the Equipping ELLs MembershipShop our TpT Store[FREEBIE] Newcomer Welcome Kit[FREEBIE] Newcomers Scope & SequenceReady for more? Grab our best-selling Newcomer Yearlong Bundle

This week in Together in Literacy we continue our discussion on supporting older students with dyslexia. Last episode we talked about the why, and now we want to talk about the how. We explore practical, research-based strategies that help middle and high school students move from struggle to success, including explicit decoding routines, morphology instruction, and scaffolded writing supports. We talk about the importance of assessing students closely, breaking learning into manageable steps, and building conceptual understanding to foster confidence and independence. Resources mentioned in this episode: readworks.org (for finding short non-fiction articles) keystoliteracy.com (for two-column note-taking method) Season 5 Episode 2: Honoring the Emotional Landscape of Older Students with Dyslexia (part 1 of this discussion) Season 3 Episode 7: The Importance of Scaffolding in Decoding If you like this episode, please take a few minutes to rate, review, and subscribe. Your support and encouragement are so appreciated! We officially have merch! Show your love for the Together in Literacy podcast! Have a question you'd like us to cover in a future episode of Together in Literacy? Email us at support@togetherinliteracy.com! If you'd like more from Together in Literacy, you can check out our website, Together in Literacy, or follow us on Facebook and Instagram. For more from Emily, check out The Literacy Nest. For more from Casey, check out The Dyslexia Classroom. Let us know what you want to hear this season! Thank you for listening and joining us in this exciting and educational journey into dyslexia as we come together in literacy!

Frustrated with keeping your ELL students engaged? Or struggling to give everyone the chance for output in a short amount of time?In this episode of the Equipping ELLs Podcast, we dive into 4 practical Kagan Cooperative Learning strategies that will help you keep every student participating. Boost engagement, scaffold activities, and empower your students to take the lead in their learning journey. Join us for insights that'll make your teaching life easier and your classroom time more productive!Resources: ⁠⁠⁠Join the Equipping ELLs Membership (Everything you need for your school year!)Shop our TpT StoreSign Up for the FREE WebinarFREEBIE: Using Cooperative Learning Strategies with ELLs

Simon Cullen + Danny Oppenheimer help us rethink student attendance policies toward deeper engagement and learning on episode 591 of the Teaching in Higher Ed podcast. Quotes from the episode There's a lot of evidence that coming to class is one of the best things a student can do to facilitate their learning and performance in class. -Danny Oppenheimer You can make students attend, and most faculty do. They set attendance as mandatory. And then students attend and they learn because they attend. But they also hate you, and they hate the subject and they hate everything to do with the class. -Danny Oppenheimer If you give people choices, sometimes they make bad choices. Scaffolding choices can help people make choices that actually align with their preferences more effectively. -Danny Oppenheimer Students love being treated like adults. They love having choice. Everybody loves having choice. People don't like other people telling them what to do. -Danny Oppenheimer In some sense students have a preference to attend class. And in some sense they have a preference to not attend class. Those preferences can coexist in some way. -Simon Cullen Resources Choosing to learn: The importance of student autonomy in higher education, by Simon Cullen and Daniel Oppenheimer Are we overlooking the power of autonomy when it comes to motivating students? by Danny Oppenheimer Consequences of Erudite Vernacular Utilized Irrespective of Necessity: Problems with Using Long Words Needlessly, by Daniel M. Oppenheimer Speak Freely, Think Critically: The Free Speech Balance Act Punished By Rewards: The Trouble with Gold Stars, Incentive Plans, A's, Praise, and Other Bribes, by Alfie Kohn The Goodness Paradox: The Strange Relationship Between Virtue and Violence in Human Evolution, by Richard Wrangham Finding Meaning in the Age of Immortality, by T.N. Eyer

Shannon Foster didn't grow up in a Latter-day Saint home where scriptures were regularly studied—and her father wasn't a member of the Church. But rather than see this as a setback, Shannon considers it one of her greatest blessings. That unique perspective has shaped her ability to relate to others and to inspire confidence in anyone seeking to better understand and love the scriptures. In this episode, Shannon shares her journey and explains why she's so passionate about helping others develop a personal, meaningful relationship with scripture—no matter their background. 1:56- A Home Without Gospel Learning 8:06- The Lord Qualifies 14:05- Compelled to Share 17:18- Scaffolding 22:50- Family Scripture Study 27:25- The Power of Families 34:31- Think Like a Coach 42:12- Imperfect Practice 46:25- What Does It Mean to Be All In the Gospel of Jesus Christ? “I feel like I can stand in my spot and relate and say I was that girl who knew nothing about the scriptures and now I have found great power in the scriptures.” Link:  The Red Headed Hostess guidebooks- https://www.deseretbook.com/category/church-resources_teaching-helps_the-red-headed-hostess/church-resources_teaching-helps_the-red-headed-hostess_guidebooks/  

Sometimes, your kids can handle frustration or disappointment with ease, and other times the exact same challenge sends them into meltdown mode. This can feel really baffling! Why are they so inconsistent?Well, part of that difference comes down to their window of stress tolerance.In this episode, you'll learnWhat the window of stress tolerance is and how it connects to your child's Owl, Watchdog, and Possum brainsWhy widening the window matters for learning, relationships, and everyday lifePractical ways you can help your child (and yourself!) expand the window through connection, playfulness, noticing the good, and self-compassionResources mentioned in this podcast:What Does Co-Regulation Really Look Like? {EP 81}Scaffolding is a Form of Co-Regulation {EP 82}Boundaries with Connection Part 1 of 3 {EP 111}Felt Safety (Inside) - Part 1 {Ep 161}Read the full transcript at: RobynGobbel.com/windowoftoleranceApplications for the 2026 cohorts of the Baffling Behavior Training Institute's Professional Immersion Program are now open! Get on the waiting list at RobynGobbel.com/immersion :::Grab a copy of my book Raising Kids with Big, Baffling Behaviors robyngobbel.com/bookJoin us in The Club for more support! robyngobbel.com/TheClubApply for the Baffling Behavior Training Institute's Professional Immersion Program (formerly Being With) robyngobbel.com/ImmersionFollow Me On:FacebookInstagram Over on my website you can find:Webinar and eBook on Focus on the Nervous System to Change Behavior (FREE)eBook on The Brilliance of Attachment (FREE)LOTS & LOTS of FREE ResourcesOngoing support, connection, and co-regulation for struggling parents: The ClubYear-Long Immersive & Holistic Training Program for Parenting Professionals: The Baffling Behavior Training Institute's (BBTI) Professional Immersion Program (formerly Being With)

The profound impact of teaching on unlocking human potential is the subject of McKay's focus today, arguing that everyone, whether a parent, coach, or team leader, plays the role of a teacher. The episode delves into the lives of such inspirational educators and mentors as Jaime Escalante, who transformed his students' lives by believing in them against all odds, among many others.McKay reveals that the most effective teaching transcends simply conveying information. It's about creating human connection, seeing the potential in others before they see it in themselves, and providing the right tools for growth. He introduces two powerful teaching strategies: creating a "hook" or "cognitive anchor" to make learning relevant and memorable, and using "scaffolding"—a process of explaining, demonstrating, practicing, and evaluating—to build skills and confidence. Through the stories of Thomas Edison and the Wright brothers, he also illustrates the immense power of "learning by doing." This episode is the guide for anyone looking to inspire, lead, and help others reach their full potential.Main Themes:The essence of teaching is to help others discover their own potential.Great teachers see students for who they can become.Discipline, focus, and mentorship are as crucial as raw talent.Effective teaching uses "hooks" to anchor new information to existing knowledge.Scaffolding (explain, demonstrate, practice, evaluate) is a key model for building skills."Learning by doing" is one of the most powerful forms of education.The joy of teaching comes from the human connection and witnessing growth.Everyone is a teacher, with the ability to leave a lasting legacy.Reading aloud to children is a powerful tool for cognitive and emotional development.Top 10 Quotes:"If students don't have to challenge themselves, then there's no teaching, there's no learning going on, there's no potential. We're just babysitting.""I touch the future when I teach.""The joy of teaching and training comes from the human connection. It's about a bond between the trainer and the team member where encouragement can change the trajectory of life.""When you're teaching, you must create a meaningful and important hook.""Talent is nothing without discipline. You can't let raw ability carry you. Your mind has to lead the way.""Learning by doing is perhaps the best way to teach your team members.""He was a teacher who left a legacy for his children by this very small, simple habit.""Higher, Orville, higher!"Show Links:Open Your Eyes with McKay Christensen