My Favorite Moments from Episode 242 "Designing for 100 Years… in 100 Seconds?"

💬 18 lines worth keeping from TRXL 242, from fifteen voices on what an agent really is, where the risk piles up, and whether you'd want to prompt a building.

My Favorite Moments from Episode 242 "Designing for 100 Years… in 100 Seconds?"

Every episode of this series, I go back through the full conversation and pull the lines I don't want you to miss. Here are 18 of them from Episode 242, “Designing for 100 Years… in 100 Seconds?” Each one has who said it and a timestamp if you want to hear it in context.

On what an agent actually is

Oliver Goldman
“MCP servers, one way to think about them, and the way I think about them from a software perspective, is they're just like a… a new kind of API that's accessible to agents instead of to programmers.”
Oliver Goldman, Autodesk · ▶ 0:15:20
Mike Soldan
“An atomic agent… is something that you can write a task for that can get something done at a certain level. And then you have to orchestrate them, and that's how you drive the bigger process.”
Mike Soldan, Egnyte · ▶ 1:07:00
Mike Soldan
“What we're really doing here is business process analysis, the same thing that humans have done to try to make businesses more efficient for 50 years. You just have better tools to do it that are more automated.”
Mike Soldan, Egnyte · ▶ 1:10:10
Michael Jansen
“A lot of the assistance you're seeing added on to Revit and Trimble and other tools like this—these are not agentic systems. They count doors and windows… It's not really agentic behavior.”
Michael Jansen, TwinMaster · ▶ 1:31:50

On risk and trust

Evan Troxel
“Stack enough agents together and you get a different kind of risk, each one inheriting the last one's mistakes, a small error compounding until you're left with a confident answer and no way to see how it got there.”
Evan Troxel · ▶ 0:47:40
Marty Rozmanith
“What we don't want is an AI to be a black box, where you feed it 20 years of firm history, and then it starts spitting out designs and you don't know why.”
Marty Rozmanith, Skema · ▶ 1:03:00
Scott Reynolds
“You never have a decision in isolation. You always have the traceability.”
Scott Reynolds, UpCodes · ▶ 0:49:30
Theodoros Galanos
“They just treat it as a data engineering problem, but it's actually a core expertise problem.”
Theodoros Galanos, Aurecon · ▶ 1:24:40

On what's working right now

Greg Demchak
“Show me this complete building model and render and isolate all the concrete and then color code the concrete based on the quantity of embodied carbon… And that is something you can do today.”
Greg Demchak, Bentley Systems · ▶ 0:19:30
Matt Wash
“And the agent said, 'There is no QA/QC process here. It's clear that people are marking up on the same drawing at the same time. The recommendation is to move to Bluebeam Studio.'”
Matt Wash, Bimbeats · ▶ 1:15:50
Ariel Cooke-Zamora
“Revit crashes. I lose an hour of work. I smash my head against the wall, and I open Revit again, and I keep working. And IT probably had no idea that this even happened.”
Ariel Cooke-Zamora, Bimbeats · ▶ 1:13:20
Marty Rozmanith
“It's not paying to be a Luddite and say, 'Well, nobody's using AI,' or, 'We're not gonna use it,' 'cause it can save you a hell of a lot of time.”
Marty Rozmanith, Skema · ▶ 0:41:10
Gavin Nicholls
“For a while people said the best code is self-commenting. I think AI is better at reading comments.”
Gavin Nicholls, The Aussie BIM Guru · ▶ 0:53:40

On prompting a building

Jesper Wallgren
“I don't think you should design anything that should last for 100 years in 100 seconds.”
Jesper Wallgren, Finch · ▶ 0:00:00
Jesper Wallgren
“Prompt architecture, for me, that sounds like the person that goes to the architect. They speak. They say, 'I want the building with this, and that,' and then the architect goes to work and turn that into drawings.”
Jesper Wallgren, Finch · ▶ 1:54:20
Holger Kreienbrink
“It's not just a hair blower or something mechanical which you can create, which is there a thousand times, which you can prompt. But for architecture, I don't want to have it, and I don't believe in that.”
Holger Kreienbrink, Graphisoft · ▶ 1:58:40
Roderick Bates
“If you could almost ingest all of the work of, say, Frank Lloyd Wright, and then you could show him your project and just have him critique you, it'd just be brutal.”
Roderick Bates, Chaos · ▶ 1:41:30
Campbell Yule
“The part of conceptual design that an architect commonly does isn't just following the rules. There's multiple things that you're holding in your head, many of them at tension with each other.”
Campbell Yule, campbellyule.com · ▶ 2:06:30
This series brought to you by
Graitec Graitec provides AEC software, training, and expert support to help architects, engineers, and construction teams design, build, and manage projects more effectively.
With support from
AVAIL AVAIL's content management system (CMS) helps architecture and engineering teams find, manage, and reuse their Revit, AutoCAD, Civil 3D, and other technical content in one place.
😎
Win a pair of Ray-Ban Meta Smart Glasses, courtesy of series partner Graitec. Enter the giveaway. (Entering shares your contact info with Graitec.)

That's the whole episode's worth of highlights. Full conversation's at trxl.co/242 if any of these made you want the rest.