Podcasts about scaffold

In Episode 208 of the Equipping ELLs podcast, Beth Vaucher tackles one of the most widely discussed and most misunderstood concepts in ELL instruction: scaffolding. Every ELL teacher has heard the word, most can name a few strategies, and most genuinely believe they are scaffolding for their students. But when Beth observes teachers using these tools, she consistently finds the same problem — scaffolds are being used inconsistently, without clear purpose, and without any plan to eventually remove them. And when scaffolding never gets phased out, it stops being a scaffold entirely.Beth begins with the definition most teacher training programs get wrong. Scaffolding comes from the construction metaphor — a temporary structure built alongside a building while it is going up. The key word is temporary. The whole point of a scaffold is that it eventually comes down. In teaching, scaffolding is any temporary support that allows a student to access content they cannot access independently yet. That word yet is everything. Scaffolding is always pointed toward independence — always building toward the moment when the support is no longer needed. This is what makes scaffolding fundamentally different from accommodation, which is a permanent adjustment. Both have their place, but treating them as interchangeable is one of the most common mistakes in ELL classrooms — one Beth admits she was guilty of early in her own teaching career.The most common scaffolding mistake, Beth explains, is keeping the same scaffold long after it has stopped helping students grow. She uses sentence frames as the example most teachers will recognize: a teacher introduces frames for writing, students use them, lessons go better, and the teacher keeps using the same frames week after week. Students get comfortable. They rely on them completely. The teacher feels good because language is being produced. But completing a frame is not the same as internalizing a structure. Students can fill in the same sentence frame for six months without ever acquiring the academic language it contains. The scaffold has stopped building — it is only carrying.The fix is gradual release, not sudden removal. Beth walks through the progression: I do it, we do it together, you do it with support, you do it alone. Each step is a little more independent than the last. That progression is what turns a scaffold into real acquisition.The heart of the episode is a walkthrough of five scaffolding strategies that consistently make the biggest difference for ELL students. Sentence frames and sentence starters are the most versatile and highest-impact tools in the toolkit — but their power depends entirely on whether complexity is increasing over time. Beth walks through how to move from a complete frame to a partial frame to a prompt word to a word bank to nothing at all. Graphic organizers make thinking visible and are especially powerful for writing and reading comprehension — Beth recommends picking one organizer to master deeply before introducing others, and phasing out from fully structured to blank to student-created. Visual supports are not decoration — every image in a sheltered classroom should carry meaning, and Beth addresses how to move students toward generating their own visual connections over time. Pre-teaching vocabulary is the most commonly skipped scaffold and the one that makes the single biggest difference — five to eight essential words introduced before the lesson begins, not during and not at the end, with context, visuals, and multiple exposures. And modeling through think-alouds is the most underused scaffold of all, one that costs nothing — doing the task yourself out loud in front of students before asking them to attempt it, including making mistakes visibly so students see that confusion and self-correction are part of the process.Beth closes with the reminder that scaffolding is not one size fits all — the right scaffold always depends on the student's language stage and the specific task. And she leaves teachers with one question to ask before every lesson about every scaffold they plan to use: am I using this because my students need it to access the content right now, or am I using it because it makes the lesson feel smoother and I am not sure what else to do? FREE RESOURCE: DM the word SCAFFOLD to @EquippingELLs on Instagram for the free ELL Scaffolding Strategy Guide — scaffolding strategies organized by proficiency level with examples from Level 1 through Level 5.

Jonathan Tuckey founded his design practice in 2000 having previously worked for David Chipperfield Architects and Fletcher Priest Architects. He has long been one of the UK's leading advocates for remodelling and radically transforming old buildings for modern uses.The podcast is supported this week by Velux, and features a short pre-reel interview with Thomas Vonier — architect and former president of the International Union of Architects. th UIA is assembling in Barcelona this month for the World Congress of Architects, which Velux are also supporting. Jonathan's episode begins around the 12 minute mark.Scaffold is an Architecture Foundation production, hosted by Matthew Blunderfield. Hosted on Acast. See acast.com/privacy for more information.

**Episode Description:**A God-sized dream will always intimidate a man-sized mind. In this morning's episode of *Failure Isn't Final*, Harold Mawela teaches the divine law of the "Scaffold of Possibility." Stop staring at the overwhelming mountain peak and learn how to build the next six feet of your destiny. Through a powerful story of local resilience, you will discover how to stop trying to build the roof before you've laid the floor. Tune in to receive the practical, three-step morning protocol that will help you transform a crushing, distant vision into a methodical, climbable reality through the power of daily obedience.#LifeFaithPodcast#DailyDevotionalInspiration#DailyFaithInspiration#InspirationalFaithTalks#FaithAndPurposeMessages#ChristianDailyMotivation#ChristianMotivationalTalks

SVP and Stanford Steve are back to discuss a great game 7 between the Spurs and Thunder. Wemby is the story, but his supporting cast was incredible. The guys make sure to give Champagnie, Johnson, Vassell, Harper and Castle their credit as San Antonio reaches its first Finals in 12 years. Shai played lights out, but the same thing can't be said for Chet. What should the Thunder do there? Plus, Shai's demeanor and words after the game were great, and that should be applauded. The guys also preview the Stanley Cup Final, discuss the Knicks-Spurs matchup and Steve gives a lengthy NCAA baseball tournament update. Finally, the origin story of SVP wearing glasses, whether or not to leave a voicemail, a nose-waxing recap and why SVP may not attend the Emmys anymore for more reasons than one. | SVPod Time Codes/Topics (0:00) Intro (1:10) Flag is over (1:52) Spurs-Thunder game 7 recap (4:47) Wemby has done something special (9:30) Spurs supporting cast has been great (12:16) Shai played & handled himself greatly (20:25) The Chet situation (29:20) Finals preview (43:50) First Finals you remember? (48:10) Stanley Cup Final preview (53:37) NCAA Baseball Tourney update (1:04:23) Texas vs. Tennessee orange (1:05:38) More baseball talk (1:08:03) The origin story of SVP getting glasses (1:15:05) Leave voicemail or no? (1:17:58) Swim season update (1:23:15) SVP got his nose waxed! (1:26:55) Scaffold guy made it about him (1:29:58) Thanks for watching Learn more about your ad choices. Visit podcastchoices.com/adchoices

This week, Eric and Pascale trick Josh into making at least half the episode to be all about basketball (with some movie related basketball stuff in there, like Space Jam, Hoop Dreams, Hoosiers, and Air Bud, just to keep us on point). We also discuss Holey Confections, bartering, Herb Albert, The Mighty Ducks, Saturday Night Sinema, Wes Anderson's box office, Uncut Gems, the silent film era, and more! Plus, the movies screening the week of Friday May 22 - Thursday May 28: Everyone Is Lying To You For Money, The Drama, The Wicker Man, The Docks Of New York, and The Darjeeling Limited!

Do you ever wonder why your child, who can spend hours building or creating something they love, just can't seem to get started on a simple task? Does it seem like they're just not motivated—even though you know they do care? This week's episode of the podcast dives deep into one of the most misunderstood challenges in homeschooling neurodivergent kids: motivation vs. executive dysfunction. Key Takeaways Motivation isn't a character trait—it depends on fragile conditions, especially in neurodivergent kids. Kids aren't refusing tasks out of laziness; they're often stuck somewhere along the executive function path. Scaffold your child's success: break tasks down, work alongside them, and focus on small wins. Motivation grows from success, autonomy, and a regulated nervous system—not from pressure or shame. 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 Executive Function Struggles in Homeschooling: Why Smart Kids Can't Find Their Shoes (and What to Do About It) How Adventuring Together Grows Confidence, Curiosity, and Executive Function Understanding Executive Function Skills in Gifted and Twice-Exceptional Children Strengthening Executive Function Skills: A Conversation with Sarah Collins Strengthen Executive Function Skills The Best Books for Teaching About Executive Functions Skills 7 Executive Functioning Activities for Small Children RLL #84: Exploring Education and Executive Function with Seth PerlerThe Unmeasured Executive Functioning Issue RLL 20: Helping Your Kiddo with Executive Function Skills Struggles | A Listener Question RLL LIVE | Improving Executive Functions Helping Kids Who Resist: Low-Demand Homeschooling for Autonomy and Skill-Building Why Is Finishing So Hard? Helping Neurodivergent Kids Cross the Finish LineWhy Typical Organization Systems Fail Neurodivergent Homeschoolers and What Works Instead  

Success is not a product of luck; it is a product of structure. In this episode, Harold Mawela breaks down why your "Daily Discipline Decodes your Divine Destiny." If you are seeking a platform before you've built a pillar, you are building on a vacuum. Learn why Jesus spent thirty years in the dark of preparation for three years in the light of presentation. Stop waiting for spontaneous miracles and start building the scriptural scaffold that can hold the weight of your calling. Your private prayer is the price for your public power—it's time to count the cost.#LifeFaithPodcast#DailyDevotionalInspiration#DailyFaithInspiration#InspirationalFaithTalks#FaithAndPurposeMessages#ChristianDailyMotivation#ChristianMotivationalTalks

In this reflection episode, Jocelynn takes off the "Interviewer" hat and steps into the "Coach's" seat. After modeling student consultations in Episode 11, she dives deep into the four core "Treasures" that were unearthed during those conversations. This isn't just about what was said—it's about how we as educators Reflect, Learn, and Implement the truth to build radical trust in our classrooms.The 4 Treasures Revealed:Connection Over Everything: Why the "Getting to Know You" worksheets we rely on often miss the mark, and what students actually crave instead.Scaffold, Scaffold, Scaffold: A look at how shifting our language from the abstract to the concrete (e.g., from "Mapping" to "Planning") unlocks the brilliance of every learner.Pause & Excavate: The power of the "Gold Statement." Why we must be willing to stop the script and "excavate" when a student shares a deep truth.Theory into Practice: Moving from the "How" to the "Do." How the Friday Lab and Co-Design routines turn student voice into the engine of classroom culture.What You'll Hear in This Episode:The Trust Loop: Understanding that it's not enough to know your students; they must know that they are known.Structured Independence: A tactical breakdown of the "Friday Lab" (Reader's/Writer's Workshop and Social Studies Lab) and how it creates the space for 1-on-1 advocacy.The Co-Design Lab: Defining the collaborative workspace where students become the architects of their own learning.Radical Grace: Reflections on the "simmer down" period and the necessity of processing our own emotions before advocating for change.Featured Resources:The First 10 Days: Building a Welcoming & Respectful Classroom of BelongingThe Student Connection Profile ToolCoaching Corner Highlights:Anchor Question: What are my students learning about themselves when I give them the space to plan?Implementation Intention: “This week, I will facilitate a Co-Design Lab during the last 20 minutes of class on Friday to brainstorm our next unit.”

Zdravo. Tokrat začnemo z revizijo zgodovine (za obe vojni so krivi Avstrijci, to je jasno) in ker je ravno tak dan, spet obudimo protiimperialistično fronto, ki je bila pred OF tudi uradno ime gibanja, dokler se komunisti niso razbohotili v gibanju in pobrali žoge in šli izpred bloka. Ugotovimo, da smo hujši k Žižek, tokratni komad tedna je Ritem človeštva Nietov mi pa obdelamo še vojaške tehnologije v civilni rabi in znižanje davkov, zaradi katerega bo, kot vemo, vse bolje. Preden v Garambi obiščemo nilske konje, gremo še na Roško, nilski konji pa niso nevarni, razen tistega leva, ki je nekaj tednov kasneje nekoga pojedel, zato se mi posvetimo entrepreneurjem in vprašanju plač. Če so delavci z nižjimi plačami premalo plačani, smo tudi mi premalo plačani, oziroma če smo mi premalo, so premalo plačani tudi oni. Smrt imperializmu, svoboda delavcem! ✊

Jaakko Pallasvuo is a Helsinki-based artist and writer, best known for his Instagram account Avocado Ibuprofen. In this episode he reflects on the role he sees for art and writing in a world increasingly shaped by social media platforms and artificial intelligence, and he discusses his recently published collection of performance texts Mouthing the Words (Khaos, 2025).Scaffold is an Architecture Foundation production, hosted by Matthew Blunderfield. Download the London Architecture Guide App via the App Store or Google PlayBecome an Architecture Foundation Patreon member and be a part of a growing coalition of architects and built environment professionals supporting our vital and independent work. Hosted on Acast. See acast.com/privacy for more information.

All students need access to rich, challenging text to grow as readers. But how do we support them? Dr. Jennifer Throndsen shares the why and HOW of scaffolding complex texts. This episode is for you no matter what grade you teach.Click here for this episode's show notes.Free differentiated passages: https://www.themeasuredmom.com/tmm_optin/differentiated-passages/ Sign up for my free masterclass, 5 Essential Steps to Reach All Readers.Get my book, Reach All Readers! Looking for printable resources that align with the science of reading? Click here to learn more about our popular and affordable membership for PreK through 3rd grade educators.Connect with me here!BlogInstagramFacebookTwitter (X)

INNOVATION COMPETITION: Retrievable Scaffold Therapy: The Spur Elute Coronary Retrievable Scaffold System

We're proud to release this ahead of Ryan's keynote at AIE Europe. Hit the bell, get notified when it is live! Attendees: come prepped for Ryan's AMA with Vibhu after.Move over, context engineering. Now it's time for Harness engineering and the age of the token billionaires.Ryan Lopopolo of OpenAI is leading that charge, recently publishing a lengthy essay on Harness Eng that has become the talk of the town:In it, Ryan peeled back the curtains on how the recently announced OpenAI Frontier team have become OpenAI's top Codex users, running a >1m LOC codebase with 0 human written code and, crucially for the Dark Factory fans, no human REVIEWED code before merge. Ryan is admirably evangelical about this, calling it borderline “negligent” if you aren't using >1B tokens a day (roughly $2-3k/day in token spend based on market rates and caching assumptions):Over the past five months, they ran an extreme experiment: building and shipping an internal beta product with zero manually written code. Through the experiment, they adopted a different model of engineering work: when the agent failed, instead of prompting it better or to “try harder,” the team would look at “what capability, context, or structure is missing?”The result was Symphony, “a ghost library” and reference Elixir implementation (by Alex Kotliarskyi) that sets up a massive system of Codex agents all extensively prompted with the specificity of a proper PRD spec, but without full implementation:The future starts taking shape as one where coding agents stop being copilots and start becoming real teammates anyone can use and Codex is doubling down on that mission with their Superbowl messaging of “you can just build things”.Across Codex, internal observability stacks, and the multi-agent orchestration system his team calls Symphony, Ryan has been pushing what happens when you optimize an entire codebase, workflow, and organization around agent legibility instead of human habit.We sat down with Ryan to dig into how OpenAI's internal teams actually use Codex, why the real bottleneck in AI-native software development is now human attention rather than tokens, how fast build loops, observability, specs, and skills let agents operate autonomously, why software increasingly needs to be written for the model as much as for the engineer, and how Frontier points toward a future where agents can safely do economically valuable work across the enterprise.We discuss:* Ryan's background from Snowflake, Brex, Stripe, and Citadel to OpenAI Frontier Product Exploration, where he works on new product development for deploying agents safely at enterprise scale* The origin of “harness engineering” and the constraint that kicked off the whole experiment: Ryan deliberately refused to write code himself so the agent had to do the job end to end* Building an internal product over five months with zero lines of human-written code, more than a million lines in the repo, and thousands of PRs across multiple Codex model generations* Why early Codex was painfully slow at first, and how the team learned to decompose tasks, build better primitives, and gradually turn the agent into a much faster engineer than any individual human* The obsession with fast build times: why one minute became the upper bound for the inner loop, and how the team repeatedly retooled the build system to keep agents productive* Why humans became the bottleneck, and how Ryan's team shifted from reviewing code directly to building systems, observability, and context that let agents review, fix, and merge work autonomously* Skills, docs, tests, markdown trackers, and quality scores as ways of encoding engineering taste and non-functional requirements directly into context the agent can use* The shift from predefined scaffolds to reasoning-model-led workflows, where the harness becomes the box and the model chooses how to proceed* Symphony, OpenAI's internal Elixir-based orchestration layer for spinning up, supervising, reworking, and coordinating large numbers of coding agents across tickets and repos* Why code is increasingly disposable, why worktrees and merge conflicts matter less when agents can resolve them, and what it really means to fully delegate the PR lifecycle* “Ghost libraries”, spec-driven software, and the idea that a coding agent can reproduce complex systems from a high-fidelity specification rather than shared source code* The broader future of Frontier: safely deploying observable, governable agents into enterprises, and building the collaboration, security, and control layers needed for real-world agentic workRyan Lopopolo* X: https://x.com/_lopopolo* Linkedin: https://www.linkedin.com/in/ryanlopopolo/* Website: https://hyperbo.la/contact/Timestamps00:00:00 Introduction: Harness Engineering and OpenAI Frontier00:02:20 Ryan's background and the “no human-written code” experiment00:08:48 Humans as the bottleneck: systems thinking, observability, and agent workflows00:12:24 Skills, scaffolds, and encoding engineering taste into context00:17:17 What humans still do, what agents already own, and why software must be agent-legible00:24:27 Delegating the PR lifecycle: worktrees, merge conflicts, and non-functional requirements00:31:57 Spec-driven software, “ghost libraries,” and the path to Symphony00:35:20 Symphony: orchestrating large numbers of coding agents00:43:42 Skill distillation, self-improving workflows, and team-wide learning00:50:04 CLI design, policy layers, and building token-efficient tools for agents00:59:43 What current models still struggle with: zero-to-one products and gnarly refactors01:02:05 Frontier's vision for enterprise AI deployment01:08:15 Culture, humor, and teaching agents how the company works01:12:29 Harness vs. training, Codex model progress, and “you can just do things”01:15:09 Bellevue, hiring, and OpenAI's expansion beyond San FranciscoTranscriptRyan Lopopolo: I do think that there is an interesting space to explore here with Codex, the harness, as part of building AI products, right? There's a ton of momentum around getting the models to be good at coding. We've seen big leaps in like the task complexity with each incremental model release where if you can figure out how to collapse a product that you're trying to.Build a user journey that you're trying to solve into code. It's pretty natural to use the Codex Harness to solve that problem for you. It's done all the wiring and lets you just communicate in prompts. To let the model cook, you have to step back, right? Like you need to take a systems thinking mindset to things and constantly be asking, where is the Asian making mistakes?Where am I spending my time? How can I not spend that time going forward? And then build confidence in the automation that I'm putting in place. So I have solved this part of the SDLC.swyx: [00:01:00] All right.[00:01:03] Meet Ryan swyx: We're in the studio with Ryan from OpenAI. Welcome.Ryan Lopopolo: Hi,swyx: Thanks for visiting San Francisco and thanks for spending some time with us.Ryan Lopopolo: Yeah, thank you. I'm super excited to be here.swyx: You wrote a blockbuster article on harness engineering. It's probably going to be the defining piece of this emerging discipline, huh?Ryan Lopopolo: Thank you. It is it's been fun to feel like we've defined the discourse in some sense.swyx: Let's contextualize a little bit, this first podcast you've ever done. Yes. And thank you for spending with us. What is, where is this coming from? What team are you in all that jazz?Ryan Lopopolo: Sure, sure.Ryan Lopopolo: I work on Frontier Product Exploration, new product development in the space of OpenAI Frontier, which is our enterprise platform for deploying agents safely at scale, with good governance in any business. And. The role of VMI team has been to figure out novel ways to deploy our models into package and products that we can sell as solutions to enterprises.swyx: And you have a background, I'll just squeeze it in there. Snowflake, brick, [00:02:00] stripe, citadel.Ryan Lopopolo: Yes. Yes. Same. Any kind of customerswyx: entire life. Yes. The exact kind of customer that you want to,Vibhu: so I'll say, I was actually, I didn't expect the background when I looked at your Twitter, I'm seeing the opposite.Stuff like this. So you've got the mindset of like full send AI, coding stuff about slop, like buckling in your laptop on your Waymo's. Yes. And then I look at your profile, I'm like, oh, you're just like, you're in the other end too. Oh, perfect. Makes perfect.Ryan Lopopolo: I it's quite fun to be AI maximalist if you're gonna live that persona.Open eye is the place to do it. And it'sswyx: token is what you say.Ryan Lopopolo: Yeah. Certainly helps that we have no rate limits internally. And I can go, like you said, full send at this stay.swyx: Yeah. Yeah. So the Frontier, and you're a special team within O Frontier.Ryan Lopopolo: We had been given some space to cook, which has been super, super exciting.[00:02:47] Zero Code ExperimentRyan Lopopolo: And this is why I started with kind of a out there constraint to not write any of the code myself. I was figuring if we're trying to make agents that can be deployed into end to enterprises, they should be [00:03:00] able to do all the things that I do. And having worked with these coding models, these coding harnesses over 6, 7, 8 months, I do feel like the models are there enough, the harnesses are there enough where they're isomorphic to me in capability and the ability to do the job.So starting with this constraint of I can't write the code meant that the only way I could do my job was to get the agent to do my job.Vibhu: And like a, just a bit of background before that. This is basically the article. So what you guys did is five months of working on an internal tool, zero lines of code over a mi, a million lines of code in the total code base.You say it was cenex, more like it was cenex faster than you would've. If you had done it by end. SoRyan Lopopolo: yeah, thatVibhu: was the mindset going into this, right?Ryan Lopopolo: That's right.[00:03:46] Model Upgrades LessonsRyan Lopopolo: Started with some of the very first versions of Codex CLI, with the Codex Mini model, which was obviously much less capable than the ones we have today.Which was also a very good constraint, right? Quite a visceral feeling to ask the [00:04:00] model to build you a product feature. And it just not being able to assemble the pieces together.Which kind of defined one of the mindsets we had for going into this, which is whenever the model just cannot, you always pop open at the task, double click into it, and build smaller building blocks that then you can reassemble into the broader objective.And it was quite painful to do this. Honestly, the first month and a half was. 10 times slower than I would be. But because we paid that cost, we ended up getting to something much more productive than any one engineer could be because we built the tools, the assembly station for the agent to do the whole thing.[00:04:43] Model Generations, Build Systems & Background ShellsRyan Lopopolo: But yeah, so onward to G BT 5, 5, 1, 5, 2, 5, 3, 5 4. To go through all these model generations and see their kind of corks and different working styles also meant we had to adapt the code base to change things up when the model was revved. [00:05:00] One interesting thing here is five two, the Codex harness at the time did not have background shells in it, which means we were able to rely on blocking scripts to perform long horizon work.But with five, three and background shells, it became less patient, less willing to block. So we had to retool the entire build system to complete in under a minute and. This is not a thing I would expect to be able to do in a code base where people have opinions. But because the only goal was to make the Asian productive over the course of a week, we went from a bespoke make file build to Basil, to turbo to nx and just left it there because builds were fast at that point.swyx: Interesting. Talk more about Turbo TenX. That's interesting ‘cause that's the other direction that other people have been doing.Ryan Lopopolo: Ultimately I have. Not a lot of experience with actual frontend repo architecture.swyx: You're talking that Jessica built the sky. So I'm like, I know the NX team. I know Turbo from Jared [00:06:00] Palmer.And I'm like, yeah, that's an interesting comparison.[00:06:02] One Minute Build LoopRyan Lopopolo: The hill we were climbing right, was make it fast.swyx: Is there a micro front end involved? Is it how how complex reactRyan Lopopolo: electron base single app sort of thingswyx: And must be under a minute. That's an interesting limitation. I'm actually not super familiar with the background shelf stuff.Probably was talked about in the fight three release.Ryan Lopopolo: BA basically means that codex is able to spawn commands in the background and then go continue to work while it waits for them to finish. So it can spawn an expensive build and then continue reviewing the code, for example.swyx: Yeah.Ryan Lopopolo: And this helps it be more time efficient for the user invoking the harness.swyx: And I guess and just to really nail this, like what does one minute matter? Like why not five, okay, good. We want no. WeRyan Lopopolo: want the inner loop to be as fast as possible. Okay. One minute was just a nice round number and we were able to hit it.swyx: And if it doesn't complete, it kills it or some something,Ryan Lopopolo: No.We just take that as a signal that we need to stop what we're doing, double click, decompose a build graph a bit to get us to high back under so that we [00:07:00] can able the agent continue to operate.swyx: It's almost like you're, it's like a ratchet. It's like you're forcing build time discipline, because if you don't, it'll just grow and grow.That's right. And you mentioned that my current, like the software I work on currently is at 12 minutes. It sucks.Ryan Lopopolo: This has been my experience with platform teams in the past, where you have an envelope of acceptable build times and you let it go up to breach and then you spend two, three weeks to bring it back down to the lower end of the average low bed stop.But because tokens are so cheap Yeah. And we're so insanely parallel with the model, we can just constantly be gardening this thing to make sure that we maintain these in variants, which means. There's way less dispersion in the code and the SDLC, which means we can simplify in a way and rely on a lot more in variance as we write the software.[00:07:45] Observability, Traces & Local Dev StackVibhu: Lovely.[00:07:46] Humans Are BottleneckVibhu: You mentioned in your article, like humans became the bottleneck, right? You kicked off as a team of three people. You're putting out a million line of code, like 1500 prs, basically. What's the mindset there? So as much as code is disposable, you're doing a lot of review. A lot [00:08:00] of the article talks about how you wanna rephrase everything is prompting everything, is what the agent can't see.It's kind of garbage, right? You shouldn't have it in there. So what's like the high level of how you went about building it, and then how you address okay, humans are just PR review. Like how is human in the loop for this?Ryan Lopopolo: We've moved beyond even the humans reviewing the code as well.[00:08:19] Human Review, PR Automation & Agent Code ReviewRyan Lopopolo: Most of the human review is post merge at this point.But post, post merge, that's not even reviewed. That's justswyx: Oh, let's just make ourselves happy by YouRyan Lopopolo: haven't used fundamentally. The model is trivially paralyzable, right? As many GPUs and tokens as I am willing to spend, I can have capacity to work with my hood base.The only fundamentally scarce thing is the synchronous human attention of my team. There's only so many hours in the day we have to eat lunch. I would like to sleep, although it's quite difficult to, stop poking the machine because it makes me want to feed it. You have to step back, right?Like you need to take a systems thinking mindset to things and [00:09:00] constantly be asking where is the agent making mistakes? Where am I spending my time? How can I not spend that time going forward? And then build confidence in the automation that I'm putting in place. So I have solved this part of the SDLC, and usually what that has looked like is like we started needing to pay very close attention to the code because the agent did not have the right building blocks to produce.Modular software that decomposed appropriately that was reliable and observable and actually accrued a working front end in these things, right?[00:09:35] Observability First SetupRyan Lopopolo: So in order to not spend all of our time sitting in front of a terminal at most, doing one or two things at a time, invested in giving the model that observability, which is that that graph in the post here.swyx: Yeah. Let's walk through this traces and which existed firstRyan Lopopolo: we started with just the app and the whole rest of it. From vector through to all these login metrics, APIs was, I dunno, half an [00:10:00] afternoon of my time. We have intentionally chosen very high level fast developer tools. There's a ton of great stuff out there now.We use me a bunch, which makes it trivial to pull down all these go written Victoria Stack binaries in our local development. Tiny little bit of python glue to spin all these up. And off you go. One neat thing here is we have tried to invert things as much as possible, which is instead of setting up an environment to spawn the coding agent into, instead we spawn the coding agent, like that's the entry point.It's just Codex. And then we give Codex via skills and scripts the ability to boot the stack if it chooses to, and then tell it how to set some end variables. So the app and local Devrel points at this stack that it has chosen to spin up. And this I think is like the fundamental difference between reasoning models and the four ones and four ohs of the past, where these models could not think so you had to put them in [00:11:00] boxes with a predefined set of state transitions.Whereas here we have the model, the harness be the whole box. And give it a bunch of options for how to proceed with enough context for it to make intelligent choices. SoVibhu: sales, so like a lot of that is around scaffolding, right? Yes. Previous agents, you would define a scaffold. It would operate in that.Lube, try again. That's pivoted off from when we've had reasoning models. They're seeming to perform better when you don't have a scaffold, right? That's right.[00:11:28] Docs Skills GuardrailsVibhu: And you go into like niches here too, like your SPEC MD and like having a very short agent MG Agent md.swyx: Yes. Yes.Vibhu: Yeah. So you even lay out what it is here, but I likeswyx: the table contents.Vibhu: Yeah.swyx: Like stuff like this, it really helps guide people because everyone's trying to do this.Ryan Lopopolo: This structure also makes it super cheap to put new content into the repository to steer both the humans and the agents.swyx: You, you reinvented skills, right?Vibhu: One big agents andswyx: skills from first princip holdsRyan Lopopolo: all skills did not exist when we started doing this.Vibhu: You have a short [00:12:00] one 100 line overall table of contents and then you have little skills, right? Core beliefs, MD tech tracker. Yeah. Yeah. The scale is overRyan Lopopolo: The tech jet tracker and the quality score are pretty interesting because this is basically a tiny little scaffold, like a markdown table, which is a hook for Codex to review all the business logic that we have defined in the app, assess how it matches all these documented guardrails and propose follow up work for itself.Before beads and all these ticketing systems, we were just tracking follow up work as notes in a markdown file, which, we could spa an agent on Aron to burn down. There's this really neat thing that like the models fundamentally crave text. So a lot of what we have done here is figure out ways to inject textswyx: intoRyan Lopopolo: the system right when we get a page, because we're missing a timeout, for example.I can just add Codex in Slack on that page and say, I'm gonna fix this by adding a timeout. Please update our reliability documentation. To require that all network calls have [00:13:00] timeouts. So I have not only made a point in time fix, but also like durably encoded this process knowledge around what good looks like.swyx: Yeah.Ryan Lopopolo: And we give that to the root coding agent as it goes and does the thing. But you can also use that to distill tests out of, or a code review agent, which is pointed at the same things to narrow the acceptable universe of the code that's produced.swyx: I think one of the concerns I have with that kind of stuff is you think you're making the right call by making, it's persisted for all time across everything.Yes. But then you didn't think about the exceptions that you need to make, right? And that you have to roll it back.Vibhu: Part of it isswyx: also sometimes it can follow your s instructions too.Vibhu: It's somewhat a skill, right? So it determines when it uses the tools, right? Like it's not like it'll run outta every call.It'll determine when it wants to check quality score, right?Ryan Lopopolo: Yeah. And we do in the prompts we give these agents, allow them to push back,[00:13:51] Agent Code Review RulesRyan Lopopolo: When we first started adding code review agents to the pr, it would be Codex, CLI. Locally writes the change, pushes up a PR on [00:14:00] those PR synchronizations of review agent fires.It posts a comment. We instruct Codex that it has to at least acknowledge and respond to that feedback. And initially the Codex driving the code author was willing to be bullied by the PR reviewer, which meant you could end up in a situation where things were not converging. So yeah, we had to,swyx: he's just a thrash.Ryan Lopopolo: We had to add more optionality to the prompts on both of these things, right? The reviewer agents were instructed to bias toward merging the thing to not surface anything greater than a P two in priority. We didn't really define P two, but we gave it, youswyx: did define P two.Ryan Lopopolo: We gave it a framework within which to score its outputswyx: and then greater than P zero is worse, right?Yes. P two is very good.Ryan Lopopolo: P zero is you will mute the code place ifswyx: you merch thisRyan Lopopolo: thing, right?swyx: Yeah.Ryan Lopopolo: But also on the code authoring agent side, we also gave it the flexibility to either defer or push back against review feedback, right? This happens all the time, right? Like I happen to notice something and leave a code review, [00:15:00] which.Could blow up the scope by a factor of two. I usually don't mean for that to be addressed Exactly. In the moment. It's more of an FYI file it to the backlog, pick it up in the next fix it week sort of thing. And without the context that this is permissible, the coding agents are gonna bias toward what they do, which is following instructions.swyx: Yeah.[00:15:19] Autonomous Merging Flowswyx: I do wanted to check in on a couple things, right? Sure. All the coding review agent, it can merge autonomously. I think that's something that a lot of people aren't comfortable with. And you have a list here of how much agents do they do Product code and tests, CI configuration and release tooling, internal Devrel tools, documentation eval, harness review, comments, scripts that manage the repository itself, production dashboard definition files, like everything.Yes. And so they're just all churning at the same time, is there like a record that, that any human on the team pulls to stop everythingRyan Lopopolo: Because we are building a native application here. We're not doing continuous deploy. So there's still a human in the loop for cutting the release branch.I see. We require a blessed [00:16:00] human approved smoke test of the app before we promote it to distribution, these sort of things.swyx: So you're working on the app, you're not building like infrastructure where you have like nines of reliability, that kinda stuff?Ryan Lopopolo: That's correct. That's correct. Okay. And also like full recognition here that all of this activity took in a completely greenfield repository.There's. Should be no script that this applies generally toswyx: this is a production thing, you're gonna shipRyan Lopopolo: toswyx: customers. Of course. Yeah, of course. So this is realVibhu: And like one of the things there is, you mentioned you started this as a repo from scratch. The onboarding first month or so was pretty, it was like working backwards, right?Yeah. And then you had to work with the system and now you're at that point where you know, you're very autonomous. I'm curious like, okay, so what, how human in the loop is it? So what are the bottlenecks that you wish you could still automate? And part of that is also like, where do you see the model trajectory improving and offloading more human in the loop?We just got 5.4. It's a really good,Ryan Lopopolo: fantastic model, by the way.Vibhu: Yeah. Yeah. It's the first one that's merged. Top tier coding. So it's codex level coding and reasoning. So general reasoning both in one model. SoRyan Lopopolo: andVibhu: computer [00:17:00] use vision.Ryan Lopopolo: Now we now with five four, I can just have Codex write the blog post, whereas for this one I had to balance between chat.swyx: Oh, I need to, I might be out of a job. Oh my God.Ryan Lopopolo: Oh,swyx: I know. You just gave me an idea for a completely AI newsletter that five four could do. Yeah, I get it Now.Ryan Lopopolo: This sort of thing is just one example of closing the loop, right? Like the dashboard thing you mentioned. We have Codex authoring the Js ON, for the Grafana dashboards and publishing them and also responding to the pages, which means when it gets the page, it knows exactly which dashboards are defined and what alerts.What alert was triggered by which exact log in the code base. ‘cause all of this stuff is collated together.swyx: It has to own everything.Yes. Yeah. Yeah.Ryan Lopopolo: And it means that if we have an outage that did not result in a page. It has the existing set of dashboards available to it. It has the existing set of metrics and logs and can figure out where the gaps in the dashboard are or [00:18:00] in the underlying metrics and fix them in one go.In the same way, you would have a full stack engineer be able to drive a feature from the backend all the way to the front end.Vibhu: So it, it seems like a lot of the work you guys had to do was you as a small team are fully working for a way that the model wants the software to be written. It's like less human legible for better. Code legibility, agent legibility. How do you think that affects broader teams? So one at OpenAI, do liaison, like this is how software should be written. Like I can imagine, say you join a new team with this methodology, this mindset there's ways that, teams do code review, teams write code, like teams are structured and a lot of it is for human legibility.So should we all swap? Like how does this play back one broader into OpenAI and then like broader into the software engineering, right? Is it like teams that pick this up will it's pretty drastic, right? You have to make a pretty big switch. Should they just full send Yeah.Ryan Lopopolo: The mindset is very much that I'm removed from the process, right? I can't really have deep code level opinions about [00:19:00] things. It's as if I'm. Group tech leading a 500 person organization.Vibhu: Yeah.Ryan Lopopolo: Like it's not appropriate for me to be in the weeds on every pr. This is why that post merge code review thing is like a good analog here, right?Like I have some representative sample of the code as it is written, and I have to use that to infer what the teams are struggling with, where they could use help, where they're already moving quickly and I can pivot my focus elsewhere.Vibhu: Yeah.Ryan Lopopolo: So I don't really have too many opinions around the code as it is written.I do, however, have a command based class, which is used to have repeatable chunks of business logic that comes with tracing and metrics and observability for free. And the thing to focus on is not how that business logic is structured, but that it uses this primitive ‘cause I know that's gonna give leverage by default.Vibhu: Yeah.Ryan Lopopolo: Yeah, back to that sort of systems stinking,Vibhu: and you have part of that in your blog post, enforcing architecture and ta taste how you set boundaries for what's used. There's also a section on redefining [00:20:00] engineering and stuff, but yeah, it's just, it's interesting to hear,Ryan Lopopolo: and as the models have gotten better, they have gotten better at proposing these abstractions to unblock themselves, which again, lets me move higher and higher up the stack to look deeper into the future on what ultimately blocked the team from shipping.swyx: Yeah. You mentioned so you, this is primarily a, it is like a 1 million line of code base electron app. But it manages its own services as well, so it's like a backend for front end type thing.Ryan Lopopolo: We do have a backend in there, but that's hosted in the cloud.Yeah. This sort of structure is actually within the separate main and render processesWithin theswyx: electric.That's just how electronic works.Ryan Lopopolo: Yeah, of course. So have also treated like. MVC style decomposition with the same level of rigor, which has been very fun.swyx: I have a fun pun. This is a tangent, NVC is model view controller. Any sort of full stack web Devrel knows that.But my AI native version of this is Model view Claw, the clause the harness.Ryan Lopopolo: That's right. That's right. I do think that there is an interesting space to [00:21:00] explore here with Codex, the harness as part of building AI products, right? There's a ton of momentum around getting the models to be good at coding.We've seen big leaps in like the task complexity with each incremental model release where if you can figure out how to collapse a product that you're trying to build, a user journey that you're trying to solve into code, it's pretty natural to use the Codex Harness to solve that problem for you. It's done all the wiring and lets you just communicate and prompts to let the model cook.Yeah. It's been very fun. And there's also a very engineering legible way of increasing capabil. It's fantastic, right? Yeah. Just give you, just give the model scripts, the same scripts you would already build for yourself.swyx: Yeah.Yeah. So for listeners, this is Ryan saying that software engineering or coding against will eat knowledge work like the non-coding parts that you would normally think.Oh, you have to build a separate agent for it. No, start a coding agent and go out from there. Which open Claw has like it's pie Underhood.Ryan Lopopolo: [00:22:00] Yes.Vibhu: Basically define your task in code. Everything is a codingswyx: agent by the way. Since I brought it up, it's probably the only place we bring it up. Is any open claw usage from you?Any?Ryan Lopopolo: No. No. Not for me. I don't have any spare Mac Minis rattling around my house.swyx: You can afford it? No. I just, I'm curious if it's changed anything in opening eye yet, but it's probably early days. And then the other, the other thing I, I wanna pull on here is like you mentioned ticketing systems and you mentioned prs and I'm wondering if both those things have to go away or be reinvented for this kind of coding.So the git itself and is like very hostile to multi-agent.Ryan Lopopolo: Yeah. We make very heavy use of work trees.swyx: But like even then, like I just did a, dropped a podcast yesterday with Cursors saying, and they said they're getting rid of work trees ‘cause it still has too many merge conflicts.It's still un too un unintuitive. But go ahead.Ryan Lopopolo: The models are really great at resolving merge conflicts. Yeah. And to get to a state where I'm not synchronously in the loop in my terminal, I almost don't care that there are mergeswyx: with disposable.[00:23:00] Yeah.Ryan Lopopolo: We invoke a dollar land skill and that coaches codex to push the PR Wait for human and agent reviewers Wait for CI to be green.Fix the flakes if there are any merged upstream. If the PR comes into conflict, wait for everything to pass. Put it in the merge queue. Deal with flakes until it's in Maine. End. This is what it means to delegate fully, right? This is in a, very large model re probably a significant tax on humans to get PRS merged, but the agent is more than capable of doing this and I really don't have to think about it other than keep my laptop open.swyx: Yeah. I used to be much more of a control freak, but now I'm like, yeah, actually you could do a better job of this than me. Yeah. With the right context. Yes.[00:23:47] Encoding Requirementsswyx: Anything else in harness in general? Just this piece, I just wanna make sure we,Ryan Lopopolo: I think one thing that I maybe didn't make super clear in the article that I heard on Twitter as an interesting, that's respond [00:24:00]swyx: to them.What's the chatter and then what's your response?Ryan Lopopolo: Ultimately, all the things that we have encoded in docs and tests and review agents and all these things are ways to put all the non-functional requirements of building high scale, high quality, reliable software into a space that prompt injects the agent.We either write it down as docs, we add links where the error messages tell how to do the right thing. So the whole meta of the thing is to basically tease out of the heads of all the engineers on my team, what they think good looks like, what they would do by default, or what they would coach a new hire on the team to do to get things to merch.And that's why we pay attention to all the mistakes, mistakes that the agent makes, right? This is code being written that is misaligned with some as yet not written down, non-functional requirement.swyx: Sorry, what? Did the online people misunderstand orRyan Lopopolo: No,swyx: whatyouRyan Lopopolo: responded to? Somebody just literally said that.I was like, oh yeah,swyx: okay,Ryan Lopopolo: This is the [00:25:00] thing. This is what I've been doing. Oh, youswyx: agree? Yeah. I see. Interesting.Ryan Lopopolo: One other neat thing, which I did totally did not expect is folks were just. Taking the link to the article and giving it to pi or Codex and say, make my repo this,Vibhu: you achi a whole recursion.Ryan Lopopolo: And it was wildly effective. Really? It was wildly effective. NoVibhu: way. It just actually is something I tried with five, four yesterday. I didn't have time. Last time I was like out speaking of something, and this is one of my things, I was like, okay, I have this article. Can we just scaffold out what it would be like to run this?And I, I did it first as that and then I was like, okay, let me take another little side repo and say okay, if I was to fully automate this like this because I haven't written a line of code, it'sRyan Lopopolo: like over full, setVibhu: it right. The side thing I'm doing of voice. TTS I'm just like, slobbing out, whatever.It's nothing production. I'm like, how would I make this like this? And it's actually like a really good way. It's like a good way to learn what could be changed, what could be like, it's just a good analyzing, right? You give it all the codes, you give it all the context, you give it the article and it walks you through it very well.That's right. That's right.[00:25:57] Inlining Dependencies[00:25:57] Dependencies Going Away & Brett Taylor's Responseswyx: I guess one more thing before we go to Symphony is I wanted to cover [00:26:00] Brett Taylor's response. We had him on the show. He is your chairman, which is wild. Yeah. That he's reading your articles as well and like getting engaged in it. He says software dependencies are going away.Basically they can just be like vendored. Yes. Response.Ryan Lopopolo: Aswyx: hundred percent. A hundred percent agree. You still pro qr, you still pay Datadog. You still pay Temporal. Thank you.Ryan Lopopolo: Yep. The level of complexity of the dependencies that we can internalize is, I would say low, medium right now. Just based on model capability.What does the,swyx: what is medium?Ryan Lopopolo: I would say like a. A couple thousand line dependency is a thing that we could in-house No problem. Call in an afternoon of time. One neat thing about it is like probably most of that code you don't even need. Like by in-house and abstraction, you can strip away all the generic parts of it and only focus on what you need to enable the specific thing.Yes. You're building,swyx: I've been calling this the end of b******t plugins.Ryan Lopopolo: Yeah.swyx: Because there's so much when I published an open source thing, I want to accept everything, be liberal. I want to accept, this is post's law, but that means there's so much bloat. Yes. There's so much overhead.Ryan Lopopolo: One other neat thing about [00:27:00] this too is when we deploy Codex Security on the repo, it is able to deeply review and change. The internalized dependencies in a much lower friction way than it would be to like, push patches upstream, wait for them to be released, pull them down, make sure that's compatible with all the transitive I have in my repo and things like that.So it's also much lower friction to internalize some of these things if code is free. ‘cause the tokens are cheap sort of thing.swyx: Yeah. Yeah. I think like the only argument I have against this is basically scale testing, which obviously the larger pieces of software like Linux, MySQL, he calls up even the Datadog and Temporals and then maybe security testing where Yes.Classically, I think, is it linis tos, it said security open source is the best disinfectant.Ryan Lopopolo: Many eyes.swyx: Many eyes. And if inline your dependencies and code them up, you're gonna have to relearn mistakes from other people that Yep.Ryan Lopopolo: Yep. And to internalize that dependency, you're back to zero and you have to start.Reassembling all those bits and pieces to Yeah. Have [00:28:00] high confidence in the code as it is written. Yeah.Vibhu: Even part of the first intro of this, you basically mentioned like everything was written by codex, including internal tooling, right? So internal tooling, like when you're visualizing what's going on it's writing it for itself.swyx: Yeah. I'm built internal tools way I now, and like I just show them off and they're like, how long did you spend? And I didn't spend any time. I just prompted it,Ryan Lopopolo: very funny story here.swyx: Yeah, go ahead.Ryan Lopopolo: We had deployed our app to the first dozen users internally had some performance issues, so we asked them to export a trace for us get a tar ball, gave it to our on-call engineer, and he did a fantastic job of working with Codex to build this beautiful local Devrel tool, next JS app, the drag and drop the tar ball in, and it visualizes the entire trace.It's fantastic. Took an afternoon, but none of this was necessary. Because you could just spin up codex and give it the tar ball and ask the same thing and get the response immediately. So in a way, optimizing for human [00:29:00] legibility of that debugging process was wrong. It kept him in the loop unnecessarily when instead he could have just like Codex cooked for five minutes and gotten this same.swyx: Yeah, you verify your instincts here of this is how we used to do it. Or this is how I would have used to solve it.Ryan Lopopolo: Yeah. In this local observability stack. Like sure, you can de deploy Yeager to visualize the traces, but I wouldn't expect to be looking at the traces in the first place because I'm not gonna write the code to fix them.swyx: Yeah. So basically there needs to be like this kind of house stack and owning the whole loop. I think that is very well established. And it sounds like you might be like sharing more about that in the future, right?Ryan Lopopolo: Yeah. I think we're excited to do[00:29:36] Ghost Libraries Specs[00:29:36] Ghost Libraries & Distributing Software as SpecsRyan Lopopolo: We're gonna talk about Symphony in a little bit, but like the way we distribute it as a spec, which I think folks are calling Ghost Libraries on Twitter.This is like a such a cool name. It does mean it becomes much cheaper to share software with the world, right? You define a spec, how you could build your own specifying as much as is required for a coding agent to reassemble it [00:30:00] locally. The flow here is very cool. Like we have taken. All the scaffolding that has existed in our proprietary repo spun up a new one.Ask Codex with our repo as a reference. Write the spec. We tell it. Spin up a team ox spawn a disconnected codex to implement the spec. Wait for it to be done. Spawn another codex and another team ox to review the spec com or review the implementation compared to upstream and update the spec so it diverges less.And then you just loop over and over Ralph style until you get a spec that is with high fidelity able to reproduce the system as it is. It's fantastic.Vibhu: And you're basically, you're not really adding any of your human bias in there, right? That's correct. A lot of times people write a spec and be like, okay, I think it should be done this way, and you'll riff on something.And it's no, the agent could have just handled it like you're still scaffolding in a sense, right? I want it done this way. It can determine its spec better.swyx: That's right. That's right. Part of me it, I'm, I've been working a lot on evals recently, and part of me is wondering if [00:31:00] an agent can produce a spec that it cannot solve.Is it always capable of things that he can imagine or can you imagine things that it is impossible to do?Ryan Lopopolo: I think with Symphony, we, there's like this there's this axis where you have things that are easier, hard, or established or new, right? And I think things that are hard and new is still something that the models need humans.Yeah. Drive.swyx: Yeah. Yeah.Ryan Lopopolo: But I think those other quadrants are largely salt. Given the right scaffold and the right thing that's gonna drive the agent to completion,swyx: it's crazy that it solved,Ryan Lopopolo: but it means that the humans, the ones with limited time and attention get to work on the hardest stuff, like the problems where it's pure white space out in front. Or like the deepest refactorings where you don't know what the proper shape of the interfaces are. And this is where I wanna spend my time. ‘cause it lets me set up for the next level of scale.swyx: Yeah. Yeah. Amazing. Let's introduce Symphony.I think we've been mentioning it every now and then. Elixir. Interesting option.Ryan Lopopolo: Yeah.swyx: Yeah. I'm not,Ryan Lopopolo: again, like the [00:32:00] elixir manifestation here is just a derivative. Is it a modelswyx: chosen? Yeah.Ryan Lopopolo: Yeah. Yeah. And it chose that because the process supervision and the gen servers are super amenable to the type of process orchestration that we're doing here.You are essentially spinning up little Damons for every task that is in execution and driving it to completion, which. Means the mall gets a ton of stuff for free by using Elixir and the Beam.swyx: I had to go do a crash course in Beam and Elixir, and I think most people are not operating at that scale of concurrency where you need that.But it is a good mental model for Resum ability and all those things. And these are things I care about. But tell me the story, the origin story of Symphony. What do you use it for? Is this, how did it form maybe any abandoned paths that you didn't take?[00:32:46] Terminal Free Orchestration[00:32:46] Symphony: Removing Humans from the LoopRyan Lopopolo: At the end of December we were at about three and a half PRS per engineer per day.This was before five two came out in the beginning of January. Everyone gets back from holiday with five two and no other work [00:33:00] on the repository. We were up in the five to 10 PRS per day per engineer. And I don't know about y'all, but like it's very taxing to constantly be switching like that. Like I was pretty tapped out at the end of the day, again, where are the humans spending their time? They're spending their time context switching between all these active tmox pains to drive the agent forward.swyx: Yeah. No way. Yeah.Ryan Lopopolo: So let's again, build something to remove ourselves from the loop. And this is what frantic sprinted adapt here to find a way to remove the need for the human to sit in front of their terminal.So a lot of experimentation with Devrel boxes and, automatically spinning up agents, like it seems like a fantastic end state here, where my life is beach. I open live twice a day and say yes no to these things. Yeah. And this is again, a super, super interesting framing for how the work is done.Because I become more latency and sensitive. I have [00:34:00] way less attachment to the code as it is written. Like I've had close to zero investment in the actual authorship experience. So if it's garbage. I can just throw it away and not care too much about it. In Symphony, there's this like rework state where once the PR is proposed and it's escalated to the human for review, it should be a cheap review.It is either mergeable or it is not. And if it's not, you move it to rework. The elixir service will completely trash the entire work tree NPR and start it again from scratch. Okay. And this is that opportunity again to say, why was it trash right? What did the agent do that wasswyx: bad. Yeah.Ryan Lopopolo: Fix that before moving the ticket toswyx: endRyan Lopopolo: of progress again.swyx: Yeah. Why is this not in codex app? I guess this, you guys are ahead of Codex app,Ryan Lopopolo: yeah, so the way the team has been working is basically to be as AI pilled as possible and spread ahead. And a lot of the things we have worked on have fallen out [00:35:00] into a lot of the products that we have.Like we were in deep consultation with the Codex team to. Have the Codex app be a thing that exists, right? To have skills be a thing that Codex is able to use. So we didn't have to roll our own to put automations into the product. So all of our automatic refactoring agents didn't have to be these hand rolled control loops.It has been really fantastic to be, in a way, un anchored to the product development of Frontier and Codex and just very quickly try to figure out what works and then later find the scalable thing that can be deployed widely. It's been a very fun way to operate. It's certainly chaotic. I have lost track very often of what the actual state of the code looks like.‘cause I'm not in the loop. There was. One point where we had wired playwright directly up to the Electron app. With MCPM CCPs, I'm pretty bearish on because the harness forcibly injects all those tokens in the [00:36:00] context, and I don't really get a say over it. They mess with auto compaction. The agent can forget how to use the tool.There's probably only what three calls in playwright that I actually ever want to use. So I pay the cost for a ton of things. Somebody vibed a local Damon that boots playwright and exposes a tiny little shim CLI to drive it. And I had zero idea that this had occurred because to me, I run Codex and it's able to, it's oh, it's better.Yeah. Like no knowledge of this at all. Uhhuh.[00:36:30] Multi Human ChaosRyan Lopopolo: So we have had like in human space to spend a lot of time doing synchronous knowledge sharing. We have a daily standup that's 45 minutes long because we almost have to. Fan out the understanding of the current state.swyx: Yeah, I was gonna say this is good for a single human multi-agent, but multi human, multi-agent is a whole like po like explosion of stuff.Ryan Lopopolo: Yeah. And that this is fundamentally why we have such a rigid, like 10,000 [00:37:00] engineer level architecture in the app because we have to find ways to carve up the space so people are not trampling on each other.swyx: Sorry, I don't get the 10,000 thing. Did I miss that?Ryan Lopopolo: The structure of the repository is like 500 NPM packages.It's like architecture to the excess for what you would consider, I think normal for a seven person team. But if every person is actually like 10 to 50. Then the like numbers on being super, super deep into decomposition and sharding and like proper interface boundaries make a lot more sense.swyx: Yeah. To me, that's why I talked about Microfund ends and I, an anex is from that world, but Cool. It is just coming back to, to, to this I dunno if you have other, thoughts on. Orchestrating so much work coin going through this. Is this enough? Is this like any aha moments?Vibhu: It'll be interesting to see like where, okay, so right now you pick linear as your issue tracker, right?swyx: Or it's like a is it actually linear? This is actually linear.[00:37:55] Linear vs Slack WorkflowVibhu: Oh, that's linear. It's linear.swyx: Oh I never looked atVibhu: video. The demo video I had to download to [00:38:00] run.swyx: So I, because I'm a Slack maxie, but Yeah, linear. Linear is also really good. Yes,Ryan Lopopolo: we do make a good use of Slack. We we fire off codex to do all these lotion, elasticity, fix ups, the things that like sync that knowledge into the repository.It's super cheap. Yeah.swyx: Yeah.Ryan Lopopolo: Just do it in Codex.swyx: My biggest plug is OpenAI needs to build Slack. You need to own Slack. Build yours. Turn this into Slack.Ryan Lopopolo: I did read about it. Youswyx: did?Ryan Lopopolo: Yeah.[00:38:25] Collaboration Tools for AgentsRyan Lopopolo: I would say that if we think that we want these agents to do economically valuable work, which is like this is the mission, right?We want AI to be deployed widely, to do economically valuable work, then we need to find ways for them to naturally collaborate with humans, which means collaboration tooling, I think, is an interesting space to explore.swyx: Yeah, totally. Yeah. GitHub, slack, linear.Vibhu: Yeah, that was my thing. Okay, where do we see right now Codex has started Codex Model, then CLI, now there's an app, app can let me shoot off multiple Codex is in parallel, but there's no great team collaboration for Codex.And it [00:39:00] seems like your team had some say into what comes out, right? So you talked to ‘em, codex kind of was a thing. From there, if you guys are on the bound, what stuff that like, you might not focus on, but what do you expect other people to be building, right? So people that are like five x 50 Xing.Should you build stuff that's like very niche for your workflow, for your team? Should it be more general so other people can adopt? Is there a niche there? ‘Cause part of it is just okay, is everything just internal tooling? Do we have everything our own way? Like the way our team operates has our own ways that we like to communicate or is there a broader way to do it?Is it something like a issue tracker? Just thoughts if you wanna riff on that.[00:39:35] Standardizing Skills and CodeRyan Lopopolo: I think TBD we have not figured this out in a general way. I do think that there is leverage to be had in making the code and the processes as much the same as possible. If you think that code is context, code is prompts, it's better from the agent behavior perspective to be able to look in a package in directory X, Y, Z, and it not to have to page so [00:40:00] deeply into directory if you C, because they have the same structure, use the same language, they have the same patterns internally.And that same like leverage comes from aligning on a single set of skills that you're pouring every engineer's taste into to make sure that the agent is effective. So like in our code base, we have, I think, six skills. That's it. And if some part of the software development loop is not being covered, our first attempt is to encode it in one of the existing setup skills, which means that we can change the agent behavior.Yeah. More cheaply than changing the human driver behavior.swyx: Yeah.[00:40:39] Self Improvement via Logsswyx: Have you ever, have you experimented with agents changing their own behavior?Ryan Lopopolo: We do.swyx: Yeah. Or parent agent changing a subagents, behavior or something like that.Ryan Lopopolo: We have some bits for skill distillation. So for example, there's one neat thing you can do with Codex, which is just point it at its own session logs to ask it to tell you how you can use [00:41:00] the tool pedal better.swyx: It's like introspectionRyan Lopopolo: or ask it to do things. I useVibhu: this session better. What skills should Iswyx: high? I like the modification of, you can do, just do things to you can just ask agent to do things.Ryan Lopopolo: Yeah. You can just codex things. This is like a, this is like a silly emoji that we have, right? You can just codex things, you can just prompt things.It's really glorious future we live in, but okay, you can do that one-on-one. But we're actually slurping these up for the entire team into blob storage and. Running agent loops over them every day to figure out where as a team can we do better and how do we reflect that back into the repositories?Yes, though everybody benefits from everybody else's behavior for free. Same for like PR comments, right? These are all feedback. That means the code as written, deviated from what was good, a PR comment, a failed build. These are all signals that mean at some point the agent was missing context. We gotta figure out how toswyx: Yeah.Ryan Lopopolo: Slurp it up and put it back in the reboot.swyx: By the way, I do this exactly right. I used to, when I use cloud code for [00:42:00] knowledge work, cloud cowork is like a nice product, right? Yes. In I think you would agree. I always have it tell me what do I do better next time? And that's the meta programming reflection thing.So I almost think like you have six reflection extraction levels in symphony and almost like the zero of layer. So the six levels are PO policy, configuration, coordination, execution, integration, observability. We've talked about a couple of these, but the zero layer is like the, okay, are we working well?Can we improve how we work? Yes. Can I modify my own workflow without MD or something? I don't know.Ryan Lopopolo: Yeah, of course. Yeah, of course you can. Like this thing is also able to cut its own tickets ‘cause we give it full access.Yeah. Make it a ticket to have it cut. Tickets you can.Put in the ticket that you expect it to file as on follow up work,swyx: like Yeah. Self-modifying. Yeah.Ryan Lopopolo: Yeah.[00:42:44] Tool Access and CLI FirstRyan Lopopolo: Put, don't put the agent in a box. Give the agent full accessibility over it. Domain.swyx: I had a mental reaction when you said don't put the agent in a box. So I think you should put it in a box. Like it's just that you're giving the box everything it needs.Ryan Lopopolo: Yeah. Context and tools.swyx: But we're like, as developers, we're used to calling [00:43:00] out to different systems, but here you use the open source things like the Prometheus, whatever, and you run it locally so that you can have the full loop. I assume.Ryan Lopopolo: Yep.Vibhu: I think likeRyan Lopopolo: another, you wanna minimize cloud, cloud dependencies.Vibhu: You also want to make sure that you think about what the agent has access to. What does it see? Does it go back into the loop, like from the most basic sense of you let it see its own like calls, traces it can determine where it went wrong. But are you feeding that back in? So you know, just the most basic level of you wanna see exactly what's input output, like does the agent have access to.What is being outputted, right? It can self-improve a lot of these things. It's allRyan Lopopolo: text, right? My job is to figure out ways to funnel text from one agent to the other.swyx: It's so strange like way back at the start of this whole AI wave Andre was like, English is the hottest day programming language.It's here, it's just Yeah. The feature as well.Vibhu: A lot of, okay. Like a lot of software, a lot of stuff. There's a gui, it's made for the human. We're seeing the evolution of CLI for everything, right? All tools have CLIs. Your agents can use [00:44:00] them well, do we get good vision? Do we get good little sandboxes?Like right now? It's a really effective way, right? Models love to use tools. They love the best. They love to read through text. So slap a CLI let it go loose. That works for everything.Ryan Lopopolo: It does. Yeah. Yeah.[00:44:14] UI Perception and RasterizingRyan Lopopolo: We've also been adapting nont, textual things to that shape in order to improve model behavior in some ways, right?We want the agent to be able to see the UI agents do not perceive visually in the same way that we do. They don't see a red box, they see red box button, right? They see these things in latent space. So if we want, Hey, yeah, I do. We haveswyx: a ding if that goes off every time. Alien spaceRyan Lopopolo: ding.Anyway if we wanna actually make it see the layout, it's almost easier to rasterize that image to ask EOR and feed it in to the agent. Ha. And there's no reason you can't do both, right? To like further refine how the model perceives the object it's [00:45:00] manipulating.swyx: Cool. Could we, you wanna talk about a couple more of these layers that might bear more introspection or that you have personal passion for?[00:45:07] Coordination Layer with ElixirRyan Lopopolo: I will say that the coordination layer here was a really tricky piece to get right.swyx: Let's do it. Yep. I'm all about that. And this is Temporal core.Ryan Lopopolo: This is where when we turn the spec into Elixir, where like the model takes a shortcut, right? Like it's oh, I have all these primitives that I can make use of in this lovely runtime that has native process supervision.Which is I think, a neat way to have taken the spec and made it more choices achievable by making choices that naturally mapswyx: Yeah.Ryan Lopopolo: To the domain, right? In the same way that like you would prefer to have a TypeScript model repo if you are doing full stack web development, right? Because the ability to share types across the front end and backend reduces a lot of complexity.And becauseswyx: that's what graph kill used to be.Ryan Lopopolo: That's right. Andswyx: I don't know if it's still alive, butRyan Lopopolo: [00:46:00] no humans in the loop here. So like my own personal ability to write or not write elixir. Doesn't really have to bias us away from using the right tool for the job. It is just wild.swyx: Love it. I love it.Yeah. I wonder if any languages struggle more than others because of this? I feel like everyone has their own abstractions. That would make sense. But maybe it might be slower, it might be more faulty where like you'd have to just kick the server every now and then. I, I don't know. I think observability layer is really well understood.Integration layer, CP is dead. I think all these just like a really interesting hierarchy to travel up and down. It's common language for people working on the system to understandRyan Lopopolo: The policy stuff is really cool, right? Yeah. You don't really have to build a bunch of code to make sure the system wait for the, to passswyx: it's institutional knowledge.Ryan Lopopolo: Yeah. You just give it the G-H-C-L-I with some text that say CI has to pass. It makes the maintenance of these systems a lot easier.[00:46:57] Agent Friendly CLI Outputswyx: Do you think that CLI maintainers need to be [00:47:00] do anything special for agents or just as is? It's good because like I don't think when people made the G GitHub, CLI, they anticipated this happening.Ryan Lopopolo: That's correct. The GH CLI is fantastic. It's great super industry.swyx: Everyone go try GH repo create GH pull and then pull request number, right? GH HPR, like 1 53, whatever. And then it like pullsRyan Lopopolo: basically my only interaction with the GitHub web UI at this point is GH PR view dash web.Exactly. Glanceswyx: at the diffRyan Lopopolo: and be like Sure thing. Send it. Yeah. But the CLI are nice ‘cause they're super token efficient and they can be made more token efficient really easily. Like I'm sure you all have seen like I go to build Kite or Jenkins and I could just get this massive wall of build output.And in order to unblock the humans, your developer productivity team is almost certainly gonna write some code that parses the actual exception out of the build logs and sticks it in a sticky note at the top of the page. And you basically [00:48:00] want CLI to be structured in a similar way, right? You're gonna want to patch dash silent to prettier because the agent doesn't care that every file was already formatted.Just wants to know it's either formatted or not. So it can then go run a right command. Similarly, like in our PNPM distributed script runner, when we had one, when you do dash recursive, like it produces a absolute mountain of text. But all of that is for passing. Test suites. So we ended up wrapping all of this in another scriptswyx: to suppress the,Ryan Lopopolo: which you can vibe the channel only output the failing parts of the tests.swyx: You make a pipe errors versus the standard, standard out. I don't know. Okay. Whatever. Too much thinking have to do that. The CII used to maintain SCLI for my company and yeah, this is like core, very core to my heart. But you're vibing my job.Ryan Lopopolo: That's right.swyx: Cool. Any other things?This is a long spec. [00:49:00] I appreciate that. It's got a lot of strong opinions in here. Any other things that we should highlight? I think obviously you can spend the whole day going through some of these, but I do think that some of these have a lot of care or some of this you might wanna tell people, Hey, take this, but, make it your own.[00:49:15] Blueprint Spec and GuardrailsRyan Lopopolo: Fundamentally, software is made more flexible when it's able to adapt to the environment in which it is deployed, which means that things like linear or GitHub even are specified within the spec, but not required pieces of it. There's like a more platonic ideal of the thing that you could swap in like Jira or Bitbucket, for example.But being able to tightly specify things like the ID formats or how the Ralph Loop works for the individual agents. Basically means you can get up and running with a fully specified system quickly that you then evolve later on. I think we never intended for this to be a static spec that you can [00:50:00] never change.It's more like a blueprint to get something worth a starting point up and running.swyx: Yeah.Ryan Lopopolo: For you then to vibe later to your heart's content,swyx: you have like code and scripts in here where it's oh, I think this is a really good prompt. It's just a very long prompt.Ryan Lopopolo: Fundamentally, the agents are good at following instructions, so give them instructions.And it will, improve the reliability of the result. We, much like the way we use Symphony, we don't want folks to have to monitor the agent as it is vibing the system into existence. So being very opinionatedVery strict around what these success criteria are means that our deployment success rate goes up. Yeah. It means we don't have to get tickets on this thing.Vibhu: Think it all goes back to that like code to disposable, right? Like early on when you had CLI or you'd kick off a Codex run, it would take two hours. You would wanna monitor okay, I'm in the workflow of just using one.I don't want it to go down the wrong path. I'll cut it off and, just shoot off four, like that was my favorite thing of the Codex app, right? Yeah. Just Forex it like, [00:51:00] it's okay. One of them will probably be right, one of them might be better. Stop overthinking it. Like my first example was probably like deep research.When you put out deep research and I'd ask it something like, I asked it something about LLM, it thought it was legal something and spent an hour, came back with a report completely off the rails. And I was like, okay, I gotta monitor this thing a bit. No don't monitor it. Just you want to build it so it's that it, it goes the right way.And you don't wanna, you don't wanna sit there and babysit, right? You don't want to babysit your agentsRyan Lopopolo: with that deep research query that you made. Looking at the bad result, you probably figured out you needed to tweak your prompt Yeah. A bit, right? That's that guardrail that you fed back into the code base for the task, your prompt to further align the agent's execution.Same sort of concept supply there too.swyx: When you talk, how are the customers feelingRyan Lopopolo: for Symphony? I think we have none, right? This is a thing we have put out into theswyx: world. Symphony's internal, right? As long as you are happy, you are the customer. That'

Recorded live in London at the Barbican Centre earlier this month, this episode marks the publication of Order Prevails in Berlin, a new essay by the Italian novelist Vincenzo Latronico that acts as an autobiographical key to his highly acclaimed and Booker Prize-shortlisted novel Perfection. Published by the Architecture Foundation and translated by Sophie Hughes, Order Prevails in Berlin is available now via the AF's online shop.Scaffold is an Architecture Foundation production, hosted by Matthew Blunderfield. Download the London Architecture Guide App via the App Store or Google PlayBecome an Architecture Foundation Patreon member and be a part of a growing coalition of architects and built environment professionals supporting our vital and independent work. Hosted on Acast. See acast.com/privacy for more information.

Riley has been driven insane by a… company hinging on a single Australian man that appears to be bamboozling the British State with complex financial chicanery, and now you all have to hear the story of how NScale started out as a landlord for bitcoin miners and became the government's best hope for a “Sovereign AI” but that has only a scaffolding yard to its name. Except it also doesn't own the scaffolding yard either. If you want to hear more bonus episodes like this one, consider signing up on our Patreon! TF Merch is still available here! *MILO ALERT* Check out Milo's tour dates here: https://www.miloedwards.co.uk/liveshows Trashfuture are: Riley (@raaleh), Milo (@Milo_Edwards), Hussein (@HKesvani), Nate (@inthesedeserts), and November (@postoctobrist)

Riley has been driven insane by a… company hinging on a single Australian man that appears to be bamboozling the British State with complex financial chicanery, and now you all have to hear the story of how NScale started out as a landlord for bitcoin miners and became the government's best hope for a “Sovereign AI” but that has only a scaffolding yard to its name. Except it also doesn't own the scaffolding yard either.   Get the whole episode on Patreon here!   TF Merch is still available here! *MILO ALERT* Check out Milo's tour dates here: https://www.miloedwards.co.uk/liveshows Trashfuture are: Riley (@raaleh), Milo (@Milo_Edwards), Hussein (@HKesvani), Nate (@inthesedeserts), and November (@postoctobrist)

In this episode, co-hosts Alex Quigley and Corinne Settle (EEF's Teaching and Learning Specialist) discuss the implementation of metacognition strategies. Experts and practitioners from various phases and subject areas join us to unpack these approaches, exploring what they look like in practice and the impact they have on learners. Guest speakers: Dr Beverley Jennings (EEF Programme Manager) Tom Colquhoun (Director of Somerset Research School and Assistant Headteacher at The Blue School, Wells) BlueSky: @somersetrs.bsky.social; Instagram: @somersetresearchschool; LinkedIn: https://uk.linkedin.com/in/somerset-research-school-134400386 Emily Smeaton (Director of North Yorkshire Coast Research School and Lecturer in ITE at York St John University) X: @NYCResearchSch; LinkedIn: https://www.linkedin.com/company/north-yorkshire-coast-research-school Further resources:  Education Endowment Foundation (2024) Metacognition and Self-regulated Learning: Guidance Report. London: Education Endowment Foundation. Available at: https://educationendowmentfoundation.org.uk/education-evidence/guidance-reports/metacognition - Education Endowment Foundation (2024) ‘Updated EEF guide to metacognition and self-regulation', EEF News, 21 November. Available at: https://educationendowmentfoundation.org.uk/news/updated-eef-guide-to-metacognition-and-self-regulation Resources: EEF's Metacognitive strategies EEF's Scaffold pupil's use of metacognition EEF's Promoting metacognitive talk Transcript: Metacognition: Moving forward with new evidence | Transcript  

You think you've seen it all before, perched on top of the wobbly commentary gantry at the Chigwell Construction Stadium... and then West Ham deliver those last 10 minutes against Brighton. Chloe and Rachel saw all the drama in the flesh and reflect on it all. What a relegation battle we've got on our hands!But first off, there's the small matter of Arsenal beating the league leaders Manchester City to continue the Renéeformation and at long, long last just going direct with Olivia Smith up top. We also discuss Chelsea's less than convincing win against Spurs and what the departure of their influential head of football means for the club moving forward. And Madonna rocks up to a WSL game! But we're not Hung Up on it...Follow us on X, Instagram, TikTok and YouTube! Email us show@upfrontpod.com.For ad-free episodes and much more from across our football shows, head over to the Football Ramble Patreon and subscribe: patreon.com/footballramble.**Please rate and review us on Apple, Spotify or wherever you get your pods. It means a lot and makes it easy for other people to find us. Thank you!** Hosted on Acast. See acast.com/privacy for more information.

Hello Interactors,Minnesota has seen federal incursion and overreach before. And not just in 2020. These removal tests we're witnessing are rooted in the premise of US ‘manifest destiny' and how quickly the notion of ‘home' can be made fungible by a violent state. But likeminded bodies always resist being bullied.SCAFFOLD, SOVEREIGNTY, AND SEIZUREOn December 26, 1862, during the Civil War, President Abraham Lincoln authorized the hanging of 38 Dakota men in Mankato, Minnesota. The execution, staged as public theater, was not a solemn judicial act. A special scaffold was built, martial law was declared, and an estimated 4,000 spectators witnessed the largest mass execution in U.S. history. The spectacle mattered because it carried meaning beyond Mankato. The hanging marked the end of the six-week U.S.–Dakota War of 1862. This brutal conflict devastated the Minnesota River Valley and left deep trauma in Dakota communities. It also conveyed that the state could swiftly and effectively attempt control of contested land by violent force.Mankato was the visible climax, but Fort Snelling was the quieter cruelty that continued. After the war, Dakota families — women, children, elders — were confined in harsh conditions near the fort during the winter of 1862–63. Disease and exposure killed between 130 and 300 Dakota people. Execution and exile worked together. One provided public power, the other attempted to ensure territorial outcomes.Here's what Dakota Chief Wabasha's son-in-law, Hdainyanka, wrote to him shortly before his execution:“You have deceived me. You told me that if we followed the advice of General Sibley, and gave ourselves up to the whites, all would be well; no innocent man would be injured. I have not killed, wounded or injured a white man, or any white persons. I have not participated in the plunder of their property; and yet to-day I am set apart for execution, and must die in a few days, while men who are guilty will remain in prison. My wife is your daughter, my children are your grandchildren. I leave them all in your care and under your protection. Do not let them suffer; and when my children are grown up, let them know that their father died because he followed the advice of his chief, and without having the blood of a white man to answer for to the Great Spirit.”This moral failing was part of a larger burgeoning political economy. In 1862, the Twin Cities were still emerging, with mills, river commerce, and infrastructure. Yet the region's future as an urban, financial, and political center depended on converting Dakota and Ojibwe homelands into transferable property. The spring prior to the massacre, in May 1862, Lincoln signed the Homestead Act, handing out 160-acre chunks of stolen land labeled now as “public.” Colonizers and immigrants could occupy this land, and be defended by the US government, if they showed they could “improve” it through five years of occupation.This act negated all Dakota treaties, seized 24 million acres of Minnesota lands, and mandated removal of what were now called Dakota “outlaws.” This converted communal Indigenous homelands into surveyed “public domain” eligible for homesteading, auctions, and rail grants, directly feeding wheat production for Minneapolis mills. Speculators and railroads exploited the act via proxy filings, reselling “cleared” parcels at profit to European immigrants.By 1870, non-Native population surged from 172,000 to over 439,000. The “clearing” of land was not metaphorical. It was the prerequisite for surveying, fencing, settlement, rail corridors, and the wider commodity circuits that would bind the Upper Midwest to national and global markets.That is what Harvard historian Sven Beckert calls war capitalism. He argues that global capitalism's ascent was not a clean evolution toward free exchange. It relied on coercion, conquest, and violence. As his book on the history of Capitalism lays out, state funded war capitalism fundamentally relied on slavery, the dispossession of Indigenous peoples, imperial expansion, armed commerce, and the imposition of sovereignty over both people and territory. In this framing, the Dakota and Ojibwe were obstacles to industrialization and commodification. The frontier needed to be safe for settlement and investment of Germans, Irish, and Scandinavians, as well as railroads and industry. This included these two flour mills, the world's largest by 1880: General Mills and Pillsbury.The gallows in Mankato were the blunt instrument that made the state-capital alliance credible. The point was not only to punish alleged crimes, but to demonstrate a capacity and will to kill. The American state needed to show it could override Indigenous sovereignty and reorder space. The subsequent removals and confinement at Fort Snelling completed the transformation. “Home” was recoded from relationship into asset. This land was no longer lived geography but extractable territory, from stewarding real soil to the selling of real estate.TOPHOPHILIA, TIES, AND TENSIONSWar capitalism is not merely to punish resistance, but to convert a lived place into a fungible asset. But violence plays a deeper role than just legal rearrangement. It has to break this constant of human life: our attachment to place.Behavioral geographer Yi-Fu Tuan borrowed the term topophilia to describe this attachment — the “affective bond between people and place or setting.” The phrase can sound soft and sentimental but it can also cause friction in projects of political economy.The state may be able to abolish or rewrite a treaty, redraw a border, rename a river, and issue new deeds, but it still confronts bodies that have been oriented by firm ground. It's on these grounds that paths are walked, food gathered, relatives buried, stories anchored to landmarks, and seasonal rhythms internalized as a habit of life. The obstacle is embedded and embodied in the physiology, including cognitive, and grounds to location.Modern neuroscience gives a concrete account of how place becomes part of a person. The hippocampus plays a central role in spatial memory and navigation, and research on place cells shows that hippocampal neurons fire in relation to specific locations in an environment. Familiar surroundings are not only around us they are within us. The brain builds spatial scaffolding that links location to memory, routine, prediction, and emotional regulation.When cognition is tied to the specificity of place, it becomes hard for a parcel to be made equivalent to another. Commodification demands interchangeability. A home cannot easily be made equivalent to another home when it's part of the nervous system — not quickly, not cleanly, and often not at all. When the state-capital alliance imagines territory as a grid of extractable value, it is implicitly trying to override how humans experience territory. That is why “simple” displacement so often produces disproportionate harm. Psychiatrist Mindy Fullilove coined the term root shock to describe the traumatic stress that follows the destruction of one's “emotional ecosystem.” Root shock is not only grief or nostalgia. It is a stress response to the sudden loss of the social and spatial cues that stabilize daily life. The shredding of a mesh of relationships, routines, and meanings embedded in a neighborhood or homeland.The root shock of the state violence of 1862 was not just incidental to the project of transformation. It was structurally necessary. If topophilia is a biological and psychological anchor, then a purely legal or economic strategy (bureaucratic coercion) will often be insufficient because the anchor of topophilia holds. To clear land at speed and scale, the state reaches for tools that can sever attachment abruptly. Public executions, mass incarceration, forced marches, and exile doesn't just relocate people. They're violent attempts to scramble the conditions under which people can remain attached at all. It transforms topophilia into vulnerability.Work on social exclusion and “social pain” helps explain why. In a widely cited fMRI study, Naomi Eisenberger and colleagues found increased activity in the anterior cingulate cortex during experiences of exclusion. This parallels patterns seen in physical pain studies where distress is tracked with painful activities. The point is not that social threat is “just like” physical injury, but that the brain treats social severing as a serious alarm condition. It's something that demands attention, vigilance, and behavioral change to overcome.ROOTS, RESISTANCE, AND REPAIRTopophilia doesn't end with the so-called frontier or attempts at ‘removing' its inhabitants. It reappears wherever people form durable bonds. That includes the streets and schools, churches and parks, language, kin, and the local economies and cultures war capitalism eventually built. The Dakota and Ojibwe were never “removed” in any final sense. Many live and organize in and around the Twin Cities today.In South Minneapolis, the Indigenous Protector Movement, a biproduct of the American Indian Movement, works out of the American Indian Cultural Corridor along Franklin Avenue — an immediate target for ICE. The protectors made their presence known as a form of ongoing place-based care and defense. It is a living archive of tactics for defending attachment under pressure through direct action, community building, patrols, and the mundane discipline of showing up. What it offers is not merely a critique of state violence, but vigilance without spectacle, care without permission, and solidarity as a daily habit rather than a momentary sentiment.Other areas of Minneapolis show how when federal enforcement turns public space into a zone of uncertainty, topophilic neighbors often respond by adopting exactly those same “weapons” of persistence — care, documentation, rapid communication, mutual aid — that have long characterized Indigenous resistance and slavery abolitionist networks.Standing Rock, where the Standing Rock Sioux Tribe and allies gathered in 2016 to oppose the Dakota Access Pipeline, demonstrated how quickly infrastructure can scale when a place becomes a shared object of defense.The #NoDAPL movement assembled a broad coalition of Indigenous nations and allies, over 200 tribes, alongside legal support, medical care, and communications systems designed to withstand state patience. The 2020 George Floyd uprising in Minneapolis also revealed how love of place can become a platform for organized care rather than retreat. Alongside protest, residents built mutual-aid channels, street-medic networks, food distribution, and neighborhood defense efforts that treated the city as an emotional ecosystem worth repairing. What looked to outsiders like spontaneous eruption was, on the ground, a rapid layering of roles that included medics, legal observers, supply runners, translators, and de-escalators. This ecology of participation made it possible for large numbers of people to act without centralized command.Social psychology helps explain why these movements generate allies rather than only sympathizers. One key concept is collective efficacy — the combination of social cohesion and a shared willingness to intervene for the common good. It blossoms when people repeatedly see each other act, learn local norms of mutual obligation, and build trust that intervention will be supported rather than punished. All rooted in topophilia.Place attachment can bridge boundaries that would otherwise keep people separate. Work in community psychology and planning shows that place attachment and meaning can support participation and collective engagement, especially when development or coercion threatens everyday life. In other words, topophilia is not just private feeling. When it's under threat it can become public motive and an engine for coalition.The coalition in Minneapolis is being characterized by the federal government as terrorists. This borrows from a long history of resistance to violence because war capitalism has never been only domestic. The United States and its allies refined coercive governance overseas through night raids and “capture-or-kill” operations in Afghanistan, midnight house raids in Iraq, and broader militarized campaigns that treat homes as “searchable terrain” and communities as “intelligence environments.”Many of the officials, contractors, and voters who authorized or normalized these methods rarely imagined the same atmosphere of violent seizure in their neighborhood. As unimaginable as it may be watching unmarked vehicles, sudden detentions, and public uncertainty coming to American streets — used against the very citizens and taxpayers who fund such operations — it's not to those victims overseas in places like Afghanistan, Iraq, Palestine, or even inner city America.That return is what the poet and politician Aimé Césaire called the “imperial boomerang” effect, the idea that techniques tolerated in peripheral countries can come home to roost. In the U.S., the boomerang has long “landed” first on people of color. It emerges through surveillance and disruption campaigns like the two decades of the covert and illegal COINTELPRO program where the FBI targeted counterculture groups of the so-called New Left.Or the “Palmer Raids” of 1919 and 1920 targeting largely Italian and Eastern European Jewish immigrants and their left-leaning politics. These led to riots in 30 US cities and culminated in the bombing of the home of A. Mitchell Palmer, the US attorney general. These programs all reflect the notion that war can come home — just look at the increased militarizing of policing complete with SWAT tactics. And the same history that produced the scaffold of war capitalism of the past also produced reservoirs of resistance we see here and now. When neighbors anywhere respond to incursions not only with fear but with organized vigilance and material support, they are adapting older strategies of care found in Indigenous, abolitionist, and other movement-based defenses of people and places against infiltration, intimidation, and attempted violent removal.We can see how war capitalism endures. Mankato's 1862 gallows aimed to clear Dakota homelands of their people for homesteading, rails, and mills. Meanwhile, today's Operation Metro Surge includes thousands of federal agents raiding Minneapolis homes and streets, attempting to sever immigrant attachments to allegedly enforce labor control and national security. These militarized spectacles of warrantless entries, tear gas, and shootings echo what Beckert has uncovered. They treat people and place as obstacles to commodification rather than roots of stewardship.Yet topophilia also persists. These cross cultural rapid-response networks are not new to these lands, even though the US government tried to erase them centuries ago. The inspiring actions we see in Minneapolis reflect the values of compassion, positiveness, and respect for all relatives with neighborly solidarity that the first occupants of that land embraced. They're now woven with their allied 21st century neighbors in common and shared resistance. As best expressed here by Indigenous studies and political ecology scholar Melanie Yazzie. (and the longer version here) Minneapolis, like those acts of resistance in the nearby Dakotas, enacts and rehearses an alternative form of civil governance that centers mutual obligation over coercion and extraction. It shows how cities can survive the strain and stay alive — not through fear and gain, but through care that grounds and sustains. This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit interplace.io

The graphic designer John Morgan passed away last September at the age of 52.His final book, Baskerville's Teardrop Explodes, was published this week, and to mark the occasion we've collected som reflections on Morgan and his work from some of his collaborators. These include, in order of appearance, Tom Weaver former editor of the AA files, Shumi Bose and Kieran Long, who both worked with Morgan on the 2012 Venice architecture Biennale, Ros Barr, who worked with Morgan on a altar design for St Augustine's Church, Nick Hill, who was designing Morgan's new studio before he passed away, and Tom Emerson, a director of 6a architects whose collaborations with Morgan extend across many years and projects. You'll note this list is relatively narrow and hews closely to the world of architecture. The more interviews we collected, the more we realised the scope of this memorial episode risked expanding into an entire series - there are so many people who've been changed by Morgan and his work, to say nothing of his students and studio colleagues and publishers, none of whom are featured here. This following voices are just a drop in the bucket in terms of conveying who John was and the influence he had. Scaffold is an Architecture Foundation production, hosted by Matthew Blunderfield. Download the London Architecture Guide App via the App Store or Google PlayBecome an Architecture Foundation Patreon member and be a part of a growing coalition of architects and built environment professionals supporting our vital and independent work. Image credit: The Picture of Dorian Gray, Four Corners Books, 2007Photo: Michael Harvey © John Morgan studio Hosted on Acast. See acast.com/privacy for more information.

Why can smart kids explain everything yet can't get started? The Executive Function Trap reveals how dysregulated brains block task initiation. Dr. Roseann Capanna-Hodge, creator of Regulation First Parenting™, helps parents calm the brain and restore executive skills.Ever watched your smart child know everything about black holes—but freeze at putting on their shoes or starting homework? It's frustrating, confusing, and can feel impossible to fix. You're not imagining it—and it's not laziness. There's a real reason bright kids struggle with starting and finishing tasks: executive function challenges.In this episode, we unpack why executive function deficits often masquerade as disobedience, defiance, or lack of motivation. You'll learn what these core executive function skills are, why task initiation often fails in dysregulated brains, and practical, science-backed strategies to support your child's success in school and everyday life.Why does my child freeze even when they're so smart?Smart kids often know the content—they just can't see the path from start to finish. Their prefrontal cortex struggles with task initiation and planning ahead, creating what I call the executive function trap.Visualize the end goal: Help your child picture the completed task.Break tasks into small, concrete steps: 3–5 micro-steps instead of overwhelming lists.Use movement and gestures: Activate visual and motor pathways to strengthen memory and planning.Real-Life ExampleMilo could explain black holes in depth but couldn't start homework. Once we taught him to see the finished project and work backward, he could initiate tasks without panic.How can I teach executive function skills at home?Executive function isn't fixed—these key skills can be developed over time with consistent practice. Think of it like learning to cook a new recipe: you visualize the final dish, then reverse engineer the steps.Scaffold the first steps without creating dependence.Encourage cognitive flexibility and impulse control by offering choices within structured limits.Use visual schedules, sticky notes, or body doubling to support working memory.Parent Tip: Cue the nervous system to regulate first—if your child is dysregulated, no executive function strategy will stick.Try Quick CALM for a quick regulation reset before tackling tasks.What's the first executive function skill to address?The single most impactful skill is task initiation. Without the ability to start, even the most intelligent child can feel paralyzed. By teaching children to:Imagine the end resultWork backward through the steps

Commentary by Dr. Jian'an Wang.

In part 2 of Kenneth Frampton's Scaffold interview, we focus on his own experiences - from his early desire to become a farmer, and the long hesitation that kept him from starting a family, and his regrets around leaving architectural practice for a life of writing. These biographical threads are woven through his encounters with key thinkers – from Herbert Marcuse and Tomas Maldonado to Juhani Pallasmaa and Hannah Arendt – and with buildings like Corringham and Aalto's Villa Mairea and the transformation in perspective they represent.The discussion moves between the question of anti-capitalist architecture, the inundation of images in contemporary life, and the importance of what Frampton calls the microcosmos – architecture as the creation of “a small world” where society can begin to recognise itself. Along the way, Frampton reflects on what it might mean not to separate the reality of work from the pleasure of life.Scaffold is an Architecture Foundation production, hosted by Matthew Blunderfield. Download the London Architecture Guide App via the App Store or Google PlayBecome an Architecture Foundation Patreon member and be a part of a growing coalition of architects and built environment professionals supporting our vital and independent work. Hosted on Acast. See acast.com/privacy for more information.

We review four clips from the Dwarkesh Patel Podcast with Satya Nadella, Microsoft's CEO. I highly recommend Dwarkesh's show—technical & nerdy, but excellent.Satya talks about scaffolding—the software wrapped around AI models to make them actually work.So we speak with someone building that scaffolding: Neil McKechnie runs two AI-first startups as a CTO. He discusses how he orchestrates up to twelve different language models—GPT-5, Claude, Gemini, Llama, Mistral, Cohere, Perplexity. We discuss what it actually takes to build production systems with LLMs today—and what that reveals about the agent future we're being pitched.Dwarkesh's Podcast:https://www.youtube.com/@DwarkeshPatelTo stay in touch, sign up for our newsletter at https://www.superprompt.fm

Commentary by Dr.  Martin Bergmann.

Architectural historian Kenneth Frampton remembers the exact moment of his political awakening. Arriving in the United States in 1965, flying over the blazing island of Manhattan and suddenly grasping the visibility of capitalist power there—“a ferocious panorama” of light, cars and consumption that stood in stark contrast to what he calls the “concealed” capitalism of mid-century Britain. From that moment, his architectural writing became inseparable from politics: shaped by Hannah Arendt's idea of the space of appearance, by phenomenology's insistence on embodied experience, and by a Marxist attention to exploitation, power and the global neoliberal order.In this first episode of a two-part interview, Kenneth Frampton, arguably the most celebrated and influential architectural thinker of the past half century, looks back over nearly six decades of his writing and teaching.In the first half of the conversation he addresses the idea critical regionalism as “an architecture of resistance” to commodification, connects phenomenology to political agency rather than aesthetic escapism, and defends his own “operative” criticism—writing that openly aims to influence how architects practice. He is unsparing about the state of architectural education, where social-justice rhetoric often displaces serious engagement with construction and craft, and where capitalism itself remains strangely unnamed. Along the way he reflects on being, as he puts it, “a Marxist who believes in phenomenology,” on the tectonic poetics of building, and, closing out the episode, he reckons with becoming a father at 52 and a grandfather in his mid-90s—thinking about legacy, continuity and what it means for architects, in Álvaro Siza's phrase, not to invent anything, but to transform reality.Scaffold is an Architecture Foundation production, created and hosted by Matthew Blunderfield. Become an Architecture Foundation Patreon member and be a part of a growing coalition of architects and built environment professionals supporting our vital and independent work. Hosted on Acast. See acast.com/privacy for more information.

Send us a textIn this episode, Patti from Madly Learning helps you take the overwhelm out of differentiation. You'll learn how to design one strong core lesson that meets diverse student needs — without doubling your workload. Patti shares real classroom examples, practical tips, and mindset shifts that make differentiation both manageable and meaningful.Tuck these in your teacher pocket:Differentiation is not about 30 separate lessons — it's one lesson with multiple access points.Focus on flexibility, not perfection.Use assessment (formal and informal) to guide your adjustments.Scaffold for support and extend for enrichment — all anchored in the same big idea.Start small with one new strategy and build confidence over time! Remember to Subscribe for more insights on how to navigate the complexities of teaching with efficiency and impact. Share your experiences and strategies in the comments to join the conversation with fellow educators.To find our highly effective, time-saving resources Check out the Ignited Teaching Membership that gives you access to hundreds of downloadable lessons on demand! https://madlylearning.com/sp/ignitedteaching/ Checkout our Madly Learning Store at www.madlylearning.com/storeCheckout our Teachers Pay Teachers store Join our FREE Facebook community for teachers here: https://bit.ly/IYT-FB

234: All students need access to rich, challenging text to grow as readers. But how do we support them? Dr. Jennifer Throndsen shares the why and HOW of scaffolding complex texts. This episode is for you no matter what grade you teach.Click here for this episode's show notes.Get free differentiated passages: https://www.themeasuredmom.com/tmm_optin/differentiated-passages/ Sign up for my free masterclass, 5 Essential Steps to Reach All Readers. Get my book, Reach All Readers! Looking for printable resources that align with the science of reading? Click here to learn more about our popular and affordable membership for PreK through 3rd grade educators.Connect with me here! Blog Instagram Facebook Twitter (X)

Today's episode considers a part of the built environment that's often overlooked in architectural discourse, yet has become one of the most vibrant sites of experimentation in recent years: the nightclub.Since the post-COVID resurgence of nightlife, we've seen club spaces music festivals become laboratories again — places where architects, artists and designers, artists test how bodies move, gather, and connect. After years of enforced separation, there's been a renewed appetite for intimacy, tactility, and collective presence. Nightclubs have stepped into that space, foregrounding not just sound and spectacle, but how architecture can invite touch, trust, and new forms of social closeness.There are few people exploring that frontier more boldly than today's guests: Thea Arde and Joel Jjio, the duo behind playbody. Playbody is far more than a club night — it's an ongoing design research project that treats the dancefloor as a site of architectural inquiry. Their events incorporate sculptural objects, spatial interventions, and choreographic prompts that encourage people to rediscover their own physicality in relation to others.In a time when digital life keeps pulling us apart, their work asks a simple but radical question: how can design rebuild social intimacy? Today we'll talk about how playbody grew from a nightlife concept into a design studio, how they prototype through parties, and why they see the club as a critical testing ground for the future of spatial practice.Scaffold is an Architecture Foundation production. Support our work by becoming a member on Patreon. Hosted on Acast. See acast.com/privacy for more information.

Today's poem is The Poem Climbs the Scaffold and Tells You What It Sees by Natasha Oladokun. The Slowdown is your daily poetry ritual. In this episode, Maggie writes… “There is power in naming, as today's poem reminds us. Once you've seen the violence tucked inside the place name Lynchburg, barely hidden at all—hidden in plain sight—I don't think you'll be able to see or say the word the same way again. Once you see it, you can't unsee it. Nor should you.”Celebrate the power of poems with a gift to The Slowdown today. Every donation makes a difference: https://tinyurl.com/rjm4synp

Dr. Sanjay Kakkar, CEO of Tensive, has developed an innovative bioresorbable polymeric scaffold for breast regeneration following a lumpectomy. The scaffold was designed to address a significant unmet need for breast cancer patients who have limited options for reconstruction. A key feature of this technology is that it facilitates a natural wound-healing response, allowing the body's own vascular, connective, and fat tissues to regrow as the scaffold gradually dissolves. Sanjay explains, "What we've been developing at Tensive is at a late clinical stage of these advanced biomaterials, and we've spent the last decade or so pioneering this bioresorbable polymeric scaffold for natural tissue regeneration. So, coming directly to your question, we're on this mission to provide breast cancer survivors with the option of a natural breast reconstruction. What we developed is this resorbable biopolymer that can be implanted at the time of the lumpectomy procedure." "But what it does is it replaces volume immediately, and it facilitates new tissue growth without cells or growth factors. This sponge, which is made of a fine scaffold matrix, gradually degrades. So it immediately fills the cavity left by the tumor removal. It facilitates natural tissue regeneration, allowing the body's own cells to grow back into the 97% of empty space, which is formed by this sponge. And that basically means that initially vascular tissue regrows inside the porous architecture, then connective tissue, and then fat comes back." #Tensive #BreastCancer #BreastCancerAwareness #ClinicalTrials #ReconstructiveSurgery #REGENERA #BreastHealth #BreastReconstruction #Lumpectomy #Innovation tensive.com Download the transcript here

Dr. Sanjay Kakkar, CEO of Tensive, has developed an innovative bioresorbable polymeric scaffold for breast regeneration following a lumpectomy. The scaffold was designed to address a significant unmet need for breast cancer patients who have limited options for reconstruction. A key feature of this technology is that it facilitates a natural wound-healing response, allowing the body's own vascular, connective, and fat tissues to regrow as the scaffold gradually dissolves. Sanjay explains, "What we've been developing at Tensive is at a late clinical stage of these advanced biomaterials, and we've spent the last decade or so pioneering this bioresorbable polymeric scaffold for natural tissue regeneration. So, coming directly to your question, we're on this mission to provide breast cancer survivors with the option of a natural breast reconstruction. What we developed is this resorbable biopolymer that can be implanted at the time of the lumpectomy procedure." "But what it does is it replaces volume immediately, and it facilitates new tissue growth without cells or growth factors. This sponge, which is made of a fine scaffold matrix, gradually degrades. So it immediately fills the cavity left by the tumor removal. It facilitates natural tissue regeneration, allowing the body's own cells to grow back into the 97% of empty space, which is formed by this sponge. And that basically means that initially vascular tissue regrows inside the porous architecture, then connective tissue, and then fat comes back." #Tensive #BreastCancer #BreastCancerAwareness #ClinicalTrials #ReconstructiveSurgery #REGENERA #BreastHealth #BreastReconstruction #Lumpectomy #Innovation tensive.com Listen to the podcast here

This week, Eric and Josh are joined by Friend-of-Mayfair Pascale Arpin to chat about a documentery crew following her around, her new hand-painted sign work addition to the front doors of our cinema, and the First Ladies of Film Fest postcards that she designed! They also discuss: Gongfu Bao, small business community support, The Rocky Horror Picture Show, big screen Netflix, Guinness World Records, Wikipedia, American Mythology comic books, and more! And, they mention the movies screening the week of Friday October 17 - Thursday October 23: Eleanor The Great, Ballad Of A Small Player, The Room, Nosferatu, Ju-on: The Grudge, The Return Of The Living Dead, Saturday Morning All-You-Can-Eat-Cereal Cartoon Party, and Monster Pool 9!

Scaffold is back this week, with an episode that asks a simple question: why be an architect today?The Architecture Foundation is based inside the office of AHMM in Clerkenwell, which, back in July, hosted a summer school for teenagers just beginning to explore architecture.We decided to speak with some of them, to try and understand what draws young people to this profession today, what they think architecture is for, and how they imagine their futures in it.In these short conversations you get a strong impression of the perennial motivations that push people toward careers in shaping the built environment, despite the seemingly diminishing returns of practicing architecture today.Speaking with these students about their convictions give us a lot of hope: that the culture of architecture today, its perceived importance in society, and the esteem it's held in, might still be elevated, and remain worthy of the ambition and altruism that is clearly in no short supply in this incoming generation.Special thanks this week to all the summer school students, and to Claire Pollock / AHMM Hosted on Acast. See acast.com/privacy for more information.

Send us a textOn today's episode poet and critic Adam Wyeth reviews nine new poetry collections. Under the microscope are Infinity Pool by Vona Groarke; Belfast Twilight by Liam Carson; Harbour Doubts by Bebe Ahley; Over Here by Alan Gillis; Chic to be Sad by Molly Twomey; New Arcana by Jesica Traynor; The Convent of Mercy by Tom French; À la Belle Étoile: The odyssey of Jeanne by Afric McGlinchey and Scaffold by Thomas Brezing. A strong poet of coffee needed!This episode is supported by a Project Award from the Arts Council/An Chomhairle Ealaíon.Intro/outro music: Colm Mac Con Iomaire, ‘Thou Shalt Not Carry' from The Hare's Corner, 2008, with thanks to Colm for permission to use it. Logo designed by Freya Sirr.Support the show

He had a raft of big hit singles in the 1960's and 70's and many of his acclaimed photographs are held the National Portrait Gallery.In the Misadventures in Music podcast episode 36, Mike talks to Ian and Mick lovingly about life in the McCartney family home and about some of the larger than life characters he encountered over the years including Keith Moon, Burton and Taylor and of course, the Beatles.Indeed, his band The Scaffold made their own unique contribution to our pop culture – so much so that Cherry Red Records have released a 5 CD/DVD Box Set of their recordings, including many unreleased tracks.If you enjoy listening to REAL stories from a genuine participant and eye witness to the golden era of pop music this episode is for you.Enjoy."

Do you ever feel like your lesson plans are just a collection of random activities—fun in the moment but not really building toward anything? You're not alone. Many teachers, especially those working with English language learners, find themselves overwhelmed trying to fit in every domain, standard, and activity into a short block of time. The result? Lessons that feel scattered, students who walk away unclear on the purpose, and a teacher who's left wondering if any of it really stuck.In this episode of Equipping ELLs, Beth Vaucher shares a simple yet powerful framework to bring clarity and direction back into your teaching. She calls it your GPS: Goal, Personalize, Scaffold. By asking three quick questions before you plan, you can transform your lessons from disconnected to intentional, ensuring every activity builds toward language growth and student success.Beth breaks down how to set a clear goal for each lesson, why personalization is the secret ingredient to boosting student engagement, and how to choose scaffolds that support without holding students back. You'll also hear practical examples—from using tortillas to teach main idea to tying ecosystems to students' own neighborhoods—that show just how simple (and powerful) these strategies can be.Whether you're planning tomorrow's lesson or mapping out a unit, this GPS system will keep your teaching aligned, purposeful, and student-centered all year long.LINKS AND RESOURCES:Sign Up for the FREE Webinar⁠⁠⁠Join the Equipping ELLs Membership Shop our TpT Store

All the leaves are brown and the sky's a bit unruly but mellow fruitfulness abounds in this week's pick of the rock and roll news. Add to basket … … is Morrissey hacked off, broke or just desperate for attention? … are stadium gigs the new tourism? … bucket hats, Man City, lads culture … how did America finally ‘get' Oasis? … singles that weren't on albums … are we sated by an overabundance of music? … how Gary Numan got a record deal … why Gene Loves Jezebel are the new Sam & Dave! … the new age of the rock and roll pilgrimage … did Slade record the Hokey Cokey? The Dave Clark Five did Neil Young? The Troggs did Foxy Lady? … the Jam, the Yardbirds, The Nice, the Smiths: bands who broke up because they couldn't crack America … selling Barry White records to Middle Eastern airline pilots Plus Tubeway Army, the Scaffold doing Ging Gang Goolie, “Mister Ferry's diction” and birthday guest Jelltex.Find out more about how to help us to keep the conversation going: https://www.patreon.com/wordinyourear Hosted on Acast. See acast.com/privacy for more information.

All the leaves are brown and the sky's a bit unruly but mellow fruitfulness abounds in this week's pick of the rock and roll news. Add to basket … … is Morrissey hacked off, broke or just desperate for attention? … are stadium gigs the new tourism? … bucket hats, Man City, lads culture … how did America finally ‘get' Oasis? … singles that weren't on albums … are we sated by an overabundance of music? … how Gary Numan got a record deal … why Gene Loves Jezebel are the new Sam & Dave! … the new age of the rock and roll pilgrimage … did Slade record the Hokey Cokey? The Dave Clark Five did Neil Young? The Troggs did Foxy Lady? … the Jam, the Yardbirds, The Nice, the Smiths: bands who broke up because they couldn't crack America … selling Barry White records to Middle Eastern airline pilots Plus Tubeway Army, the Scaffold doing Ging Gang Goolie, “Mister Ferry's diction” and birthday guest Jelltex.Find out more about how to help us to keep the conversation going: https://www.patreon.com/wordinyourear Hosted on Acast. See acast.com/privacy for more information.

All the leaves are brown and the sky's a bit unruly but mellow fruitfulness abounds in this week's pick of the rock and roll news. Add to basket … … is Morrissey hacked off, broke or just desperate for attention? … are stadium gigs the new tourism? … bucket hats, Man City, lads culture … how did America finally ‘get' Oasis? … singles that weren't on albums … are we sated by an overabundance of music? … how Gary Numan got a record deal … why Gene Loves Jezebel are the new Sam & Dave! … the new age of the rock and roll pilgrimage … did Slade record the Hokey Cokey? The Dave Clark Five did Neil Young? The Troggs did Foxy Lady? … the Jam, the Yardbirds, The Nice, the Smiths: bands who broke up because they couldn't crack America … selling Barry White records to Middle Eastern airline pilots Plus Tubeway Army, the Scaffold doing Ging Gang Goolie, “Mister Ferry's diction” and birthday guest Jelltex.Find out more about how to help us to keep the conversation going: https://www.patreon.com/wordinyourear Hosted on Acast. See acast.com/privacy for more information.

A special episode of More Rosebud today with a great poet, and filled with great poetry. Roger McGough tells Gyles about his striking first memories, his childhood in Liverpool, and interweaves this with some readings of poems inspired by his life. Roger remembers his hardworking father, the long line of men who came to the house to pay their respects to his father laid out in the coffin after his death, meeting Philip Larkin at Hull University, and then his early days performing poetry and sketches in clubs in Liverpool in the sixties - which led to his fame as a poet and as an unlikely pop star in the group The Scaffold - with hits like "Thank You Very Much" and "Lily the Pink". Plus Gyles and Harriet enjoy a poem written by a Rosebud listener. Hosted on Acast. See acast.com/privacy for more information.

Scott and Wes share their top strategies for getting high-quality results from AI coding tools like Cursor, Claude, ChatGPT, and Windsurf. From better prompting to building reusable rule sets, they cover practical tips for making AI your most productive coding partner. Show Notes 00:00 Welcome to Syntax! Wes' Tweet 02:56 How to get the best results when using AI. 03:15 Scaffold it out yourself. 05:40 Be clear with your prompts. 07:45 Use XML tags around specific items 08:47 Utilize Rules like Cursor rules or Copilot rules. 13:20 Ask it to create some rules based on an existing codebase. 16:03 Break things down into clear concise actionable items. 17:22 Where to store your rules files. 18:37 Utilizing llm.txt files. 19:24 Context7. 20:28 Tag relevant files, functions, etc. 21:38 Feed logs back into the AI. 22:36 Logging Errors. 22:54 Brought to you by Sentry.io. 24:14 Long running chats get worse. Wes' Tweet Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

In the 35th Patreon bonus podcast you join me for the second part of a paranormal investigation deep within a vast, dark, forest. Our focus is the site of a former isolation hospital that held those with infectious diseases such as scarlet fever and tuberculosis.    We pick up our paranormal investigation as Tom, John and I enter a building that was once used to wash the bodies of the dead. So tonight, let us once again ask the question, just how haunted is the Scaffold Hill Hospital? Get access to the full episode right now at https://www.patreon.com/howhauntedpod. If you don't wish to subscribe to Patreon, but would still like to hear this episode, all Patreon exclusive episodes are available to be purchased individually for a one off fee of £4.99. Check out the Patreon link to find out more. Find out more about the pod at https://www.how-haunted.com and you can email Rob at Rob@how-haunted.com   Music in this episode includes: "Darren Curtis - Demented Nightmare" https://youtu.be/g_O4kS9FP3k   " HORROR PIANO MUSIC " composed and produced by "Vivek Abhishek" Music link : https://youtu.be/xbjuAGgk5lU SUBSCRIBE us on YOUTUBE: https://youtu.be/DQQmmCl8crQ Follow on Facebook: https://bit.ly/33RWRtP Follow on Instagram: https://bit.ly/2ImU2JV

Many Christians feel lost when it comes to prayer. How should one go about praying? Other believers feel aimless, "how can I come up with a novel & unique prayer every single day?!" In this episode I explain how the Lord's Prayer (Our Father, Pater Noster) serves as a scaffold for my own praying. Or, perhaps better, how the Lord's Prayer serves as a targeting system for my praying. Jesus' prayer is a prayer for soldiers. We were born into a war when we exited our mother's placenta and we were born into a war when we confessed Christ and became new creations. So I name each phrase of the established prayer and then theologically unpack what it means, peel back some layers, and even clarify how I pray with regard to that phrase. In the show's cultural-examination opening I variously discuss: the attacks on ICE agents, the rioting in Portland and Dallas and California, the ongoing opaque nature of the Epstein files, and what I want to happen with regard to what went on at Epstein's sex island. Come laugh and think with me!

In the 34th Patreon bonus podcast you join me at the site of a former infectious diseases hospital, which is today the countryside centre for the vast country park in which it is located.   But what would happen when John, Tom and I joined Spiritus Paranormal for a night which none of us would forget in a hurry. Tonight, let us together ask the question, just how haunted is the Scaffold Hill Hospital? Get access to the full episode right now at https://www.patreon.com/howhauntedpod. If you don't wish to subscribe to Patreon, but would still like to hear this episode, all Patreon exclusive episodes are available to be purchased individually for a one off fee of £4.99. Check out the Patreon link to find out more. Find out more about the pod at https://www.how-haunted.com and you can email Rob at Rob@how-haunted.com   Music in this episode includes: "Darren Curtis - Demented Nightmare" https://youtu.be/g_O4kS9FP3k   " HORROR PIANO MUSIC " composed and produced by "Vivek Abhishek" Music link : https://youtu.be/xbjuAGgk5lU SUBSCRIBE us on YOUTUBE: https://youtu.be/DQQmmCl8crQ Follow on Facebook: https://bit.ly/33RWRtP Follow on Instagram: https://bit.ly/2ImU2JV

Things reached breaking point. And then… everything changed.This week on the Happy Families Podcast, Justin and Kylie share a raw and transformative parenting story from their own home—a story of tough love, compassion, and the unexpected joy that emerged when one of their children went screen-free. If you've ever wrestled with screen-time battles, wondered whether stepping in might do more harm than good, or felt at a loss watching your child withdraw behind a phone… this is the episode you need to hear. KEY POINTS: Not all kids respond to screens the same way—some are more deeply affected mentally, socially, and physically. Despite multiple conversations, one of Justin and Kylie’s children struggled to reduce screen use on her own. Justin made the tough call to temporarily remove the smartphone, despite knowing it would be met with resistance. The decision was supported with compassion, calm, and a consistent message of love and presence. Within days, they saw remarkable emotional and relational transformation. The child herself later initiated a conversation to renegotiate her phone use, ultimately choosing to remove social media apps and suggest her own boundaries. The family experienced a visible increase in connection, laughter, and joy—without screens. QUOTE OF THE EPISODE:"With enough scaffolding, with enough support, with enough conversation around why sometimes we as parents are going to make decisions that the children may not agree with… the children are able to deal with and respond to these challenges in much more productive ways." – Justin Coulson RESOURCES MENTIONED: “The Doctor’s Desk” podcast episode #1270 mentioned a study on improved wellbeing after removing smartphone internet access. Study from 'Nature' happyfamilies.com.au for more resources on parenting and screen time. Parental Guidance Season 3 starts Monday June 30 on Channel 9 — new episodes discussed throughout the week on the podcast. ✅ ACTION STEPS FOR PARENTS: Trust your instincts – If screen use is affecting your child’s wellbeing, don't ignore the signs. Lead with compassion – Any intervention should be anchored in calm, empathy, and connection. Scaffold the change – Offer alternatives, create structure, and maintain open communication. Invite their input – When emotions settle, include your child in designing new tech boundaries. Watch for the joy – Pay attention to the surprising upside: more laughter, connection, and peace. See omnystudio.com/listener for privacy information.

Our Joes which consist of Hardman, Scaffold, Classified, and Reaper, head to Cybertron to investigate the metallic planet invading our space.... What could go wrong.... Also, be sure to check out the website http://headcast.headspeaks.com for the Supplemental material under The Energon Protocols Debrief. Write in to gijoe@headspeaks.com and we'll read your letter on the air! Take a listen and let us know what you think. On Facebook and Twitter we can be found by searching for G.I. Joe: A Real American Headcast And be sure to look for us on Patreon. If you like what we're doing, join Big Danny Cool and Shawn Adams and throw a few bucks in the tin at http://patreon.com/HeadcastNetwork. You can also call us at 559-500-3182‬ and leave a message and we will play your message on the air. Yo Joe!

In episode 109 we are doing something a bit different as I'm taking you along on a big summer ghost hunt. You join me at the site of a former infectious diseases hospital, which is today the countryside centre for the vast country park in which it is located. My small team and I will be part of an organised paranormal investigation and you'll hear almost an hour of audio from that night. And trust me, it's a night that no one in attendance will forget in a hurry........as hard as they may try. So join Tom, John and I and let us find out together, just how haunted is the Scaffold Hill Hospital? Huge thanks to Spiritus Paranormal, check out their future investigations on their Facebook page www.facebook.com/SpiritusParanormalInvestigations Check out Rob Davies' YouTube channel at www.youtube.com/c/DeadAirTV Support How Haunted? by subscribing and leaving a review. In July Rob will be taking on the "most difficult" walk in the North York Moors to raise money for Cancer Research UK. If you'd wish to sponsor us you can do so at justgiving.com/page/walk4john2025 Find out more about the pod at https://www.how-haunted.com and you can email Rob at Rob@how-haunted.com You can become a Patreon for as little as £1 a month. You can choose from three tiers and get yourself early access to episodes, and exclusive monthly episodes - much like this one - where Rob will conduct ghost hunts and you'll hear the audio from the night. You can even get yourself some exclusive How Haunted? merch. To sign up, and take advantage of a free seven day trial, visit https://patreon.com/HowHauntedPod Perhaps you'd rather buy me a coffee to make a one off donation to support the pod, you can do that at https://www.buymeacoffee.com/HowHauntedPod Music in this episode includes: Darren Curtis – Lurking Evil: https://youtu.be/3i0aVnpeppw " HORROR PIANO MUSIC " composed and produced by "Vivek Abhishek" Music link :https://youtu.be/xbjuAGgk5lU || SUBSCRIBE us on YOUTUBE: https://youtu.be/DQQmmCl8crQ || Follow on Facebook: https://bit.ly/33RWRtP || Follow on Instagram: https://bit.ly/2ImU2JV

Mike McCartney never meant to form a pop group, he was too busy cutting hair and cutting up The post Mike McCartney's Box of Scaffold appeared first on The Strange Brew .

To mark the 25th Anniversary of the Tate Modern this week, the Architecture Foundation's Director Ellis Woodman speaks with two key figures behind the museum's conception: Nicholas Serota and Jacques Herzog.Scaffold is an Architecture Foundation production, hosted by Matthew Blunderfield. Download the London Architecture Guide App via the App Store or Google PlayBecome an Architecture Foundation Patreon member and be a part of a growing coalition of architects and built environment professionals supporting our vital and independent work. Hosted on Acast. See acast.com/privacy for more information.