Applied science
POPULARITY
Categories
In a post-scarcity civilization where material needs are met, black markets don't vanish—they evolve. Explore why scarcity shifts to identity, risk, privacy, and desire.Get Nebula using my link for 50% off an annual subscription: https://go.nebula.tv/isaacarthurWatch my exclusive video Lazarus Protocols: https://nebula.tv/videos/isaacarthur-lazarus-protocols-reviving-civilizations-after-extinctionCheck out Abolish Everything https://nebula.tv/abolish?ref=isaacarthur
In a post-scarcity civilization where material needs are met, black markets don't vanish—they evolve. Explore why scarcity shifts to identity, risk, privacy, and desire.Get Nebula using my link for 50% off an annual subscription: https://go.nebula.tv/isaacarthurWatch my exclusive video Lazarus Protocols: https://nebula.tv/videos/isaacarthur-lazarus-protocols-reviving-civilizations-after-extinctionCheck out Abolish Everything https://nebula.tv/abolish?ref=isaacarthur
Microsoft's anti-"Microslop" censorship backfired spectacularly; Australia is cracking down on AI age verification while Meta is busy targeting toddlers; prediction markets are basically just insider trading with extra steps; AI chatbots are getting people killed and exposing spy operations; the Moon landing got pushed again; Opera got nostalgic at 30; Sony bought Charlie Brown; and Netflix is making documentaries with robot people now.Show notes at https://gog.show/736Watch on YouTube at https://youtu.be/6lw2Hy_U8QASponsors:DeleteMe - Get 20% off your DeleteMe plan when you go to JoinDeleteMe.com/GOG and use promo code GOG at checkout.Private Internet Access - Go to GOG.Show/vpn and sign up today. For a limited time only, you can get OUR favorite VPN for as little as $2.03 a month.SetApp - With a single monthly subscription you get 240+ apps for your Mac. Go to SetApp and get started today!!!1Password - Get a great deal on the only password manager recommended by Grumpy Old Geeks! gog.show/1passwordFOLLOW UPMicrosoft Bans the Word “Microslop” on Copilot Discord, Gets So Humiliated That It Locks Down the Whole ServerAustralia will consider requiring app stores to block AI services without age verificationA Day in the Life of an EnshittificatorIN THE NEWSMeta's what-if for tweensHow Meta Executives Talked About Child Safety Behind the ScenesThe Great Insider Trading Reckoning Reportedly Hits OpenAIKhamenei market meltdown on Kalshi shows how prediction markets still can't decide what ‘counts'Some Alleged Polymarket Insiders Made a Fortune on U.S. Strikes on IranPolymarket Decides Incentivizing a Nuclear Detonation Might Be a Bad IdeaA Chinese official's use of ChatGPT accidentally revealed a global intimidation operation‘Our Bond Is the Only Thing That's Real:' A New Lawsuit Alleges Google Gemini Drove a Man to SuicideThe Data Centers Have Arrived at the Edge of the Arctic CircleBig tech companies agree to not ruin your electric bill with AI data centersTerraPower gets OK to start construction of its first nuclear plantThe Supreme Court doesn't care if you want to copyright your AI-generated artAnthropic CEO Dario Amodei calls OpenAI's messaging around military deal 'straight up lies,' report saysThe $100 Billion OpenAI-Nvidia Deal Is Not HappeningNASA Announces Major Change to Plans For Putting Humans on The MoonThe US Senate empowers NASA to fully engage in lunar space raceAstronomers Estimated the Lifespan of Alien Civilizations, and It's Not Looking Good for UsMEDIA CANDYCharlie Brown now works for SonyThese AI Avatars in a Netflix True Crime Doc Are Disturbing ViewersNetflix buys Ben Affleck's AI film tech company, InterPositiveAPPS & DOODADSOpera Has Turned 30 and Is Celebrating With a Compelling Tribute to Web NostalgiaWeb Design MuseumMeta hit with a class action lawsuit over smart glasses' privacy claimsApple Macbook NeoAT THE LIBRARYUncommon People: Britpop and Beyond in 20 Songs by Miranda SawyerSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.
Send a textDaniel Gledhill is a seasoned manufacturing and engineering leader whose career bridges high-risk industrial operations and precision-driven medical device manufacturing. Daniel leads engineering teams responsible for multiple production areas supporting transcatheter heart valve delivery systems—products where quality, reliability, and patient safety are absolutely critical.Daniel's journey to medical devices began in heavy industry, where he worked as a process, chemical, and metallurgical engineer at Rio Tinto, including leadership roles at copper smelters overseeing sulfuric acid plants, powerhouses, and byproduct operations. These early roles shaped his systems-level thinking, comfort with complex processes, and respect for disciplined operations—skills that would later translate powerfully into regulated medical manufacturing environments.Over nearly ten years at Edwards Lifesciences, Daniel has progressed from manufacturing management into senior engineering leadership, guiding teams through scale-up, process improvement, cross-functional collaboration, and organizational change. His work sits at the intersection of engineering, manufacturing, quality, and leadership—where decisions directly impact both operational performance and patient outcomes.Daniel holds a Bachelor's degree in Chemical Engineering from the University of Utah, along with an MBA from the University of Utah's David Eccles School of Business. This combination of technical and business education informs his balanced approach to leadership—one that values data, people, and long-term system health over short-term wins.In this conversation, we explore what it really means to lead engineering teams in medical device manufacturing, how leadership expectations evolve as engineers move into management, and what lessons from heavy industry can sharpen execution in highly regulated, patient-critical environments.LINKS:Guest LinkedIn: https://www.linkedin.com/in/daniel-gledhill-a6155237/Guest website: https://www.edwards.com/ Aaron Moncur, hostDownload the Essential Guide to Designing Test Fixtures: https://pipelinemedialab.beehiiv.com/test-fixture Subscribe to the show to get notified so you don't miss new episodes every Friday.The Being An Engineer podcast is brought to you by Pipeline Design & Engineering. Pipeline partners with medical & other device engineering teams who need turnkey equipment such as cycle test machines, custom test fixtures, automation equipment, assembly jigs, inspection stations and more. You can find us on the web at www.teampipeline.us Watch the show on YouTube: www.youtube.com/@TeamPipelineus
For episode 687 of the BlockHash Podcast, host Brandon Zemp is joined by Yuannan Yang, Security Engineer at CertiK, the largest Web3 security services provider. CertiK offers a wide range of products and services to support the Web3 industry, project teams, and users alike. CertiK's products and services span the entire lifecycle of project development, from incubation and early stages, to growth and maturity. CertiK is one of the most globally recognized companies in the Web3 industry, serving users across 150 countries/regions.Yuannan Yang, based in Washington, DC, US, is currently a Security Engineer at CertiK. Yuannan Yang brings experience from previous roles at Johns Hopkins Whiting School of Engineering, Tsinghua University and Red Hat. Yuannan Yang holds a 2019 - 2020 Master's degree in information security @ Johns Hopkins Whiting School of Engineering.
PlastChicks Lynzie Nebel and Mercedes Landazuri host Geoff Foster, CEO and President of Core Technology. They discuss how he founded his own plastics injection molding company, what's fueling their 300% growth since Covid, critical skills for engineering students, the importance of building diversity and inclusion into all levels of the company, the value of internships, considering potential employees from different industries, and the nonprofit Molding Kids for Success, which strives to educate youth in science, technology, engineering and mathematics by combining classroom experiments with real-world applications on the manufacturing floor. Watch the PlastChicks podcast on the SPE YouTube Channel.PlastChicks is sponsored by SPE-Inspiring Plastics Professionals and the Plastics Industry Association. Look for new episodes on the first Friday of every month.
In this episode, Joe sits down with Jim Hirsch of Air Tractor to explore a career built on engineering and a lifelong passion for aviation. A Texas A&M graduate in Aeronautical Engineering, Jim shares how his technical foundation led him into agricultural aviation and ultimately into a leadership role at one of the industry's most influential aircraft manufacturers.Jim reflects on the legacy of Leland Snow and how Air Tractor's innovative designs shaped modern ag aviation, while also tracing the company's expansion into firefighting and military roles. He discusses the challenges of a cyclical industry, the need for constant innovation, and what has allowed Air Tractor to adapt and grow over time.The conversation also dives into company culture, including employee ownership, the importance of the PT6 engine, and why truly understanding the aircraft matters at every level. Jim also shares personal insights from his own flying, including how owning a Piper Meridian has changed his approach to travel and aviation.M-Class Spring 2026 is approaching, and spots are filling up quickly. Reserve your seat now! https://flycasey.com/m-class/Joe just released his very first book! You can grab your copy of Long Story Short: Stories From a Lifetime in the Cockpit on Amazon: https://a.co/d/4JGtIgq
Joe Bates, Senior Researcher at the ACEC Research Institute, sits down with WSVA-AM/FM Harrisonburg, VA Radio Station to discuss the engineering shortage that the U.S. faces. In 2022 about 184,000 engineers retired or left while only 166,000 new engineers entered the workforce, creating an 18,000‑person shortfall. The radio interview covers causes (retirements, career changes, and restrictive H‑1B visa caps that block many international graduates from staying), the economic impact on projects and companies, and solutions like boosting recruitment in K–12, updating university programs (including AI skills), and policy changes to retain trained international engineers.
Interstellar city-states may dominate future space travel, governing the laser highways that connect stars and shape galactic civilization.Get Nebula using my link for 50% off an annual subscription: https://go.nebula.tv/isaacarthurWatch my exclusive video Lazarus Protocols: https://nebula.tv/videos/isaacarthur-lazarus-protocols-reviving-civilizations-after-extinction
Interstellar city-states may dominate future space travel, governing the laser highways that connect stars and shape galactic civilization.Get Nebula using my link for 50% off an annual subscription: https://go.nebula.tv/isaacarthurWatch my exclusive video Lazarus Protocols: https://nebula.tv/videos/isaacarthur-lazarus-protocols-reviving-civilizations-after-extinction
In this episode of Startup Hustle, Matt Watson interviews Mark Roberge, a former HubSpot executive and current venture capitalist, about his journey from engineering to sales and the importance of scaling startups. Mark discusses the genesis of HubSpot, the significance of sales in startups, and the concept of product-market fit. He emphasizes the need for customer research, avoiding false positives in feedback, and identifying the ideal customer profile. Mark also shares insights on scaling strategies, key metrics for success, and the science behind scaling businesses effectively.⏱️ Episode Breakdown00:00 The Genesis of HubSpot02:56 Transitioning from Engineering to Sales06:06 The Science of Scaling08:53 The Importance of Selling Early12:12 Understanding Customer Needs14:58 Avoiding False Positives in Feedback15:39 Design Partner Dilemma18:21 Target Audience Insights19:56 Ideal Customer Profile Framework23:00 The Science of Scaling25:05 Understanding Growth Investment30:55 Navigating Growth Challenges35:25 Final Thoughts on Scaling SuccessTAKEAWAYSSales is crucial for startup success.Understanding product-market fit is essential before scaling.Customer research should start at the ideation stage.Avoid false positives by validating customer interest.Identify your ideal customer profile to focus efforts.Scaling should be approached methodically and strategically.Establish leading indicators of customer retention.Sales methodologies must evolve as the company grows.Demand generation must align with growth aspirations.The science of scaling involves data-driven decision making.Links & ResourcesConnect with Mark Roberge on LinkedInWhat Smart CTOs Are Doing Differently With Offshore Teams in 2025Subscribe to the Global Talent SprintFull Scale – Build your dev team quickly and affordablyIf you're trying to get your team out of the basement and into real product ownership, this episode is your playbook. Stop being a ticket factory. Build teams that think, create, and lead.Follow the show, rate it, and send this to someone who's still trying to do “real Scrum.” They need it more than you do.
We are excited to welcome a friend of the show, Brent Sullivan of The Tax Alpha Insider. We discuss all things Tax Alpha as the investment puzzle is different when it comes to taxable investors. I have been fortunate to have known Brent since the very beginnings of his Tax Alpha Insider Newsletter, a highly successful, focused publication in the wealth management space. I often say that he could become the Michael Kitces of Tax Alpha. Brent is also behind the first Tax Alpha Conference, Basis Northwest, in Seattle on May 28th and 29th, which I will be attending. Brent has an interesting career background, both corporate and entrepreneurial. As mentioned before, he is the Founder of The Tax Alpha Insider, as well as the Basis Northwest Conference. He was also a Software Engineer at Parametric, who is the godfather of direct indexing. Before that, he worked in Investment Banking and Asset Management. Brent holds a Masters of Engineering from Cornell University (Financial Engineering/Statistics), as well as a Bachelor of Science in Mathematics from the University of California, Riverside. In this episode, we discuss all things Tax Alpha, as this is our first interview with Brent. We talk about the reasons he decided to launch this, why Tax Alpha is important now, and how this is one of the best times in history to be a taxable investor with all of the tools available. We discuss everything from householding/asset location, to direct indexing, to tax-aware long-short, buffer ETF's, 351 exchanges, advisor launched ETF's, assets that shouldn't be used for taxable investors, collars/variable prepaid forward contracts, heartbeat trades/ETF share classes, box loans, tax alpha as a volatility buffer, trader funds, etc. We also discuss the impact of AI on advisors and taxable investing, as well as taking the other side, why not just pay the taxes and keep things simple. Today's hosts are Steve Curley, CFA (Co-Managing Principal, 55 North Private Wealth) & co-host Chris Cannon, CFA (CIO/Principal, FirsTrust). Please enjoy the episode. You can follow us on Twitter & LinkedIn or at investorsfirstpodcast.com Learn more: https://www.taxalphainsider.com/ https://www.basisconf.com/
From lifelong hobbies to deep nostalgia, there is no doubt that personal connections with our vehicles are real. But true car lovers know that the future is built on what we've learned from the past. Listen in as we sit down with SAE History of Ground Vehicle Systems Committee members Terry Mueller, George Nicols, and Jeff Singer to explore what makes cars so special. As historical engineering storytellers, these automotive enthusiasts are creating a library within SAE that includes the evolution of vehicle systems and subsystems, making knowledge accessible for enthusiasts, engineers, and educators alike. If you're an industry professional, retired engineer, or automotive enthusiast with experience in the automotive or aerospace sectors, learn how you can join and help us preserve history. We'd love to hear from you. Share your comments, questions and ideas for future topics and guests to podcast@sae.org. Don't forget to take a moment to follow SAE Tomorrow Today—a podcast where we discuss emerging technology and trends in mobility with the leaders, innovators and strategists making it all happen—and give us a review on your preferred podcasting platform. Follow SAE on LinkedIn, Instagram, Facebook, X, and YouTube. Follow host Grayson Brulte on LinkedIn, X, and Instagram.
The reception to our recent post on Code Reviews has been strong. Catch up!Amid a maelstrom of discussion on whether or not AI is killing SaaS, one of the top publicly listed SaaS companies in the world has just reported record revenues, clearing well over $1.1B in ARR for the first time with a 28% margin. As we comment on the pod, Aaron Levie is the rare public company CEO equally at home in both worlds of Silicon Valley and Wall Street/Main Street, by day helping 70% of the Fortune 500 with their Enterprise Advanced Suite, and yet by night is often found in the basements of early startups and tweeting viral insights about the future of agents.Now that both Cursor, Cloudflare, Perplexity, Anthropic and more have made Filesystems and Sandboxes and various forms of “Just Give the Agent a Box” cool (not just cool; it is now one of the single hottest areas in AI infrastructure growing 100% MoM), we find it a delightfully appropriate time to do the episode with the OG CEO who has been giving humans and computers Boxes since he was a college dropout pitching VCs at a Michael Arrington house party.Enjoy our special pod, with fan favorite returning guest/guest cohost Jeff Huber!Note: We didn't directly discuss the AI vs SaaS debate - Aaron has done many, many, many other podcasts on that, and you should read his definitive essay on it. Most commentators do not understand SaaS businesses because they have never scaled one themselves, and deeply reflected on what the true value proposition of SaaS is.We also discuss Your Company is a Filesystem:We also shoutout CTO Ben Kus' and the AI team, who talked about the technical architecture and will return for AIE WF 2026.Full Video EpisodeTimestamps* 00:00 Adapting Work for Agents* 01:29 Why Every Agent Needs a Box* 04:38 Agent Governance and Identity* 11:28 Why Coding Agents Took Off First* 21:42 Context Engineering and Search Limits* 31:29 Inside Agent Evals* 33:23 Industries and Datasets* 35:22 Building the Agent Team* 38:50 Read Write Agent Workflows* 41:54 Docs Graphs and Founder Mode* 55:38 Token FOMO Culture* 56:31 Production Function Secrets* 01:01:08 Film Roots to Box* 01:03:38 AI Future of Movies* 01:06:47 Media DevRel and EngineeringTranscriptAdapting Work for AgentsAaron Levie: Like you don't write code, you talk to an agent and it goes and does it for you, and you may be at best review it. That's even probably like, like largely not even what you're doing. What's happening is we are changing our work to make the agents effective. In that model, the agent didn't really adapt to how we work.We basically adapted to how the agent works. All of the economy has to go through that exact same evolution. Right now, it's a huge asset and an advantage for the teams that do it early and that are kinda wired into doing this ‘cause you'll see compounding returns. But that's just gonna take a while for most companies to actually go and get this deployed.swyx: Welcome to the Lane Space Pod. We're back in the chroma studio with uh, chroma, CEO, Jeff Hoover. Welcome returning guest now guest host.Aaron Levie: It's a pleasure. Wow. How'd you get upgraded to, uh, to that?swyx: Because he's like the perfect guy to be guest those for you.Aaron Levie: That makes sense actually, for We love context. We, we both really love context le we really do.We really do.swyx: Uh, and we're here with, uh, Aaron Levy. Welcome.Aaron Levie: Thank you. Good to, uh, good to be [00:01:00] here.swyx: Uh, yeah. So we've all met offline and like chatted a little bit, but like, it's always nice to get these things in person and conversation. Yeah. You just started off with so much energy. You're, you're super excited about agents.I loveAaron Levie: agents.swyx: Yeah. Open claw. Just got by, got bought by OpenAI. No, not bought, but you know, you know what I mean?Aaron Levie: Some, some, you know, acquihire. Executiveswyx: hire.Aaron Levie: Executive hire. Okay. Executive hire. Say,swyx: hey, that's my term. Okay. Um, what are you pounding the table on on agents? You have so many insightful tweets.Why Every Agent Needs a BoxAaron Levie: Well, the thing that, that we get super excited by that I think is probably, you know, should be relatively obvious is we've, we've built a platform to help enterprises manage their files and their, their corporate files and the permissions of who has access to those files and the sharing collaboration of those files.All of those files contain really, really important information for the enterprise. It might have your contracts, it might have your research materials, it might have marketing information, it might have your memos. All that data obviously has, you know, predominantly been used by humans. [00:02:00] But there's been one really interesting problem, which is that, you know, humans only really work with their files during an active engagement with them, and they kind of go away and you don't really see them for a long time.And all of a sudden, uh, with the power of AI and AI agents, all of that data becomes extremely relevant as this ongoing source of, of answers to new questions of data that will transform into, into something else that, that produces value in your organization. It, it contains the answer to the new employee that's onboarding, that needs to ramp up on a project.Um, it contains the answer to the right thing to sell a customer when you're having a conversation to them, with them contains the roadmap information that's gonna produce the next feature. So all that data. That previously we've been just sort of storing and, and you know, occasionally forgetting about, ‘cause we're only working on the new active stuff.All of that information becomes valuable to the enterprise and it's gonna become extremely valuable to end users because now they can have agents go find what they're looking for and produce new, new [00:03:00] value and new data on that information. And it's gonna become incredibly valuable to agents because agents can roam around and do a bunch of work and they're gonna need access to that data as well.And um, and you know, sometimes that will be an agent that is sort of working on behalf of, of, of you and, and effectively as you as and, and they are kind of accessing all of the same information that you have access to and, and operating as you in the system. And then sometimes there's gonna be agents that are just.Effectively autonomous and kind of run on their own and, and you're gonna collaborate and work with them kind of like you did another person. Open Claw being the most recent and maybe first real sort of, you know, kind of, you know, up updating everybody's, you know, views of this landscape version of, of what that could look like, which is, okay, I have an agent.It's on its own system, it's on its own computer, it has access to its own tools. I probably don't give it access to my entire life. I probably communicate with it like I would an assistant or a colleague and then it, it sort of has this sandbox environment. So all of that has massive implications for a platform that manage that [00:04:00] enterprise data.We think it's gonna just transform how we work with all of the enterprise content that we work with, and we just have to make sure we're building the right platform to support that.swyx: The sort of shorthand I put it is as people build agents, everybody's just realizing that every agent needs a box. Yes.And it's nice to be called box and just give everyone a box.Aaron Levie: Hey, I if I, you know, if we can make that go viral, uh, like I, I think that that terminology, I, that's theswyx: tagline. Every agentAaron Levie: needs a box. Every agent needs a box. If we can make that the headline of this, I'm fine with this. And that's the billboard I wanna like Yeah, exactly.Every agent needs a box. Um, I like it. Can we ship this? Like,swyx: okay, let's do it. Yeah.Aaron Levie: Uh, my work here is done and I got the value I needed outta this podcast Drinks.swyx: Yeah.Agent Governance and IdentityAaron Levie: But, but, um, but, but, you know, so the thing that we, we kind of think about is, um, is, you know, whether you think the number 10 x or a hundred x or whatever the number is, we're gonna have some order of magnitude more agents than people.That's inevitable. It has to happen. So then the question is, what is the infrastructure that's needed to make all those agents effective in the enterprise? Make sure that they are well governed. Make sure they're only doing [00:05:00] safe things on your information. Make sure that they're not getting exposed. The data that they shouldn't have access to.There's gonna be just incredibly spectacularly crazy security incidents that will happen with agents because you'll prompt, inject an agent and sort of find your way through the CRM system and pull out data that you shouldn't have access to. Oh, weJeff Huber: have God,Aaron Levie: right? I mean, that's just gonna happen all over the place, right?So, so then the thing is, is how do you make sure you have the right security, the permissions, the access controls, the data governance. Um, we actually don't yet exactly know in many cases how we're gonna regulate some of these agents, right? If you think about an agent in financial services, does it have the exact same financial sort of, uh, requirements that a human did?Or is it, is the risk fully on the human that was interacting or created the agent? All open questions, but no matter what, there's gonna need to be a layer that manages the, the data they have access to, the workflows that they're involved in, pulling up data from multiple systems. This is the new infrastructure opportunity in the era of agents.swyx: You have a piece on agent identities, [00:06:00] which I think was today, um, which I think a lot of breaking news, the security, security people are talking about, right? Like you basically, I, I always think of this as like, well you need the human you and then there you need the agent. YouAaron Levie: Yes.swyx: And uh, well, I don't know if it's that simple, but is box going to have an opinion on that or you're just gonna be like, well we're just the sort of the, the source layer.Yeah. Let's Okta of zero handle that.Aaron Levie: I think we're gonna have an opinion and we will work with generally wherever the contours of the market end up. Um, and the reason that we're gonna have an opinion more than other topics probably is because one of the biggest use cases for why your agent might need it, an identity is for file system access.So thus we have to kind of think about this pretty deeply. And I think, uh, unless you're like in our world thinking about this particular problem all day long, it might be, you know, like, why is this such a big deal? And the reason why it's a really big deal is because sometimes sort of say, well just give the agent an, an account on the system and it just treats, treat it like every other type of user on the system.The [00:07:00] problem is, is that I as Aaron don't really have any responsibility over anybody else's box account in our organization. I can't see the box account of any other employee that I work with. I am not liable for anything that they do. And they have, I have, I have, you know, strict privacy requirements on everything that they're able to, you know, that, that, that they work on.Agents don't have that, you know, don't have those properties. The person who creates the agent probably is gonna, for the foreseeable future, take on a lot of the liability of what that agent does. That agent doesn't deserve any privacy because, because it's, you know, it can't fully be autonomously operated and it doesn't have any legal, you know, kind of, you know, responsibility.So thus you can't just be like, oh, well I'll just create a bunch of accounts and then I'll, I'll kind of work with that agent and I'll talk to it occasionally. Like you need oversight of that. And so then the question is, how do you have a world where the agent, sometimes you have oversight of, but what if that agent goes and works with other people?That person over there is collaborating with the agent on something you shouldn't have [00:08:00] access to what they're doing. So we have all of these new boundaries that we're gonna have to figure out of, of, you know, it's really, really easy. So far we've been in, in easy mode. We've hit the easy button with ai, which is the agent just is you.And when you're in quad code and you're in cursor, and you're in Codex, you're just, the agent is you. You're offing into your services. It can do everything you can do. That's the easy mode. The hard mode is agents are kind of running on their own. People check in with them occasionally, they're doing things autonomously.How do you give them access to resources in the enterprise and not dramatically increased the security risk and the risk that you might expose the wrong thing to somebody. These are all the new problems that we have to get solved. I like the identity layer and, and identity vendors as being a solution to that, but we'll, we'll need some opinions as well because so many of the use cases are these collaborative file system use cases, which is how do I give it an agent, a subset of my data?Give it its own workspace as well. ‘cause it's gonna need to store off its own information that would be relevant for it. And how do I have the right oversight into that? [00:09:00]Jeff Huber: One thing, which, um, I think is kind interesting, think about is that you know, how humans work, right? Like I may not also just like give you access to the whole file.I might like sit next to you and like scroll to this like one part of the file and just show you that like one part and like, you know,swyx: partial file access.Jeff Huber: I'm just saying I think like our, like RA does seem to be dead, right? Like you wanna say something is dead uhhuh probably RA is dead. And uh, like the auth story to me seems like incredibly unsolved and unaddressed by like the existing state of like AI vendors.ButAaron Levie: yeah, I think, um, we're, I mean you're taking obviously really to level limit that we probably need to solve for. Yeah. And we built an access control system that was, was kind of like, you know, its own little world for, for a long time. And um, and the idea was this, it's a many to many collaboration system where I can give you any part of the file system.And it's a waterfall model. So if I give you higher up in the, in the, in the system, you get everything below. And that, that kind of created immense flexibility because I can kind of point you to any layer in the, in the tree, but then you're gonna get access to everything kind of below it. And that [00:10:00] mostly is, is working in this, in this world.But you do have to manage this issue, which is how do I create an agent that has access to some of my stuff and somebody else's stuff as well. Mm-hmm. And which parts do I get to look at as the creator of the agent? And, and these are just brand new problems? Yeah. Crazy. And humans, when there was a human there that was really easy to do.Like, like if the three of us were all sharing, there'd be a Venn diagram where we'd have an overlapping set of things we've shared, but then we'd have our own ways that we shared with each other. In an agent world, somebody needs to take responsibility for what that agent has access to and what they're working on.These are like the, some of the most probably, you know, boring problems for 98% of people on, on the internet, but they will be the problems that are the difference between can you actually have autonomous agents in an enterprise contextswyx: Yeah.Aaron Levie: That are not leaking your data constantly.swyx: No. Like, I mean, you know, I run a very, very small company for my conference and like we already have data sensitivity issues.Yes. And some of my team members cannot see Yes. Uh, the others and like, I can't imagine what it's like to run a Fortune 500 and like, you have to [00:11:00] worry about this. I'm just kinda curious, like you, you talked to a lot like, like 70, 80% of your cus uh, of the Fortune 500, your customers.Aaron Levie: Yep. 67%. Just so we're being verySEswyx: precise.So Yeah. I'm notAaron Levie: Okay. Okay.swyx: Something I'm rounding up. Yes. Round up. I'm projecting to, forAaron Levie: the government.swyx: I'm projecting to the end of the year.Aaron Levie: Okay.swyx: There you go.Aaron Levie: You do make it sound like, like we, we, well we've gotta be on this. Like we're, we're taking way too long to get to 80%. Well,swyx: no, I mean, so like. How are they approaching it?Right? Because you're, you don't have a, you don't have a final answer yet.Why Coding Agents Took Off FirstAaron Levie: Well, okay, so, so this is actually, this is the stark reality that like, unfortunately is the kinda like pouring the water on the party a little bit.swyx: Yes.Aaron Levie: We all in Silicon Valley are like, have the absolute best conditions possible for AI ever.And I think we all saw the dke, you know, kind of Dario podcast and this idea of AI coding. Why is that taken off? And, and we're not yet fully seeing it everywhere else. Well, look, if you just like enumerated the list of properties that AI coding has and then compared it to other [00:12:00] knowledge work, let's just, let's just go through a few of them.Generally speaking, you bring on a new engineer, they have access to a large swath of the code base. Like, there's like very, like you, just, like new engineer comes on, they can just go and find the, the, the stuff that they, they need to work with. It's a fully text in text out. Medium. It's only, it's just gonna be text at the end of the day.So it's like really great from a, from just a, uh, you know, kinda what the agent can work with. Obviously the models are super trained on that dataset. The labs themselves have a really strong, kind of self-reinforcing positive flywheel of why they need to do, you know, agent coding deeply. So then you get just better tooling, better services.The actual developers of the AI are daily users of the, of the thing that they're we're working on versus like the, you know, probably there's only like seven Claude Cowork legal plugin users at Anthropic any given day, but there's like a couple thousand Claude code and you know, users every single day.So just like, think about which one are they getting more feedback on. All day long. So you just go through this list. You have a, you know, everybody who's a [00:13:00] developer by definition is technical so they can go install the latest thing. We're all generally online, or at least, you know, kinda the weird ones are, and we're all talking to each other, sharing best practices, like that's like already eight differences.Versus the rest of the economy. Every other part of the economy has like, like six to seven headwinds relative to that list. You go into a company, you're a banker in financial services, you have access to like a, a tiny little subset of the total data that's gonna be relevant to do your job. And you're have to start to go and talk to a bunch of people to get the right data to do your job because Sally didn't add you to that deal room, you know, folder.And that that, you know, the information is actually in a completely different organization that you now have to go in and, and sort of run into. And it's like you have this endless list of access controls and security. As, as you talked about, you have a medium, which is not, it's not just text, right? You have, you have a zoom call that, that you're getting all of the requirements from the customer.You have a lot of in-person conversations and you're doing in-person sales and like how do you ever [00:14:00] digitize all of that information? Um, you know, I think a lot of people got upset with this idea that the code base has all the context, um, that I don't know if you follow, you know, did you follow some of that conversation that that went viral?Is like, you know, it's not that simple that, that the code base doesn't have all the knowledge, but like it's a lot, you're a lot better off than you are with other areas of knowledge work. Like you, we like, we like have documentation practices, you write specifications. Those things don't exist for like 80% of work that happens in the enterprise.That's the divide that we have, which is, which is AI coding has, has just fully, you know, where we've reached escape velocity of how powerful this stuff is, and then we're gonna have to find a way to bring that same energy and momentum, but to all these other areas of knowledge work. Where the tools aren't there, the data's not set up to be there.The access controls don't make it that easy. The context engineering is an incredibly hard problem because again, you have access control challenges, you have different data formats. You have end users that are gonna need to kind of be kind of trained through this as opposed to their adopting [00:15:00] these tools in their free time.That's where the Fortune 500 is. And so we, I think, you know, have to be prepared as an industry where we are gonna be on a multi-year march to, to be able to bring agents to the enterprise for these workflows. And I think probably the, the thing that we've learned most in coding that, that the rest of the world is not yet, I think ready for, I mean, we're, they'll, they'll have to be ready for it because it's just gonna inevitably happen is I think in coding.What, what's interesting is if you think about the practice of coding today versus two years ago. It's probably the most changed workflow in maybe the history of time from the amount of time it's changed, right? Yeah. Like, like has any, has any workflow in the entire economy changed that quickly in terms of the amount of change?I just, you know, at least in any knowledge worker workflow, there's like very rarely been an event where one piece of technology and work practice has so fundamentally, you know, changed, changed what you do. Like you don't write code, you talk to an agent and it goes and [00:16:00] does it for you, and you may be at best review it.And even that's even probably like, like largely not even what you're doing. What's happening is we are changing our work to make the agents effective. In that model, the agent didn't really adapt to how we work. We basically adapted to how the agent works. Mm-hmm. All of the economy has to go through that exact same evolution.The rest of the economy is gonna have to update its workflows to make agents effective. And to give agents the context that they need and to actually figure out what kind of prompting works and to figure out how do you ensure that the agent has the right access to information to be able to execute on its work.I, you know, this is not the panacea that people were hoping for, of the agent drops in, just automates your life. Like you have to basically re-engineer your workflow to get the most out of agents and, uh, and that, that's just gonna take, you know, multiple years across the economy. Right now it's a huge asset and an advantage for the teams that do it early and that are kinda wired into doing this.‘cause [00:17:00] you'll see compounding returns, but that's just gonna take a while for most companies to actually go and get this deployed.swyx: I love, I love pushing back. I think that. That is what a lot of technology consultants love to hear this sort of thing, right? Yeah, yeah, yeah. First to, to embrace the ai. Yes. To get to the promised land, you must pay me so much money to a hundred percent to adopt the prescribed way of, uh, conforming to the agents.Yes. And I worry that you will be eclipsed by someone else who says, no, come as you are.Aaron Levie: Yeah.swyx: And we'll meet you where you are.Aaron Levie: And, and, and and what was the thing that went viral a week ago? OpenAI probably, uh, is hiring F Dees. Yeah. Uh, to go into the enterprise. Yeah. Yeah. And then philanthropic is embedded at Goldman Sachs.Yeah. So if the labs are having to do this, if, if the labs have decided that they need to hire FDE and professional services, then I think that's a pretty clear indication that this, there's no easy mode of workflow transformation. Yeah. Yeah. So, so to your point, I think actually this is a market opportunity for, you know, new professional services and consulting [00:18:00] firms that are like Agent Build and they, and they kind of, you know, go into organizations and they figure out how to re-engineer your workflows to make them more agent ready and get your data into the right format and, you know, reconstruct your business process.So you're, you're not doing most of the work. You're telling agents how to do the work and then you're reviewing it. But I haven't seen the thing that can just drop in and, and kinda let you not go through those changes.swyx: I don't know how that kind of sales pitch goes over. Yeah. You know, you're, you're saying things like, well, in my sort of nice beautiful walled garden, here's, there's, uh, because here's this, here's this beautiful box account that has everything.Yes. And I'm like, well, most, most real life is extremely messy. Sure. And like, poorly named and there duplicate this outdated s**tAaron Levie: a hundred percent. And so No, no, a hundred percent. And so this is actually No. So, so this is, I mean, we agree that, that getting to the beautiful garden is gonna be tough.swyx: Yeah.Aaron Levie: There's also the other end of the spectrum where I, I just like, it's a technical impossibility to solve. The agent is, is truly cannot get enough context to make the right decision in, in the, in the incredibly messy land. Like there's [00:19:00] no a GI that will solve that. So, so we're gonna have to kind of land in somewhere in between, which is like we all collectively get better at.Documentation practices and, and having authoritative relatively up-to-date information and putting it in the right place like agents will, will certainly cause us to be much better organized around how we work with our information, simply because the severity of the agent pulling the wrong data will be too high and the productivity gain of that you'll miss out on by not doing this will be too high as well, that you, that your competition will just do it and they'll just have higher velocity.So, uh, and, and we, we see this a lot firsthand. So we, we build a series of agents internally that they can kind of have access to your full box account and go off and you give it a task and it can go find whatever information you're looking for and work with. And, you know, thank God for the model progress, but like, if, if you gave that task to an agent.Nine months ago, you're just gonna get lots of bogus answers because it's gonna, it's gonna say, Hey, here's, here are fi [00:20:00] five, you know, documents that all kind of smell like the right thing. And I'm gonna, but I, but you're, you're putting me on the clock. ‘cause my assistant prompt says like, you know, be pretty smart, but also try and respond to the user and it's gonna respond.And it's like, ah, it got the wrong document. And then you do that once or twice as a knowledge worker and you're just neverswyx: again,Aaron Levie: never again. You're just like done with the system.swyx: Yeah. It doesn't work.Aaron Levie: It doesn't work. And so, you know, Opus four six and Gemini three one Pro and you know, whatever the latest five 3G BT will be, like, those things are getting better and better and it's using better judgment.And this sort of like the, all of these updates to the agentic tool and search systems are, are, we're seeing, we're seeing very real progress where the agent. Kind of can, can almost smell some things a little bit fishy when it's getting, you know, we, we have this process where we, we have it go fan out, do a bunch of searches, pull up a bunch of data, and then it has to sort of do its own ranking of, you know, what are the right documents that, that it should be working with.And again, like, you know, the intelligence level of a model six months ago, [00:21:00] it'd be just throwing a dart at like, I'm just, I'm gonna grab these seven files and I, I pray, I hope that that's the right answer. And something like an opus first four five, and now four six is like, oh, it's like, no, that one doesn't seem right relative to this question because I'm seeing some signal that is making that, you know, that's contradicting the document where it would normally be in the tree and who should have access.Like it's doing all of that kind of work for you. But like, it still doesn't work if you just have a total wasteland of data. Like, it's just not, it's just not possible. Partly ‘cause a human wouldn't even be able to do it. So basically if a, if a really, really smart human. Could not do that task in five or 10 minutes for a search retrieval type task.Look, you know, your agent's not gonna be able to do it any better. You see this all day long. SoContext Engineering and Search Limitsswyx: this touches on a thing that just passionate about it was just context engineering. I, I'm just gonna let you ramble or riff on, on context engineering. If, if, if there's anything like he, he did really good work on context fraud, which has really taken over as like the term that people use and the referenceAaron Levie: a hundred percent.We, we all we think about is, is the context rob problem. [00:22:00]Jeff Huber: Yeah, there's certainly a lot of like ranking considerations. Gentech surgery think is incredibly promising. Um, yeah, I was trying to generate a question though. I think I have a question right now. Swyx.Aaron Levie: Yeah, no, but like, like I think there was this moment, um, you know, like, I don't know, two years ago before, before we knew like where the, the gotchas were gonna be in ai and I think someone was like, was like, well, infinite context windows will just solve all of these problems and ‘cause you'll just, you'll just give the context window like all the data and.It's just like, okay, I mean, maybe in 2035, like this is a viable solution. First of all, it, it would just, it would just simply cost too much. Like we just can't give the model like the 5,000 documents that might be relevant and it's gonna read them all. And I've seen enough to, to start believing in crazy stuff.So like, I'm willing to just say, sure. Like in, in 10 years from now,swyx: never say, never, never.Aaron Levie: In, in 10 years from now, we'll have infinite context windows at, at a thousandth of the price of today. Like, let's just like believe that that's possible, but Right. We're in reality today. So today we have a context engineering [00:23:00] problem, which is, I got, I got, you know, 200,000 tokens that I can work with, or prob, I don't even know what the latest graph is before, like massive degradation.16. Okay. I have 60,000 tokens that I get to work with where I'm gonna get accurate information. That's not a lot of tokens for a corpus of 10 million documents that a knowledge worker might have across all of the teams and all the projects and all the people they work with. I have, I have 10 million documents.Which, you know, maybe is times five pages per document or something like that. I'm at 50 million pages of information and I have 60,000 tokens. Like, holy s**t. Yeah. This is like, how do I bridge the 50 million pages of information with, you know, the couple hundred that I get to work with in that, in that token window.Yeah. This is like, this is like such an interesting problem and that's why actually so much work is actually like, just like search systems and the databases and that layer has to just get so locked in, but models getting better and importantly [00:24:00] knowing when they've done a search, they found the wrong thing, they go back, they check their work, they, they find a way to balance sort of appeasing the user versus double checking.We have this one, we have this one test case where we ask the agent to go find. 10 pieces of information.swyx: Is this the complex work eval?Aaron Levie: Uh, this is actually not in the eval. This is, this is sort of just like we have a bunch of different, we have a bunch of internal benchmark kind of scenarios. Every time we, we update our agent, we have one, which is, I ask it to find all of our office addresses, and I give it the list of 10 offices that we have.And there's not one document that has this, maybe there should be, that would be a great example of the kind of thing that like maybe over time companies start to, you know, have these sort of like, what are the canonical, you know, kind of key areas of knowledge that we need to have. We don't seem to have this one document that says, here are all of our offices.We have a bunch of documents that have like, here's the New York office and whatever. So you task this agent and you, you get, you say, I need the addresses for these 10 offices. Okay. And by the way, if you do this on any, you know, [00:25:00] public chat model, the same outcome is gonna happen. But for a different kind of query, you give it, you say, I need these 10 addresses.How many times should the agent go and do its search before it decides whether or not, there's just no answer to this question. Often, and especially the, the, let's say lower tier models, it'll come back and it'll give you six of the 10 addresses. And it'll, and I'll just say I couldn't find the otherswyx: four.It, it doesn't know what It doesn't know. ItAaron Levie: doesn't know what It doesn't know. Yeah. So the model is just like, like when should it stop? When should it stop doing? Like should it, should it do that task for literally an hour and just keep cranking through? Maybe I actually made up an office location and it doesn't know that I made it up and I didn't even know that I made it up.Like, should it just keep, re should it read every single file in your entire box account until it, until it should exhaust every single piece of information.swyx: Expensive.Aaron Levie: These are the new problems that we have. So, you know, something like, let's say a new opus model is sort of like, okay, I'm gonna try these types of queries.I didn't get exactly what I wanted. I'm gonna try again. I'm gonna, at [00:26:00] some point I'm gonna stop searching. ‘cause I've determined that that no amount of searching is gonna solve this problem. I'm just not able to do it. And that judgment is like a really new thing that the model needs to be able to have.It's like, when should it give up on a task? ‘cause, ‘cause you just don't, it's a can't find the thing. That's the real world of knowledge, work problems. And this is the stuff that the coding agents don't have to deal with. Because they, it just doesn't like, like you're not usually asking it about, you're, you're always creating net new information coming right outta the model for the most part.Obviously it has to know about your code base and your specs and your documentation, but, but when you deploy an agent on all of your data that now you have all of these new problems that you're dealing withJeff Huber: our, uh, follow follow-up research to context ride is actually on a genetic search. Ah. Um, and we've like right, sort of stress tested like frontier models and their ability to search.Um, and they're not actually that good at searching. Right. Uh, so you're sort of highlighting this like explore, exploit.swyx: You're just say, Debbie, Donna say everything doesn't work. Like,Aaron Levie: well,Jeff Huber: somebody has to be,Aaron Levie: um, can I just throw out one more thing? Yeah. That is different from coding and, and the rest [00:27:00] of the knowledge work that I, I failed to mention.So one other kind of key point is, is that, you know, at the end of the day. Whether you believe we're in a slop apocalypse or, or whatever. At the end of the day, if you, if you build a working product at the end of, if you, if you've built a working solution that is ultimately what the customer is paying for, like whether I have a lot of slop, a little slop or whatever, I'm sure there's lots of code bases we could go into in enterprise software companies where it's like just crazy slop that humans did over a 20 year period, but the end customer just gets this little interface.They can, they can type into it, it does its thing. Knowledge work, uh, doesn't have that property. If I have an AI model, go generate a contract and I generate a contract 20 times and, you know, all 20 times it's just 3% different and like that I, that, that kind of lop introduces all new kinds of risk for my organization that the code version of that LOP didn't, didn't introduce.These are, and so like, so how do you constrain these models to just the part that you want [00:28:00] them to work on and just do the thing that you want them to do? And, and, you know, in engineering, we don't, you can't be disbarred as an engineer, but you could be disbarred as a lawyer. Like you can do the wrong medical thing In healthcare, you, there's no, there's no equivalent to that of engineering.Like, doswyx: you want there to be, because I've considered softwareJeff Huber: engineer. What's that? Civil engineering there is, right? NotAaron Levie: software civil engineer. Sure. Oh yeah, for sure. But like in any of our companies, you like, you know, you'll be forgiven if you took down the site and, and we, we will do a rollback and you'll, you'll be in a meeting, but you have not been disbarred as an engineer.We don't, we don't change your, you know, your computer science, uh, blameJeff Huber: degree, this postmortem.Aaron Levie: Yeah, exactly. Exactly. So, so, uh, now maybe we collectively as an industry need to figure out like, what are you liable for? Not legally, but like in a, in a management sense, uh, of these agents. All sorts of interesting problems that, that, that, uh, that have to come out.But in knowledge work, that's the real hostile environments that we're operating in. Hmm.swyx: I do think like, uh, a lot of the last year's, 2025 story was the rise of coding agents and I think [00:29:00] 2026 story is definitely knowledge work agents. Yes. A hundredAaron Levie: percent.swyx: Right. Like that would, and I think open claw core work are just the beginning.Yes. Like it's, the next one's gonna just gonna be absolute craziness.Aaron Levie: It it is. And, and, uh, and it's gonna be, I mean, again, like this is gonna be this, this wave where we, we are gonna try and bring as many of the practices from coding because that, that will clearly be the forefront, which is tell an agent to go do something and has an access to a set of resources.You need to be responsible for reviewing it at the end of the process. That to me is the, is the kind of template that I just think goes across knowledge, work and odd. Cowork is a great example. Open Closet's a great example. You can kind of, sort of see what Codex could become over time. These are some, some really interesting kind of platforms that are emerging.swyx: Okay. Um, I wanted to, we touched on evals a little bit. You had, you had the report that you're gonna go bring up and then I was gonna go into like, uh, boxes, evals, but uh, go ahead. Talk about your genetic search thing.Jeff Huber: Yeah. Mostly I think kinda a few of the insights. It's like number one frontier model is not good at search.Humans have this [00:30:00] natural explore, exploit trade off where we kinda understand like when to stop doing something. Also, humans are pretty good at like forgetting actually, and like pruning their own context, whereas agents are not, and actually an agent in their kind of context history, if they knew something was bad and they even, you could see in the trace the reason you trace, Hey, that probably wasn't a good idea.If it's still in the trace, still in the context, they'll still do it again. Uhhuh. Uh, and so like, I think pruning is also gonna be like, really, it's already becoming a thing, right? But like, letting self prune the con windowsswyx: be a big deal. Yeah. So, so don't leave the mistake. Don't leave the mistake in there.Cut out the mistake but tell it that you made a mistake in the past and so it doesn't repeat it.Jeff Huber: Yeah. But like cut it out so it doesn't get like distracted by it again. ‘cause really, you know, what is so, so it will repeat its mistake just because it's been, it's inswyx: theJeff Huber: context. It'sAaron Levie: in the context so much.That's a few shot example. Even if it, yeah.Jeff Huber: It's like oh thisAaron Levie: is a great thing to go try even ifJeff Huber: it didn't work.Aaron Levie: Yeah,Jeff Huber: exactly.Aaron Levie: SoJeff Huber: there's like a bunch of stuff there. JustAaron Levie: Groundhogs Day inside these models. Yeah. I'm gonna go keep doing the same wrongJeff Huber: thing. Covering sense. I feel like, you know, some creator analogy you're trying like fit a manifold in latent space, which kind is doing break program synthesis, which is kinda one we think about we're doing right.Like, you know, certain [00:31:00] facts might be like sort of overly pitting it. There are certain, you know, sec sectors of latent space and so like plug clean space. Yeah. And, uh, andswyx: so we have a bell, our editor as a bell every time you say that. SoJeff Huber: you have, you have to like remove those, likeswyx: you shoulda a gong like TPN or something.IfJeff Huber: we gong, you either remove those links to like kinda give it the freedom, kind of do what you need to do. So, but yeah. We'll, we'll release more soon. That'sAaron Levie: awesome.Jeff Huber: That'll, that'll be cool.swyx: We're a cerebral podcast that people listen to us and, and sort of think really deep. So yeah, we try to keep it subtle.Okay. We try to keep it.Aaron Levie: Okay, fine.Inside Agent Evalsswyx: Um, you, you guys do, you guys do have EVs, you talked about your, your office thing, but, uh, you've been also promoting APEX agents and complex work. Uh, yeah, whatever you, wherever you wanna take this just Yeah. How youAaron Levie: Apex is, is obviously me, core's, uh, uh, kind of, um, agent eval.We, we supported that by sort of. Opening up some data for them around how we kind of see these, um, data workspaces in, in the, you know, kind of regular economy. So how do lawyers have a workspace? How do investment bankers have a workspace? What kind of data goes into those? And so we, [00:32:00] we partner with them on their, their apex eval.Our own, um, eval is, it's actually relatively straightforward. We have a, a set of, of documents in a, in a range of industries. We give the agent previously did this as a one shot test of just purely the model. And then we just realized we, we need to, based on where everything's going, it's just gotta be more agentic.So now it's a bit more of a test of both our harness and the model. And we have a rubric of a set of things that has to get right and we score it. Um, and you're just seeing, you know, these incredible jumps in almost every single model in its own family of, you know, opus four, um, you know, sonnet four six versus sonnet four five.swyx: Yeah. We have this up on screen.Aaron Levie: Okay, cool. So some, you're seeing it somewhere like. I, I forget the to, it was like 15 point jump, I think on the main, on the overall,swyx: yes.Aaron Levie: And it's just like, you know, these incredible leaps that, that are starting to happen. Um,swyx: and OP doesn't know any, like any, it's completely held out from op.Aaron Levie: This is not in any, there's no public data which has, you know, Ben benefits and this is just a private eval that we [00:33:00] do, and then we just happen to show it to, to the world. Hmm. So you can't, you can't train against it. And I think it's just as representative of. It's obviously reasoning capabilities, what it's doing at, at, you know, kind of test time, compute capabilities, thinking levels, all like the context rot issues.So many interesting, you know, kind of, uh, uh, capabilities that are, that are now improvingswyx: one sector that you have. That's interesting.Industries and Datasetsswyx: Uh, people are roughly familiar with healthcare and legal, but you have public sector in there.Aaron Levie: Yeah.swyx: Uh, what's that? Like, what, what, what is that?Aaron Levie: Yeah, and, and we actually test against, I dunno, maybe 10 industries.We, we end up usually just cutting a few that we think have interesting gains. All extras, won a lot of like government type documents. Um,swyx: what is that? What is it? Government type documents?Aaron Levie: Government filings. Like a taxswyx: return, likeAaron Levie: a probably not tax returns. It would be more of what would go the government be using, uh, as data.So, okay. Um, so think about research that, that type of, of, of data sets. And then we have financial services for things like data rooms and what would be in an investment prospectus. Uhhuh,swyx: that one you can dog food.Aaron Levie: Yeah, exactly. Exactly. Yes. Yes. [00:34:00] So, uh, so we, we run the models, um, in now, you know, more of an agent mode, but, but still with, with kinda limited capacity and just try and see like on a, like, for like basis, what are the improvements?And, and again, we just continue to be blown away by. How, how good these models are getting.swyx: Yeah, I mean, I think every serious AI company needs something like that where like, well, this is the work we do. Here's our company eval. Yeah. And if you don't have it, well, you're not a serious AI company.Aaron Levie: There's two dimensions, right?So there's, there's like, how are the models improving? And so which models should you either recommend a customer use, which one should you adopt? But then every single day, we're making changes to our agents. And you need to knowswyx: if you regressed,Aaron Levie: if you know. Yeah. You know, I've been fully convinced that the whole agent observability and eval space is gonna be a massive space.Um, super excited for what Braintrust is doing, excited for, you know, Lang Smith, all the things. And I think what you're going to, I mean, this is like every enter like literally every enterprise right now. It's like the AI companies are the customers of these tools. Every enterprise will have this. Yeah, you'll just [00:35:00] have to have an eval.Of all of your work and like, we'll, you'll have an eval of your RFP generation, you'll have an eval of your sales material creation. You'll have an eval of your, uh, invoice processing. And, and as you, you know, buy or use new agentic systems, you are gonna need to know like, what's the quality of your, of your pipeline.swyx: Yeah.Aaron Levie: Um, so huge, huge market with agent evals.swyx: Yeah.Building the Agent Teamswyx: And, and you know, I'm gonna shout out your, your team a bit, uh, your CTO, Ben, uh, did a great talk with us last year. Awesome. And he's gonna come back again. Oh, cool. For World's Fair.Aaron Levie: Yep.swyx: Just talk about your team, like brag a little bit. I think I, I think people take these eval numbers in pretty charts for granted, but No, there, I mean, there's, there's lots of really smart people at work during all this.Aaron Levie: Biggest shout out, uh, is we have a, we have a couple folks at Dya, uh, Sidarth, uh, that, that kind of run this. They're like a, you know, kind of tag tag team duo on our evals, Ben, our CTO, heavily involved Yasha, head of ai, uh, you know, a bunch of folks. And, um, evals is one part of the story. And then just like the full, you know, kind of AI.An agent team [00:36:00] is, uh, is a, is a pretty, you know, is core to this whole effort. So there's probably, I don't know, like maybe a few dozen people that are like the epicenter. And then you just have like layers and layers of, of kind of concentric circles of okay, then there's a search team that supports them and an infrastructure team that supports them.And it's starting to ripple through the entire company. But there's that kind of core agent team, um, that's a pretty, pretty close, uh, close knit group.swyx: The search team is separate from the infra team.Aaron Levie: I mean, we have like every, every layer of the stack we have to kind of do, except for just pure public cloud.Um, but um, you know, we, we store, I don't even know what our public numbers are in, you know, but like, you can just think about it as like a lot of data is, is stored in box. And so we have, and you have every layer of the, of the stack of, you know, how do you manage the data, the file system, the metadata system, the search system, just all of those components.And then they all are having to understand that now you've got this new customer. Which is the agent, and they've been building for two types of customers in the past. They've been building for users and they've been building for like applications. [00:37:00] And now you've got this new agent user, and it comes in with a difference of it, of property sometimes, like, hey, maybe sometimes we should do embeddings, an embedding based, you know, kind of search versus, you know, your, your typical semantic search.Like, it's just like you have to build the, the capabilities to support all of this. And we're testing stuff, throwing things away, something doesn't work and, and not relevant. It's like just, you know, total chaos. But all of those teams are supporting the agent team that is kind of coming up with its requirements of what, what do we need?swyx: Yeah. No, uh, we just came from, uh, fireside chat where you did, and you, you talked about how you're doing this. It's, it's kind of like an internal startup. Yeah. Within the broader company. The broader company's like 3000 people. Yeah. But you know, there's, there's a, this is a core team of like, well, here's the innovation center.Aaron Levie: Yeah.swyx: And like that every company kind of is run this way.Aaron Levie: Yeah. I wanna be sensitive. I don't call it the innovation center. Yeah. Only because I think everybody has to do innovation. Um, there, there's a part of the, the, the company that is, is sort of do or die for the agent wave.swyx: Yeah.Aaron Levie: And it only happens to be more of my focus simply because it's existential that [00:38:00] we get it right.swyx: Yeah.Aaron Levie: All of the supporting systems are necessary. All of the surrounding adjacent capabilities are necessary. Like the only reason we get to be a platform where you'd run an agent is because we have a security feature or a compliance feature, or a governance feature that, that some team is working on.But that's not gonna be the make or break of, of whether we get agents right. Like that already exists and we need to keep innovating there. I don't know what the right, exact precise number is, but it's not a thousand people and it's not 10 people. There's a number of people that are like the, the kind of like, you know, startup within the company that are the make or break on everything related to AI agents, you know, leveraging our platform and letting you work with your data.And that's where I spend a lot of my time, and Ben and Yosh and Diego and Teri, you know, these are just, you know, people that, that, you know, kind of across the team. Are working.swyx: Yeah. Amazing.Read Write Agent WorkflowsJeff Huber: How do you, how do you think about, I mean, you talked a lot about like kinda read workflows over your box data. Yep.Right. You know, gen search questions, queries, et cetera. But like, what about like, write or like authoring workflows?Aaron Levie: Yes. I've [00:39:00] already probably revealed too much actually now that I think about it. So, um, I've talked about whatever,Jeff Huber: whatever you can.Aaron Levie: Okay. It's just us. It's just us. Yeah. Okay. Of course, of course.So I, I guess I would just, uh, I'll make it a little bit conceptual, uh, because again, I've already, I've already said things that are not even ga but, but we've, we've kinda like danced around it publicly, so I, yeah, yeah. Okay. Just like, hopefully nobody watches this, um, episode. No.swyx: It's tidbits for the Heidi engaged to go figure out like what exactly, um, you know, is, is your sort of line of thinking.Sure. They can connect the dots.Aaron Levie: Yeah. So, so I would say that, that, uh, we, you know, as a, as a place where you have your enterprise content, there's a use case where I want to, you know, have an agent read that data and answer questions for me. And then there's a use case where I want the agent to create something.And use the file system to create something or store off data that it's working on, or be able to have, you know, various files that it's writing to about the work it's doing. So we do see it as a total read write. The harder problem has so far been the read only because, because again, you have that kind of like 10 [00:40:00] million to one ratio problem, whereas rights are a lot of, that's just gonna come from the model and, and we just like, we'll just put it in the file system and kinda use it.So it's a little bit of a technically easier problem, but the only part that's like, not necessarily technically hard, it is just like it's not yet perfected in the state of the ecosystem is, you know, building a beautiful PowerPoint presentation. It's still a hard problem for these models. Like, like we still, you know, like, like these formats are just, we're not built for.They'reswyx: working on it.Aaron Levie: They're, they're working on it. Everybody's working on it.swyx: Every launch is like, well, we do PowerPoint now.Aaron Levie: We're getting, yeah, getting a lot, getting a lot of better each time. But then you'll do this thing where you'll ask the update one slide and all of a sudden, like the fonts will be just like a little bit different, you know, on two of the slides, or it moved, you know, some shape over to the left a little bit.And again, these are the kind of things that, like in code, obviously you could really care about if you really care about, you know, how beautiful is the code, but at the end, user doesn't notice all those problems and file creation, the end user instantly sees it. You're [00:41:00] like, ah, like paragraph three, like, you literally just changed the font on me.Like it's a totally different font and like midway through the document. Mm-hmm. Those are the kind of things that you run into a lot of in the, in the content creation side. So, mm-hmm. We are gonna have native agents. That do all of those things, they'll be powered by the leading kind of models and labs.But the thing that I think is, is probably gonna be a much bigger idea over time is any agent on any system, again, using Box as a file system for its work, and in that kind of scenario, we don't necessarily care what it's putting in the file system. It could put its memory files, it could put its, you know, specification, you know, documents.It could put, you know, whatever its markdown files are, or it could, you know, generate PDFs. It's just like, it's a workspace that is, is sort of sandboxed off for its work. People can collaborate into it, it can share with other people. And, and so we, we were thinking a lot about what's the right, you know, kind of way to, to deliver that at scale.Docs Graphs and Founder Modeswyx: I wanted to come into sort of the sort of AI transformation or AI sort of, uh, operations things. [00:42:00] Um, one of the tweets that you, that you wanted to talk about, this is just me going through your tweets, by the way. Oh, okay. I mean, like, this is, you readAaron Levie: one by one,swyx: you're the, you're the easiest guest to prep for because you, you already have like, this is the, this is what I'm interested in.I'm like, okay, well, areAaron Levie: we gonna get to like, like February, January or something? Where are we in the, in the timelines? How far back are we going?swyx: Can you, can you describe boxes? A set of skills? Right? Like that, that's like, that's like one of the extremes of like, well if you, you just turn everything into a markdown file.Yeah. Then your agent can run your company. Uh, like you just have to write, find the right sequence of words toAaron Levie: Yes.swyx: To do it.Aaron Levie: Sorry, isthatswyx: the question? So I think the question is like, what if we documented everything? Yes. The way that you exactly said like,Aaron Levie: yes.swyx: Um, let's get all the Fortune five hundreds, uh, prepared for agents.Yes. And like, you know, everything's in golden and, and nicely filed away and everything. Yes. What's missing? Like, what's left, right? LikeAaron Levie: Yeah.swyx: You've, you've run your company for a decade. LikeAaron Levie: Yeah. I think the challenge is that, that that information changes a week later. And because something happened in the market for that [00:43:00] customer, or us as a company that now has to go get updated, and so these systems are living and breathing and they have to experience reality and updates to reality, which right now is probably gonna be humans, you know, kinda giving those, giving them the updates.And, you know, there is this piece about context graphs as as, uh, that kinda went very viral. Yeah. And I, I, I was like a, i, I, I thought it was super provocative. I agreed with many parts of it. I disagree with a few parts around. You know, it's not gonna be as easy as as just if we just had the agent traces, then we can finally do that work because there's just like, there's so much more other stuff that that's happening that, that we haven't been able to capture and digitize.And I think they actually represented that in the piece to be clear. But like there's just a lot of work, you know, that that has to, you just can't have only skills files, you know, for your company because it's just gonna be like, there's gonna be a lot of other stuff that happens. Yeah. Change over time.Yeah. Most companies are practically apprenticeships.swyx: Most companies are practically apprenticeships. LikeJeff Huber: every new employee who joins the team, [00:44:00] like you span one to three months. Like ramping them up.Aaron Levie: Yes. AllJeff Huber: that tat knowledgeAaron Levie: isJeff Huber: not written down.Aaron Levie: Yes.Jeff Huber: But like, it would have to be if you wanted to like give it to an Asian.Right. And so like that seems to me like to beAaron Levie: one is I think you're gonna see again a premium on companies that can document this. Mm-hmm. Much. There'll be a huge premium on that because, because you know, can you shorten that three month ramp cycle to a two week ramp cycle? That's an instant productivity gain.Can you re dramatically reduce rework in the organization because you've documented where all the stuff is and where the answers are. Can you make your average employee as good as your 90th percentile employee because you've captured the knowledge that's sort of in the heads of, of those top employees and make that available.So like you can see some very clear productivity benefits. Mm-hmm. If you had a company culture of making sure you know your information was captured, digitized, put in a format that was agent ready and then made available to agents to work with, and then you just, again, have this reality of like add a 10,000 person [00:45:00] company.Mapping that to the, you know, access structure of the company is just a hard problem. Is like, is like, yeah, well, you just, not every piece of information that's digitized can be shared to everybody. And so now you have to organize that in a way that actually works. There was a pretty good piece, um, this, this, uh, this piece called your company as a file is a file system.I, did you see that one?swyx: Nope.Aaron Levie: Uh, yes. You saw it. Yeah. And, and, uh, I actually be curious your thoughts on it. Um, like, like an interesting kind of like, we, we agree with it because, because that's how we see the world and, uh,swyx: okay. We, we have it up on screen. Oh,Aaron Levie: okay. Yeah. But, but it's all about basically like, you know, we've already, we, we, we already organized in this kind of like, you know, permission structure way.Uh, and, and these are the kind of, you know, natural ways that, that agents can now work with data. So it's kind of like this, this, you know, kind of interesting metaphor, but I do think companies will have to start to think about how they start to digitize more, more of that data. What was your take?Jeff Huber: Yeah, I mean, like the company's probably like an acid compliant file system.Aaron Levie: Uh,Jeff Huber: yeah. Which I'm guessing boxes, right? So, yeah. Yes.swyx: Yeah. [00:46:00]Jeff Huber: Which you have a great piece on, but,swyx: uh, yeah. Well, uh, I, I, my, my, my direction is a little bit like, I wanna rewind a little bit to the graph word you said that there, that's a magic trigger word for us. I always ask what's your take on knowledge graphs?Yeah. Uh, ‘cause every, especially at every data database person, I just wanna see what they think. There's been knowledge graphs, hype cycles, and you've seen it all. So.Aaron Levie: Hmm. I actually am not the expert in knowledge graphs, so, so that you might need toswyx: research, you don't need to be an expert. Yeah. I think it's just like, well, how, how seriously do people take it?Yeah. Like, is is, is there a lot of potential in the, in the HOVI?Aaron Levie: Uh, well, can I, can I, uh, understand first if it's, um, is this a loaded question in the sense of are you super pro, super con, super anti medium? Iswyx: see pro, I see pros and cons. Okay. Uh, but I, I think your opinion should be independent of mine.Aaron Levie: Yeah. No, no, totally. Yeah. I just want to see what I'm stepping into.swyx: No, I know. It's a, and it's a huge trigger word for a lot of people out Yeah. In our audience. And they're, they're trying to figure out why is that? Because whyAaron Levie: is this such aswyx: hot item for them? Because a lot of people get graph religion.And they're like, everything's a graph. Of course you have to represent it as a graph. Well, [00:47:00] how do you solve your knowledge? Um, changing over time? Well, it's a graph.Aaron Levie: Yeah.swyx: And, and I think there, there's that line of work and then there's, there's a lot of people who are like, well, you don't need it. And both are right.Aaron Levie: Yeah. And what do the people who say you don't need it, what are theyswyx: arguing for Mark down files. Oh, sure, sure. Simplicity.Aaron Levie: Yeah.swyx: Versus it's, it's structure versus less structure. Right. That's, that's all what it is. I do.Aaron Levie: I think the tricky thing is, um, is, is again, when this gets met with real humans, they're just going to their computer.They're just working with some people on Slack or teams. They're just sharing some data through a collaborative file system and Google Docs or Box or whatever. I certainly like the vision of most, most knowledge graph, you know, kind of futuristic kind of ways of thinking about it. Uh, it's just like, you know, it's 2026.We haven't seen it yet. Kind of play out as as, I mean, I remember. Do you remember the, um, in like, actually I don't, I don't even know how old you guys are, but I'll for, for to show my age. I remember 17 years ago, everybody thought enterprises would just run on [00:48:00] Wikis. Yeah. And, uh, confluence and, and not even, I mean, confluence actually took off for engineering for sure.Like unquestionably. But like, this was like everything would be in the w. And I think based on our, uh, our, uh, general style of, of, of what we were building, like we were just like, I don't know, people just like wanna workspace. They're gonna collaborate with other people.swyx: Exactly. Yeah. So you were, you were anti-knowledge graph.Aaron Levie: Not anti, not anti. Soswyx: not nonAaron Levie: I'm not, I'm not anti. ‘cause I think, I think your search system, I just think these are two systems that probably, but like, I'm, I'm not in any religious war. I don't want to be in anybody's YouTube comments on this. There's not a fight for me.swyx: We, we love YouTube comments. We're, we're, we're get into comments.Aaron Levie: Okay. Uh, but like, but I, I, it's mostly just a virtue of what we built. Yeah. And we just continued down that path. Yeah.swyx: Yeah.Aaron Levie: And, um, and that, that was what we pursued. But I'm not, this is not a, you know, kind of, this is not a, uh, it'sswyx: not existential for you. Great.Aaron Levie: We're happy to plug into somebody else's graph.We're happy to feed data into it. We're happy for [00:49:00] agents to, to talk to multiple systems. Not, not our fight.swyx: Yeah.Aaron Levie: But I need your answer. Yeah. Graphs or nerd Snipes is very effective nerd.swyx: See this is, this is one, one opinion and then I've,Jeff Huber: and I think that the actual graph structure is emergent in the mind of the agent.Ah, in the same way it is in the mind of the human. And that's a more powerful graph ‘cause it actually involved over time.swyx: So don't tell me how to graph. I'll, I'll figure it out myself. Exactly. Okay. All right. AndJeff Huber: what's yours?swyx: I like the, the Wiki approach. Uh, my, I'm actually
On this episode of The Association Podcast, we welcome Ravi Rooprai, Director of IT and PMO at the Million Dollar Round Table (MDRT). Ravi shares his unique journey from molecular microbiology and pharmaceutical consulting into association technology leadership, bringing a scientific mindset to digital transformation and innovation.The conversation explores how MDRT is modernizing association technology by decoupling legacy systems, building scalable data ecosystems, and experimenting with AI-driven personalization. Ravi explains how his team approaches technology through experimentation, feasibility studies, and agile thinking to improve member experiences and operational efficiency.We also dive into MDRT's cutting-edge meeting technology, including large-scale multilingual interpretation powered by AI and the infrastructure required to support thousands of attendees simultaneously streaming translated sessions. Ravi discusses how associations can better leverage data, personalization, and experimentation to drive engagement, retention, and measurable member value.From building a culture of innovation to applying e-commerce thinking to membership value, this episode offers practical insights for association leaders navigating digital transformation.00:01:00 Introduction to Ravi Rooprai and MDRT00:01:30 Rapid Fire Questions00:02:40 Ravi's Career Journey from Science to Association Technology00:04:30 Lessons from Industry Applied to Associations00:05:30 Using ROI and Value Metrics in Association Technology Decisions00:07:00 Measuring Member Lifetime Value00:08:30 The Value of MDRT Membership for Financial Professionals00:10:30 Reworking Legacy AMS Systems Through Decoupled Data Architecture00:12:00 Building a Modern Data Ecosystem Around Legacy Platforms00:13:30 Scaling Membership Systems to Handle Peak Demand00:14:45 Managing 60–70K Membership Applications During Renewal Season00:16:00 Leveraging AI and Technology at Large Global Conferences00:17:00 Simultaneous Translation and Multilingual Meeting Experiences00:18:30 Solving Conference Connectivity and Infrastructure Challenges00:20:00 Improving the Member Experience Through Technology00:21:00 Favorite Tools: AI, Copilot, and Power Apps00:23:30 Empowering Staff to Experiment with Technology00:24:30 Personalization and Data-Driven Engagement00:26:00 Using Engagement Data to Shape Event Programming00:28:00 The Future of Digital Transformation in Associations00:29:00 Applying a Scientific Mindset to Technology Innovation00:31:00 Building a Culture of Experimentation and Safe Failure00:33:00 Feasibility Studies and Agile Technology Testing00:35:00 Applying E-commerce Thinking to Membership Value00:37:00 The Future of AI and Meeting Technology at MDRT00:39:00 Rethinking the Conference Experience00:40:00 Closing Thoughts
Winning races often comes down to one thing: precision chassis setup.In this episode of Race Industry Now, we explore the advanced engineering tools and measurement systems that help teams unlock maximum performance from their race cars.Featuring Brett Barker, Co-Founder & Chief Engineer of Creative Racing Products, and Charles Lewandoski, Founder of ChaLew Performance Products, this technical discussion dives deep into modern race car setup technology used across NASCAR-style stock cars, road racing, modifieds, drifting, and drag racing.Hosted by Brad Gillie from SiriusXM Ch. 90 Late Shift.Topics covered in this webinar include:• Wireless ride height sensors for ultra-precise measurements• Suspension load measurement using wireless load sticks• Dual load-cell racing scales for accurate corner weight distribution• Integrated chassis setup software and wireless data systems• Engineering methods used by professional race teams• How modern measurement tools eliminate setup guessworkThese technologies allow teams to monitor ride height, suspension loads, and weight distribution simultaneously, giving engineers the data they need to fine-tune performance and gain a competitive edge on track. Whether you're a race engineer, chassis builder, crew chief, or serious racer, this episode offers valuable insight into the next generation of race car setup tools and performance engineering.
Join Michael Newton, CEO of Qorium, for a visionary conversation on the power of synthetic biology to reshape our material world. With a track record of scaling products to over $1 billion in annual turnover at Nike, Michael is now leading the charge in cellular agriculture. In this episode, we explore the immense promise of synthetic biology, why Qorium's unique approach to lab-grown leather is a game-changer for the planet, and how we can re-engineer global value chains for a sustainable future.
NASA has announced a major restructuring of the Artemis program, reshaping the roadmap for returning humans to the Moon. At a February 27 press conference, agency leadership addressed the rollback of Artemis II following post–wet–dress–rehearsal testing and unveiled significant changes to upcoming missions, including shifting Artemis III from a planned lunar landing to a low-Earth-orbit rendezvous and integrated systems test. In this episode, you’ll hear remarks from NASA Administrator Jared Isaacman and Lori Glaze, Moon to Mars program manager and acting associate administrator for NASA’s Exploration Systems Development Mission Directorate. They explain what happened with Artemis II and why NASA is changing course. Then, host Sarah Al-Ahmed is joined by Jack Kiraly, director of government relations at The Planetary Society, and Ari Koeppel, AAAS science and technology policy fellow, to unpack the political and strategic forces behind this shift and what it means for the future of lunar exploration. In What’s Up, Bruce Betts, our chief scientist, looks back at Apollo 9, the Earth-orbiting mission that proved the Lunar Module could operate independently before NASA attempted a lunar landing. Discover more at: https://www.planetary.org/planetary-radio/2026-artemis-updateSee omnystudio.com/listener for privacy information.
Plus: Kraken becomes the first crypto firm to win access to the Federal Reserve's core payments system. And OpenAI CEO Sam Altman defended his Pentagon deal during an all-hands meeting. Danny Lewis hosts. Learn more about your ad choices. Visit megaphone.fm/adchoices
Ken Little: Bridging Engineering and BusinessToday, we're tackling one of the most expensive and underestimated problems in modern organizations: the communication gap between technical professionals and nontechnical leaders. I'm joined by Ken Little, SVP of Engineering, to explore where engineers most often struggle with nontechnical audiences, how to make complex ideas understandable to business-minded leaders so they can make better decisions, and what happens when that translation breaks down. We also dig into how organizations can build stronger communication muscles, and how engineers can move from explaining problems to making recommendations.To learn more about Ken, visit https://www.linkedin.com/in/kennethllittle/__TEACH THE GEEK (http://teachthegeek.com) Prefer video? Visit http://youtube.teachthegeek.comGet Public Speaking Tips for STEM Professionals at http://teachthegeek.com/tips
Did you know that millions of Americans drive each day in cars with open safety recalls that, if ignored, could have fatal consequences? This podcast hour we discussed how you can check if your vehicle has an open recall.8:05PM: Each year in the U.S., more than 500,000 people are treated and about 300 die from ladder-related injuries, according to CDC/NIOSH. In almost every case, these incidents are preventable. March is National Ladder Safety Month & the American Ladder Institute is offering free online Ladder Safety Training.Guest: Mike Van Bree - Director of Product Safety & Engineering with the American Ladder Institute 8:15PM: Can we still have private conversations if we live our lives online? A look at what our right is to digital privacy in today’s world.Guest: Cindy Cohn – Executive Director of the Electronic Frontier Foundation & Author of the book: Privacy's Defender: My Thirty-Year Fight Against Digital Surveillance8:30PM: March 2 – 8 is Vehicle Safety Recalls Week. From defective airbags to overheating batteries, millions of Americans drive each day in cars with open safety recalls that, if ignored, could have fatal consequences. How you can check if your vehicle has an open recall…Guest: Mark Schieldrop - Senior Spokesperson for AAA Northeast8:45PM: The best education for future success might surprise you…Career-focused programs mistakenly assume that what seems useful today will be useful tomorrow.Guest: Greg Weiner - professor of political science & president of Assumption University in Worcester, MassachusettsSee omnystudio.com/listener for privacy information.
In this episode of Construction Corner, host Dillon breaks down the right and wrong ways to use AI in business. While AI tools are everywhere, most people are using them for the wrong tasks—like writing generic emails or generating soulless responses that scream "bot." Instead, Dillon argues that AI's real power lies in strategic work: condensing weeks of market research into minutes, creating total addressable market analyses, plotting historical data trends, and automating time-consuming tasks like transcription and content scheduling. He emphasizes the 95/5 rule: let AI take you 95% of the way, then add your own voice, edits, and human touch for the final 5%. Drawing examples from yacht influencer Kevin's Instagram page and his own content workflow, Dillon makes it clear that AI should multiply your leverage and productivity—not replace your authenticity. Use it for the big strategic moves, not the bullshit busy work.Comment your thoughts below and don't forget to like, SHARE, and subscribe!Want an Engineering firm BUILT for Electrical Contractors? Let's see how we can help speed up your Design/Build projects. Visit https://verticaldesignservices.com/ Connect with Dillon MitchellLinkedIn - https://www.linkedin.com/in/dillon-mitchell-pe/Vertical Design Serviceshttps://www.instagram.com/vertical_designservices/#Revit #BIM #Automation #VerticalDesignServices #VDS #MEP #Contractors #Engineering #ElectricalContractor
The Parallel Reality Engineering Framework Shaun walks through the practical steps he uses when intentionally designing future outcomes. 1. Run the Simulation Imagine a future reality in detail: A new home A promotion A relocation A different financial lifestyle Go beyond the surface and imagine the full experience: Daily routines Responsibilities Trade-offs Emotional impact Ask yourself: Does this future actually light me up? 2. Write It Down Writing forces clarity. Turn imagination into strategy by identifying: What it looks like What it costs What it requires Who you must become This is where the metaphysical meets the physical. 3. Share the Vision When appropriate, bring others into the process. Whether it's a spouse, partner, or family member, shared futures accelerate progress because multiple people begin adapting to the same possibility. Ask yourself: Is this a shared future or just my ego future? 4. Build the Physical Plan Manifestation must eventually meet structure. Create a real-world framework: Budgets Time commitments Travel expectations Lifestyle adjustments When the logistics make sense, the vision becomes real. 5. Accept the Energy Cost Living in multiple potential futures can be exhausting. That's normal. You are expanding your nervous system and preparing for: New responsibilities New identity levels New financial realities Most people quit here because they want instant manifestation. 6. Use Technology as a Tool Modern tools like AI can assist with: Planning scenarios Budget simulations Career mapping Timeline possibilities But technology cannot replace the emotional signal that tells you whether a future truly aligns with you. 7. Release the Timeline The final step is critical. Feel it. Plan it. Align with it. Act toward it. Then detach from when it will happen. Ironically, when you stop forcing the timeline, progress often happens faster. The Warning: Passive Manifesting If you do not intentionally design your future, your subconscious will run the program for you. Often that means replaying: Old fears Scarcity thinking Past limitations People who consistently stack wins often do so because they have trained themselves to focus on possibility, growth, and positive expectation. Final Thought Manifesting should be fun. But it should also require effort. You are not wishing for the future. You are: rehearsing it aligning with it engineering it And when you consistently step into the emotional and physical reality of your next chapter, your future begins organizing itself around you. Connect with Shaun Podcast: https://podcasts.apple.com/us/podcast/business-finance-and-soul/id1680587418 https://www.linkedin.com/in/shaunenders/ Host: Shaun Enders Follow for more conversations at the intersection of business, personal growth, and intentional living. www.BusinessFinanceAndSoul.com
What does it take to lead a 70-year engineering firm into its next chapter of growth without losing the culture that built it?Katie Cash sits down with Carrie Stokes, President and CEO of Barge Design Solutions, and Erika Booker, Chief Marketing Officer of Barge Design Solutions, to unpack how leadership vision, marketing alignment, and data-driven strategy fuel sustainable growth in today's competitive AEC market. From intentional CEO transition planning to integrating communications and sales enablement, they share how employee ownership, disciplined client selection, and CRM-backed business development decisions protect both culture and profitability.If you lead an engineering firm or support one through marketing and business development, this conversation offers a clear look at how alignment across the C-suite and marketing team drives measurable impact and long-term brand strength.Topics discussed in this episode:Engineering firm leadershipAEC marketing strategyStrategic growth planningEmployee-owned firm modelCRM implementation in AECBusiness development analyticsConnect with Erika and Carrie, BARGE:https://bargedesign.comConnect with Katie: https://smartegies.com/ Rate, Review, & Follow on Apple Podcasts:We hope you're finding value in our AEC Marketing For Principals. Your feedback is important to us and we'd love to hear from you. Here's how you can help. Scroll to the bottom, rate our podcast with five stars, and select “Write a Review.” Let us know what you found most helpful from this episode! And if you haven't done so already, give the podcast a follow, and you'll be notified when new episodes come out.
Salesforce Solution Engineers are like general contractors, according to David Young, who leads a team of them at Salesforce. They need skills like carpentry and framing and plumbing but also know when to stop and call in an expert. In the Salesforce world this might be knowing when to bring in a service cloud or an Agentforce expert. They need to know enough to see the business challenge and know who to tap for help.I have always advocated that ISVs spend time thinking about SEs, even moreso than AEs, because the math just maths. AEs have shorter tenure at Salesforce than SEs. AEs have more ISVs reaching out to them than SEs. And AEs might have 1 or 5 accounts in the enterprise, but SEs often support multiple AEs which just multiplies the number of accounts that a single session with you could reach. We cover a bunch of topics, but here is a summary:What does an SE at Salesforce do?What type of person is an SE at Salesforce?How does David decide which ISVs to engage with?How do SEs learn about new ISVs?What are some dos and don'ts when ISVs are engaging with SEs? Shoutout to Myroad.io, who is doing a great job of it.What should an ISV know/do before they are “ready” to engage with Salesforce SEs?How do SEs work with SDOs and IDOs to demo Salesforce's tech?Thanks again to David for sharing with the community!And thank you to Sam Yarborough for the intro. If any of you have a Salesforce AE or RVP that might give us the real talk, it'd be great to get their pov. This episode is brought to you by ISVApp. ISVapp the usage analytics platform built specifically for Salesforce ISV and OEM applications.ISVapp is your central toolbox for reducing churn, increasing renewals, uncovering upsell opportunities, and closing more deals.
In this second part of our series on engineering organizations, Jeff and Luca explore how companies that build products should focus their efforts differently depending on their stage and scope. We start with startups and early-stage companies desperately searching for product-market fit, where the brutal truth is: quality doesn't matter yet. Your MVP should embarrass you—if it doesn't, you waited too long. We discuss the critical mental shift from throwaway prototypes to proper engineering once validation arrives, and why technical founders often fail by solving the wrong problem brilliantly. Moving up the ladder, we examine narrow-focus companies that have found their niche—like the German firm that does nothing but maintain a 100-year-old anchor chain machine, or specialists in medium-power electrical switches. These companies win through efficiency and deep expertise, but face existential risk if the market shifts. Finally, we tackle wide-focus companies introducing multiple product lines, where the challenge becomes running internal startups while managing established products, each requiring radically different approaches. The key insight: your focus must match your product's lifecycle stage, whether that's ruthless speed, cost optimization, or high-level process learning. Key Topics [02:30] Startups and early-stage companies: the existential search for product-market fit [06:45] The MVP philosophy: if you're not embarrassed, you waited too long [11:20] Quality vs. speed vs. scope: why quality doesn't matter in early stages [15:40] The Potemkin village approach: building facades to validate demand [19:15] Embedded products and MVPs: when physical products need creative shortcuts [23:50] The critical switch: from prototypes to proper engineering after validation [28:30] Narrow-focus companies: German hidden champions and deep specialization [34:10] Wide-focus companies: running internal startups within established organizations [40:25] Product teams and parallel focuses: managing different lifecycle stages simultaneously [45:00] Large established companies: high-level process learning and avoiding organizational weight Notable Quotes "If you read the Lean Startup, they will explicitly say: if you weren't embarrassed by your MVP, you waited too long. It really has to be painfully flimsy because you cannot afford to do it well." — Luca "Quality doesn't even factor because you're very explicitly building mock-ups from chewing gum and paper mache. They are fully intended to be thrown away." — Luca "Getting that product-market fit is existential. You will die if you do not get it and get it relatively quickly." — Jeff Resources Mentioned The Lean Startup - Eric Ries' book discussing MVP philosophy and the importance of being embarrassed by your first product The Mom Test - Rob Fitzpatrick's book about getting real customer feedback and validation through financial commitment The Art of Innovation - Tom Kelley's book on IDEO's design process, including the clothespin switch story Luca's Website - Trainings on embedded agile, AI in embedded systems, and more Jeff's Website - Consulting services for medical device software development You can find Jeff at https://jeffgable.com.You can find Luca at https://luca.engineer.Want to join the agile Embedded Slack? Click hereAre you looking for embedded-focused trainings? Head to https://agileembedded.academy/Ryan Torvik and Luca have started the Embedded AI podcast, check it out at https://embeddedaipodcast.com/
In this special International Women's Day episode of Skip the Queue, guest host Claire Furnival brings together four leaders from across the global visitor attractions industry to discuss progress, challenges and what comes next. Joining Claire are Emily Popovich of KMI International, Rachael Hamilton of Rise AV, Liz Sanchez Rasking of Looking Glass Strategies and Entertainment SHE-nanigans, and Ruth Read of blooloop. They share personal career journeys and discuss the ongoing barriers women face, including pay gaps, unconscious bias, burnout, safety at trade shows and confidence in leadership. The episode highlights practical initiatives driving change, such as mentoring programmes, representation in awards and panels, pay transparency advocacy and grassroots networking groups. The conversation reinforces the importance of community, allyship, visibility and self advocacy in accelerating equality across the sector, while recognising there is still work to do before women focused initiatives are no longer needed. Key Topics Discussed Career pathways in attractions, AV, media and themed entertainment Confidence gaps and self advocacy Burnout and workplace pressures Gender pay transparency Safety and inclusion at trade shows Mentoring and leadership development Representation on boards and industry awards The role of allyship Building safe and supportive networks Priorities for the next five years Show References: Claire Furnival, Client Success Manager of JP Showsystems & previously Head of Engineering of Merac http://www.jpshowsystems.com https://www.linkedin.com/in/claire-furnival-exec/ Emily Popovich, Director of Global Business Development of KMI International https://www.kmiintl.com/ https://www.linkedin.com/in/emilypopovich/ Rachael Hamilton, Managing Director of Rise AV https://www.rise-av.com/ https://www.iamrachael.co.uk/ https://www.linkedin.com/in/rachael-hamilton-836a5825/ Liz Sanchez Rasking, Founder | Director of Business Development, Looking Glass Strategies https://www.looking-glass.pro/ https://www.linkedin.com/in/lizsanchezrasking/ Ruth Read, Director of blooloop http://www.blooloop.com/ https://www.linkedin.com/in/ruthread/ There's an incredible line-up of events taking place for this year's #IWD that you can be a part of:
In this episode, Donna and Tom sit down with Kathy Fulton, Executive Director of the American Logistics Aid Network (ALAN), to explore how supply chain expertise saves lives during disasters. Kathy shares her journey from IT leadership at Saddle Creek Logistics Services to building ALAN's Supply Chain Intelligence Center, which predicts disaster impacts and coordinates relief efforts. She discusses the evolution from responding to three major events annually to managing constant mobilizations, her 2023 testimony before the U.S. Senate Budget Committee on climate change impacts, and strategies for building supply chain resilience. Listeners will gain insights on humanitarian logistics, disaster preparedness, and how private sector professionals can leverage their skills for meaningful impact beyond efficiency metrics. Takeaways: The transition from commercial logistics to humanitarian supply chain leadership Building predictive systems for disaster response coordination Supply chain resilience strategies for climate-related disruptions How logistics professionals can contribute expertise to disaster relief efforts Stay connected with CSCR on LinkedIn (Center for Supply Chain Research) and Instagram (@pennstatesupplychain), and be sure to follow us on Spotify, Apple Podcasts, or wherever you are tuning into Unpacked: Insights hosted by the Penn State Smeal Center for Supply Chain Research™. Thank you for joining us! Visit our website: https://www.smeal.psu.edu/cscr Guest Bio: Kathy Fulton is the Executive Director of American Logistics Aid Network (ALAN), focusing on the critical role industry expertise can play in disaster relief. She leads the organization in delivering logistics and supply chain assessment, coordination, and education to support responsible disaster relief. Kathy has served on national workgroups focused on efficient coordination of logistics activities during disasters, including those hosted by the National Academies of Science, Engineering, and Medicine, the Department of Homeland Security, the Transportation Research Board, National Voluntary Organizations Active in Disaster, and the National Emergency Management Association. In 2023, Kathy was invited to testify before the U.S. Senate Committee on the Budget on the impact of climate change on supply chains and in 2019 she was named a Supply Chain Rainmaker by DC Velocity Magazine. Prior to joining ALAN, Kathy served as senior manager of information technology services at Saddle Creek Logistics Services, where she led IT infrastructure implementation and support, corporate systems, and business continuity planning. She holds a bachelor's degree in mathematics from Northwestern State University of Louisiana and dual master's degrees in business administration and management information systems from the University of South Florida.
Join Dominique Surinx, CEO and President of Ansana, for a high-level discussion on the digital transformation of the healthcare industry. With 20 years of experience in the corporate pharmaceutical world and a decade as a successful entrepreneur, Dominique brings a rare perspective to the table. In this episode, we explore how AI is moving from a back-office tool to a frontline catalyst for innovation, improving patient outcomes and accelerating the development of life-saving treatments.
In this episode, Héctor Montilla-Peña, EIT, CMIT, field engineer at Allan Myers, and Jocivan Cabrera, graduate engineer at Walter P Moore, join the conversation to share how they found their path into civil engineering and became active in the American Concrete Institute (ACI). Both guests reflect on discovering the field through early academic experiences and getting involved with ACI through student chapters—Héctor in Ecuador and Jocivan at the University of Central Florida. They discuss stepping into leadership roles and how ACI opened doors to friendships, faculty relationships, research opportunities, and professional networks that helped shape their careers. The discussion also explores their first ACI convention experiences and their involvement in committee work focused on supporting students and young professionals. Héctor and Jocivan reflect on key decisions during college and the early stages of their careers, including graduate school choices, internships, and evolving interests across design, structures, and construction management. They close by encouraging students and emerging professionals to seek opportunities, step outside their comfort zones, and take advantage of programs like ACI's mentor program to make the most of conventions and build lasting professional connections. Check out the video podcast here: https://youtu.be/Bc40uDRwprY Engineering Greatness is produced by Association Briefings.
In this episode Ben Pearce and Nic Neate discuss what it's really like to build and be part of an AI native engineering team. Nic shares his experiences and insights on how AI is fundamentally changing the way software is developed, the skills required for engineers in this new landscape, and the challenges organizations face in adapting to these changes. Nic Neate is the CTO of @Nimbus. He has many years working in the software world and previously worked at Metaswitch and Microsoft. Show Links Ben Pearce LinkedIn - https://www.linkedin.com/in/benpthoughts/ Tech World Human Skills Home - https://www.techworldhumanskills.com Nic Neate Linked In - https://www.linkedin.com/in/nic-neate-b3515210/ Nimbus - https://www.nimbusmaps.co.uk/ Takeaways AI is fundamentally changing software engineering. Vibe coding is using AI to write code. AI native means riding the wave of AI tooling. Being AI native enables you to do so much more. AI can do it in 10 minutes what you could do in a week. Context engineering is a key skill for engineers. Decision making is crucial in an AI native world. You need to invest in your tool chain. Recruitment processes need to change for AI roles. Maximize value for people working in AI. Keywords AI native engineering, software development, generative AI, engineering teams, AI tools, context engineering, software productivity, AI integration, engineering leadership, tech transformation
On February 28, the United States and Israel launched a campaign against Iran targeting military infrastructure and the regime's core leadership. Supreme Leader Ayatollah Ali Khamenei and several senior officials died in the attacks, which triggered a leadership crisis and inflamed tensions throughout the Middle East. In the immediate aftermath, Iran launched extensive barrages of drones and ballistic missiles aimed at Israel, US military bases, and other targets in neighboring Gulf states. Energy prices rose sharply. This regional shift carries immediate and enduring consequences for global geopolitics and the stability of international energy flows. The outcome of the conflict—and the ultimate fate of the Iranian regime—remains deeply uncertain. Even with these open questions, the trajectory of this escalation will likely redefine the future of Middle Eastern security, global power dynamics, and the world's energy markets. How is the conflict evolving, and how might it end? What are the impacts on Gulf states and what are some of the possible paths forward? And how is this all impacting oil and gas markets across the globe? Today on the show, Jason Bordoff speaks with four experts from the Center on Global Energy Policy—Anne-Sophie Corbeau, Richard Nephew, Daniel Sternoff, and Karen Young—to discuss the escalating conflict and its impact on energy and geopolitics. Anne-Sophie is a global research scholar at CGEP, where she focuses on hydrogen and natural gas. She previously worked as a senior analyst at BP and the International Energy Agency. Richard is a senior research scholar at CGEP and formerly served as the US deputy special envoy for Iran under the Biden administration, where he played a key role in negotiations over the Iran nuclear deal. Daniel is a senior fellow at CGEP and heads its corporate partnership strategy. Karen is a senior research scholar at CGEP with expertise in the Middle East focusing on geopolitics, the political economy of Gulf states, and energy policy. The Center on Global Energy Policy at Columbia University SIPA is closely following the escalating conflict in Iran and its implications for US national security, Middle East geopolitics, and global energy markets. See all of our coverage here. Credits: Hosted by Jason Bordoff and Bill Loveless. Produced by Mary Catherine O'Connor, Caroline Pitman, and Kyu Lee. Engineering by Gregory Vilfranc.
So, there are dire wolves living on Earth again. They were “de-extincted” by Colossal Biosciences. And today on the show their Chief Science Officer joins me to share her view on why the de-extinction matters — not as a science project, but because it will help solve problems that threaten every species on earth, including us. Beth Shapiro is the Chief Science Officer at Colossal Biosciences, and she helped to bring back the dire wolf or, as others call it, a gray wolf with 20 genetic edits. There is a fierce debate about what de-extinction even means, and we discuss that, but whatever you call them, there are now three big wolves living in an undisclosed location and they wouldn't be there if not for the DNA that Beth and her team edited. Colossal is also working to bring back the wooly mammoth, the Tasmanian tiger, the dodo and other animals that have long been extinct. Why? Listen to find out… Chapters:(01:19) - The Most Oprah Question Beth's Ever Been Asked (03:04) - Moonshots Require You to Create a Giant List of Problems (04:19) - The Things We'll Solve Along the Way, a la the Original Moonshot… to the Moon (05:57) - Beth's Journey: From Broadcast Journalism to Ancient DNA (09:13) - How a Sediment Core Solved a Mammoth Mystery (11:36) - Why Charismatic Animals Matter (a.k.a. Why Riz Is Everything) (12:38) - What's Up With Romulus, Remus, and Khaleesi? (14:19) - But Are They Really “Dire Wolves”? The Controversy Over 20 Genetic Edits (21:45) - Should We Do This? Beth's Ethics Framework for Builders (23:51) - Advice for Moonshot Builders (25:10) - Why We Want Dodos, Mammoths, and Thylacines Back Links & Resources:Colossal BiosciencesBeth ShapiroPopTech -- a conference I love! Support Future Around & Find OutFollow Dan on LinkedInGet the free Future Around & Find Out newsletterBecome a paid subscriber and help future proof the podcast!Sponsor the show? Are you looking to reach an audience of senior technologists and decision-makers? Email me: dan@modernproductminds.com---Music by Jonathan Zalben
Allen, Rosemary, Yolanda, and Matthew discuss highlights from Blades USA including the carbon blade debate. Plus TPI Composites’ bankruptcy sale hits major obstacles as partners dispute over $100M in claims. And Europe’s offshore and onshore wind developers clash over state aid, with WindEurope’s new CEO urging unity. Sign up now for Uptime Tech News, our weekly newsletter on all things wind technology. This episode is sponsored by Weather Guard Lightning Tech. Learn more about Weather Guard’s StrikeTape Wind Turbine LPS retrofit. Follow the show on YouTube, Linkedin and visit Weather Guard on the web. And subscribe to Rosemary’s “Engineering with Rosie” YouTube channel here. Have a question we can answer on the show? Email us! [00:00:00] The Uptime Wind Energy Podcast brought to you by Strike Tape, protecting thousands of wind turbines from lightning damage worldwide. Visit strike tape.com. And now your hosts. Allen Hall 2025: Welcome to the Uptime Wind Energy Podcast. I’m your host Alan Hall, and I’m here with Yolanda Padron, Rosemary Barnes and Matthew Stead. Yolanda and Matthew have just wrapped up a couple of days at the Blade USA forum in Austin, Texas. Maybe we should start there. Thoughts on the forum this year? Things that were highlights? Matthew Stead: Yeah. Lightning Root de bond. One positive was that, um, there are a couple of startups there, so, you know, kudos to them for, you know, making the investment. There was a. There was a startup around, you know, data analytics and, you know, bringing machine learning in. And then there was also another startup looking at recycling. [00:01:00] Um, really trying to get that, that food chain through of, um, you know, grinding and then turning into some sort of valuable product. Um, yeah. However, I think someone also from EPRI said that, you know, at the moment, you know, the recycling path is, you know, eight times more expensive than the, um, the landfill path. There was a lot of carbon discussion actually. So, and, um, yeah, a lot of discussion about repairs, a lot of discussion about testing, uh, a lot of discussion about, you know, how maybe a carbon blade can last 40 years. Um, so a lot of discussion about lifetime extensions around carbon. Um, but, but, but, but, you know, really, really hard to repair. Allen Hall 2025: That goes back to the comments Rosemary and Morton Hanberg made about carbon blades. Should we be making. Carbon blades are not. And I think Morton’s opinion, and maybe Rosemary’s, I don’t wanna speak for her, was carbon blades are okay, but they are really difficult to repair. Almost impossible to repair. And is it [00:02:00] worth even building them? Rosemary Barnes: I think if you consider the blade in isolation, then it probably is adding more headaches than it’s worth. But carbon fiber is a bit of an enabler for improvements across the whole system of a, a wind turbine. ’cause when you take, like you can take a lot of weight out of a blade by using carbon fiber. I mean, it’s never been cheaper to make a blade with carbon fiber than an equivalent blade with glass. You do, you buy the more expensive carbon fiber blade because it’s lighter, a like, a lot lighter, and then you can take, um, weight. It, it reduces the requirements for basically every other component in the wind turbine, but especially stuff like the pitch bearings. Um, so you solve a lot of other problems, but you create blade problems. So. I think if you ask some of the only works on maintaining blades, then you’re gonna be like, why would you make a carbon fiber blade? It is so much headache. Um, but that’s not the reason why they were ever made in the first place. [00:03:00] So you’d need to talk to, you know, somebody on, uh, I dunno, front end engineering. Someone from the sales team about why it is that they are going with a more expensive carbon fiber blade. Even acknowledging that they probably underestimate how many problems there are with o and m with, uh, carbon fiber blades. But even so, like they’re already aware that there are trade offs. Um, and yeah, there’s non blade reasons for, for taking, taking that pain. Allen Hall 2025: Are there other fibers that could be substituted besides carbon? There, I, I know fiberglass. A, a good, relatively strong fiber and carbon obviously is much stronger. But are there things in the middle that could be substituted that are non-conductive? Rosemary Barnes: Uh, y yeah, there are, but carbon fibers, it’s not just strong. It’s really stiff. And that’s what its benefit is. Um, like there’s Kevlar but it’s not very stiff. So you would, we would make a really heavy blade if you used Kevlar. It would be probably bulletproof though. So I guess that would be a plus. I, I haven’t looked into it recently, but nothing is [00:04:00] at the, um, like got the performance specs and the cost specs that you would need to, um, make it replace carbon fiber. Matthew Stead: So one thing that I picked up I thought was pretty, uh, interesting was that by having a stronger, you know, carbon protrusion, you know, the, you know, the backbone of the blade, um, it took a little bit of pressure off the skin. And so therefore, um, you know, the life, life of the blade, um, and the ability to keep running it ’cause the skin is not so critical. Those seem to be a real, a real plus as well. Rosemary Barnes: I don’t know, people talk about this in like absolutes, but everything is just a con continuum, right? Like you can make an all glass blade that would last a thousand years if you really wanted to. You just, you know, you just have to make it very, very strong. ’cause it’s, you know, it’s all based on fatigue lifetime. And the smaller that your, um, strain on every component in the blade is, then the less, um, the less fatigue damage is gonna accumulate. Making it a little bit stiffer will actually increase the lifetime by [00:05:00] a a lot. I think the main benefit to protrusions is just that you avoid all of the um, or you avoid a lot of the possibilities for manufacturing defects. It’s easy to control the manufacture ’cause carbon fiber, like much more so than glass fiber. It’s so, um, it’s so dependent on the fibers being perfectly straight. If you have a little wrinkle, like a little wrinkle is bad in glass fiber, but it’s like really bad in carbon fiber. So protrusions mean that you won’t get wrinkles. Uh, and you can, you know, control the manufacturing process a lot better, but they are barely repairable, right? So that’s the trade off. You can do some small repairs, but you’re not gonna be just. Um, if you’ve got a, a, a full thickness crack or something, it’s, you know, it’s gonna be game over. You’re not gonna be building that up again. Allen Hall 2025: Delamination and bottomline failures and blades are difficult problems to [00:06:00] detect early. These hidden issues can cost you millions in repairs and lost energy production. C-I-C-N-D-T are specialists to detect these critical flaws before they become expensive burdens. Their non-destructive test technology penetrates deep to blade materials to find voids and cracks. Traditional inspections, completely. Miss C-I-C-N-D-T Maps. Every critical defect delivers actionable reports and provides support to get your blades. Back in service, so visit cic ndt.com because catching blade problems early Yolanda Padron: will save you millions. Allen Hall 2025: Well keep going on the, the subject of blades. Imagine if you were selling your house and you told the bank you owe nothing on it. Then the bank shows up with a bill for over a hundred million dollars. That is essentially what’s happening right now in the TPI composites bankruptcy. Uh, the wind blade manufacturer canceled its [00:07:00] February 17th asset auction after only one bidder came forward. A firm called ECP five LLC, which is, uh, part of Energy Capital Partners, which is based in New Jersey. Uh, but before TPI. Can hand over the keys. It has to settle up with its business partners. TPI told the court many of those partners were owed little or nothing. Uh, the partners check their books. Strongly disagree. Now, the judge has a mountain of competing claims to sort through before the sale can close. And everyone, I mean, the, the claims are big. Uh, there are several large names listed, and if you go through the filings, uh, Siemens C Mesa is probably the largest one, and it, it claims TPI owes about 84 million plus an unpaid inspection, repair, and replacement costs. Plus under 22 million [00:08:00]under apparent guarantee. Others include Aurora Energy Services stating it is owned about $5 million, uh, for post-bankruptcy services, plus 38,000, uh, for before the filing of bankruptcy. The landlord up in Iowa for the TPI facility there is objecting because they’re owed some rent. Some other ones include, uh. Oracle, uh, which is, uh, has a lot of software licenses that TPI currently has, and they’re saying those licenses will not swap over to the new owner. So there, this is a series of these filings going on at the minute, and they’re pushing back the closing of the, uh, sale hearing until March 9th. So they got about another two weeks as we record right now. This is a big deal and, and although I have seen almost nothing about it in the press. Because it’s hard. One, it’s hard to find, and two, it’s really [00:09:00] difficult to sort through. Uh, but it is a major milestone for TPI that they’re gonna be able to sell the, or at least transfer ownership to, uh, energy capital partners. And the none of the buyers investors had bought part of the facilities. But GE Renova or Siemens cesa, for that matter, are not involved, at least at the top level. Which is really to, in my opinion, odd. I thought GE Renova would’ve been involved, at least at some level. They have been supporting TPI through this process. But in terms of going forward, doesn’t look like too much is going on with Renova or Siemens Ga Mesa in, in terms of the operations of these facilities. Thoughts. Rosemary Barnes: Yeah, I agree. It’s strange that they wouldn’t have taken that opportunity and that makes me wonder what I don’t know that, you know, ’cause obviously it’s not a strange decision to the people who have made it so. They’ve got more information, a lot more information than us. So what is it that made it unappealing to them? That’s, um, that’s my question. [00:10:00] Yolanda Padron: What did TP, I think was gonna happen with all of that money that they owe everyone? Allen Hall 2025: Well, it’s a bankruptcy hearing. Obviously they like to wipe that debt free and so would Energy Capital partners. They don’t wanna pay the a hundred million plus of whatever, uh, the court would ict, but. You just like to get the assets. If you can do it, that’s your cheapest option if you’re Energy Capital partners. But do you see Energy Capital Partners running the facilities? There’s a lot of organization within TPI that manages those facilities and controls the operation. From the quality side engineering side, there’s, there’s a lot of pieces to TPI here. Do you think they’re just gonna pick it up and run, run the company as it stands today? Or, or, Rosemary Barnes: oh my goodness. I would be so nervous to, um, buy blades, uh, from them in that situation. I mean, we’ve seen so many examples in the last few years of decisions being made by senior management that have really compromised the quality at the end of the day. Like in theory, yes, the factory, you know, all the processes are in place to do things. Um, to do things [00:11:00] right, but you know, as soon as they get the next new project, which they’re doing constantly, right? It’s not like they just make a blade and they just make it over and over again. They make many different kinds of blades. There’s decisions to be made and you’re trying to get the price right and the quality right. And then, you know, given that we know that TPI was not profitable the way they were doing it before, they’re gonna have to spend less money. Then somebody who isn’t from the industry is making those calls about where to save it. It just seems like totally implausible to me. Matthew Stead: Can I just add though, you know, TPI was mentioned multiple times at, um, at Blades, USA, and so, you know, a lot of people are relying on them or have relied on them and so forth. And so maybe this is a strategy about supporting the industry into the future. Like I think Alan, you, you said that they’re involved in, um, this investment business has other wind assets, so maybe it’s just like. Securing supply chain and, which I mean, that’s a pretty logical approach, isn’t it? Allen Hall 2025: Oh, it would be. Uh, they’re about 50% owners of Ted’s US onshore fleet and a number. There are [00:12:00] other projects they’re involved in a number of renewable projects. Uh, so it would make sense for them to try to keep the supply chain going. But the largest purchaser of GB GE turbines that I know of is NextEra. So you would think NextEra would want to step into the mix too and at least in all the court filings, I haven’t seen much from NextEra or nothing from them at all. It if Osted US is wanting to keep their supply chain and Energy Capital partners wanted to keep the supply chain going, that would make a lot of sense to me. However, I just don’t know if they have the infrastructure to manage it. As Rosemary has described on numerous occasions running LM wind power is not easy. There’s just a lot of moving pieces, supply chain problems. You’ve got people problems, you have quality problems, you have repair problems, warranty issues. It’s a lot to that business. It isn’t like you’re stamping out widgets. You, you have a responsibility to that product after it goes out into [00:13:00] service. So if you have problems out in service, you’re, you’re kind of on the hook for all those warranty claims. It’s complicated. Rosemary Barnes: You make it sound like I was running lm Yolanda Padron: Rosie runs the world. Rosemary Barnes: I just wanna make it clear I was not running lm Allen Hall 2025: Not yet. Rosie. There’s still time. Rosemary Barnes: I was ru running one very tiny, tiny corner of it. Yolanda Padron: I’d almost be curious ’cause like since ECP is so much into risk management and just, just in general, they have so many things that they are like part owners in, but they don’t necessarily manage the day to day hands on. Uh. I’d almost be curious to see if maybe they take a page out of Rosie’s book and try to make one thing. Well, Matthew Stead: mm, that’d be novel, wouldn’t it? Rosemary Barnes: It has actually been tried before. Um, you know, it’s, it’s uh, not something that has escaped the notice of blade engineers, uh, that if you make one thing, you can do it right. And wind turbine blades are a pretty similar there. No, you know, like great [00:14:00] differentiator between. How well performing the blades are from one company to another. I know at, at least at lm, they did have a blade that they designed, and their plan was to sell just heaps and heaps of those to multiple different manufacturers and just no one wanted it. Um, so it just quietly died. Um, so yeah, the, the concept is good. I think it’s. A little bit harder to pull off than you would hope. There are also some Chinese companies that are kind of selling just parts, generic parts. And so if you wanted to make your own wind turbine, um, company, if you wanted to be a wind energy o and m Yolanda, you could just buy an assortment of parts from Chinese manufacturers and put a. Yolanda Wind energy sticker on it and um, and, and, and you could be an an OEM. So it is, it, it, it is possible. I haven’t seen any of these out in the wild. Um, I have [00:15:00] heard of, you know, people considering it for, you know, certain aspects of certain types of projects. So it kind of exists in a way. Matthew Stead: But the financial aspect, I mean, that’s accounting 1 0 1, I mean. You gotta know your assets and to owe people a hundred million dollars, that’s absolutely shocking. Really? Allen Hall 2025: They owed a lot more than that before the bankruptcy. It is a lot of money. Matthew Stead: How do you miss that? Allen Hall 2025: Well, I don’t think they missed it. I just think the warranty claims and some of the repair that was going on and the, the, it sounded like price discounting was happening to some of the OEMs just caught up to ’em. But at the end of the day, I, I, I guess the question is. Does TPI as an entity remain? Obviously the Vestas portion will, because Vestas is gonna make them Vestas factories in a sense, and, uh, integrate as part of their overall operations. But Renova is not, Siemens is not interested in doing it, at least as we speak. No one’s [00:16:00] making any noise over at Nordex. It, it does leave these assets questionable as to what the real value is. We haven’t heard how much, uh, ECP has paid for them yet. The Vestas factories that were purchased, I think the, the two TPI factories in Mexico, I think Vestas paid about $10 million for each factory, which is a really inexpensive price to pay for new factories because Vestus had talked about at one point a year or two ago, about standing up a new factory saying it would cost him roughly a half a billion dollars to do. So buying a, that same asset for $10 million is a discount, a deep, deep discount, which maybe Vestas figures, Hey, it’s 20 million bucks, plus they got the India operations. Uh, it’s not that much money. If it all goes sour, it’s not that much money and we’re okay. Whereas Ver Nova decided to not to participate in that. As wind energy professionals, staying informed is crucial, and let’s face it difficult. That’s why [00:17:00] the Uptime podcast recommends PES Wind Magazine. PES Wind offers a diverse range of in-depth articles and expert insights that dive into the most pressing issues facing our energy future. Whether you’re an industry veteran or new to wind, PES Wind has the high quality content you need. Don’t miss out. Visit p ps wind.com. Today, over in Denmark, a fight has been brewing between offshore and onshore wind developers and. Sted once State Aid brought back for offshore wind auctions, onshore developers say that would tilt the playing field against them. Well, some have even walked out on their own trade group, uh, over it. Now the new CEO of Wind Europe, Tina Van Stratton, uh, is stepping in the middle of that discussion with a simple message. We need both. Don’t let offshore and onshore wind divide us. Nearly 90% of Europe’s installed wind capacity sits currently on land, and [00:18:00] she says that is not going to change anytime soon. Uh, so there, there is a big dispute about this right there. There does seem to be a, a amount of money being poured into offshore wind and requests of governments to support offshore wind at the same time. Onshore wind, which has been the primary growth market for wind in Europe, is getting the cold shoulder. In a sense. How does this play out everyone? Is there a, a good solution to it or is the need for offshore wind so great that, that they have to ignore onshore wind development for a couple of years? Matthew Stead: I think we should just all be friends. So, I mean, really. Yeah, we need both and, um, I mean for the diversity and, you know, uh, I’ll leave all the technical topics to Rosie, but, um, um, really I think we need both. I mean, so what, it’d be crazy to, to drop the onshore, onshore industry. Yolanda Padron: Yeah. I mean, it makes sense that, or said, especially Orid Europe doesn’t have any onshore anymore. Right. So it’s just [00:19:00]offshore. It would make sense that they really wanna push for help for themselves. And it’s, it’s great. It, it’s, it’s great to help, but I, I agree with Matt. Allen Hall 2025: Well, the Northern Europe and Scandinavian countries are talking about 100 gigawatts in the water by what, 2050? Something of that sort. So that’s a lot of energy in the water. In order to do that, you have to devote a number of resources to it, which. Will mean onshore wind is not gonna get the support it probably deserves, even though it has a proven track record. Rosemary Barnes: I just think it, it’s really interesting because I guess wind is, um, a very Europe. LED industry. Um, and so yeah, in Europe, e everything big and exciting is in offshore and the volume is in offshore. Um, I feel like that’s kind of filtered through to other regions though, because I mean, in Australia we don’t even have any offshore wind yet. We are probably getting some, but you go to any wind energy event, it’s gonna be. [00:20:00] More than 50% offshore wind and sometimes like 90% offshore wind, um, focused, which is, I think crazy when onshore is, is exists and has plenty of problems that need to be solved, and we need to be building more, a lot faster. I, I do actually wish that. If we could spend as much of the, you know, like some of the effort and the political effort that’s going into paving the way for offshore wind, I think would be much better spent on solving the problems. Um, the obstacles stopping us from rolling out onshore wind faster. Because we’re not on track in Australia to meet our renewable energy targets if we can’t get that under control. And then in the US yes you have some offshore wind, but it is not a growth industry at the moment or it’s not very appealing at the moment, at least. Right. So, and I dunno how much you talk about it there, but I do hear a lot of, like a whole lot of talk about offshore compared to how important it is for regions outside of Europe. Yolanda Padron: I think it’s important too to [00:21:00] note that. When you have a lot of offshore wind in your fleet, like you can sometimes test out products onshore that maybe they’re, of course not the exact same conditions, but you can test out products to a degree onshore. And I’ve seen, you know, owner operators that have to go across continents just to test that product because it’s cheaper to do that onshore than to do it offshore in your home site, in your backyard. So I mean that that would really benefit from an RD standpoint. It would really benefit everyone. If Allen Hall 2025: they gave it up attention Yolanda Padron: to onshore. Rosemary Barnes: When I was at lm, one of my, well my key team member who was an electrical engineer, he had, um, done a bunch of work for a system that was only implemented on an offshore wind farm. And it sucked up so much time when stuff started going wrong with that, like even small things. And he was the only one [00:22:00] that could do it. You know, you go out, if you’ve got a five minute job to do, to get, you know, like turn something off and on again off. Reconnect something that’s a whole day of work, right? Like you, and, and not like a normal day, but like a 12 hour day, you’re gonna go out in the morning, they, you know, they go around in a boat or whatever and drop people off and they don’t come get you when you’re done 10 minutes later, you know, they come get you at the end of the day when they’re picking everyone up again. So, um, it, it was, it was incredibly challenging. I mean, for him personally and the team. Um, and I always recommend to, or, you know, sometimes I’m advising, um, companies that have offshore wind, um, technologies. And I’m always advising anything that you can test on shore, do it and get creative about it as well. ’cause you might think that you can’t, you certainly can’t get all the way there without testing in your real operating environment. But any problem that could happen onshore that you, um, learn about when it’s onshore is gonna cost you probably like, you know, one 10th as much [00:23:00] to fix. Um. So, and, and the time as well. So, yeah, I, I think that you’re right that we should be actually considering onshore as an opportunity for, um, improving offshore technology as well. Allen Hall 2025: Can we talk about, uh, data centers for a minute? Just off the top of mind, I’ve been listening to a number of podcasts over the last month or two talking about powering AI data centers and how much coal or natural gas. It’s gonna be needed to provide the stable, reliable power that these data centers supposedly need. In the meantime, there’s like this industry being built, uh, and you see the, the purchases of gas turbines going out to like, what, 2032? I think it’s what Renova is talking about now is when you could actually get in line for a gas turbine. Other manufacturers or gas turbines are basically saying the same thing in the meantime. [00:24:00] Elon Musk and SpaceX are talking about putting AI data centers up in space where you don’t have any regulatory issues. You don’t have to burn coal or natural gas or any of these things. So the, the ground-based AI data centers appear to be locked into making these really expensive buildings and assets and putting generation and transmission and, and this infrastructure together, which will cost them. Hundreds of millions at a minimum, likely tens of billions of dollars to do, and that’s just in the United States. Meanwhile, SpaceX is really on a pathway of doing this up in the sky for probably a fraction of the cost. Is there a break point here? Because it does seem like the, the natural gas, coal, oil, petroleum industry and the on ground build, the building, people are ignoring that. SpaceX has a [00:25:00] capability of doing this, and if Musk decides to do it, and SpaceX decides to do it, that all those gas turbine orders, all that infrastructure, all the gas pipeline, all the drilling that would have to happen would just go immediately. Poof. Gone. Rosemary Barnes: I don’t know about immediately because I mean, we’re not at the point yet where you can just launch a data center into space. So there is a bit of a, a, a transition period. Um, I. I also think that it’s overblown that, you know, I think you might have even fallen into the trap also, where you’re like, oh, when data centers need more energy, so therefore it has to be coal or gas or nuclear. Allen Hall 2025: Nope, I agree with you. Rosemary Barnes: Those things aren’t quick to build either. If you truly wanted to do it quickly, you’d be putting in, um, you know, heaps of solar panels and batteries and, and you know, wind turbines where that made sense. But that said, I, I do agree that, uh, like I, I don’t think space-based data centers is farfetched at all. I, I guess the biggest [00:26:00] challenges, uh, are, um, the cooling and heating requirements space has very large temperature fluctuations. So I guess you’re gonna need to design that carefully. I don’t think it’s insurmountable. Um, and then the next thing is a cost of launch, which I’m sure you’re about to tell me how. Dramatically the cost of launch is dropping. Um, you know, like, it, it’s got, it’s got a very good learning curve. The space launches, which is basically, you know, SpaceX is probably the main reason why that is just dropping and dropping and dropping. So I don’t think that it’s unrealistic at all. I don’t know the timeframe. You would know more, Alan, you work in, um, aerospace. I just. You know, um, follow it for general interest. Matthew Stead: I reckon it’s stupid. He’s really stupid on a number of grounds. So first of all, you know, why do that when. You just, I can’t see how it can ever be more cost effective and you know, [00:27:00] I, you know, you should really, should be putting that effort into things like, you know, better healthcare and so forth. I mean, what a waste of resources. But why? I mean, why, why? Allen Hall 2025: Because it’s a lot less expensive and it’s faster. Matthew Stead: You’d do it in the ocean before that, wouldn’t you? Rosemary Barnes: No, but the ocean still has, like how do you power it? You, you get the 24 7 solar power in space. That’s what you. That’s what you get, um, which you can’t get on Earth Matthew Stead: or you put it next to a wind farm and you, you, and you make the load go up and down depending on the wind. I mean, seriously, there’s so many other ways of doing it. You put it next to a wind and solar. Rosemary Barnes: I agree with you, Matt, that I think that the, the bulk of the solutions with data centers is gonna come from one demand not being what people think it is today. Like the numbers that get reported are just like the. Absolute best, best, best case scenario and then multiplied by three or four times because they’re looking at different options for locating each of the data centers they plan to make. So I think I wouldn’t be surprised if we end up with 10% of what people think that we’re gonna get. [00:28:00] Now, the first thing, secondly, people assume that it needs to be 24 7. Just, you know, like a hundred percent reliable power, and that’s. That’s simply, yeah, it’s not, not everything needs to be just, um, you know, done at, at the exact time that it’s requested. There’s heaps of things that can be shifted and uh, when the price differential is there, then people are naturally going to choose that. And in fact, there are already some companies offering different levels of reliability depend, you know, for different prices. And companies can choose which of their processes can be put on hold. Like a lot of the training stuff, you’re happy don’t. Need 99.999% reliability, you’re probably happy with 90% reliability. And so, you know, if it costs a whole lot less than you will, I, I agree with you, Matt, that that’s gonna take most of it. But I do still think that for the, like, super reliable, um, data centers, I, I bet that we see at least one. And even if it’s just because Elon Musk is the type to push something through, um, you know, [00:29:00] first and. Wait for the market to catch up later. Uh, maybe that will be the reason, but I, I honestly think it’s more than 50% likely that we see a data center in space in the next, in the next decade, Matthew Stead: it would make more sense to like drill a hole to the center of the earth and get the, the hot well cutting rock Rosemary Barnes: and or there’s also plenty of geothermal. You did thermal projects as well. Matthew Stead: Yeah, it’s just ridiculous. Rosemary Barnes: I think that we’ve had our first hot take from Matthew, so I don’t know some sort of sound effect to be added here. Claire. Uh, yeah, Allen Hall 2025: that wraps up another episode of the Uptime Wind Energy Podcast. If today’s discussion sparked any questions or ideas, we’d love to hear from you. Just reach out to us on LinkedIn and don’t forget to subscribe so you never miss an episode. And if you found value in today’s conversation, please give us a review. It really helps other wind energy professionals discover the show. For Rosa, Yolanda and [00:30:00] Matthew, I’m Alan Hall, and we’ll see you next week on the Uptime Wind Energy Podcast.
Consumers aren't lacking for choice. Instead, they're usually drowning in a sea of options, and it's up to brands to find ways to go beyond simply removing friction and bring back the joy in shopping. Adding AI, and agentic AI into the mix can unlock new opportunities, but also brings with it new challenges. We're going to talk a little about all of it.We are recording here at eTail Palm Springs, and hearing from leading brands and the platforms and companies they rely on to innovate in retail. To help me discuss these topics, I'd like to welcome back to the show Noah Zamansky, VP Product, Tech, & Design, Client Experience at Stitch Fix About Noah Zamansky Noah Zamansky serves as the Vice President of Product and Client Experience at Stitch Fix, where he leads cross-functional teams spanning Product, Design, Engineering, Algorithms, and Platform Development. A seasoned leader, Noah has a proven track record of shaping product vision and strategy, designing exceptional user experiences, and spearheading the launch of new business ventures. Before joining Stitch Fix, Noah held the role of Senior Director of Product Management at eBay, overseeing Fashion and Vertical Experiences. Noah Zamansky on LinkedIn: https://www.linkedin.com/in/nzamansky/ Resources Stitch Fix: https://www.stitchfix.com The Agile Brand podcast is brought to you by TEKsystems. Learn more here: https://aglbrnd.co/r/2868abd8085a9703 Drive your customers to new horizons at the premier retail event of the year for Retail and Brand marketers. Learn more at CRMC 2026, June 1-3. https://aglbrnd.co/r/d15ec37a537c0d74 Enjoyed the show? Tell us more at and give us a rating so others can find the show at: https://aglbrnd.co/r/faaed112fc9887f3 Connect with Greg on LinkedIn: https://www.linkedin.com/in/gregkihlstromDon't miss a thing: get the latest episodes, sign up for our newsletter and more: https://aglbrnd.co/r/35ded3ccfb6716ba Check out The Agile Brand Guide website with articles, insights, and Martechipedia, the wiki for marketing technology: https://www.agilebrandguide.com The Agile Brand is produced by Missing Link—a Latina-owned strategy-driven, creatively fueled production co-op. From ideation to creation, they craft human connections through intelligent, engaging and informative content. https://www.missinglink.company
Gaius recounts meeting Prime Minister Mossadegh as a child, framing the current crisis within a century of failed American "engineering" in Persian affairs. They reflect on the unsustainable, "European-import" nature of the Shah's regime and conclude that foreign intervention historically backfires, leading to revolutionary outcomes inimical to American interests.1979 TEHRAN
email chris@drchrisloomdphd.com with "Podcast freebie" to book a coveted FREE guest spot on the show. To book a PREMIUM spot on the Podcast: https://www.drchrisloomdphd.com/_paylink/AZpgR_7fBook a 1-on-1 coaching call: https://www.drchrisloomdphd.com/booking-calendar/introductory-session Subscribe to our email list: https://financial-freedom-podcast-with-dr-loo.kit.com/
In this episode, Jack Cochran and Matthew James sit down with Micah Joel, GTM leader and demo engineering pioneer, to explore what it means to build a dedicated demo engineering function from scratch. Micah shares his journey from theater kid to SE to leading Salesforce's legendary Q Branch, and unpacks why demo engineering might be the most underutilized lever in presales today. They cover the difference between deal-focused and infrastructure-focused demo engineers, how to structure the team, why blended teams fail, and how a mature demo engineering org can swim upstream into product strategy to reduce time-to-revenue. This is part one of two. Part two will focus on measuring and proving the value of a demo engineering team. Follow Us Connect with Jack Cochran: https://www.linkedin.com/in/jackcochran/ Connect with Matthew James: https://www.linkedin.com/in/matthewyoungjames/ Connect with Micah Joel: https://www.linkedin.com/in/micahjoel/ Links and Resources Mentioned Join Presales Collective Slack: https://www.presalescollective.com/slack SoulCon 2026 (Chicago, August 2026): https://www.presalescollective.com/solcon-2026 Presales Collective Podcast: https://www.presalescollective.com/podcast Key Topics Covered Micah's Background: From Theater to SE to Demo Engineering What Is Demo Engineering and How Is It Different from Being an SE? When Does an Organization Need a Demo Engineering Team? The Two Sides of Demo Engineering: Deal Support vs. Infrastructure/Scale How to Hire and Structure the Team Demo Engineering as a Talent Pipeline and Retention Strategy Swimming Upstream: Demo Engineering's Role in Go-to-Market Strategy Common Mistakes and How to Avoid Them Timestamps 00:00 Welcome 02:48 Intro Micah Joel 05:42 Demo engineering definition 08:33 When do you need a DE team? 11:13 Deal side vs. infrastructure/scale side 15:48 Demo engineering as SE retention 23:55 Swimming upstream 27:11 Final advice
In celebration of Women in Construction Week, this episode explores how the construction industry is evolving, technically, culturally, and professionally. Concrete is often misunderstood as simple. In reality, it is chemistry, data, performance modeling, and long-term durability engineering. This conversation pulls back the curtain on the science behind the material that quite literally shapes our world and highlights the next generation of technical leadership helping move the industry forward. You'll Learn Why concrete is far more scientific and complex than most people realize How R&D teams test and scale new materials responsibly The real tension between innovation and field adoption What early-career leadership growth looks like in a technical role How visibility and credibility shape long-term career opportunity Why modern construction requires broader skill sets than ever before Meet Our Guest Lauren Kinslow is a Quality Engineer at Titan America, where she evaluates and tests new materials to assess performance and ensure quality standards. She holds a degree in Chemical Engineering from the Virginia Tech College of Engineering and is committed to continuous learning and professional development. Lauren maintains multiple industry certifications, including: ACI Concrete Strength and Aggregate Testing Technician NRMCA Certified Concrete Technologist Levels 1 and 2 She is currently a member of the Virginia Ready Mixed Concrete Association's Concrete Leadership Program and is set to graduate in May 2026. Todd Takes Culture Shifts Through Reinforcement Lasting change happens through consistency, competence, and trust built over time. Innovation Is About Adoption New ideas only matter when they are proven, trusted, and implemented in the field. The Mold Has Broadened Today's construction industry demands analytical thinkers, scientists, data-driven leaders, and problem solvers alongside traditional field expertise. More Resources Thanks for listening! Please be sure to leave a rating and/or review and follow up our social accounts. Bridging the Gap Website Bridging the Gap LinkedIn Bridging the Gap Instagram Bridging the Gap YouTube Todd's LinkedIn Lauren's LinkedIn Titan America's Website Thank you to our sponsors! Graitec North America Graitec North America LinkedIn Autodesk's Website
This week's guest is Doug C. Brown, CEO of CEO Sales Strategies and a leading authority on building predictable, measurable, and scalable sales growth. After a career as a top salesperson, including serving as president of sales and training for peak performance coach Tony Robbins, Doug is now advising CEOs on how to rethink their approach to sales. Among the companies Doug and his team have advised are Procter & Gamble, Enterprise Rent-A-Car, and Embassy Suites. Doug challenges the belief that charisma, closing tricks, or motivational hype drive sales success. Conversational selling, he explains, builds trust faster than persuasion-based tactics. Doug has spent three decades finding hidden profits for founder-led companies. Most companies can quickly achieve a 20-30% improvement in operating profits by following his recommendations. For business owners, CEOs, and entrepreneurs, this episode provides a clear framework for turning sales into a reliable engine for valuation, cash flow, and sustainable growth. Monday Morning Radio is hosted by the father-son duo of Dean and Maxwell Rotbart. Photo: Doug C. Brown, CEO Sales Strategies Posted: March 2,, 2026 Monday Morning Run Time: One hour and two minutes Episode: 14.35 RELATED EPISODES: UX is the Most Powerful Differentiator in Today's Highly Competitive Business World Huddle Up. Head Coach Rob Cornilles is About To Share the Secrets of His Sales Playbook Starting Today, You Can Profit by Running Your Business Like It's "Day One"
Why do we still struggle with resilience in 2026? Is it the growing complexity of systems, the pressure to ship fast, or a lack of education around resilient design? In this episode we welcome Adrian Hornsby from Resilium Labs to explore these questions and learn about chaos, complexity, and the importance of continuous learning!Adrian has learned his chaos engineering skills while working at AWS for many years. He shares insights from his upcoming book and his experience helping organizations embrace resilience as a continuous learning practice. We discuss:Why traditional chaos engineering assumptions break down when AI starts writing your code.The rise of AI-powered SRE agents—are they a blessing or a missed learning opportunity?Organizational challenges and the importance of tracking near misses.Links we discussedAdrians LinkedIn: https://www.linkedin.com/in/adhorn/Resilium Labs: https://www.resiliumlabs.com/Upcoming Book: https://leanpub.com/whywestillsuckatresilience
In this episode of Construction Corner, host Dillon delivers a passionate manifesto on the power of making fast decisions and sticking with them. Reflecting on seven years of podcasting and a recent conversation with fellow entrepreneurs, he challenges the paralysis that keeps people from taking action. From Joe Rogan's 500 episodes before anyone cared to Mr. Beast's 15-year grind, Dillon illustrates how consistency and commitment—not perfection—lead to success. He shares practical examples from his own work, including how three days spent refining a simple pole base detail saved clients $50,000, and emphasizes that overthinking kills momentum. Whether it's starting a podcast, creating content, or standardizing construction details, Dillon's message is clear: make a decision, run with it, get better as you go, and stop worrying about looking silly. Be authentic, embrace the learning curve, and remember that the internet trolls probably weren't going to buy from you anyway.Comment your thoughts below and don't forget to like, SHARE, and subscribe!Want an Engineering firm BUILT for Electrical Contractors? Let's see how we can help speed up your Design/Build projects. Visit https://verticaldesignservices.com/ Connect with Dillon MitchellLinkedIn - https://www.linkedin.com/in/dillon-mitchell-pe/Vertical Design Serviceshttps://www.instagram.com/vertical_designservices/#Revit #BIM #Automation #VerticalDesignServices #VDS #MEP #Contractors #Engineering #ElectricalContractor
From Steel Mills to Quantum Scale-Up: Inside Illinois's Bold Bet on the Future of ComputingWhat does it take to build the world's largest dedicated quantum technology park — on the site of a former steel mill? Harley Johnson is leading that effort, and the answer involves equal parts materials science, economic development, and a 30-year bet on quantum that's finally paying off.Why This Episode MattersIf you're following the quantum computing industry's path from lab prototypes to commercial-scale systems, this episode maps the terrain. Harley Johnson — a computational materials scientist turned CEO of the Illinois Quantum and Microelectronics Park (IQMP) — explains how Illinois assembled a unique combination of federal research funding, state economic investment, national labs, and top-tier universities into a 128-acre technology park designed to solve the quantum industry's hardest problem: scaling up.Whether you're a researcher, a founder, a policymaker, or someone trying to understand where quantum jobs and applications are actually headed, this conversation lays out how one state is building the infrastructure — physical, institutional, and human — to make large-scale quantum computing real.What You'll LearnHow a 1994 bet on quantum mechanics in a mechanical engineering lab led to directing the largest dedicated quantum tech park in the worldWhy Illinois chose a "beyond silicon" strategy for the CHIPS and Science Act — and how landing 4 of the first 10 federal quantum centers positioned the state for what came nextHow IQMP's public-private governance model works: a university-governed LLC partnering with private developers, accountable to the public while incentivizing industryWhy the park deliberately hosts a diverse portfolio of hardware modalities — including PsiQuantum, IBM, Inflection, Dirac, and Pascal — and how that mirrors venture portfolio thinkingHow IQMP's algorithm center connects quantum hardware companies with Fortune 500 end users in finance, insurance, energy, logistics, and pharmaWhat the DARPA Quantum Benchmarking Initiative means for tenant selection and validationWhy roughly two-thirds of future quantum industry jobs may require a bachelor's degree or less — and what that means for workforce development on a former industrial siteHow the Duality Accelerator, Chicago Quantum Exchange, and Polsky Center create a pipeline from early-stage startups to scale-up tenantsWhy the convergence of physics, engineering, and computer science — all housed in one college at UIUC — is accelerating quantum's transition from science to engineeringResources & LinksGuest LinksHarley Johnson — Professor, University of Illinois Urbana-Champaign, Department of Mechanical Science and Engineering and Materials Science Illinois Quantum and Microelectronics Park (IQMP)Organizations & ProgramsChicago Quantum Exchange (CQE) — regional hub coordinating quantum research, workforce studies, and industry engagement Duality Accelerator — quantum startup accelerator run through the Polsky Center at the University of Chicago Polsky Center for Entrepreneurship and Innovation, University of ChicagoDARPA Quantum Benchmarking Initiative — federal program validating progress toward useful quantum computing NSF MRSEC at UIUC — Materials Research Science and Engineering Center focused on electronic and quantum materials Policy & FundingCHIPS and Science Act — federal legislation driving investment in semiconductor and quantum technology manufacturing in the US Companies MentionedPsiQuantum — photonic quantum computing company scaling up at IQMPIBM — anchor tenant at IQMP with longstanding partnership with UIUCKey Quotes & Insights"Help me pick a problem, a topic that is not big now, but would be big in 10 years." — Harley Johnson, on the question he asked his advisor in 1994 that launched his career in quantum materials"When I heard my friends who are experimental physicists say, 'We know how to do it, now it's just an engineering problem,' I said great — now you've thrown down the gauntlet. Let the engineers at it.""Something like two-thirds of the jobs that this industry will eventually create will require a bachelor's degree or less." — On workforce projections from Chicago Quantum Exchange research"Our neighbors and community members are learning about quantum and thinking about how my grandson gets a job in quantum. Because my family, until now, we're steelworkers." — On the community impact of building a quantum park on a former US Steel site"We're seeing a convergence of the great productive academic minds from computer science, engineering, and physics working now on the same problems. I'm not sure we saw that even five years ago."Related EpisodesAlejandra Y. Castillo — Quantum as a Regional Economic Development Engine — Castillo, former Assistant Secretary of Commerce for Economic Development, discusses how quantum technologies fit into federal and state economic strategy through the CHIPS and Science Act, EDA Tech Hubs, and inclusive workforce development. Essential context for understanding the policy and economic framework that IQMP operates within.Martin Laforest — Building Quebec's Quantum Ecosystem — Laforest, partner at Quantacet and advisor to Canada's National Quantum Strategy, traces how Quebec built one of the world's strongest quantum ecosystems through decades of strategic investment — starting with a bet on condensed matter physics in the 1970s. A compelling parallel to the Illinois story and a window into how this pattern is playing out globally.Nadya Mason — Quantum Leadership — Mason, the dean of the Pritzker School of Molecular Engineering at University of Chicago, is a major force on the academic side of the Illinois quantum ecosystem, and has strong views on what's needed in terms of inclusion and education. Calls to ActionIf you're working on quantum scale-up challenges or building a quantum startup approaching the growth stage, explore what IQMP and the Illinois quantum ecosystem offer — from cryogenic facilities to algorithm partnerships to connections with Fortune 500 end users.Subscribe to the NQE Podcast to follow the people and institutions building the infrastructure for quantum computing's next chapter.Share this episode with anyone in economic development, science policy, or workforce planning who wants a concrete example of how quantum investment translate...
Most guys say they are referral-based, but they are still letting random leads waste their week. This one is all about what an ideal referral actually looks like and how to shape expectations, messaging, and follow-up so you get more of the right clients. Show Notes: 0:00 Expectations First 8:43 Orlando Recap 10:37 Tyler's Build Stuff 12:47 "Slip the Truck" 15:22 What Makes a Good Referral 19:41 Reviews & Testimonials 24:41 Pre-Con Protects You 32:49 Qualify Faster 36:53 Control the Narrative 1:00:17 Trade Partner Referrals 1:04:01 Stay Top of Mind 1:05:26 Wrap & Newsletter Video Version:https://youtu.be/cBxWsw7g7qA Partners: Andersen Windows Harnish Workwear Use code H1025 and get 10% off their H-label gear The Modern Craftsman: linktr.ee/moderncraftsmanpodcast Find Our Hosts: Nick Schiffer Tyler Grace Podcast Produced By: Motif Media
Could life on Earth have arrived from space? Explore panspermia, alien comets, and how life might spread across the galaxy.Get Nebula using my link for 50% off an annual subscription: https://go.nebula.tv/isaacarthurWatch my exclusive video Lazarus Protocols: https://nebula.tv/videos/isaacarthur-lazarus-protocols-reviving-civilizations-after-extinctionCheck out Day Pass: https://nebula.tv/daypass?ref=isaacarthur
Could life on Earth have arrived from space? Explore panspermia, alien comets, and how life might spread across the galaxy.Get Nebula using my link for 50% off an annual subscription: https://go.nebula.tv/isaacarthurWatch my exclusive video Lazarus Protocols: https://nebula.tv/videos/isaacarthur-lazarus-protocols-reviving-civilizations-after-extinctionCheck out Day Pass: https://nebula.tv/daypass?ref=isaacarthur
Jif Paines | 10 Percent True | EP82ChaptersGet the full episode:https://www.10percenttrue.com/pricing-plans/listIn this episode, former RAF Harrier pilot and X-35B test pilot “Jif” Paines explains how the F-35B's revolutionary STOVL flight control system was born.From early Harrier night attack operations to experimental fly-by-wire research on the VAAC Harrier, Jif traces the technical and philosophical battle that led to Unified Flight Control — the system that made the F-35B dramatically easier to fly.Along the way he discusses:• Auto-eject systems and pilot safety philosophy• The lift-fan mechanics behind the F-35B's STOVL capability• The X-35 concept demonstrations and engineering decisions behind them• Why automation can “de-skill” pilots — and why that may be necessary• How test pilots and engineers negotiate control authority• And why automation forces a fundamental rethink of the human role in combat aviationThis conversation provides rare insight into test pilot culture, engineering decision-making, and the future of autonomous airpower.0:00 “A stupid question?”1:15 Welcome Jif1:38 Auto-eject subscriber question (Sedlo)4:24 Thanks to Super for the introduction4:48 Jif's introduction11:40 Transferring TPS knowledge and skills to testing in the X-3514:00 What decisions had been made before joining the program?17:12 VAAC Harrier control laws and pilot resistance to the concepts being developed20:15 Unified Flight Control explained25:15 Engineering the “feel” for the pilot — reversion and safety features, de-skilling31:10 “A stupid question?”32:16 Integration of the control laws into the X-3534:19 Lift-fan dynamics and operating process37:00 Differences between flying the VAAC Harrier and the F-3538:10 STOVL initially implemented in Harrier style — why?40:22 Flying characteristics and aircraft feel43:16 Exciting?44:40 Transferring expertise to the X and F variants and defending Unified Flight Control49:40 The Farley climb53:50 The future of the pilot in military aviation57:30 Thanks Jif (please return!)
This week on VG Pulse, we’ve got a whole pile of stupid to go over! We start off with side notes of new phones and giant movie posters, before we dive into the stupid where we discuss Discord being stupid! Oh why do companies have to be stupid… after the stupid, we discuss the rocky future of Microsoft, Toyota making their own weird game engine, and some incredibly upsetting losses in the legacy gaming sphere these past few weeks. After the news we realize we’ve gone very long on this one, and skip right on to finishing off with talk of anime!! All this and more up next on VGP … Continue reading "VG Pulse 430: NASA Grade Engineering"
Starting off in FOLLOW UP, we've got a tax economist who actually made money betting against the "efficiency" of Elon's budget-slashing fever dreams, while Tesla is busy trying to dodge a $243 million jury verdict for an Autopilot-assisted fatality. Not content with being legally liable, Tesla is also suing the California DMV because they're offended someone called their "Autopilot" and "Full Self-Driving" marketing deceptive—ironic, since Jack Dorsey just "proactively" halved the staff at Block to make room for more AI slop. Speaking of which, Goldman Sachs is here to remind us that all this AI spending added a grand total of zero to the US GDP last year, mostly because we're just exporting all that cash to overseas chip makers while 80% of execs admit the tech hasn't actually done anything for productivity yet.Moving into IN THE NEWS, Sam Altman had the audacity to compare ChatGPT's energy-sucking habits to the 20-year evolution of a human, though the internet wasn't exactly buying the "my bot is just like a baby" defense. Anthropic actually stood its ground against the Pentagon's demand for killer robots and mass surveillance, so naturally, the military just signed a deal to put Elon's Grok in their classified systems instead—because what could go wrong with an "edgy" LLM in the war room? Meanwhile, cities are dumping AI surveillance contracts as citizens start a literal "smash-the-snitch-box" campaign against Flock's license plate readers, Google's AI is busy inserting racial slurs into news alerts, and the White House is apparently harboring a staffer moonlighting as a racist "masterpiece" creator on X. We've also got Reddit being slapped with a $20 million fine in the UK for being lazy with age checks, while Discord and Apple scramble to build verification tools that hopefully won't leak your entire identity to a hacker in Belarus.In MEDIA CANDY, the Paramount-Skydance merger is leaving the industry in a cold sweat of "synergy" layoffs, but at least we're getting more Game of Thrones spinoffs and Star Trek reboots to rot our brains. Face/Off 2 lost its director, Ryan Coogler is taking on The X-Files, and Google wants to use AI to turn music into generic "lo-fi" background noise for the masses.Over in APPS & DOODADS, OpenAI is planning a 2027 smart speaker that literally watches you through a camera—because you definitely wanted a $300 Sam Altman-shaped eye in your kitchen—while the Dark Sky creators are back with "Acme Weather" for the low price of $25 a year.We wrap up THE DARK SIDE WITH DAVE with a deep dive into "Under Pressure" and Coruscant's urban sprawl, leaving us to reminisce about the days when KPT Bryce was the pinnacle of tech—back when "generative art" was just a fractal that took six hours to render.Sponsors:DeleteMe - Get 20% off your DeleteMe plan when you go to JoinDeleteMe.com/GOG and use promo code GOG at checkout.SquareSpace - go to squarespace.com/GRUMPY for a free trial. And when you're ready to launch, use code GRUMPY to save 10% off your first purchase of a website or domain.Private Internet Access - Go to GOG.Show/vpn and sign up today. For a limited time only, you can get OUR favorite VPN for as little as $2.03 a month.SetApp - With a single monthly subscription you get 240+ apps for your Mac. Go to SetApp and get started today!!!1Password - Get a great deal on the only password manager recommended by Grumpy Old Geeks! gog.show/1passwordShow notes at https://gog.show/735Watch on YouTube: https://youtu.be/jdz--v3eeU4FOLLOW UPGuy Bets Entire Life Savings Against Elon Musk, WinsTesla sues California DMV after it banned the term 'Autopilot'Jack Dorsey just halved the size of Block's employee base — and he says your company is nextIN THE NEWSSam Altman: Know What Else Used a Lot of Energy? Human CivilizationStatement from Dario Amodei on our discussions with the Department of WarAnthropic Tells Pete Hegseth to Take a HikeCities Are Shredding Their AI Surveillance Contracts en MasseKalshi Suspended a California Politician and a YouTuber for Insider TradingDiscord delays age verification to address user concernsApple introduces age verification for apps in Utah, Louisiana and AustraliaMEDIA CANDYAs Paramount Skydance wins the battle for Warner Bros. as Netflix ends its bid, here's the mood inside all three companies.A Knight of the Seven KingdomsStar Trek: Starfleet AcademyThe Night Agent Season 3'Face/Off 2' Director Adam Wingard is Now/GoneRyan Coogler's X-Files reboot gets the green light at HuluMortal Kombat II | Official Trailer IIGoogle's AI Slop Machine Is Coming for Your MusicDropping Names... and other things with Jonathan Frakes and Brent SpinerOnce We Were SpacemenAPPS & DOODADSOpenAI will reportedly release an AI-powered smart speaker in 2027Instagram Will Notify Parents When Teens Use Search Terms Related to SuicideThe creators of Dark Sky have a new weather appThis App Warns You if Someone Is Wearing Smart Glasses NearbyTHE DARK SIDE WITH DAVEDave BittnerThe CyberWireHacking HumansCaveatControl LoopOnly Malware in the BuildingStrong Songs - S08E02 - "Under Pressure" by Queen and David BowieThe Problem with Coruscant (Planet Cities Explained)Reminds me of KPT Fractal ExplorerKPT Bryce 1.0 with John Dvorak and Kai KrauseSingle-Biome PlanetKPT Shapes by Dave BittnerBald Mr Clean mascot "retired"My childhood disappointment with scrubbing bubbles.CLOSING SHOUT-OUTSActor Robert Carradine Dies At Age 71See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.
Doug Messier reports that persistent thruster failures and engineering incompetence have marred Boeing's Starlinerprogram, leaving astronauts marooned and NASA heavily dependent on SpaceX for crewed orbital missions. 8.1952