Podcasts about specifications

Perhaps indicative of the hard trading conditions and highly competitivenew vehicle market Mazda has taken the axe to pricing on its CX-60 SUV.Up to $5,560 has been shaved from some models in the luxury CX-60 line-up - now priced from $53,990 drive-away while six new variants have beenadded across the Pure and Touring grades. First launched in 2023 theMazda CX-60 was criticised for its harsh ride and twitchy gear shifts. Assuch the update brings new rear springs and dampers, revised stabilitycontrols and a recalibrated 8-speed automatic transmission. Plus, allmodels now get a 360-degree camera and front cross traffic alert.Specification has been added right across the Mazda CX-60 range which isthe best seller in the medium SUV segment above $60,000, ahead of theLexus NX and the Kia EV5. I’m David BerthonSee omnystudio.com/listener for privacy information.

Send us a textWe dive into the often-overlooked world of specification engineers and their critical role in ensuring successful low voltage infrastructure projects. Roy Chamberlain from Leviton Network Solutions shares insights on how these behind-the-scenes experts help project managers, estimators, and technicians navigate complex specifications and standards.• Specification engineers serve as the glue between manufacturers, contractors, designers, and end-users• They help interpret specifications, fill in gaps, and ensure all components work together seamlessly• Many specifications contain outdated standards due to template reuse—spec engineers help keep everything current• Manufacturers offer solution-based approaches rather than just individual products• Future-proofing isn't necessarily more expensive—it just requires different thinking• Technicians can directly contact spec engineers for troubleshooting and on-site challenges• Working with established manufacturers provides access to expertise that online retailers can't match• Spec engineers stay current with evolving standards through regular training and industry participationCheck out Leviton's website or connect with Roy Chamberlain on LinkedIn to learn more about how specification engineers can help with your next project.Support the showKnowledge is power! Make sure to stop by the webpage to buy me a cup of coffee or support the show at https://linktr.ee/letstalkcabling . Also if you would like to be a guest on the show or have a topic for discussion send me an email at chuck@letstalkcabling.com Chuck Bowser RCDD TECH#CBRCDD #RCDD

In addition to MCP, Google, IBM and others have presented protocols and frameworks that will help AI agents talk to each other. These protocols are essential unlocks to getting value out of agents. This hosted briefing walks through the protocols and why they matter.

This episode of the Smart Buildings Academy Podcast focuses on critical discussions that directly impact building automation professionals. Instructors Matt Scott, Ethan Morris, and Michael Roper explore the evolving relationship between BAS professionals and IT departments, common pitfalls in BAS specifications, and the practical value of trend logging. The conversation is centered on real-world challenges and strategies for success in modern building projects. The team shares insights based on field experiences, addressing issues that affect system performance, project timelines, and professional collaboration. This episode highlights actionable points for building automation professionals committed to delivering better outcomes. Key Topics Covered: The current state of collaboration between BAS teams and IT departments Why BAS devices are increasingly treated as IT assets Risks of not coordinating with IT during BAS deployments and how to avoid project delays Specification mistakes seen in BAS projects and professional ways to offer feedback The role of trend logs in troubleshooting, compliance, and performance improvement This episode will help you strengthen your BAS practices and stay ahead in a rapidly changing environment.

Every home is built on something — but is yours built to last? In today's message, Pastor Ron Zappia opens to Matthew 7 to share 4 Specifications of a House that Stands.   This message was originally preached at Highpoint Church on Sunday, April 27, 2025 Message title: A House that Stands Passage: Matthew 7:24-27   For more info about Highpoint Church, or to find a location near you, visit our website at https://highpoint.church.   Connect with Pastor Ron and find more Bible teaching at https://ronzappia.com

Is the use of threats to repel dishonest people a good idea? On this episode of Troubleshooting Agile, Squirrel and Jeffrey talk about the “threat of reference check” and whether the benefits of reducing dishonesty outweigh the drawbacks of damaging trust. Get in touch to tell us what you think. SHOW LINKS: - Domain-Driven Design: en.wikipedia.org/wiki/Domain-driven_design - Big Book of Concepts: mitpress.mit.edu/books/big-book-concepts - Specification by Example: gojko.net/books/specification-by-example/ - Walking Skeleton: wiki.c2.com/?WalkingSkeleton -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

It's time to talk about commitment! Not engagement, which is insufficient to produce effective results. In this episode - a repost of a previous conversation - Squirrel and Jeffrey offer specific tools for effective commitments and tell a story about a company that created a pile of bones instead of a Walking Skeleton. You'll hear lots of references to “the book.” That's our book - Agile Conversations!! You can learn more about that here: https://agileconversations.com/agile-conversation-book/ SHOW LINKS: - Domain-Driven Design: en.wikipedia.org/wiki/Domain-driven_design - Big Book of Concepts: mitpress.mit.edu/books/big-book-concepts - Specification by Example: gojko.net/books/specification-by-example/ - Walking Skeleton: wiki.c2.com/?WalkingSkeleton -------------------------------------------------- You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication. Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/

ERC-7527: Token Bound Function Oracle AMMInterfaces that wrap FT to NFT and unwrap NFT to FT based on an embedded Function Oracle AMM.Resources: - EIP-7527 - Discussion - Ramble On-Chain Pricing Mechanism - PresentationOther Resources: - Economics Paper - On-Chain Pricing - PremiumDAO - PremiumDAO TwitterUse Cases: - WrapCoin - WrapGM - WrapCoinLab - AgentBallRelated EIP: - ERC-7615PEEPanEIP Playlist: - PEEPanEIP PlaylistFollow on Twitter: -------------------------- - Lanyin Zhang - Pooja Ranjan --------------------------Edited by: Akash KshirsagarTopics Covered: ------------------------- 00:00 - Episode Recap 00:25 - Intro 01:14 - About ERC-7527 01:59 - Lanyin Zhang Introduction 04:29 - Presentation Starts 04:40 - What is ERC-7527? 06:06 - Motivation 07:51 - Overview of On-Chain Asset Pricing 08:47 - AMM Curves 10:58 - Bonding Curve 14:36 - Auction Mechanisms 17:49 - Introducing ERC-7527 19:59 - ERC-7527 Pricing Mechanism 22:27 - Specification 29:15 - Advantages of ERC-7527 33:42 - Application & Use Cases 36:22 - Use Case 37:40 - After Presentation 38:11 - Q&A 38:33 - How is the Use Case of This Proposal Different From Custodial Wallet Providers? 42:16 - How Can ERC-7527 Integrate With Existing DeFi Protocols Like Lending Platforms, Decentralized Exchanges, or NFT Fractionalization? 44:54 - What Security Measures Are in Place to Prevent Manipulation, Reentrancy Attacks, or Oracle Exploits? 47:32 - What Kind of Impact Will ERC-7527 Bring to NFT, DeFi, etc.? 49:27 - Rapid Fire Section 51:15 - Closing Words by Pooja------------------------- #ERC7527 #Ethereum #PEEPanEIP #Token #NFT

This sponsored episode features mathematician Ohad Asor discussing logical approaches to AI, focusing on the limitations of machine learning and introducing the Tau language for software development and blockchain tech. Asor argues that machine learning cannot guarantee correctness. Tau allows logical specification of software requirements, automatically creating provably correct implementations with potential to revolutionize distributed systems. The discussion highlights program synthesis, software updates, and applications in finance and governance.SPONSOR MESSAGES:***Tufa AI Labs is a brand new research lab in Zurich started by Benjamin Crouzier focussed on o-series style reasoning and AGI. They are hiring a Chief Engineer and ML engineers. Events in Zurich. Goto https://tufalabs.ai/***TRANSCRIPT + RESEARCH:https://www.dropbox.com/scl/fi/t849j6v1juk3gc15g4rsy/TAU.pdf?rlkey=hh11h2mhog3ncdbeapbzpzctc&dl=0Tau:https://tau.net/Tau Language:https://tau.ai/tau-language/Research:https://tau.net/Theories-and-Applications-of-Boolean-Algebras-0.29.pdfTOC:1. Machine Learning Foundations and Limitations [00:00:00] 1.1 Fundamental Limitations of Machine Learning and PAC Learning Theory [00:04:50] 1.2 Transductive Learning and the Three Curses of Machine Learning [00:08:57] 1.3 Language, Reality, and AI System Design [00:12:58] 1.4 Program Synthesis and Formal Verification Approaches2. Logical Programming Architecture [00:31:55] 2.1 Safe AI Development Requirements [00:32:05] 2.2 Self-Referential Language Architecture [00:32:50] 2.3 Boolean Algebra and Logical Foundations [00:37:52] 2.4 SAT Solvers and Complexity Challenges [00:44:30] 2.5 Program Synthesis and Specification [00:47:39] 2.6 Overcoming Tarski's Undefinability with Boolean Algebra [00:56:05] 2.7 Tau Language Implementation and User Control3. Blockchain-Based Software Governance [01:09:10] 3.1 User Control and Software Governance Mechanisms [01:18:27] 3.2 Tau's Blockchain Architecture and Meta-Programming Capabilities [01:21:43] 3.3 Development Status and Token Implementation [01:24:52] 3.4 Consensus Building and Opinion Mapping System [01:35:29] 3.5 Automation and Financial ApplicationsCORE REFS (more in pinned comment):[00:03:45] PAC (Probably Approximately Correct) Learning framework, Leslie Valianthttps://en.wikipedia.org/wiki/Probably_approximately_correct_learning[00:06:10] Boolean Satisfiability Problem (SAT), Varioushttps://en.wikipedia.org/wiki/Boolean_satisfiability_problem[00:13:55] Knowledge as Justified True Belief (JTB), Matthias Steuphttps://plato.stanford.edu/entries/epistemology/[00:17:50] Wittgenstein's concept of the limits of language, Ludwig Wittgensteinhttps://plato.stanford.edu/entries/wittgenstein/[00:21:25] Boolean algebras, Ohad Osorhttps://tau.net/tau-language-research/[00:26:10] The Halting Problemhttps://plato.stanford.edu/entries/turing-machine/#HaltProb[00:30:25] Alfred Tarski (1901-1983), Mario Gómez-Torrentehttps://plato.stanford.edu/entries/tarski/[00:41:50] DPLLhttps://www.cs.princeton.edu/~zkincaid/courses/fall18/readings/SATHandbook-CDCL.pdf[00:49:50] Tarski's undefinability theorem (1936), Alfred Tarskihttps://plato.stanford.edu/entries/tarski-truth/[00:51:45] Boolean Algebra mathematical foundations, J. Donald Monkhttps://plato.stanford.edu/entries/boolalg-math/[01:02:35] Belief Revision Theory and AGM Postulates, Sven Ove Hanssonhttps://plato.stanford.edu/entries/logic-belief-revision/[01:05:35] Quantifier elimination in atomless boolean algebra, H. Jerome Keislerhttps://people.math.wisc.edu/~hkeisler/random.pdf[01:08:35] Quantifier elimination in Tau language specification, Ohad Asorhttps://tau.ai/Theories-and-Applications-of-Boolean-Algebras-0.29.pdf[01:11:50] Tau Net blockchain platformhttps://tau.net/[01:19:20] Tau blockchain's innovative approach treating blockchain code itself as a contracthttps://tau.net/Whitepaper.pdf

RIP-7759 is specification of rules for L2 transaction fee derivation, payout, and display to any of the participants in an L2 platform.Resources: -----------------Presentation: https://docs.google.com/presentation/d/1Q4b64udLfeS019HJ37WG_3mkXYP1KTT9YMnweqNcMjY/edit?usp=sharingRIP: https://github.com/ethereum/RIPs/blob/master/RIPS/rip-7759.mdDiscussion - https://ethereum-magicians.org/t/rip-7759-layer-2-transaction-fee-specification/20862/1-----------------Other Resources: RIP 7810: https://github.com/ethereum/RIPs/blob/master/RIPS/rip-7810.md-----------------Check out upcoming EIPs in Peep an EIP series at https://github.com/ethereum-cat-herders/PM/projects/2PEEPanEIP - https://www.youtube.com/playlist?list=PL4cwHXAawZxqu0PKKyMzG_3BJV_xZTi1FFollow at Twitter:--------------------------Andreas Freund - https://twitter.com/AndreasFRHAPooja Ranjan - https://twitter.com/poojaranjan19--------------------------Edited by Akash Kshirsagar https://twitter.com/oceansofmilkTopics covered:-------------------------00:00 - Quick Recap00:22 - PEEPanEIP Intro00:35 - Starting Words02:44 - Andreas Introduction06:26 - Presentation Start06:32 - Leveling the Playing Field07:47 - The Ethereum OASIS L2 Standards Project08:48 - RIP-7759: Standard Transparent Fees10:00 - Clear Fees, Clear Roles10:56 - Benefits: The Power of Transparent L2 Fees11:35 - Join the Effort for Transparent L2 Fees12:57 - Presentation End13:28 - Q&A Session13:33 - What is Fee Refund Criteria?19:05 - What is the roadmap look like for this implementation?23:20 - Challenges in Adoption.25:45 - Did Andreas Freund receive any feedback that could change the specifications and standardization of this proposal?27:02 - Which is best suited category for this proposal?30:19 - Rapid Fire Session34:48 - Closing words by Andreas Freund35:30 - Closing words by Pooja Ranjan-------------------------#rip7759 #Ethereum #PEEPanEIP #RIP

Are your specification limits holding you back from improving your products and services? Should you throw out specifications? What does Stephen Hawking have to do with it? In this episode, Bill Bellows and host Andrew Stotz discuss specifications and variation. TRANSCRIPT 0:00:02.5 Andrew Stotz: My name is Andrew Stotz, and I'll be your host as we dive deeper into the teachings of Dr. W Edwards Deming. Today, I'm continuing my discussion with Bill Bellows, who has spent 31 years helping people apply Dr. Deming's ideas to become aware of how their thinking is holding them back from their biggest opportunities. Today is episode 12, and the title is Do Specification Limits Limit Improvement. Bill, take it away.   0:00:31.4 Bill Bellows: Hey, Andrew. How's it going? All right.   0:00:33.8 Andrew Stotz: Great. Great to have you back and great to see you. For those that are just listening, you can watch the video on DemingNEXT. But for those listening, Bill looks handsome, full of energy, ready to go, and it's my 8:30 in the morning in Bangkok, Thailand. So let's rock Bill.   0:00:56.3 Bill Bellows: So. I spoke recently to one of the folks I'd met on LinkedIn that have listened to our podcast and took the offer to reach out and we now talk regularly. And I just wanna say I've gotta, before we get to some, the story behind the title, I wanted to share, a heads up. And if anyone would like a copy of this article that I wanna, take some excerpts from, then just reach out to me on LinkedIn and ask for a copy of the article. The article's entitled 'A Brief History of Quality,' and there's three parts. So it's about 10 pages overall, and it was published in 2015 in the Lean Management Journal, which I don't believe still exists. I was writing articles at the end once a month for this journal, I think based out of the UK.   0:02:04.3 Bill Bellows: I think there was a manufacturing magazine that still exists and had this as a special topic and my interest was bringing Dr. Deming's ideas, to the Lean community, which is why it was a Lean Management Journal, so the article was entitled 'Brief History Equality.' And so I wanna get to those topics, but when I was reading the article, reminding myself of it, I thought, oh, I'll just share this story online with Andrew and our audience. And so here I'm just gonna read the opening paragraph. It says, "several years ago, I had the opportunity to attend an hour-long lecture by Stephen Hawking," right? So the article was written in 2015. So the presentation by Hawking would've been maybe 2012, 2013. And back to the article, it says, "he, Hawking, returns to Pasadena every summer for a one-month retreat, a ritual he started in the 1970s, several thousand attendees sitting in both a lecture hall and outdoors on a lawn area complete with a giant screen were treated to an evening of reflection of the legendary Cambridge physicist."   0:03:14.3 Bill Bellows: And I'll just pause. I have friends who work at JPL and they got me seats, and they got me an inside seat in the balcony, front row of the balcony, but they had big screens outside. I mean, it was like a rock concert for Stephen Hawking, right?   0:03:34.3 Andrew Stotz: That's amazing.   0:03:34.9 Bill Bellows: Oh, it was so cool. Oh, it was so cool. So anyway, "his focus was my brief history offering us a glimpse of his life through a twist on his treatise, A Brief History of Time. His introspective presentation revealed his genius, his humility, his search for black holes, his passion for life, not to mention his dry sense of humor. It ended with questions from three Caltech students, the last of which came from a postdoc student, an inquiry Hawking had likely tackled many times before."   0:04:06.6 Bill Bellows: So realize he's answering the questions through a voice activated thing. And it appeared that the questions were, his answers were prerecorded, but they're still coming through a device that is a synthesized voice. But I get the impression that he knew the questions were coming, so we in the audience were hearing the questions for the first time. But he had already answered the questions. So anyway, it ended with questions. There was an undergraduate student, a graduate student, then a postdoc, and I said, "the last of which came from a postdoc student, an inquiry Hawking had likely tackled many times before. And the student relayed the story of an unnamed physicist who once compared himself to both Isaac Newton and Albert Einstein." So this unnamed physicist compared himself to Einstein and Newton each placed on a scale of 1 lowest to 10 highest. "With this context, Hawking was asked where he would rank himself."   0:05:22.0 Bill Bellows: So this physicist said, oh, you know, Andrew, I see myself as this. And so the guy relays the story, and he says to Hawking, so given this other physicist said this, where would you rank yourself? "Well, I do not recall the relative rankings posed in the query. I'll never forget Hawking's abrupt reply. He says, “anyone who compares themselves to others is a loser." And I found online that he was, that commentary, this was not the first time he said that.   0:06:04.9 Andrew Stotz: Right.   0:06:06.5 Bill Bellows: And I just thought, oh, anyone who compares himself to others is a loser. And then the end of the paragraph is "in reference to Dr. Deming," Andrew, "variation, there will always be. So can't we just get used to variation?" So the title, are you in favor? No, no, no, no. That was last time. Are you in favor of improving the quality was number 10. Number 11 was to improve quality, don't measure quality. For 12, the specification limits limit improvement.   0:06:46.9 Andrew Stotz: Now, if that was true, first of all, that would be a little scary, 'cause we spend a lot of time working on specification limits. There's a lot of people working on that.   0:06:55.4 Bill Bellows: But here's what's behind the title. In 1995, I was invited to speak, not for the first time, but for the first time I ever spoke to an audience of the American Society of Quality. It was a San Fernando Valley chapter. I forget the number. I've spoken there many, many times over the years, but this is the first time I ever spoke to quality professionals as opposed to project managers or Society of Manufacturing Engineers. I was there with my wife. There's dinner, then after dinner in the next room, and the chairs were set up, theater style, that'd be 70, 80 people. And I was talking about what I would, I mean, things I still talk about, I talk about new things, to have new things done. But the big thing I was trying to get across the audience is, the difference between meeting requirements, which in this series, we call it acceptability versus desirability, which is, I want this value, I want this professor, I want to date this person. And so I was relaying that concept to that audience. And the question I asked that night was do specification limits limit improvement?   0:08:31.0 Bill Bellows: And there was a guy about seven rows back, and I built up to that. That wasn't the opening thing, but what I was really pushing on was a focus on Phil Crosby's goal of striving for zero defects. And, then what? Once you achieve that, then what? And we've talked about the doorway and that's like the door is closed, we get up to the doorway and we've achieved zero defects. And, what we've talked about is going through the doorway and the attitude is, well, why open the door? I mean, don't open the door, Andrew. There's a wall on the other side of that door, Andrew. So it might be a door, but everybody knows there's a wall behind it, and I was poking at that with this audience, and prepared to show them the value proposition of going through that.   0:09:34.0 Bill Bellows: So anyway, I remember I got to the point of asking, do specification limits limit thinking about improvement or something like that. And a more senior gentleman, about seven or eight rows back, and fortunately, he was seven or eight rows back, fortunately, because he stood up and he says, "Are you saying we don't need specification limits?" There's a lot more anger in his voice. And I said, "No," I said, "I'm saying I think they limit our thinking about improvement." And, but he was really upset with me, and I was deliberately provoking because again, you and I have talked about, how can we inspire through this podcast and other podcasts that you do with the others, to get people to think about the possibilities that Dr. Deming shared with us. And it's not believing that there's a door that you can't walk through. You open the door and there's an opening and you can go through. There's a lot more going on there. So anyway, so I had prepared them. The whole reason for being there was to share what we were doing at Rocketdyne, and not just talk about the possibilities, but show them the possibilities. But he got very upset with me. But if he was in the front row, he might've hit me.   0:11:08.9 Andrew Stotz: May have thrown a book at you.   0:11:11.5 Bill Bellows: Oh, he...   0:11:12.2 Andrew Stotz: May have thrown a Specification Limit at you.   0:11:17.0 Bill Bellows: Twice I've had people get, well, I've gotten a number of people upset with me over the years, but that night was, I'll never forget, and I'll never forget, because my wife was sitting in the front row and she asked me never to be that provocative again. It might be dangerous to my health. But I was doing another class, also for the American Society of Quality, I was a member of the local chapter, and there was a big movement within Rocketdyne that all Quality Engineers within Rocketdyne be Certified Quality Engineers. And so two or three of us from Rocketdyne got involved in helping the local chapter train people to prepare to take this one day exam. Very, very, very rigorous. And it's a valuable credential for quality professionals.   0:12:20.1 Bill Bellows: And so the company was pushing that every single quality engineer was certified. So we did the classes on site. So instead of going to the nearby Cal State Northridge and doing it over there, we wanted to do it onsite, make it easy for our employees to attend. And so I would do one and a half sessions. So a given session was three hours long, and then there'd be a half session. And my topics were Design of Experiments and Dr. Taguchi's work. And so as I got this group this one night for the very first time, I was the second half of that three-hour session, and there's 30 some people in the room at Rocketdyne. And the question I wanted to raise is, why run experiments? What would provoke you to run an experiments either, planned experimentation, Design of Experiments or Dr. Taguchi's approach to it.   0:13:15.1 Bill Bellows: So I was throwing that out and I said, in my experience, we're either applying it to make something better - that's improvement, Andrew, - or we're applying it to find out why something doesn't work, which is rearward looking. And I was saying that in my experience, I spend like a whole lot of time running experiments to solve a problem, to fix something that was broken, to get it back to where it was before the fire alarm, not as much time focusing on good to make it better. And so I was just playing in that space of, you know, I guess I was asking the audience are we running experiments to go from bad to good and stop, or from good to better? And I was playing with that 30 people in the room, and all of a sudden, four or five feet in front of me, this guy stands up, says this is BS, but he didn't use the initials, he actually said the word and walked out of the room. And all of us are looking at him like, and there was no provocation. Now, I admit for the ASQ meeting, I was poking to make sure they were paying attention. Here, I was just plain just, why do we run experiments? So, he stands up, he lets out that word, pretty high volume, storms out of the room.   0:14:42.1 Bill Bellows: Well, at Rocketdyne, you can't... You need a... You have to walk around with someone who works there. You just can't go walk around the place, so I had to quickly get one of my coworkers who was in the room to go escort him to the lobby or else, we're all gonna get fired for having somebody unescorted. So the specification limits limit thinking about improvement, I think they do. I am constantly working with university courses or in my consulting work and acceptability in terms of the quality goal, that this is acceptable, it meets requirements is alive and well and thriving, thriving. And, I think what goes on in organizations, I think there's such a focus on getting things done, that to be done is to be good and is to stop that I could pass my work on to you.   0:15:45.2 Bill Bellows: And, the challenge becomes, even if you're aware that you can walk through the doorway and move from acceptability to desirability, how do you sell that to an organization, which you, what I see in organizations, there's a lot of kicking the can down the road. There's a lot of, and even worse than that, there's a lot of toast scraping going on because there's not a lot of understanding that the person toasting it is over toasting it because all they do is put the toast into the oven. Somebody else takes it out, somebody else scrapes it, somebody else sends it back to a different toaster. And I see a lack of understanding of this because the heads are down. That's part of what I see. What I also see in organizations is, with students is this is their first drop.   0:16:51.0 Bill Bellows: Wherever they are, engineering, manufacturing, quality, they're new, they're excited, they're excited to be on their own, to have an income. And they're taking what they learned in universities, and now, they get to apply it. And I remember what that was like. I worked the summer after getting my bachelor's degree, my last semester, I took a class at heat transfer, the prior semester, took a class in jet engines, and I just fell in love with heat transfer and I fell in love with jet engines. And that summer, I was coming back in the fall to go to graduate school for my master's degree. That summer, I worked for a jet engine company as a heat transfer engineer, I was in heaven.   0:17:37.6 Andrew Stotz: Yeah. That's gotta be the coolest thing.   0:17:40.1 Bill Bellows: Just incredible. So I can imagine people coming out of college, going to work, and you get to apply what you learned. You get to use computers, you get to work with some really cool people, and you're doing what you're doing, and it's a blast. And I think it takes a few years before you start to listen to what the veterans are talking about. And you might hear that they're challenging how decisions are made, they're challenging how the company is run. I think prior to that, your heads are down and you're just the subject matter expert. It could be, you know, engineering and manufacturing, finance, and you're doing what you're doing. Their head is down, you're receiving, you're delivering. I still remember when I went to work with my Ph.D. at the same jet engine company, they hired me back. And, I remember walking down the hallway with a colleague and somebody says, that's the VP of Engineering.   0:18:42.7 Bill Bellows: And I thought, we have a VP of Engineering? I mean, I know we have a Vice President of the United States, but I didn't know anything about titles like that. And I think... And I don't think I'm the only one. I've shared those with some younger folks recently, and they agree, you come in, it's heads down, we don't know management, all I get to work on this great stuff. I go and I, and so what we're, but I think what happens is, I think at some point of time you start to look up and you're hearing what the more senior people that are there are saying you've had some experience. And, I know when people join Rocketdyne, and they would come to my class and I would share these stories that had some things that were, if your experience would be questionable, some other things that are pretty cool.   0:19:34.6 Bill Bellows: And, I just had the feeling and I found out people would walk outta there thinking what you mean that, I mean the things, the use of incentives, like why do we need incentives? But, and what I found was it took a couple of years and I would bump into these same people and they'd say, now I'm beginning to understand what you were talking about and what Dr. Deming was talking about. So I throw that out. For those listeners that are trying to, that are at that phase where you're starting to wonder how are decisions being made? You're wondering what you wanna do in your profession. You're wondering what this Deming stuff is about. A whole lot of this entire series has been targeted at people that are new to Deming's ideas. Or maybe they have some experience, they're getting some exposure through these podcasts either with me and the ones you're doing with John and the others. And so, but the other thing I wanna get into today is this quality thing. I go back to this article. And then I was thinking about this article, things I didn't know when I started researching this article is, this term quality, where does that come from? And the term quality comes from, I got to pull it, I have to scroll through the article. Let me get it, let me get it.   0:21:06.4 Bill Bellows: All right. Here we go. "The word quality," Andrew "has Latin roots, beginning with qualitas coined by Roman philosopher and statesman, Marcus Tullius Cicero, who later became an adversary of Mark Antony." You know, what happened to Cicero? Wasn't pretty.   0:21:32.8 Andrew Stotz: Yeah.   0:21:33.9 Bill Bellows: "Feared by Antony," I wrote, "his power of speech led to his eventual beheading. But long after he introduces fellow Romans to the vocabulary of qualitas, that's quality; quantitas, that's quantity; humanitas, that's humanity; and essentia, which is essential. He's also credited with an extensive list of expressions that translate into English, including difference, infinity, science, and morale. When Plato invented the phrase poiotes for use by his peers." So Plato would've been Greek, "Cicero spoke of qualitas with his peers when focusing on the property of an object, not its quantity." And, what I had in mind there is counting how many things we have, so you come in and you want five apples, five suits, whatever it is, there's the quantity thing. And then what Cicero was trying to do is say, quality is not the number, but quality is a differentiation of not just any suit, not just any...   0:22:53.1 Bill Bellows: And I think that becomes the challenge is, is that still important? So when Dr. Deming came on board in 1980, at the age of 79, when the NBC white paper was written, and people got excited by quality because quality was something that people identified with Japanese products, not with American products.   0:23:19.9 Andrew Stotz: Well, not in 1980.   0:23:21.1 Bill Bellows: Not in 1980...   [laughter]   0:23:22.2 Bill Bellows: I mean, at that time, the auto companies were making a lot of money in repair businesses. And Toyota comes along and says, and the words on the street, our products don't require all that repair. And I thought, yeah. And what was neat about that is when I thought, when you think about differentiation and like how do you sell quality? Because, again, I find it, for the longest time, beginning in 1980, quality was hot. Quality improvement. I mean, the American Society of Quality membership skyrocketed. Their membership has dropped like a rock since then because they don't have this Deming guy around that got them going.   0:24:12.1 Bill Bellows: Now, they're still big in the Six Sigma, but I don't believe their membership is anything like it was, but what I was thinking and getting ready for tonight is the economics of quality is from a consumer, what, at least, when my wife and I buy Toyota, it's a value proposition. It's the idea that if we buy Toyota, in our experience, we're getting a car that doesn't break down as often, is far more reliable. That becomes the differentiation. Also in the first... In the second series, second podcast of this series, we talked about the eight dimensions of quality and David Garvin's work.   0:25:03.2 Bill Bellows: And one of them was features, that a car with cup holders is quality 'cause... And there was a time, and the more cup holders, the better. And that was... And Garvin was saying lots of features is quality. He said, reliability could perceived it as a dimension of quality. Conformance was one of the dimensions, and he attributed that to the traditional thinking of Crosby. Reliability is a thing. And so when it comes to, how do you sell quality today? How do you get people within your organizations to go beyond, 'cause what I see right now is it's almost as if quality has gone back to quantity, that it's gone, that it's lost its appeal. Now, quantity doesn't lose its appeal 'cause we're selling, five of them, 20 of them, 30 of them.   0:26:09.2 Bill Bellows: But I don't get the impression from students and others that I interact with, that quality has big appeal. But, if we convert quality to the ability to do more with less, I mean the, when I'm delivering a higher quality item to you within the organization, that it's easier for you to integrate, to do something with, that's money, that's savings of time. And the question is, well, I guess how can we help make people more aware that when you go through the door of good and go beyond looking good and start to think about opportunities for desirable? And again, what we've said in the past is there's nothing wrong with tools, nothing wrong with the techniques to use them, there's nothing wrong with acceptability, but desirability is a differentiator.   0:27:15.2 Bill Bellows: And then the challenge becomes, if everyone's focused on acceptability, where it makes sense, then within your organization going beyond that, as we've explained, and this is where Dr. Taguchi's work is very critical. Dr. Deming learned about desirability from Dr. Taguchi in 1960. And that's what I think is, for all this interest in Toyota, I guess my question is, why is everybody excited by Toyota? Is it because they do single-minute exchange of dies? I don't think so. Is it because they do mixed model production? They can have, in one production line have a red car followed by a blue car, followed by a green car as opposed to mass production? Or is it because of the incredible reliability of the product? That's my answer, and I'm sticking to it. So...   0:28:14.3 Andrew Stotz: Yeah.   0:28:14.7 Bill Bellows: So what do you think Andrew?   0:28:17.2 Andrew Stotz: Yeah. There's two things that I was thinking about. One of the things I was thinking about is the idea if we're doing good with quality, and maybe we're satisfied with good, I was thinking about the book 'Good to Great,' and like how do you make this breakthrough? And then I was maybe it's good to groundbreaking or good to amazing or whatever. But like, when you really go beyond specification limits and take it to the next level, it's like you're moving from good to great. And one of the things that I see a lot is that, and I talk a lot in my corporate strategy courses with my clients and with my students is this idea that Deming really hit home about, about focusing on your customer, not your competitor.   0:29:06.6 Andrew Stotz: And I just feel like humans have a need to classify everything, to name everything, to label everything. And once they've got that label, that's the specification. That's what we want, they will fixate on that. And whether, I think, you think about all the kids that come out of the out of some meeting with a doctor and say, oh, I'm ADHD. Okay, we got a label now that's good and bad. And so that's where I think it, when I thought about the specification limits limit improvement, I think that, specification to me, when I think about quality, I think about setting a standard, moving to a, a new standard, and then maintaining that standard. And I can see the purpose of limits and controls and trying to understand how do we maintain that. But if we only stay on maintaining that and never move beyond that, then are we really, are we really in pursuit of quality?   0:30:12.0 Andrew Stotz: Now, on the other hand, when I think about the customers of my coffee factory, CoffeeWORKS and they want the exact same experience every single morning. Now, if we can make tests and do PDSAs to improve how we're doing that, less resources, better inputs and all that, great, but they do not want a difference. And I was just thinking about it also in relation to my evaluation masterclass bootcamp, where I still have a lot of variation coming out at the end of the bootcamp. Now, in the beginning, this is bootcamp number 19. So I've done this a lot. In the beginning, man, I would have, someone really terrible and someone really great, and I wasn't satisfied. So I kept trying to improve the content, the process, the feedback to make sure that by the time they get to the end, but I was just frustrated yesterday thinking there's still a lot of variation that, and I'm not talking about, the variation of a personality or something.   0:31:15.2 Andrew Stotz: I'm just talking about the variation of understanding and implementing what they're learning. And then I was thinking as I was at the park running this morning, I was thinking like, what makes Toyota so great is that there is very little variation of the 10 million cars that they've produced last year. And how impressive that is when all I'm trying to do is do it in a small little course. So I don't know, those are some things that were coming into my head when I thought about what you're talking about.   0:31:44.6 Bill Bellows: But no, you're right, in terms of the coffee, and I think you brought up a couple of good points. One is when the customer wants that flavor, whatever that level is, now, but that, I don't know how, anything about measuring taste, but there could be, within the range, within that, when they say they want that flavor, I mean, that could still have, could be a pretty broad spectrum. So maybe there's the ability to make it more consistent within that, if that's possible.   0:32:27.8 Andrew Stotz: Yeah, I think that, I think, like we have a blend we call Hunter's Brew, and I drink that every single morning and I can say, yeah, there's a variation, but it's a small enough variation that it doesn't bother me at all. And I think it doesn't bother our customer. Could we get more conformity to that? Yes, I think we could reduce that. Is it worth it? That's another question. We're looking at some automated equipment, some automated roasting equipment that would bring automation that would allow us to reduce that variation a bit. Will the customer notice that or not? Maybe. But the customer will definitely notice if we're outside of specification limits or if it's burnt...   0:33:12.7 Bill Bellows: Yes.   0:33:13.5 Andrew Stotz: As an example, and we're still shipping it, you know, they'll definitely notice that. And we have our mechanisms to try to measure that so that we are within those limits. So I do see, I see that the function of that to me is like, okay, in fact, in any business, you're constantly chasing and putting out fires. I mean, there's always things going on in every business owner's situation.   0:33:38.6 Bill Bellows: Right.   0:33:39.9 Andrew Stotz: And so there's at points where it's like, okay, can you just keep that in specification limit for right now while I get over to here and fix how we're gonna make sure that this is at another level where that is, I would consider it kind of an improvement versus maintaining. But I don't know, I'm just, I'm riffing here, but those are some things in my head.   0:34:00.0 Bill Bellows: No, what I hear you talking about is if we shift from quality management to, I mean, what desirability is about is looking at things as a system. Acceptability is about looking at things in isolation and saying, this is good, this is good, this is good, this is good. Not necessarily with a lot of focus of how is that used. So if we move away from quality and really what we're talking about is a better way to run an organization with a sense of connectedness that we're, we can talk about working together. Well, it's hard to work together if the fundamental mindset is: here, Andrew, my part is good and I wash my hands of it. When you come back and say, well, Bill, I'm having trouble integrating it, that's more like working separately.   0:35:07.2 Bill Bellows: So if we shift the focus from quality, which could be really narrow, it could be an entry point, but I think if we step back, I mean the title of Dr. Deming's last book was 'The New Economics,' the idea which has to be, which to me, which is about a resource. The better we manage the organization as a system, the more we can do with less. And relative to the quality of the taste and yeah, the customers want this and maybe we can make that even more consistent simultaneously. Can we use control charts to see special causes before they get too far downstream that allows us to maintain that consistency? That'd be nice. Then can we figure out ways to expand our capacity as we gain more? So there's a whole lot to do. So the organization is not static. And simultaneously the challenge becomes how do we stay ahead of others who might be trying to do the same thing? Dr. Deming would say, be thankful for a good competitor. Are we just gonna sit there and say, oh, we're the only coffee... We're the only ones in house that know how to do this. What is our differentiator? And I think having a workforce that thinks in terms of how the activities are connected, that are constantly involved in improvement activities.   0:36:45.1 Bill Bellows: Short of that, what you're hoping is that no one comes along in... Remember the book, it was required reading within Boeing, sadly, 'Who Moved My Cheese?'   0:36:58.2 Andrew Stotz: It was required reading at Pepsi when I was there, and I hated that book. We had another one called 'The Game of Work,' which I just was so annoyed with, but that 'Who Moved My Cheese?' I never, never really enjoyed that at all.   0:37:07.0 Bill Bellows: We used to laugh about, within Rocketdyne 'cause, and for those who aren't aware of the book, the storyline is that there's a bunch of mice and they're living in their little cubby holes and every day they go through the mouse hole, try to avoid the cat, find the cheese, bring the cheese back into their cubby hole, and that life is good. And then one day, somebody steals the cheese, moves the cheese and one's kind of frantic and the other's like, oh, not to worry, Andrew, I'm sure it was taken by a nice person and I'm sure they'll return it. So I wouldn't lose sleep over that. That's okay. That's okay. And then kind of the moral was another company is stealing your cheese and you're sitting there thinking everything's okay, and next thing you know, you're outta business because you weren't paying attention. And so the, and it was, this is written for adults with cartoons of cheese. That's how you appeal... That's how...   0:38:15.9 Andrew Stotz: Yeah. So that's what got me annoyed about it because it felt like, just tell me what you're trying to tell me, okay. Instead of telling me this story. But yeah, it was a used to create the burning platform concept that was used... I know at Pepsi when I was there, they talked about the burning platform, the level of urgency, we're gonna get, and, and there's, I kind of understand where they were coming from with it, but yeah.   0:38:44.7 Bill Bellows: But what is interesting is nowhere in the book was a strategy to be the ones moving the cheese. What it was more like is don't be in an environment where somebody else moves the cheese. Don't be that company. And I thought, no, you wanna be the company that's moving the cheese. But that was, maybe that's an advanced book that hasn't come out yet.   [laughter]   0:39:08.6 Bill Bellows: But really...   0:39:10.5 Andrew Stotz: There's some work for you, Bill.   0:39:12.6 Bill Bellows: But, but that's what... I mean what Dr. Deming is talking about is having an environment where you have that capacity on an ongoing basis. First of all, you're not sitting back stopping at good, thinking that what you're doing is always acceptable. It's trying to do more with that. Anyway, that's what I wanted to explore today. Again, there's nothing wrong with specification limits. I told the gentleman that night, specification limits are provided to allow for variation, to allow for commerce, to allow for suppliers to provide things that meet requirements. Then the question becomes, is there value in doing something with a variation within the specification limits? Is there value in moving that variation around? And that's the desirability focus. That is what Ford realized Toyota was doing a lot, is that then improves the functionality of the resulting product, it improves its reliability. All of that is the possibility of going beyond meeting requirements. So it's not that we shouldn't have, we need specifications. Why? Because there's variation. And if we didn't allow for variation, we couldn't have commerce because we can't deliver exactly anything. So I just want, just for some...   0:40:34.9 Andrew Stotz: Okay, all right. That's a good one.   0:40:37.4 Bill Bellows: All right.   0:40:38.2 Andrew Stotz: And I'll wrap it up with a little humor.   0:40:40.4 Bill Bellows: Go ahead.   0:40:40.5 Andrew Stotz: There were some parody books that came out, in relation to 'Who Moved My Cheese.' In 2002, the book 'Who Cut the Cheese' by Stilton Jarlsberg, which was good. And in 2011 was, 'I Moved Your Cheese' by Deepak Malhotra. So there you go. A little humor for the day. Bill, on behalf of everybody at The Deming Institute, I want to thank you again for this discussion. And for listeners, remember to go to deming.org to continue your journey. And if you want to keep in touch with Bill, just find him on LinkedIn. He responds. This is your host, Andrew Stotz, and I'll leave you with one of my favorite quotes from Dr. Deming. I just love this quote. I think about it all the time. "People are entitled to joy in work."  

Jenn Morris from Ship Happens joins us to analyse the opportunities for postal operators in food delivery. Understanding the current food distribution network set-up Opportunities in semi-perishable food delivery Refrigerated and temperature-controlled transport Food products already being distributed via the post Temperature ranges and compatibility in transport The direct-to-consumer opportunity Specifications for shipping food items Practicalities of food delivery. including doorstep delivery, temperature monitoring Sailing schedules for food pickup and delivery, and implications for pricing Optimising space in refrigerated vehicles Setting up a pilot programme for food delivery First steps for a post setting up food delivery concept  

This is a special episode, where I introduce the "Big Agile Questions" survey and review some of the questions that you've already submitted! Thank you all who did! You can find the submission form here. Submit your questions, as we will be reviewing these in future episodes! To join 25,341 other Agilists on our Newsletter (˜1 post/week), visit this page, and join. The Power of Asking Better Questions At every major turning point in history, from the Renaissance to the Industrial Revolution, progress has begun with asking better questions. The Agile movement itself started with the authors of the Agile Manifesto questioning traditional software development methods. Now, in 2025, with significant changes in the industry including PMI's acquisition of the Agile Alliance, the community faces a crucial moment to shape its future direction through thoughtful inquiry and reflection. "Throughout history, the biggest leaps forward have come from people willing to ask difficult, sometimes even quite challenging, questions." The Future Beyond Agile

Radio is a powerful example of why being different doesn't mean being wrong—and how society often struggles with that distinction. Based on a true story, the film follows the relationship between high school football coach Harold Jones (played by Ed Harris) and a young man with an intellectual disability, James Robert “Radio” Kennedy (played by Cuba Gooding Jr.). Initially an outcast in the community, Radio is taken under Coach Jones's wing, gradually becoming a beloved figure at the school. The film ultimately teaches that just because someone doesn't fit traditional expectations doesn't mean they're wrong or less than. True strength lies in compassion, and real leadership is about lifting others up rather than shutting them out. Radio encourages us to rethink our biases and embrace people for who they are, not just for how they compare to societal norms.   Takeaways: Education should be student focussed Everyone should have a chance to learn One person can change a community     About Meredith Watassek: Meredith Watassek joined Stantec as an Education Planner after more than 24 years in Education. The last nine years of her career as an educator, she served as Director of Career and Technical Education (CTE) for the sixth largest school district in Texas. Meredith has guided dozens of Stantec clients through the engagement process on projects while simultaneously leading planning and specifications development for future academic spaces. Several of her most recent projects include School Master Planning for Alvin Community College, visioning and design of the Career and Technical Education Center for Lamar CISD, and School Master Planning and Specifications for Salteaux First Nations in Saskatchewan, Canada. Before joining Stantec, Meredith oversaw Stantec's design and execution of the James Reese Career and Technical Education Center for Fort Bend Independent School District in Sugar Land, TX, defining program and project scope for the new facility. With a rich background in CTE, Meredith can communicate with educators in a way that architects cannot; because she's been in their shoes, at the front of a classroom, managing both success factors and the student experience. She believes that learning environments shape a student's experience, even if just passively. It is inside schools that students develop beliefs about their ability to be successful. For this reason, Meredith maintains that designers, planners, architects, and contractors have a responsibility to provide the most nurturing environment possible for students.     Connect with Meredith Watassek: LinkedIn: https://www.linkedin.com/in/watassek-meredith-a561b23a/ Twitter: https://x.com/MWatassek   Connect with co-host, Carla Cummins: LinkedIn: https://www.linkedin.com/in/carla-cummins-01449659/   Connect with host, Kevin Stoller: LinkedIn: https://www.linkedin.com/in/kevinstoller/     Episode 219 of the Better Learning Podcast Kevin Stoller is the host of the Better Learning Podcast and Co-Founder of Kay-Twelve, a national leader for educational furniture. Learn more about creating better learning environments at www.Kay-Twelve.com.     For more information on our partners: Association for Learning Environments (A4LE) - https://www.a4le.org/ Education Leaders' Organization - https://www.ed-leaders.org/ Second Class Foundation - https://secondclassfoundation.org/ EDmarket - https://www.edmarket.org/ Catapult @ Penn GSE - https://catapult.gse.upenn.edu/ Want to be a Guest Speaker? Request on our website

If you're in SF, join us tomorrow for a fun meetup at CodeGen Night!If you're in NYC, join us for AI Engineer Summit! The Agent Engineering track is now sold out, but 25 tickets remain for AI Leadership and 5 tickets for the workshops. You can see the full schedule of speakers and workshops at https://ai.engineer!It's exceedingly hard to introduce someone like Bret Taylor. We could recite his Wikipedia page, or his extensive work history through Silicon Valley's greatest companies, but everyone else already does that.As a podcast by AI engineers for AI engineers, we had the opportunity to do something a little different. We wanted to dig into what Bret sees from his vantage point at the top of our industry for the last 2 decades, and how that explains the rise of the AI Architect at Sierra, the leading conversational AI/CX platform.“Across our customer base, we are seeing a new role emerge - the role of the AI architect. These leaders are responsible for helping define, manage and evolve their company's AI agent over time. They come from a variety of both technical and business backgrounds, and we think that every company will have one or many AI architects managing their AI agent and related experience.”In our conversation, Bret Taylor confirms the Paul Buchheit legend that he rewrote Google Maps in a weekend, armed with only the help of a then-nascent Google Closure Compiler and no other modern tooling. But what we find remarkable is that he was the PM of Maps, not an engineer, though of course he still identifies as one. We find this theme recurring throughout Bret's career and worldview. We think it is plain as day that AI leadership will have to be hands-on and technical, especially when the ground is shifting as quickly as it is today:“There's a lot of power in combining product and engineering into as few people as possible… few great things have been created by committee.”“If engineering is an order taking organization for product you can sometimes make meaningful things, but rarely will you create extremely well crafted breakthrough products. Those tend to be small teams who deeply understand the customer need that they're solving, who have a maniacal focus on outcomes.”“And I think the reason why is if you look at like software as a service five years ago, maybe you can have a separation of product and engineering because most software as a service created five years ago. I wouldn't say there's like a lot of technological breakthroughs required for most business applications. And if you're making expense reporting software or whatever, it's useful… You kind of know how databases work, how to build auto scaling with your AWS cluster, whatever, you know, it's just, you're just applying best practices to yet another problem. "When you have areas like the early days of mobile development or the early days of interactive web applications, which I think Google Maps and Gmail represent, or now AI agents, you're in this constant conversation with what the requirements of your customers and stakeholders are and all the different people interacting with it and the capabilities of the technology. And it's almost impossible to specify the requirements of a product when you're not sure of the limitations of the technology itself.”This is the first time the difference between technical leadership for “normal” software and for “AI” software was articulated this clearly for us, and we'll be thinking a lot about this going forward. We left a lot of nuggets in the conversation, so we hope you'll just dive in with us (and thank Bret for joining the pod!)Timestamps* 00:00:02 Introductions and Bret Taylor's background* 00:01:23 Bret's experience at Stanford and the dot-com era* 00:04:04 The story of rewriting Google Maps backend* 00:11:06 Early days of interactive web applications at Google* 00:15:26 Discussion on product management and engineering roles* 00:21:00 AI and the future of software development* 00:26:42 Bret's approach to identifying customer needs and building AI companies* 00:32:09 The evolution of business models in the AI era* 00:41:00 The future of programming languages and software development* 00:49:38 Challenges in precisely communicating human intent to machines* 00:56:44 Discussion on Artificial General Intelligence (AGI) and its impact* 01:08:51 The future of agent-to-agent communication* 01:14:03 Bret's involvement in the OpenAI leadership crisis* 01:22:11 OpenAI's relationship with Microsoft* 01:23:23 OpenAI's mission and priorities* 01:27:40 Bret's guiding principles for career choices* 01:29:12 Brief discussion on pasta-making* 01:30:47 How Bret keeps up with AI developments* 01:32:15 Exciting research directions in AI* 01:35:19 Closing remarks and hiring at Sierra Transcript[00:02:05] Introduction and Guest Welcome[00:02:05] Alessio: Hey everyone, welcome to the Latent Space Podcast. This is Alessio, partner and CTO at Decibel Partners, and I'm joined by my co host swyx, founder of smol.ai.[00:02:17] swyx: Hey, and today we're super excited to have Bret Taylor join us. Welcome. Thanks for having me. It's a little unreal to have you in the studio.[00:02:25] swyx: I've read about you so much over the years, like even before. Open AI effectively. I mean, I use Google Maps to get here. So like, thank you for everything that you've done. Like, like your story history, like, you know, I think people can find out what your greatest hits have been.[00:02:40] Bret Taylor's Early Career and Education[00:02:40] swyx: How do you usually like to introduce yourself when, you know, you talk about, you summarize your career, like, how do you look at yourself?[00:02:47] Bret: Yeah, it's a great question. You know, we, before we went on the mics here, we're talking about the audience for this podcast being more engineering. And I do think depending on the audience, I'll introduce myself differently because I've had a lot of [00:03:00] corporate and board roles. I probably self identify as an engineer more than anything else though.[00:03:04] Bret: So even when I was. Salesforce, I was coding on the weekends. So I think of myself as an engineer and then all the roles that I do in my career sort of start with that just because I do feel like engineering is sort of a mindset and how I approach most of my life. So I'm an engineer first and that's how I describe myself.[00:03:24] Bret: You majored in computer[00:03:25] swyx: science, like 1998. And, and I was high[00:03:28] Bret: school, actually my, my college degree was Oh, two undergrad. Oh, three masters. Right. That old.[00:03:33] swyx: Yeah. I mean, no, I was going, I was going like 1998 to 2003, but like engineering wasn't as, wasn't a thing back then. Like we didn't have the title of senior engineer, you know, kind of like, it was just.[00:03:44] swyx: You were a programmer, you were a developer, maybe. What was it like in Stanford? Like, what was that feeling like? You know, was it, were you feeling like on the cusp of a great computer revolution? Or was it just like a niche, you know, interest at the time?[00:03:57] Stanford and the Dot-Com Bubble[00:03:57] Bret: Well, I was at Stanford, as you said, from 1998 to [00:04:00] 2002.[00:04:02] Bret: 1998 was near the peak of the dot com bubble. So. This is back in the day where most people that they're coding in the computer lab, just because there was these sun microsystems, Unix boxes there that most of us had to do our assignments on. And every single day there was a. com like buying pizza for everybody.[00:04:20] Bret: I didn't have to like, I got. Free food, like my first two years of university and then the dot com bubble burst in the middle of my college career. And so by the end there was like tumbleweed going to the job fair, you know, it was like, cause it was hard to describe unless you were there at the time, the like level of hype and being a computer science major at Stanford was like, A thousand opportunities.[00:04:45] Bret: And then, and then when I left, it was like Microsoft, IBM.[00:04:49] Joining Google and Early Projects[00:04:49] Bret: And then the two startups that I applied to were VMware and Google. And I ended up going to Google in large part because a woman named Marissa Meyer, who had been a teaching [00:05:00] assistant when I was, what was called a section leader, which was like a junior teaching assistant kind of for one of the big interest.[00:05:05] Bret: Yes. Classes. She had gone there. And she was recruiting me and I knew her and it was sort of felt safe, you know, like, I don't know. I thought about it much, but it turned out to be a real blessing. I realized like, you know, you always want to think you'd pick Google if given the option, but no one knew at the time.[00:05:20] Bret: And I wonder if I'd graduated in like 1999 where I've been like, mom, I just got a job at pets. com. It's good. But you know, at the end I just didn't have any options. So I was like, do I want to go like make kernel software at VMware? Do I want to go build search at Google? And I chose Google. 50, 50 ball.[00:05:36] Bret: I'm not really a 50, 50 ball. So I feel very fortunate in retrospect that the economy collapsed because in some ways it forced me into like one of the greatest companies of all time, but I kind of lucked into it, I think.[00:05:47] The Google Maps Rewrite Story[00:05:47] Alessio: So the famous story about Google is that you rewrote the Google maps back in, in one week after the map quest quest maps acquisition, what was the story there?[00:05:57] Alessio: Is it. Actually true. Is it [00:06:00] being glorified? Like how, how did that come to be? And is there any detail that maybe Paul hasn't shared before?[00:06:06] Bret: It's largely true, but I'll give the color commentary. So it was actually the front end, not the back end, but it turns out for Google maps, the front end was sort of the hard part just because Google maps was.[00:06:17] Bret: Largely the first ish kind of really interactive web application, say first ish. I think Gmail certainly was though Gmail, probably a lot of people then who weren't engineers probably didn't appreciate its level of interactivity. It was just fast, but. Google maps, because you could drag the map and it was sort of graphical.[00:06:38] Bret: My, it really in the mainstream, I think, was it a map[00:06:41] swyx: quest back then that was, you had the arrows up and down, it[00:06:44] Bret: was up and down arrows. Each map was a single image and you just click left and then wait for a few seconds to the new map to let it was really small too, because generating a big image was kind of expensive on computers that day.[00:06:57] Bret: So Google maps was truly innovative in that [00:07:00] regard. The story on it. There was a small company called where two technologies started by two Danish brothers, Lars and Jens Rasmussen, who are two of my closest friends now. They had made a windows app called expedition, which had beautiful maps. Even in 2000.[00:07:18] Bret: For whenever we acquired or sort of acquired their company, Windows software was not particularly fashionable, but they were really passionate about mapping and we had made a local search product that was kind of middling in terms of popularity, sort of like a yellow page of search product. So we wanted to really go into mapping.[00:07:36] Bret: We'd started working on it. Their small team seemed passionate about it. So we're like, come join us. We can build this together.[00:07:42] Technical Challenges and Innovations[00:07:42] Bret: It turned out to be a great blessing that they had built a windows app because you're less technically constrained when you're doing native code than you are building a web browser, particularly back then when there weren't really interactive web apps and it ended up.[00:07:56] Bret: Changing the level of quality that we [00:08:00] wanted to hit with the app because we were shooting for something that felt like a native windows application. So it was a really good fortune that we sort of, you know, their unusual technical choices turned out to be the greatest blessing. So we spent a lot of time basically saying, how can you make a interactive draggable map in a web browser?[00:08:18] Bret: How do you progressively load, you know, new map tiles, you know, as you're dragging even things like down in the weeds of the browser at the time, most browsers like Internet Explorer, which was dominant at the time would only load two images at a time from the same domain. So we ended up making our map tile servers have like.[00:08:37] Bret: Forty different subdomains so we could load maps and parallels like lots of hacks. I'm happy to go into as much as like[00:08:44] swyx: HTTP connections and stuff.[00:08:46] Bret: They just like, there was just maximum parallelism of two. And so if you had a map, set of map tiles, like eight of them, so So we just, we were down in the weeds of the browser anyway.[00:08:56] Bret: So it was lots of plumbing. I can, I know a lot more about browsers than [00:09:00] most people, but then by the end of it, it was fairly, it was a lot of duct tape on that code. If you've ever done an engineering project where you're not really sure the path from point A to point B, it's almost like. Building a house by building one room at a time.[00:09:14] Bret: The, there's not a lot of architectural cohesion at the end. And then we acquired a company called Keyhole, which became Google earth, which was like that three, it was a native windows app as well, separate app, great app, but with that, we got licenses to all this satellite imagery. And so in August of 2005, we added.[00:09:33] Bret: Satellite imagery to Google Maps, which added even more complexity in the code base. And then we decided we wanted to support Safari. There was no mobile phones yet. So Safari was this like nascent browser on, on the Mac. And it turns out there's like a lot of decisions behind the scenes, sort of inspired by this windows app, like heavy use of XML and XSLT and all these like.[00:09:54] Bret: Technologies that were like briefly fashionable in the early two thousands and everyone hates now for good [00:10:00] reason. And it turns out that all of the XML functionality and Internet Explorer wasn't supporting Safari. So people are like re implementing like XML parsers. And it was just like this like pile of s**t.[00:10:11] Bret: And I had to say a s**t on your part. Yeah, of[00:10:12] Alessio: course.[00:10:13] Bret: So. It went from this like beautifully elegant application that everyone was proud of to something that probably had hundreds of K of JavaScript, which sounds like nothing. Now we're talking like people have modems, you know, not all modems, but it was a big deal.[00:10:29] Bret: So it was like slow. It took a while to load and just, it wasn't like a great code base. Like everything was fragile. So I just got. Super frustrated by it. And then one weekend I did rewrite all of it. And at the time the word JSON hadn't been coined yet too, just to give you a sense. So it's all XML.[00:10:47] swyx: Yeah.[00:10:47] Bret: So we used what is now you would call JSON, but I just said like, let's use eval so that we can parse the data fast. And, and again, that's, it would literally as JSON, but at the time there was no name for it. So we [00:11:00] just said, let's. Pass on JavaScript from the server and eval it. And then somebody just refactored the whole thing.[00:11:05] Bret: And, and it wasn't like I was some genius. It was just like, you know, if you knew everything you wished you had known at the beginning and I knew all the functionality, cause I was the primary, one of the primary authors of the JavaScript. And I just like, I just drank a lot of coffee and just stayed up all weekend.[00:11:22] Bret: And then I, I guess I developed a bit of reputation and no one knew about this for a long time. And then Paul who created Gmail and I ended up starting a company with him too, after all of this told this on a podcast and now it's large, but it's largely true. I did rewrite it and it, my proudest thing.[00:11:38] Bret: And I think JavaScript people appreciate this. Like the un G zipped bundle size for all of Google maps. When I rewrote, it was 20 K G zipped. It was like much smaller for the entire application. It went down by like 10 X. So. What happened on Google? Google is a pretty mainstream company. And so like our usage is shot up because it turns out like it's faster.[00:11:57] Bret: Just being faster is worth a lot of [00:12:00] percentage points of growth at a scale of Google. So how[00:12:03] swyx: much modern tooling did you have? Like test suites no compilers.[00:12:07] Bret: Actually, that's not true. We did it one thing. So I actually think Google, I, you can. Download it. There's a, Google has a closure compiler, a closure compiler.[00:12:15] Bret: I don't know if anyone still uses it. It's gone. Yeah. Yeah. It's sort of gone out of favor. Yeah. Well, even until recently it was better than most JavaScript minifiers because it was more like it did a lot more renaming of variables and things. Most people use ES build now just cause it's fast and closure compilers built on Java and super slow and stuff like that.[00:12:37] Bret: But, so we did have that, that was it. Okay.[00:12:39] The Evolution of Web Applications[00:12:39] Bret: So and that was treated internally, you know, it was a really interesting time at Google at the time because there's a lot of teams working on fairly advanced JavaScript when no one was. So Google suggest, which Kevin Gibbs was the tech lead for, was the first kind of type ahead, autocomplete, I believe in a web browser, and now it's just pervasive in search boxes that you sort of [00:13:00] see a type ahead there.[00:13:01] Bret: I mean, chat, dbt[00:13:01] swyx: just added it. It's kind of like a round trip.[00:13:03] Bret: Totally. No, it's now pervasive as a UI affordance, but that was like Kevin's 20 percent project. And then Gmail, Paul you know, he tells the story better than anyone, but he's like, you know, basically was scratching his own itch, but what was really neat about it is email, because it's such a productivity tool, just needed to be faster.[00:13:21] Bret: So, you know, he was scratching his own itch of just making more stuff work on the client side. And then we, because of Lars and Yen sort of like setting the bar of this windows app or like we need our maps to be draggable. So we ended up. Not only innovate in terms of having a big sync, what would be called a single page application today, but also all the graphical stuff you know, we were crashing Firefox, like it was going out of style because, you know, when you make a document object model with the idea that it's a document and then you layer on some JavaScript and then we're essentially abusing all of this, it just was running into code paths that were not.[00:13:56] Bret: Well, it's rotten, you know, at this time. And so it was [00:14:00] super fun. And, and, you know, in the building you had, so you had compilers, people helping minify JavaScript just practically, but there is a great engineering team. So they were like, that's why Closure Compiler is so good. It was like a. Person who actually knew about programming languages doing it, not just, you know, writing regular expressions.[00:14:17] Bret: And then the team that is now the Chrome team believe, and I, I don't know this for a fact, but I'm pretty sure Google is the main contributor to Firefox for a long time in terms of code. And a lot of browser people were there. So every time we would crash Firefox, we'd like walk up two floors and say like, what the hell is going on here?[00:14:35] Bret: And they would load their browser, like in a debugger. And we could like figure out exactly what was breaking. And you can't change the code, right? Cause it's the browser. It's like slow, right? I mean, slow to update. So, but we could figure out exactly where the bug was and then work around it in our JavaScript.[00:14:52] Bret: So it was just like new territory. Like so super, super fun time, just like a lot of, a lot of great engineers figuring out [00:15:00] new things. And And now, you know, the word, this term is no longer in fashion, but the word Ajax, which was asynchronous JavaScript and XML cause I'm telling you XML, but see the word XML there, to be fair, the way you made HTTP requests from a client to server was this.[00:15:18] Bret: Object called XML HTTP request because Microsoft and making Outlook web access back in the day made this and it turns out to have nothing to do with XML. It's just a way of making HTTP requests because XML was like the fashionable thing. It was like that was the way you, you know, you did it. But the JSON came out of that, you know, and then a lot of the best practices around building JavaScript applications is pre React.[00:15:44] Bret: I think React was probably the big conceptual step forward that we needed. Even my first social network after Google, we used a lot of like HTML injection and. Making real time updates was still very hand coded and it's really neat when you [00:16:00] see conceptual breakthroughs like react because it's, I just love those things where it's like obvious once you see it, but it's so not obvious until you do.[00:16:07] Bret: And actually, well, I'm sure we'll get into AI, but I, I sort of feel like we'll go through that evolution with AI agents as well that I feel like we're missing a lot of the core abstractions that I think in 10 years we'll be like, gosh, how'd you make agents? Before that, you know, but it was kind of that early days of web applications.[00:16:22] swyx: There's a lot of contenders for the reactive jobs of of AI, but no clear winner yet. I would say one thing I was there for, I mean, there's so much we can go into there. You just covered so much.[00:16:32] Product Management and Engineering Synergy[00:16:32] swyx: One thing I just, I just observe is that I think the early Google days had this interesting mix of PM and engineer, which I think you are, you didn't, you didn't wait for PM to tell you these are my, this is my PRD.[00:16:42] swyx: This is my requirements.[00:16:44] mix: Oh,[00:16:44] Bret: okay.[00:16:45] swyx: I wasn't technically a software engineer. I mean,[00:16:48] Bret: by title, obviously. Right, right, right.[00:16:51] swyx: It's like a blend. And I feel like these days, product is its own discipline and its own lore and own industry and engineering is its own thing. And there's this process [00:17:00] that happens and they're kind of separated, but you don't produce as good of a product as if they were the same person.[00:17:06] swyx: And I'm curious, you know, if, if that, if that sort of resonates in, in, in terms of like comparing early Google versus modern startups that you see out there,[00:17:16] Bret: I certainly like wear a lot of hats. So, you know, sort of biased in this, but I really agree that there's a lot of power and combining product design engineering into as few people as possible because, you know few great things have been created by committee, you know, and so.[00:17:33] Bret: If engineering is an order taking organization for product you can sometimes make meaningful things, but rarely will you create extremely well crafted breakthrough products. Those tend to be small teams who deeply understand the customer need that they're solving, who have a. Maniacal focus on outcomes.[00:17:53] Bret: And I think the reason why it's, I think for some areas, if you look at like software as a service five years ago, maybe you can have a [00:18:00] separation of product and engineering because most software as a service created five years ago. I wouldn't say there's like a lot of like. Technological breakthroughs required for most, you know, business applications.[00:18:11] Bret: And if you're making expense reporting software or whatever, it's useful. I don't mean to be dismissive of expense reporting software, but you probably just want to understand like, what are the requirements of the finance department? What are the requirements of an individual file expense report? Okay.[00:18:25] Bret: Go implement that. And you kind of know how web applications are implemented. You kind of know how to. How databases work, how to build auto scaling with your AWS cluster, whatever, you know, it's just, you're just applying best practices to yet another problem when you have areas like the early days of mobile development or the early days of interactive web applications, which I think Google Maps and Gmail represent, or now AI agents, you're in this constant conversation with what the requirements of your customers and stakeholders are and all the different people interacting with it.[00:18:58] Bret: And the capabilities of the [00:19:00] technology. And it's almost impossible to specify the requirements of a product when you're not sure of the limitations of the technology itself. And that's why I use the word conversation. It's not literal. That's sort of funny to use that word in the age of conversational AI.[00:19:15] Bret: You're constantly sort of saying, like, ideally, you could sprinkle some magic AI pixie dust and solve all the world's problems, but it's not the way it works. And it turns out that actually, I'll just give an interesting example.[00:19:26] AI Agents and Modern Tooling[00:19:26] Bret: I think most people listening probably use co pilots to code like Cursor or Devon or Microsoft Copilot or whatever.[00:19:34] Bret: Most of those tools are, they're remarkable. I'm, I couldn't, you know, imagine development without them now, but they're not autonomous yet. Like I wouldn't let it just write most code without my interactively inspecting it. We just are somewhere between it's an amazing co pilot and it's an autonomous software engineer.[00:19:53] Bret: As a product manager, like your aspirations for what the product is are like kind of meaningful. But [00:20:00] if you're a product person, yeah, of course you'd say it should be autonomous. You should click a button and program should come out the other side. The requirements meaningless. Like what matters is like, what is based on the like very nuanced limitations of the technology.[00:20:14] Bret: What is it capable of? And then how do you maximize the leverage? It gives a software engineering team, given those very nuanced trade offs. Coupled with the fact that those nuanced trade offs are changing more rapidly than any technology in my memory, meaning every few months you'll have new models with new capabilities.[00:20:34] Bret: So how do you construct a product that can absorb those new capabilities as rapidly as possible as well? That requires such a combination of technical depth and understanding the customer that you really need more integration. Of product design and engineering. And so I think it's why with these big technology waves, I think startups have a bit of a leg up relative to incumbents because they [00:21:00] tend to be sort of more self actualized in terms of just like bringing those disciplines closer together.[00:21:06] Bret: And in particular, I think entrepreneurs, the proverbial full stack engineers, you know, have a leg up as well because. I think most breakthroughs happen when you have someone who can understand those extremely nuanced technical trade offs, have a vision for a product. And then in the process of building it, have that, as I said, like metaphorical conversation with the technology, right?[00:21:30] Bret: Gosh, I ran into a technical limit that I didn't expect. It's not just like changing that feature. You might need to refactor the whole product based on that. And I think that's, that it's particularly important right now. So I don't, you know, if you, if you're building a big ERP system, probably there's a great reason to have product and engineering.[00:21:51] Bret: I think in general, the disciplines are there for a reason. I think when you're dealing with something as nuanced as the like technologies, like large language models today, there's a ton of [00:22:00] advantage of having. Individuals or organizations that integrate the disciplines more formally.[00:22:05] Alessio: That makes a lot of sense.[00:22:06] Alessio: I've run a lot of engineering teams in the past, and I think the product versus engineering tension has always been more about effort than like whether or not the feature is buildable. But I think, yeah, today you see a lot more of like. Models actually cannot do that. And I think the most interesting thing is on the startup side, people don't yet know where a lot of the AI value is going to accrue.[00:22:26] Alessio: So you have this rush of people building frameworks, building infrastructure, layered things, but we don't really know the shape of the compute. I'm curious that Sierra, like how you thought about building an house, a lot of the tooling for evals or like just, you know, building the agents and all of that.[00:22:41] Alessio: Versus how you see some of the startup opportunities that is maybe still out there.[00:22:46] Bret: We build most of our tooling in house at Sierra, not all. It's, we don't, it's not like not invented here syndrome necessarily, though, maybe slightly guilty of that in some ways, but because we're trying to build a platform [00:23:00] that's in Dorian, you know, we really want to have control over our own destiny.[00:23:03] Bret: And you had made a comment earlier that like. We're still trying to figure out who like the reactive agents are and the jury is still out. I would argue it hasn't been created yet. I don't think the jury is still out to go use that metaphor. We're sort of in the jQuery era of agents, not the react era.[00:23:19] Bret: And, and that's like a throwback for people listening,[00:23:22] swyx: we shouldn't rush it. You know?[00:23:23] Bret: No, yeah, that's my point is. And so. Because we're trying to create an enduring company at Sierra that outlives us, you know, I'm not sure we want to like attach our cart to some like to a horse where it's not clear that like we've figured out and I actually want as a company, we're trying to enable just at a high level and I'll, I'll quickly go back to tech at Sierra, we help consumer brands build customer facing AI agents.[00:23:48] Bret: So. Everyone from Sonos to ADT home security to Sirius XM, you know, if you call them on the phone and AI will pick up with you, you know, chat with them on the Sirius XM homepage. It's an AI agent called Harmony [00:24:00] that they've built on our platform. We're what are the contours of what it means for someone to build an end to end complete customer experience with AI with conversational AI.[00:24:09] Bret: You know, we really want to dive into the deep end of, of all the trade offs to do it. You know, where do you use fine tuning? Where do you string models together? You know, where do you use reasoning? Where do you use generation? How do you use reasoning? How do you express the guardrails of an agentic process?[00:24:25] Bret: How do you impose determinism on a fundamentally non deterministic technology? There's just a lot of really like as an important design space. And I could sit here and tell you, we have the best approach. Every entrepreneur will, you know. But I hope that in two years, we look back at our platform and laugh at how naive we were, because that's the pace of change broadly.[00:24:45] Bret: If you talk about like the startup opportunities, I'm not wholly skeptical of tools companies, but I'm fairly skeptical. There's always an exception for every role, but I believe that certainly there's a big market for [00:25:00] frontier models, but largely for companies with huge CapEx budgets. So. Open AI and Microsoft's Anthropic and Amazon Web Services, Google Cloud XAI, which is very well capitalized now, but I think the, the idea that a company can make money sort of pre training a foundation model is probably not true.[00:25:20] Bret: It's hard to, you're competing with just, you know, unreasonably large CapEx budgets. And I just like the cloud infrastructure market, I think will be largely there. I also really believe in the applications of AI. And I define that not as like building agents or things like that. I define it much more as like, you're actually solving a problem for a business.[00:25:40] Bret: So it's what Harvey is doing in legal profession or what cursor is doing for software engineering or what we're doing for customer experience and customer service. The reason I believe in that is I do think that in the age of AI, what's really interesting about software is it can actually complete a task.[00:25:56] Bret: It can actually do a job, which is very different than the value proposition of [00:26:00] software was to ancient history two years ago. And as a consequence, I think the way you build a solution and For a domain is very different than you would have before, which means that it's not obvious, like the incumbent incumbents have like a leg up, you know, necessarily, they certainly have some advantages, but there's just such a different form factor, you know, for providing a solution and it's just really valuable.[00:26:23] Bret: You know, it's. Like just think of how much money cursor is saving software engineering teams or the alternative, how much revenue it can produce tool making is really challenging. If you look at the cloud market, just as a analog, there are a lot of like interesting tools, companies, you know, Confluent, Monetized Kafka, Snowflake, Hortonworks, you know, there's a, there's a bunch of them.[00:26:48] Bret: A lot of them, you know, have that mix of sort of like like confluence or have the open source or open core or whatever you call it. I, I, I'm not an expert in this area. You know, I do think [00:27:00] that developers are fickle. I think that in the tool space, I probably like. Default towards open source being like the area that will win.[00:27:09] Bret: It's hard to build a company around this and then you end up with companies sort of built around open source to that can work. Don't get me wrong, but I just think that it's nowadays the tools are changing so rapidly that I'm like, not totally skeptical of tool makers, but I just think that open source will broadly win, but I think that the CapEx required for building frontier models is such that it will go to a handful of big companies.[00:27:33] Bret: And then I really believe in agents for specific domains which I think will, it's sort of the analog to software as a service in this new era. You know, it's like, if you just think of the cloud. You can lease a server. It's just a low level primitive, or you can buy an app like you know, Shopify or whatever.[00:27:51] Bret: And most people building a storefront would prefer Shopify over hand rolling their e commerce storefront. I think the same thing will be true of AI. So [00:28:00] I've. I tend to like, if I have a, like an entrepreneur asked me for advice, I'm like, you know, move up the stack as far as you can towards a customer need.[00:28:09] Bret: Broadly, but I, but it doesn't reduce my excitement about what is the reactive building agents kind of thing, just because it is, it is the right question to ask, but I think we'll probably play out probably an open source space more than anything else.[00:28:21] swyx: Yeah, and it's not a priority for you. There's a lot in there.[00:28:24] swyx: I'm kind of curious about your idea maze towards, there are many customer needs. You happen to identify customer experience as yours, but it could equally have been coding assistance or whatever. I think for some, I'm just kind of curious at the top down, how do you look at the world in terms of the potential problem space?[00:28:44] swyx: Because there are many people out there who are very smart and pick the wrong problem.[00:28:47] Bret: Yeah, that's a great question.[00:28:48] Future of Software Development[00:28:48] Bret: By the way, I would love to talk about the future of software, too, because despite the fact it didn't pick coding, I have a lot of that, but I can talk to I can answer your question, though, you know I think when a technology is as [00:29:00] cool as large language models.[00:29:02] Bret: You just see a lot of people starting from the technology and searching for a problem to solve. And I think it's why you see a lot of tools companies, because as a software engineer, you start building an app or a demo and you, you encounter some pain points. You're like,[00:29:17] swyx: a lot of[00:29:17] Bret: people are experiencing the same pain point.[00:29:19] Bret: What if I make it? That it's just very incremental. And you know, I always like to use the metaphor, like you can sell coffee beans, roasted coffee beans. You can add some value. You took coffee beans and you roasted them and roasted coffee beans largely, you know, are priced relative to the cost of the beans.[00:29:39] Bret: Or you can sell a latte and a latte. Is rarely priced directly like as a percentage of coffee bean prices. In fact, if you buy a latte at the airport, it's a captive audience. So it's a really expensive latte. And there's just a lot that goes into like. How much does a latte cost? And I bring it up because there's a supply chain from growing [00:30:00] coffee beans to roasting coffee beans to like, you know, you could make one at home or you could be in the airport and buy one and the margins of the company selling lattes in the airport is a lot higher than the, you know, people roasting the coffee beans and it's because you've actually solved a much more acute human problem in the airport.[00:30:19] Bret: And, and it's just worth a lot more to that person in that moment. It's kind of the way I think about technology too. It sounds funny to liken it to coffee beans, but you're selling tools on top of a large language model yet in some ways your market is big, but you're probably going to like be price compressed just because you're sort of a piece of infrastructure and then you have open source and all these other things competing with you naturally.[00:30:43] Bret: If you go and solve a really big business problem for somebody, that's actually like a meaningful business problem that AI facilitates, they will value it according to the value of that business problem. And so I actually feel like people should just stop. You're like, no, that's, that's [00:31:00] unfair. If you're searching for an idea of people, I, I love people trying things, even if, I mean, most of the, a lot of the greatest ideas have been things no one believed in.[00:31:07] Bret: So I like, if you're passionate about something, go do it. Like who am I to say, yeah, a hundred percent. Or Gmail, like Paul as far, I mean I, some of it's Laura at this point, but like Gmail is Paul's own email for a long time. , and then I amusingly and Paul can't correct me, I'm pretty sure he sent her in a link and like the first comment was like, this is really neat.[00:31:26] Bret: It would be great. It was not your email, but my own . I don't know if it's a true story. I'm pretty sure it's, yeah, I've read that before. So scratch your own niche. Fine. Like it depends on what your goal is. If you wanna do like a venture backed company, if its a. Passion project, f*****g passion, do it like don't listen to anybody.[00:31:41] Bret: In fact, but if you're trying to start, you know an enduring company, solve an important business problem. And I, and I do think that in the world of agents, the software industries has shifted where you're not just helping people more. People be more productive, but you're actually accomplishing tasks autonomously.[00:31:58] Bret: And as a consequence, I think the [00:32:00] addressable market has just greatly expanded just because software can actually do things now and actually accomplish tasks and how much is coding autocomplete worth. A fair amount. How much is the eventual, I'm certain we'll have it, the software agent that actually writes the code and delivers it to you, that's worth a lot.[00:32:20] Bret: And so, you know, I would just maybe look up from the large language models and start thinking about the economy and, you know, think from first principles. I don't wanna get too far afield, but just think about which parts of the economy. We'll benefit most from this intelligence and which parts can absorb it most easily.[00:32:38] Bret: And what would an agent in this space look like? Who's the customer of it is the technology feasible. And I would just start with these business problems more. And I think, you know, the best companies tend to have great engineers who happen to have great insight into a market. And it's that last part that I think some people.[00:32:56] Bret: Whether or not they have, it's like people start so much in the technology, they [00:33:00] lose the forest for the trees a little bit.[00:33:02] Alessio: How do you think about the model of still selling some sort of software versus selling more package labor? I feel like when people are selling the package labor, it's almost more stateless, you know, like it's easier to swap out if you're just putting an input and getting an output.[00:33:16] Alessio: If you think about coding, if there's no ID, you're just putting a prompt and getting back an app. It doesn't really matter. Who generates the app, you know, you have less of a buy in versus the platform you're building, I'm sure on the backend customers have to like put on their documentation and they have, you know, different workflows that they can tie in what's kind of like the line to draw there versus like going full where you're managed customer support team as a service outsource versus.[00:33:40] Alessio: This is the Sierra platform that you can build on. What was that decision? I'll sort of[00:33:44] Bret: like decouple the question in some ways, which is when you have something that's an agent, who is the person using it and what do they want to do with it? So let's just take your coding agent for a second. I will talk about Sierra as well.[00:33:59] Bret: Who's the [00:34:00] customer of a, an agent that actually produces software? Is it a software engineering manager? Is it a software engineer? And it's there, you know, intern so to speak. I don't know. I mean, we'll figure this out over the next few years. Like what is that? And is it generating code that you then review?[00:34:16] Bret: Is it generating code with a set of unit tests that pass, what is the actual. For lack of a better word contract, like, how do you know that it did what you wanted it to do? And then I would say like the product and the pricing, the packaging model sort of emerged from that. And I don't think the world's figured out.[00:34:33] Bret: I think it'll be different for every agent. You know, in our customer base, we do what's called outcome based pricing. So essentially every time the AI agent. Solves the problem or saves a customer or whatever it might be. There's a pre negotiated rate for that. We do that. Cause it's, we think that that's sort of the correct way agents, you know, should be packaged.[00:34:53] Bret: I look back at the history of like cloud software and notably the introduction of the browser, which led to [00:35:00] software being delivered in a browser, like Salesforce to. Famously invented sort of software as a service, which is both a technical delivery model through the browser, but also a business model, which is you subscribe to it rather than pay for a perpetual license.[00:35:13] Bret: Those two things are somewhat orthogonal, but not really. If you think about the idea of software running in a browser, that's hosted. Data center that you don't own, you sort of needed to change the business model because you don't, you can't really buy a perpetual license or something otherwise like, how do you afford making changes to it?[00:35:31] Bret: So it only worked when you were buying like a new version every year or whatever. So to some degree, but then the business model shift actually changed business as we know it, because now like. Things like Adobe Photoshop. Now you subscribe to rather than purchase. So it ended up where you had a technical shift and a business model shift that were very logically intertwined that actually the business model shift was turned out to be as significant as the technical as the shift.[00:35:59] Bret: And I think with [00:36:00] agents, because they actually accomplish a job, I do think that it doesn't make sense to me that you'd pay for the privilege of like. Using the software like that coding agent, like if it writes really bad code, like fire it, you know, I don't know what the right metaphor is like you should pay for a job.[00:36:17] Bret: Well done in my opinion. I mean, that's how you pay your software engineers, right? And[00:36:20] swyx: and well, not really. We paid to put them on salary and give them options and they vest over time. That's fair.[00:36:26] Bret: But my point is that you don't pay them for how many characters they write, which is sort of the token based, you know, whatever, like, There's a, that famous Apple story where we're like asking for a report of how many lines of code you wrote.[00:36:40] Bret: And one of the engineers showed up with like a negative number cause he had just like done a big refactoring. There was like a big F you to management who didn't understand how software is written. You know, my sense is like the traditional usage based or seat based thing. It's just going to look really antiquated.[00:36:55] Bret: Cause it's like asking your software engineer, how many lines of code did you write today? Like who cares? Like, cause [00:37:00] absolutely no correlation. So my old view is I don't think it's be different in every category, but I do think that that is the, if an agent is doing a job, you should, I think it properly incentivizes the maker of that agent and the customer of, of your pain for the job well done.[00:37:16] Bret: It's not always perfect to measure. It's hard to measure engineering productivity, but you can, you should do something other than how many keys you typed, you know Talk about perverse incentives for AI, right? Like I can write really long functions to do the same thing, right? So broadly speaking, you know, I do think that we're going to see a change in business models of software towards outcomes.[00:37:36] Bret: And I think you'll see a change in delivery models too. And, and, you know, in our customer base you know, we empower our customers to really have their hands on the steering wheel of what the agent does they, they want and need that. But the role is different. You know, at a lot of our customers, the customer experience operations folks have renamed themselves the AI architects, which I think is really cool.[00:37:55] Bret: And, you know, it's like in the early days of the Internet, there's the role of the webmaster. [00:38:00] And I don't know whether your webmaster is not a fashionable, you know, Term, nor is it a job anymore? I just, I don't know. Will they, our tech stand the test of time? Maybe, maybe not. But I do think that again, I like, you know, because everyone listening right now is a software engineer.[00:38:14] Bret: Like what is the form factor of a coding agent? And actually I'll, I'll take a breath. Cause actually I have a bunch of pins on them. Like I wrote a blog post right before Christmas, just on the future of software development. And one of the things that's interesting is like, if you look at the way I use cursor today, as an example, it's inside of.[00:38:31] Bret: A repackaged visual studio code environment. I sometimes use the sort of agentic parts of it, but it's largely, you know, I've sort of gotten a good routine of making it auto complete code in the way I want through tuning it properly when it actually can write. I do wonder what like the future of development environments will look like.[00:38:55] Bret: And to your point on what is a software product, I think it's going to change a lot in [00:39:00] ways that will surprise us. But I always use, I use the metaphor in my blog post of, have you all driven around in a way, Mo around here? Yeah, everyone has. And there are these Jaguars, the really nice cars, but it's funny because it still has a steering wheel, even though there's no one sitting there and the steering wheels like turning and stuff clearly in the future.[00:39:16] Bret: If once we get to that, be more ubiquitous, like why have the steering wheel and also why have all the seats facing forward? Maybe just for car sickness. I don't know, but you could totally rearrange the car. I mean, so much of the car is oriented around the driver, so. It stands to reason to me that like, well, autonomous agents for software engineering run through visual studio code.[00:39:37] Bret: That seems a little bit silly because having a single source code file open one at a time is kind of a goofy form factor for when like the code isn't being written primarily by you, but it begs the question of what's your relationship with that agent. And I think the same is true in our industry of customer experience, which is like.[00:39:55] Bret: Who are the people managing this agent? What are the tools do they need? And they definitely need [00:40:00] tools, but it's probably pretty different than the tools we had before. It's certainly different than training a contact center team. And as software engineers, I think that I would like to see particularly like on the passion project side or research side.[00:40:14] Bret: More innovation in programming languages. I think that we're bringing the cost of writing code down to zero. So the fact that we're still writing Python with AI cracks me up just cause it's like literally was designed to be ergonomic to write, not safe to run or fast to run. I would love to see more innovation and how we verify program correctness.[00:40:37] Bret: I studied for formal verification in college a little bit and. It's not very fashionable because it's really like tedious and slow and doesn't work very well. If a lot of code is being written by a machine, you know, one of the primary values we can provide is verifying that it actually does what we intend that it does.[00:40:56] Bret: I think there should be lots of interesting things in the software development life cycle, like how [00:41:00] we think of testing and everything else, because. If you think about if we have to manually read every line of code that's coming out as machines, it will just rate limit how much the machines can do. The alternative is totally unsafe.[00:41:13] Bret: So I wouldn't want to put code in production that didn't go through proper code review and inspection. So my whole view is like, I actually think there's like an AI native I don't think the coding agents don't work well enough to do this yet, but once they do, what is sort of an AI native software development life cycle and how do you actually.[00:41:31] Bret: Enable the creators of software to produce the highest quality, most robust, fastest software and know that it's correct. And I think that's an incredible opportunity. I mean, how much C code can we rewrite and rust and make it safe so that there's fewer security vulnerabilities. Can we like have more efficient, safer code than ever before?[00:41:53] Bret: And can you have someone who's like that guy in the matrix, you know, like staring at the little green things, like where could you have an operator [00:42:00] of a code generating machine be like superhuman? I think that's a cool vision. And I think too many people are focused on like. Autocomplete, you know, right now, I'm not, I'm not even, I'm guilty as charged.[00:42:10] Bret: I guess in some ways, but I just like, I'd like to see some bolder ideas. And that's why when you were joking, you know, talking about what's the react of whatever, I think we're clearly in a local maximum, you know, metaphor, like sort of conceptual local maximum, obviously it's moving really fast. I think we're moving out of it.[00:42:26] Alessio: Yeah. At the end of 23, I've read this blog post from syntax to semantics. Like if you think about Python. It's taking C and making it more semantic and LLMs are like the ultimate semantic program, right? You can just talk to them and they can generate any type of syntax from your language. But again, the languages that they have to use were made for us, not for them.[00:42:46] Alessio: But the problem is like, as long as you will ever need a human to intervene, you cannot change the language under it. You know what I mean? So I'm curious at what point of automation we'll need to get, we're going to be okay making changes. To the underlying languages, [00:43:00] like the programming languages versus just saying, Hey, you just got to write Python because I understand Python and I'm more important at the end of the day than the model.[00:43:08] Alessio: But I think that will change, but I don't know if it's like two years or five years. I think it's more nuanced actually.[00:43:13] Bret: So I think there's a, some of the more interesting programming languages bring semantics into syntax. So let me, that's a little reductive, but like Rust as an example, Rust is memory safe.[00:43:25] Bret: Statically, and that was a really interesting conceptual, but it's why it's hard to write rust. It's why most people write python instead of rust. I think rust programs are safer and faster than python, probably slower to compile. But like broadly speaking, like given the option, if you didn't have to care about the labor that went into it.[00:43:45] Bret: You should prefer a program written in Rust over a program written in Python, just because it will run more efficiently. It's almost certainly safer, et cetera, et cetera, depending on how you define safe, but most people don't write Rust because it's kind of a pain in the ass. And [00:44:00] the audience of people who can is smaller, but it's sort of better in most, most ways.[00:44:05] Bret: And again, let's say you're making a web service and you didn't have to care about how hard it was to write. If you just got the output of the web service, the rest one would be cheaper to operate. It's certainly cheaper and probably more correct just because there's so much in the static analysis implied by the rest programming language that it probably will have fewer runtime errors and things like that as well.[00:44:25] Bret: So I just give that as an example, because so rust, at least my understanding that came out of the Mozilla team, because. There's lots of security vulnerabilities in the browser and it needs to be really fast. They said, okay, we want to put more of a burden at the authorship time to have fewer issues at runtime.[00:44:43] Bret: And we need the constraint that it has to be done statically because browsers need to be really fast. My sense is if you just think about like the, the needs of a programming language today, where the role of a software engineer is [00:45:00] to use an AI to generate functionality and audit that it does in fact work as intended, maybe functionally, maybe from like a correctness standpoint, some combination thereof, how would you create a programming system that facilitated that?[00:45:15] Bret: And, you know, I bring up Rust is because I think it's a good example of like, I think given a choice of writing in C or Rust, you should choose Rust today. I think most people would say that, even C aficionados, just because. C is largely less safe for very similar, you know, trade offs, you know, for the, the system and now with AI, it's like, okay, well, that just changes the game on writing these things.[00:45:36] Bret: And so like, I just wonder if a combination of programming languages that are more structurally oriented towards the values that we need from an AI generated program, verifiable correctness and all of that. If it's tedious to produce for a person, that maybe doesn't matter. But one thing, like if I asked you, is this rest program memory safe?[00:45:58] Bret: You wouldn't have to read it, you just have [00:46:00] to compile it. So that's interesting. I mean, that's like an, that's one example of a very modest form of formal verification. So I bring that up because I do think you have AI inspect AI, you can have AI reviewed. Do AI code reviews. It would disappoint me if the best we could get was AI reviewing Python and having scaled a few very large.[00:46:21] Bret: Websites that were written on Python. It's just like, you know, expensive and it's like every, trust me, every team who's written a big web service in Python has experimented with like Pi Pi and all these things just to make it slightly more efficient than it naturally is. You don't really have true multi threading anyway.[00:46:36] Bret: It's just like clearly that you do it just because it's convenient to write. And I just feel like we're, I don't want to say it's insane. I just mean. I do think we're at a local maximum. And I would hope that we create a programming system, a combination of programming languages, formal verification, testing, automated code reviews, where you can use AI to generate software in a high scale way and trust it.[00:46:59] Bret: And you're [00:47:00] not limited by your ability to read it necessarily. I don't know exactly what form that would take, but I feel like that would be a pretty cool world to live in.[00:47:08] Alessio: Yeah. We had Chris Lanner on the podcast. He's doing great work with modular. I mean, I love. LVM. Yeah. Basically merging rust in and Python.[00:47:15] Alessio: That's kind of the idea. Should be, but I'm curious is like, for them a big use case was like making it compatible with Python, same APIs so that Python developers could use it. Yeah. And so I, I wonder at what point, well, yeah.[00:47:26] Bret: At least my understanding is they're targeting the data science Yeah. Machine learning crowd, which is all written in Python, so still feels like a local maximum.[00:47:34] Bret: Yeah.[00:47:34] swyx: Yeah, exactly. I'll force you to make a prediction. You know, Python's roughly 30 years old. In 30 years from now, is Rust going to be bigger than Python?[00:47:42] Bret: I don't know this, but just, I don't even know this is a prediction. I just am sort of like saying stuff I hope is true. I would like to see an AI native programming language and programming system, and I use language because I'm not sure language is even the right thing, but I hope in 30 years, there's an AI native way we make [00:48:00] software that is wholly uncorrelated with the current set of programming languages.[00:48:04] Bret: or not uncorrelated, but I think most programming languages today were designed to be efficiently authored by people and some have different trade offs.[00:48:15] Evolution of Programming Languages[00:48:15] Bret: You know, you have Haskell and others that were designed for abstractions for parallelism and things like that. You have programming languages like Python, which are designed to be very easily written, sort of like Perl and Python lineage, which is why data scientists use it.[00:48:31] Bret: It's it can, it has a. Interactive mode, things like that. And I love, I'm a huge Python fan. So despite all my Python trash talk, a huge Python fan wrote at least two of my three companies were exclusively written in Python and then C came out of the birth of Unix and it wasn't the first, but certainly the most prominent first step after assembly language, right?[00:48:54] Bret: Where you had higher level abstractions rather than and going beyond go to, to like abstractions, [00:49:00] like the for loop and the while loop.[00:49:01] The Future of Software Engineering[00:49:01] Bret: So I just think that if the act of writing code is no longer a meaningful human exercise, maybe it will be, I don't know. I'm just saying it sort of feels like maybe it's one of those parts of history that just will sort of like go away, but there's still the role of this offer engineer, like the person actually building the system.[00:49:20] Bret: Right. And. What does a programming system for that form factor look like?[00:49:25] React and Front-End Development[00:49:25] Bret: And I, I just have a, I hope to be just like I mentioned, I remember I was at Facebook in the very early days when, when, what is now react was being created. And I remember when the, it was like released open source I had left by that time and I was just like, this is so f*****g cool.[00:49:42] Bret: Like, you know, to basically model your app independent of the data flowing through it, just made everything easier. And then now. You know, I can create, like there's a lot of the front end software gym play is like a little chaotic for me, to be honest with you. It is like, it's sort of like [00:50:00] abstraction soup right now for me, but like some of those core ideas felt really ergonomic.[00:50:04] Bret: I just wanna, I'm just looking forward to the day when someone comes up with a programming system that feels both really like an aha moment, but completely foreign to me at the same time. Because they created it with sort of like from first principles recognizing that like. Authoring code in an editor is maybe not like the primary like reason why a programming system exists anymore.[00:50:26] Bret: And I think that's like, that would be a very exciting day for me.[00:50:28] The Role of AI in Programming[00:50:28] swyx: Yeah, I would say like the various versions of this discussion have happened at the end of the day, you still need to precisely communicate what you want. As a manager of people, as someone who has done many, many legal contracts, you know how hard that is.[00:50:42] swyx: And then now we have to talk to machines doing that and AIs interpreting what we mean and reading our minds effectively. I don't know how to get across that barrier of translating human intent to instructions. And yes, it can be more declarative, but I don't know if it'll ever Crossover from being [00:51:00] a programming language to something more than that.[00:51:02] Bret: I agree with you. And I actually do think if you look at like a legal contract, you know, the imprecision of the English language, it's like a flaw in the system. How many[00:51:12] swyx: holes there are.[00:51:13] Bret: And I do think that when you're making a mission critical software system, I don't think it should be English language prompts.[00:51:19] Bret: I think that is silly because you want the precision of a a programming language. My point was less about that and more about if the actual act of authoring it, like if you.[00:51:32] Formal Verification in Software[00:51:32] Bret: I'll think of some embedded systems do use formal verification. I know it's very common in like security protocols now so that you can, because the importance of correctness is so great.[00:51:41] Bret: My intellectual exercise is like, why not do that for all software? I mean, probably that's silly just literally to do what we literally do for. These low level security protocols, but the only reason we don't is because it's hard and tedious and hard and tedious are no longer factors. So, like, if I could, I mean, [00:52:00] just think of, like, the silliest app on your phone right now, the idea that that app should be, like, formally verified for its correctness feels laughable right now because, like, God, why would you spend the time on it?[00:52:10] Bret: But if it's zero costs, like, yeah, I guess so. I mean, it never crashed. That's probably good. You know, why not? I just want to, like, set our bars really high. Like. We should make, software has been amazing. Like there's a Mark Andreessen blog post, software is eating the world. And you know, our whole life is, is mediated digitally.[00:52:26] Bret: And that's just increasing with AI. And now we'll have our personal agents talking to the agents on the CRO platform and it's agents all the way down, you know, our core infrastructure is running on these digital systems. We now have like, and we've had a shortage of software developers for my entire life.[00:52:45] Bret: And as a consequence, you know if you look, remember like health care, got healthcare. gov that fiasco security vulnerabilities leading to state actors getting access to critical infrastructure. I'm like. We now have like created this like amazing system that can [00:53:00] like, we can fix this, you know, and I, I just want to, I'm both excited about the productivity gains in the economy, but I just think as software engineers, we should be bolder.[00:53:08] Bret: Like we should have aspirations to fix these systems so that like in general, as you said, as precise as we want to be in the specification of the system. We can make it work correctly now, and I'm being a little bit hand wavy, and I think we need some systems. I think that's where we should set the bar, especially when so much of our life depends on this critical digital infrastructure.[00:53:28] Bret: So I'm I'm just like super optimistic about it. But actually, let's go to w

In this episode of the Concrete Logic podcast, host Seth Tandett speaks with Larry Sutter, principal engineer at Sutter Engineering, about the development of standards and specifications for supplementary cementitious materials (SCMs) like fly ash and slag. They discuss the differences between standards and specifications, the role of fly ash in improving concrete durability, and the challenges of variability in materials. Larry also highlights emerging test methods for evaluating SCMs and the importance of performance-based specifications in the industry. Takeaways Standards are documents developed through a consensus process. Specifications serve as contracts between buyers and sellers. Fly ash is the most used SCM in concrete. SCMs improve concrete durability by reducing permeability. Variability in materials is a constant challenge in concrete engineering. Performance-based specifications are preferred over prescriptive ones. Emerging materials require new performance-based specifications. Understanding the reactivity of SCMs is crucial for concrete performance. The industry must adapt to evolving standards and specifications. Future specifications aim to encompass a wider range of SCMs. Chapters 00:00 Introduction to Standards and Specifications 03:09 Understanding Standards vs Specifications 10:17 The Role of Fly Ash in Concrete 18:03 Mechanisms of Durability Improvement 22:52 Emerging Test Methods for SCMs 30:21 Challenges in SEM Usage and Specifications 35:37 Performance-Based Specifications for SCMs 39:43 Future Directions in SCM Standards ***Did you learn something from this episode? Would you like to support the concrete industry's favorite podcast? If so, donate at https://www.concretelogicpodcast.com/support/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ . When YOU donate to the show, you will be listed as a producer of the next episode that is released! Join the Concrete Logic Academy! Enhance your learning from our podcast with engaging quizzes that test your knowledge and help you earn Professional Development Hours (PDHs). Support Concrete Logic and take your education to the next level!

Galatians 3:13 Thanks to everyone who supports TMBH at patreon.com/thetmbhpodcast You're the reason we can all do this together! Discuss the episode here Music by Jeff Foote

BONUS: Gojko Adzic on Optimizing Products for Long-Tail Users (Agile Online Summit 2024 Replay) In this BONUS episode, we revisit Gojko Adzic's insightful interview at the Agile Online Summit 2024. Gojko, an award-winning author and software expert, unpacks the principles behind his latest book, Lizard Optimization, offering a fresh perspective on improving product usability by addressing the needs of long-tail users. From learning from unexpected user behaviors to refining products with a systematic approach, this episode is filled with practical tips for product teams and Agile practitioners. What is Lizard Optimization? Drawing from his experiences as a product developer, Gojko introduces the idea of Lizard Optimization. He discusses how observing unexpected user behaviors led him to refine his SaaS tools like Narakeet and MindMup. By focusing on usability challenges and unusual patterns, he has turned serendipity into actionable insights. “Users aren't stupid—they're just finding creative ways to get value from your product. Listen to them.” Gojko explains the inspiration behind the metaphor of the “Lizardman constant,” a concept from a Scott Alexander blog post. He describes how this principle applies to product optimization: understanding and addressing the 4% of surprising, unexplainable behaviors can uncover opportunities for innovation. “The job isn't to judge users—it's to explore why they're doing what they're doing and how we can help them succeed.” The High-Level Process of Lizard Optimization Gojko outlines the systematic process described in his book to leverage unexpected user behavior: Observe Misuse: Identify how users deviate from expected patterns. Extract Insights: Focus on one unexpected behavior as a signal. Remove Obstacles: Help users achieve their goals more easily. Monitor Impacts: Detect and adjust for unintended consequences. “Start monitoring for the predictable but unexpected—those hidden gems can unlock your next big feature.” Practical Advice for Product Teams For teams ready to apply these concepts, Gojko emphasizes the importance of expanding observability tools to include product metrics and not just technical ones. He shares how tracking unpredictable user actions can inspire impactful changes. “About a third of what we do delivers value—focus on finding where unexpected value lies.” Recommended Resources To dive deeper into these ideas, Gojko recommends: Trustworthy Online Controlled Experiments by Ron Kohavi Evidence Guided by Tim Herbig LizardOptimization.org “Experimentation and evidence-based decision-making are the keys to building better products.” Closing Thoughts: “Look for the Unexpected” Gojko's parting advice for Agile practitioners is simple yet powerful: Look for the unexpected. By embracing surprises in user behavior, teams can transform minor inconveniences into major opportunities for growth. “The unexpected is where innovation begins.” About Gojko Adzic Gojko Adzic is an award-winning author, speaker, and product creator. His books, including Lizard Optimization, Impact Mapping, and Specification by Example, have become essential reads for Agile practitioners and product teams worldwide. Gojko is a 2019 AWS Serverless Hero, the winner of the 2016 European Software Testing Outstanding Achievement Award, and the 2011 Most Influential Agile Testing Professional Award. He has also co-founded several successful SaaS tools, including Narakeet, MindMup, and Votito. You can link with Gojko Adzic on LinkedIn.

Check out Krane here: https://krane.tech/Follow Eshan here

Ready to elevate your trail running game? Check out this in-depth review of the La Sportiva Prodigio Pro, the ultimate trail-ready super shoe designed for technical terrains and marathon distances. Featuring a nitrogen-infused EVA midsole with TPU core for responsive cushioning, a built-in stability frame, and a snug wire mesh upper, this shoe delivers unmatched comfort and performance. Perfect for runners tackling shorter to mid-distance races, the Prodigio Pro offers a lightweight, secure fit with a gaiter-like collar for extra protection. While it shines on technical trails, its Frixion rubber outsole and redesigned 4mm lugs ensure superior grip. #lasportivaprodigio #lasportivaprodigioreview #runninggear #trailrunningshoes CHAPTERS: 00:00 - La Sportiva Pro 00:16 - Key Features, Performance, Design 00:30 - Weight, Specifications, Durability 01:58 - Price, Value, Comparison

Sponsorships and applications for the AI Engineer Summit in NYC are live! (Speaker CFPs have closed) If you are building AI agents or leading teams of AI Engineers, this will be the single highest-signal conference of the year for you.Right after Christmas, the Chinese Whale Bros ended 2024 by dropping the last big model launch of the year: DeepSeek v3. Right now on LM Arena, DeepSeek v3 has a score of 1319, right under the full o1 model, Gemini 2, and 4o latest. This makes it the best open weights model in the world in January 2025.There has been a big recent trend in Chinese labs releasing very large open weights models, with TenCent releasing Hunyuan-Large in November and Hailuo releasing MiniMax-Text this week, both over 400B in size. However these extra-large language models are very difficult to serve.Baseten was the first of the Inference neocloud startups to get DeepSeek V3 online, because of their H200 clusters, their close collaboration with the DeepSeek team and early support of SGLang, a relatively new VLLM alternative that is also used at frontier labs like X.ai. Each H200 has 141 GB of VRAM with 4.8 TB per second of bandwidth, meaning that you can use 8 H200's in a node to inference DeepSeek v3 in FP8, taking into account KV Cache needs. We have been close to Baseten since Sarah Guo introduced Amir Haghighat to swyx, and they supported the very first Latent Space Demo Day in San Francisco, which was effectively the trial run for swyx and Alessio to work together! Since then, Philip Kiely also led a well attended workshop on TensorRT LLM at the 2024 World's Fair. We worked with him to get two of their best representatives, Amir and Lead Model Performance Engineer Yineng Zhang, to discuss DeepSeek, SGLang, and everything they have learned running Mission Critical Inference workloads at scale for some of the largest AI products in the world.The Three Pillars of Mission Critical InferenceWe initially planned to focus the conversation on SGLang, but Amir and Yineng were quick to correct us that the choice of inference framework is only the simplest, first choice of 3 things you need for production inference at scale:“I think it takes three things, and each of them individually is necessary but not sufficient: * Performance at the model level: how fast are you running this one model running on a single GPU, let's say. The framework that you use there can, can matter. The techniques that you use there can matter. The MLA technique, for example, that Yineng mentioned, or the CUDA kernels that are being used. But there's also techniques being used at a higher level, things like speculative decoding with draft models or with Medusa heads. And these are implemented in the different frameworks, or you can even implement it yourself, but they're not necessarily tied to a single framework. But using speculative decoding gets you massive upside when it comes to being able to handle high throughput. But that's not enough. Invariably, that one model running on a single GPU, let's say, is going to get too much traffic that it cannot handle.* Horizontal scaling at the cluster/region level: And at that point, you need to horizontally scale it. That's not an ML problem. That's not a PyTorch problem. That's an infrastructure problem. How quickly do you go from, a single replica of that model to 5, to 10, to 100. And so that's the second, that's the second pillar that is necessary for running these machine critical inference workloads.And what does it take to do that? It takes, some people are like, Oh, You just need Kubernetes and Kubernetes has an autoscaler and that just works. That doesn't work for, for these kinds of mission critical inference workloads. And you end up catching yourself wanting to bit by bit to rebuild those infrastructure pieces from scratch. This has been our experience. * And then going even a layer beyond that, Kubernetes runs in a single. cluster. It's a single cluster. It's a single region tied to a single region. And when it comes to inference workloads and needing GPUs more and more, you know, we're seeing this that you cannot meet the demand inside of a single region. A single cloud's a single region. In other words, a single model might want to horizontally scale up to 200 replicas, each of which is, let's say, 2H100s or 4H100s or even a full node, you run into limits of the capacity inside of that one region. And what we had to build to get around that was the ability to have a single model have replicas across different regions. So, you know, there are models on Baseten today that have 50 replicas in GCP East and, 80 replicas in AWS West and Oracle in London, etc.* Developer experience for Compound AI Systems: The final one is wrapping the power of the first two pillars in a very good developer experience to be able to afford certain workflows like the ones that I mentioned, around multi step, multi model inference workloads, because more and more we're seeing that the market is moving towards those that the needs are generally in these sort of more complex workflows. We think they said it very well.Show Notes* Amir Haghighat, Co-Founder, Baseten* Yineng Zhang, Lead Software Engineer, Model Performance, BasetenFull YouTube EpisodePlease like and subscribe!Timestamps* 00:00 Introduction and Latest AI Model Launch* 00:11 DeepSeek v3: Specifications and Achievements* 03:10 Latent Space Podcast: Special Guests Introduction* 04:12 DeepSeek v3: Technical Insights* 11:14 Quantization and Model Performance* 16:19 MOE Models: Trends and Challenges* 18:53 Baseten's Inference Service and Pricing* 31:13 Optimization for DeepSeek* 31:45 Three Pillars of Mission Critical Inference Workloads* 32:39 Scaling Beyond Single GPU* 33:09 Challenges with Kubernetes and Infrastructure* 33:40 Multi-Region Scaling Solutions* 35:34 SG Lang: A New Framework* 38:52 Key Techniques Behind SG Lang* 48:27 Speculative Decoding and Performance* 49:54 Future of Fine-Tuning and RLHF* 01:00:28 Baseten's V3 and Industry TrendsBaseten's previous TensorRT LLM workshop: Get full access to Latent Space at www.latent.space/subscribe

1UNITED STATES BANKRUPTCY COURTSOUTHERN DISTRICT OF TEXASHOUSTON DIVISIONIn re:INTRUM AB, et al.,1Debtors.Chapter 11Case No. 24-90575 (CML)(Jointly Administered)NOTICE OF APPEALPursuant to 28 U.S.C. § 158(a) and Federal Rules of Bankruptcy Procedure 8002 and 8003,notice is hereby given that the Ad Hoc Committee of holders of 2025 notes issued by Intrum AB(the “AHC”) hereby appeals to the United States District Court for the Southern District of Texasfrom (i) the Order Denying Motion of the Ad Hoc Committee of Holders of Intrum AB Notes Due2025 to Dismiss Chapter 11 Cases Pursuant to 11 U.S.C. § 1112(b) and Federal Rule ofBankruptcy Procedure 1017(f)(1) (ECF No. 262) (the “Motion to Dismiss Order”) and (ii) theOrder (I) Approving Disclosure Statement and (II) Confirming Joint Prepackaged Chapter 11Plan of Intrum AB and Its Affiliated Debtor (Further Technical Modifications) (ECF No. 263) (the“Confirmation Order”). A copy of the Motion to Dismiss Order is attached as Exhibit A and acopy of the Confirmation Order is attached as Exhibit B. Additionally, the transcript of theBankruptcy Court's oral ruling accompanying the Motion to Dismiss Order and ConfirmationOrder (ECF No. 275) is attached as Exhibit C.Below are the names of all parties to this appeal and their respective counsel:1 The Debtors in these Chapter 11 Cases are Intrum AB and Intrum AB of Texas LLC. The Debtors'service address in these Chapter 11 Cases is 801 Travis Street, Ste 2101, #1312, Houston, TX 77002.Case 24-90575 Document 296 Filed in TXSB on 01/13/25 Page 1 of 62I. APPELLANTA. Name of Appellant:The members of the AHC include:Boundary Creek Master Fund LP; CF INT Holdings Designated Activity Company; CaiusCapital Master Fund; Diameter Master Fund LP; Diameter Dislocation Master Fund II LP; FirTree Credit Opportunity Master Fund, LP; MAP 204 Segregated Portfolio, a segregated portfolioof LMA SPC; Star V Partners LLC; and TQ Master Fund LP.Attorneys for the AHC:QUINN EMANUEL URQUHART & SULLIVAN, LLPChristopher D. Porter (SBN 24070437)Joanna D. Caytas (SBN 24127230)Melanie A. Guzman (SBN 24117175)Cameron M. Kelly (SBN 24120936)700 Louisiana Street, Suite 3900Houston, TX 77002Telephone: (713) 221-7000Facsimile: (713) 221-7100Email: chrisporter@quinnemanuel.comjoannacaytas@quinnemanuel.commelanieguzman@quinnemanuel.comcameronkelly@quinnemanuel.com-and-Benjamin I. Finestone (admitted pro hac vice)Sascha N. Rand (admitted pro hac vice)Katherine A. Scherling (admitted pro hac vice)295 5th AvenueNew York, New York 10016Telephone: (212) 849-7000Facsimile: (212) 849-7100Email: benjaminfinestone@quinnemanuel.comsascharand@quinnemanuel.comkatescherling@quinnemanuel.comB. Positions of appellant in the adversary proceeding or bankruptcy case that isthe subject of this appeal:CreditorsCase 24-90575 Document 296 Filed in TXSB on 01/13/25 Page 2 of 63II. THE SUBJECT OF THIS APPEALA. Judgment, order, or decree appealed from:The Order Denying Motion of the Ad Hoc Committee of Holders of Intrum AB Notes Due2025 to Dismiss Chapter 11 Cases Pursuant to 11 U.S.C. § 1112(b) and Federal Rule ofBankruptcy Procedure 1017(f)(1) (ECF No. 262); the Order (I) Approving Disclosure Statementand (II) Confirming Joint Prepackaged Chapter 11 Plan of Intrum AB and Its Affiliated Debtor(Further Technical Modifications) (ECF No. 263); and the December 31, 2024 Transcript of OralRuling Before the Honorable Christopher M. Lopez United States Bankruptcy Court Judge (ECFNo. 275).B. The date on which the judgment, order, or decree was entered:The Motion to Dismiss Order and the Confirmation Order were entered on December 31,2024. The Court issued its oral ruling accompanying the Motion to Dismiss Order and theConfirmation Order on December 31, 2024.III. OTHER PARTIES TO THIS APPEALIntrum AB and Intrum AB of Texas LLCMILBANK LLPDennis F. Dunne (admitted pro hac vice)Jaimie Fedell (admitted pro hac vice)55 Hudson YardsNew York, NY 10001Telephone: (212) 530-5000Facsimile: (212) 530-5219Email: ddunne@milbank.comjfedell@milbank.com–and–Andrew M. Leblanc (admitted pro hac vice)Melanie Westover Yanez (admitted pro hac vice)1850 K Street, NW, Suite 1100Washington, DC 20006Telephone: (202) 835-7500Facsimile: (202) 263-7586Email: aleblanc@milbank.commwyanez@milbank.com–and–PORTER HEDGES LLPJohn F. Higgins (SBN 09597500)Case 24-90575 Document 296 Filed in TXSB on 01/13/25 Page 3 of 64Eric D. Wade (SBN 00794802)M. Shane Johnson (SBN 24083263)1000 Main Street, 36th FloorHouston TX 77002Telephone: (713) 226-6000Facsimile: (713) 226-6248Email: jhiggins@porterhedges.comewade@porterhedges.comsjohnson@porterhedges.comIV. OTHER PARTIES THAT MAY HAVE AN INTEREST IN THIS APPEALThe following chart lists certain parties that are not parties to this appeal, but that may havean interest in the outcome of the case. These parties should be served with notice of this appealby the Debtors who are aware of their identities and best positioned to provide notice.All Other Creditors of the Debtors, Including, But Not Limited To:• Certain funds and accounts managed by BlackRock Investment Management (UK)Limited or its affiliates;• Capital Four;• Davidson Kempner European Partners, LLP;• Intermediate Capital Managers Limited;• Mandatum Asset Management Ltd;• H.I.G. Capital, LLC;• Spiltan Hograntefond; Spiltan Rantefond Sverige; and Spiltan Aktiefond Stabil;• The RCF SteerCo Group;• Swedbank AB (publ).Any Holder of Stock of the Debtors• Any holder of stock of the Debtors, including their successors and assigns.Case 24-90575 Document 296 Filed in TXSB on 01/13/25 Page 4 of 65Respectfully submitted this 13th day of January, 2025.QUINN EMANUEL URQUHART &SULLIVAN, LLP/s/ Christopher D. PorterChristopher D. Porter (SBN 24070437)Joanna D. Caytas (SBN 24127230)Melanie A. Guzman (SBN 24117175)Cameron M. Kelly (SBN 24120936)700 Louisiana Street, Suite 3900Houston, TX 77002Telephone: (713) 221-7000Facsimile: (713) 221-7100Email: chrisporter@quinnemanuel.comjoannacaytas@quinnemanuel.commelanieguzman@quinnemanuel.comcameronkelly@quinnemanuel.com-and-Benjamin I. Finestone (admitted pro hac vice)Sascha N. Rand (admitted pro hac vice)Katherine A. Scherling (admitted pro hac vice)295 5th AvenueNew York, New York 10016Telephone: (212) 849-7000Facsimile: (212) 849-7100Email: benjaminfinestone@quinnemanuel.comsascharand@quinnemanuel.comkatescherling@quinnemanuel.comCOUNSEL FOR THE AD HOC COMMITTEE OFINTRUM AB 2025 NOTEHOLDERSCase 24-90575 Document 296 Filed in TXSB on 01/13/25 Page 5 of 6CERTIFICATE OF SERVICEI, Christopher D. Porter, hereby certify that on the 13th day of January, 2025, a copy ofthe foregoing document has been served via the Electronic Case Filing System for the UnitedStates Bankruptcy Court for the Southern District of Texas./s/ Christopher D. PorterBy: Christopher D. PorterCase 24-90575 Document 296 Filed in TXSB on 01/13/25 Page 6 of 6EXHIBIT ACase 24-90575 Document 296-1 Filed in TXSB on 01/13/25 Page 1 of 31IN THE UNITED STATES BANKRUPTCY COURTFOR THE SOUTHERN DISTRICT OF TEXASHOUSTON DIVISION)In re: ) Chapter 11)Intrum AB, et al.,1 ) Case No. 24-90575 (CML)))Jointly AdministeredDebtors. ))ORDER DENYING MOTION OF THE AD HOCCOMMITTEE OF HOLDERS OF INTRUM AB NOTES DUE 2025TO DISMISS CHAPTER 11 CASES PURSUANT TO 11 U.S.C. § 1112(B) ANDFEDERAL RULE OF BANKRUPTCY PROCEDURE 1017(F)(1)(Related to Docket No. 27)This matter, having come before the Court upon the Motion of the Ad Hoc Committee ofHolders of Intrum AB Notes Due 2025 to Dismiss Chapter 11 Cases Pursuant to 11 U.S.C. §1112(b) and Federal Rule of Bankruptcy Procedure 1017(f)(1) [Docket No. 27] (the “Motion toDismiss”); and this Court having considered the Debtors' Objection to the Motion of the Ad HocCommittee of Holders of Intrum AB Notes Due 2025 to Dismiss Chapter 11 Cases Pursuant to 11U.S.C. § 1112(b) and Federal Rule of Bankruptcy Procedure 1017(f)(1) (the “Objection”) andany other responses or objections to the Motion to Dismiss; and this Court having jurisdiction overthis matter pursuant to 28 U.S.C. § 1334 and the Amended Standing Order; and this Court havingfound that this is a core proceeding pursuant to 28 U.S.C. § 157(b)(2); and this Court having foundthat it may enter a final order consistent with Article III of the United States Constitution; and thisCourt having found that the relief requested in the Objection is in the best interests of the Debtors'1 The Debtors in these Chapter 11 Cases are Intrum AB and Intrum AB of Texas LLC. The Debtors' serviceaddress in these Chapter 11 Cases is 801 Travis Street, STE 2101, #1312, Houston, TX 77002.United States Bankruptcy CourtSouthern District of TexasENTEREDDecember 31, 2024Nathan Ochsner, ClerkCCaassee 2 244-9-900557755 D Dooccuummeennt t2 29662-1 F Filieledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 1 2 o of f2 32estates; and this Court having found that the Debtors' notice of the Objection and opportunity fora hearing on the Motion to Dismiss and Objection were appropriate and no other notice need beprovided; and this Court having reviewed the Motion to Dismiss and Objection and havingheard the statements in support of the relief requested therein at a hearing before this Court; andthis Court having determined that the legal and factual bases set forth in the Objectionestablish just cause for the relief granted herein; and upon all of the proceedings had beforethis Court; and after due deliberation and sufficient cause appearing therefor, it is HEREBYORDERED THAT:1. The Motion to Dismiss is Denied for the reasons stated at the December 31, 2024 hearing.2. This Court retains exclusive jurisdiction and exclusive venue with respect to allmatters arising from or related to the implementation, interpretation, and enforcement of this Order.DAeucegmubste 0r 23,1 2, 0210294CCaassee 2 244-9-900557755 D Dooccuummeennt t2 29662-1 F Filieledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 2 3 o of f2 3EXHIBIT BCase 24-90575 Document 296-2 Filed in TXSB on 01/13/25 Page 1 of 135IN THE UNITED STATES BANKRUPTCY COURTFOR THE SOUTHERN DISTRICT OF TEXASHOUSTON DIVISION)In re: ) Chapter 11)Intrum AB et al.,1 ) Case No. 24-90575 (CML)))(Jointly Administered)Debtors. ))ORDER (I) APPROVINGDISCLOSURE STATEMENT AND(II) CONFIRMING JOINT PREPACKAGED CHAPTER 11PLAN OF INTRUM AB AND ITS AFFILIATEDDEBTOR (FURTHER TECHNICAL MODIFICATIONS)The above-captioned debtors and debtors in possession (collectively, the“Debtors”), having:a. entered into that certain Lock-Up Agreement, dated as of July 10, 2024 (asamended and restated on August 15, 2024, and as further modified,supplemented, or otherwise amended from time to time in accordance with itsterms, the “the Lock-Up Agreement”) and that certain Backstop Agreement,dated as of July 10, 2024, (as amended and restated on November 15, 2024 andas further modified, supplemented, or otherwise amended from time to time inaccordance with its terms), setting out the terms of the backstop commitmentsprovided by the Backstop Providers to backstop the entirety of the issuance ofNew Money Notes (as may be further amended, restated, amended and restated,modified or supplemented from time to time in accordance with the termsthereof, the “Backstop Agreement”) which set forth the terms of a consensualfinancial restructuring of the Debtors;b. commenced, on October 17, 2024, a prepetition solicitation (the “Solicitation”)of votes on the Joint Prepackaged Chapter 11 Plan of Reorganization of IntrumAB and its Debtor Affiliate Pursuant to Chapter 11 of the Bankruptcy Code (asthe same may be further amended, modified and supplemented from time totime, the “Plan”), by causing the transmittal, through their solicitation andballoting agent, Kroll Restructuring Administration LLC (“Kroll”), to theholders of Claims entitled to vote on the Plan of, among other things: (i) the1 The Debtors in these chapter 11 cases are Intrum AB and Intrum AB of Texas LLC. The Debtors' serviceaddress in these chapter 11 cases is 801 Travis Street, STE 2102, #1312, Houston, TX 77002.United States Bankruptcy CourtSouthern District of TexasENTEREDDecember 31, 2024Nathan Ochsner, ClerkCCaassee 2 244-9-900557755 D Dooccuummeennt t2 29663-2 F Filieledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 1 2 o of f1 133452Plan, (ii) the Disclosure Statement for Joint Prepackaged Chapter 11 Plan ofReorganization of Intrum AB and its Debtor Affiliate (as the same may befurther amended, modified and supplemented from time to time, the“Disclosure Statement”), and (iii) the Ballots and Master Ballot to vote on thePlan (the “Ballots”), (iv) the Affidavit of Service of Solicitation Materials[Docket No. 7];c. commenced on November 15, 2024 (the “Petition Date”), these chapter 11 cases(these “Chapter 11 Cases”) by filing voluntary petitions in the United StatesBankruptcy Court for the Southern District of Texas (the “Bankruptcy Court”or the “Court”) for relief under chapter 11 of title 11 of the United States Code(the “Bankruptcy Code”);d. Filed on November 15, 2024, the Affidavit of Service of Solicitation Materials[Docket No. 7] (the “Solicitation Affidavit”);e. Filed, on November 16, 2024 the Joint Prepackaged Chapter 11 Plan ofReorganization of Intrum AB and its Debtor Affiliate Pursuant to Chapter 11of the Bankruptcy Code (Technical Modifications) [Docket No. 16] and theDisclosure Statement for Joint Prepackaged Chapter 11 Plan of Intrum AB andits Debtor Affiliate [Docket No. 17];f. Filed on November 16, 2024, the Declaration of Andrés Rubio in Support of ofthe Debtors' Chapter 11 Petitions and First Day Motions [Docket No. 14] (the“First Day Declaration”);g. Filed on November 17, 2024, the Declaration of Alex Orchowski of KrollRestructuring Administration LLC Regarding the Solicitation of Votes andTabulation of Ballots Case on the Joint Prepackaged Chapter 11 Plan ofReorganization of Intrum AB and its Debtor Affiliate Pursuant to Chapter 11of the Bankruptcy Code [Docket No. 18] (the “Voting Declaration,” andtogether with the Plan, the Disclosure Statement, the Ballots, and theSolicitation Affidavit, the “Solicitation Materials”);h. obtained, on November 19, 2024, the Order(I) Scheduling a Combined Hearingon (A) Adequacy of the Disclosure Statement and (B) Confirmation of the Plan,(II) Approving Solicitation Procedures and Form and Manner of Notice ofCommencement, Combined Hearing, and Objection Deadline, (III) FixingDeadline to Object to Disclosure Statement and Plan, (IV) Conditionally (A)Directing the United States Trustee Not to Convene Section 341 Meeting ofCreditors and (B) Waiving Requirement to File Statements of Financial Affairsand Schedules of Assets and Liabilities, and (V) Granting Related Relief[Docket No. 71] (the “Scheduling Order”), which, among other things: (i)approved the prepetition solicitation and voting procedures, including theConfirmation Schedule (as defined therein); (ii) conditionally approved theDisclosure Statement and its use in the Solicitation; and (iii) scheduled theCombined Hearing on December 16, 2024, at 1:00 p.m. (prevailing CentralCCaassee 2 244-9-900557755 D Dooccuummeennt t2 29663-2 F Filieledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 2 3 o of f1 133453Time) to consider the final approval of the Disclosure Statement and theconfirmation of the Plan (the “Combined Hearing”);i. served, through Kroll, on November 20, 2025, on all known holders of Claimsand Interests, the U.S. Trustee and certain other parties in interest, the Noticeof: (I) Commencement of Chapter 11 Bankruptcy Cases; (II) Hearing on theDisclosure Statement and Confirmation of the Plan, and (III) Certain ObjectionDeadlines (the “Combined Hearing Notice”) as evidence by the Affidavit ofService [Docket No. 160];j. caused, on November 25 and 27, 2024, the Combined Hearing Notice to bepublished in the New York Times (national and international editions) and theFinancial Times (international edition), as evidenced by the Certificate ofPublication [Docket No. 148];k. Filed and served, on December 10, 2024, the Plan Supplement for the Debtors'Joint Prepackaged Chapter 11 Plan of Reorganization [Docket 165];l. Filed on December 10, 2024, the Declaration of Jeffrey Kopa in Support ofConfirmation of the Joint Prepackaged Plan of Reorganization of Intrum ABand its Debtor Affiliate Pursuant to Chapter 11 of the Bankruptcy Code [DocketNo. 155];m. Filed on December 14, 2024, the:i. Debtors' Memorandum of Law in Support of an Order: (I) Approving, on aFinal Basis, Adequacy of the Disclosure Statement; (II) Confirming theJoint Prepackaged Plan of Reorganization; and (III) Granting Related Relief[Docket No. 190] (the “Confirmation Brief”);ii. Declaration of Andrés Rubio in Support of Confirmation of the JointPrepackaged Plan of Reorganization of Intrum AB and its Debtor Affiliate.[Docket No. 189] (the “Confirmation Declaration”); andiii. Joint Prepackaged Chapter 11 Plan of Reorganization of Intrum AB and itsDebtor Affiliate Pursuant to Chapter 11 of the Bankruptcy Code (FurtherTechnical Modifications) [Docket No. 191];n. Filed on December 18, 2024, the Joint Prepackaged Chapter 11 Plan ofReorganization of Intrum AB and its Debtor Affiliate Pursuant to Chapter 11of the Bankruptcy Code (Further Technical Modifications) [Docket No. 223];CCaassee 2 244-9-900557755 D Dooccuummeennt t2 29663-2 F Filieledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 3 4 o of f1 133454WHEREAS, the Court having, among other things:a. set December 12, 2024, at 4:00 p.m. (prevailing Central Time) as the deadlinefor Filing objection to the adequacy of the Disclosure Statement and/orConfirmation2 of the Plan (the “Objection Deadline”);b. held, on December 16, 2024 at 1:00 p.m. (prevailing Central Time) [andcontinuing through December 17, 2024], the Combined Hearing;c. heard the statements, arguments, and any objections made at the CombinedHearing;d. reviewed the Disclosure Statement, the Plan, the Ballots, the Plan Supplement,the Confirmation Brief, the Confirmation Declaration, the SolicitationAffidavit, and the Voting Declaration;e. overruled (i) any and all objections to approval of the Disclosure Statement, thePlan, and Confirmation, except as otherwise stated or indicated on the record,and (ii) all statements and reservations of rights not consensually resolved orwithdrawn, unless otherwise indicated; andf. reviewed and taken judicial notice of all the papers and pleadings Filed(including any objections, statement, joinders, reservations of rights and otherresponses), all orders entered, and all evidence proffered or adduced and allarguments made at the hearings held before the Court during the pendency ofthese cases;NOW, THEREFORE, it appearing to the Bankruptcy Court that notice of theCombined Hearing and the opportunity for any party in interest to object to the DisclosureStatement and the Plan having been adequate and appropriate as to all parties affected or to beaffected by the Plan and the transactions contemplated thereby, and the legal and factual bases setforth in the documents Filed in support of approval of the Disclosure Statement and Confirmationand other evidence presented at the Combined Hearing establish just cause for the relief grantedherein; and after due deliberation thereon and good cause appearing therefor, the BankruptcyCourt makes and issues the following findings of fact and conclusions of law, and orders for thereasons stated on the record at the December 31, 2024 ruling on plan confirmation;2 Capitalized terms used but not otherwise defined herein have meanings given to them in the Plan and/or theDisclosure Statement. The rules of interpretation set forth in Article I.B of the Plan apply to this CombinedOrder.CCaassee 2 244-9-900557755 D Dooccuummeennt t2 29663-2 F Filieledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 4 5 o of f1 133455I. FINDINGS OF FACT AND CONCLUSIONS OF LAWIT IS HEREBY FOUND AND DETERMINED THAT:A. Findings of Fact and Conclusions of Law.1. The findings and conclusions set forth herein and in the record of theCombined Hearing constitute the Bankruptcy Court's findings of fact and conclusions of law underRule 52 of the Federal Rules of Civil Procedure, as made applicable herein by Bankruptcy Rules7052 and 9014. To the extent any of the following conclusions of law constitute findings of fact,or vice versa, they are adopted as such.B. Jurisdiction, Venue, Core Proceeding.2. This Court has jurisdiction over these Chapter 11 Cases pursuant to28 U.S.C. § 1334. Venue of these proceedings and the Chapter 11 Cases in this district is properpursuant to 28 U.S.C. §§ 1408 and 1409. This is a core proceeding pursuant to 28 U.S.C.§ 157(b)(2) and this Court may enter a final order hereon under Article III of the United StatesConstitution.C. Eligibility for Relief.3. The Debtors were and continue to be entities eligible for relief under section109 of the Bankruptcy Code and the Debtors were and continue to be proper proponents of thePlan under section 1121(a) of the Bankruptcy Code.D. Commencement and Joint Administration of the Chapter 11 Cases.4. On the Petition Date, the Debtors commenced the Chapter 11 Cases. OnNovember 18, 2024, the Court entered an order [Docket No. 51] authorizing the jointadministration of the Chapter 11 Case in accordance with Bankruptcy Rule 1015(b). The Debtorshave operated their businesses and managed their properties as debtors in possession pursuant toCCaassee 2 244-9-900557755 D Dooccuummeennt t2 29663-2 F Filieledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 5 6 o of f1 133456sections 1107(a) and 1108 of the Bankruptcy Code. No trustee, examiner, or statutory committeehas been appointed in these Chapter 11 Cases.E. Adequacy of the Disclosure Statement.5. The Disclosure Statement and the exhibits contained therein (i) containssufficient information of a kind necessary to satisfy the disclosure requirements of applicablenonbankruptcy laws, rules and regulations, including the Securities Act; and (ii) contains“adequate information” as such term is defined in section 1125(a)(1) and used in section1126(b)(2) of the Bankruptcy Code, with respect to the Debtors, the Plan and the transactionscontemplated therein. The Filing of the Disclosure Statement satisfied Bankruptcy Rule 3016(b).The injunction, release, and exculpation provisions in the Plan and the Disclosure Statementdescribe, in bold font and with specific and conspicuous language, all acts to be enjoined andidentify the Entities that will be subject to the injunction, thereby satisfying Bankruptcy Rule3016(c).F. Solicitation.6. As described in and evidenced by the Voting Declaration, the Solicitationand the transmittal and service of the Solicitation Materials were: (i) timely, adequate, appropriate,and sufficient under the circumstances; and (ii) in compliance with sections 1125(g) and 1126(b)of the Bankruptcy Code, Bankruptcy Rules 3017 and 3018, the applicable Local Bankruptcy Rules,the Scheduling Order and all applicable nonbankruptcy rules, laws, and regulations applicable tothe Solicitation, including the registration requirements under the Securities Act. The SolicitationMaterials, including the Ballots and the Opt Out Form (as defined below), adequately informedthe holders of Claims entitled to vote on the Plan of the procedures and deadline for completingand submitting the Ballots.CCaassee 2 244-9-900557755 D Dooccuummeennt t2 29663-2 F Filieledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 6 7 o of f1 1334577. The Debtors served the Combined Hearing Notice on the entire creditormatrix and served the Opt Out Form on all Non-Voting Classes. The Combined Hearing Noticeadequately informed Holders of Claims or Interests of critical information regarding voting on (ifapplicable) and objecting to the Plan, including deadlines and the inclusion of release, exculpation,and injunction provisions in the Plan, and adequately summarized the terms of the Third-PartyRelease. Further, because the form enabling stakeholders to opt out of the Third-Party Release (the“Opt Out Form”) was included in both the Ballots and the Opt Out Form, every known stakeholder,including unimpaired creditors was provided with the means by which the stakeholders could optout of the Third-Party Release. No further notice is required. The period for voting on the Planprovided a reasonable and sufficient period of time and the manner of such solicitation was anappropriate process allowing for such holders to make an informed decision.G. Tabulation.8. As described in and evidenced by the Voting Declaration, (i) the holders ofClaims in Class 3 (RCF Claims) and Class 5 (Notes Claims) are Impaired under the Plan(collectively, the “Voting Classes”) and have voted to accept the Plan in the numbers and amountsrequired by section 1126 of the Bankruptcy Code, and (ii) no Class that was entitled to vote on thePlan voted to reject the Plan. All procedures used to tabulate the votes on the Plan were in goodfaith, fair, reasonable, and conducted in accordance with the applicable provisions of theBankruptcy Code, the Bankruptcy Rules, the Local Rules, the Disclosure Statement, theScheduling Order, and all other applicable nonbankruptcy laws, rules, and regulations.H. Plan Supplement.9. On December 10, 2024, the Debtors Filed the Plan Supplement with theCourt. The Plan Supplement (including as subsequently modified, supplemented, or otherwiseCCaassee 2 244-9-900557755 D Dooccuummeennt t2 29663-2 F Filieledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 7 8 o of f1 133458amended pursuant to a filing with the Court), complies with the terms of the Plan, and the Debtorsprovided good and proper notice of the filing in accordance with the Bankruptcy Code, theBankruptcy Rules, the Scheduling Order, and the facts and circumstances of the Chapter 11 Cases.All documents included in the Plan Supplement are integral to, part of, and incorporated byreference into the Plan. No other or further notice is or will be required with respect to the PlanSupplement. Subject to the terms of the Plan and the Lock-Up Agreement, and only consistenttherewith, the Debtors reserve the right to alter, amend, update, or modify the Plan Supplementand any of the documents contained therein or related thereto, in accordance with the Plan, on orbefore the Effective Date.I. Modifications to the Plan.10. Pursuant to section 1127 of the Bankruptcy Code, the modifications to thePlan described or set forth in this Combined Order constitute technical or clarifying changes,changes with respect to particular Claims by agreement with holders of such Claims, ormodifications that do not otherwise materially and adversely affect or change the treatment of anyother Claim or Interest under the Plan. These modifications are consistent with the disclosurespreviously made pursuant to the Disclosure Statement and Solicitation Materials, and notice ofthese modifications was adequate and appropriate under the facts and circumstances of the Chapter11 Cases. In accordance with Bankruptcy Rule 3019, these modifications do not require additionaldisclosure under section 1125 of the Bankruptcy Code or the resolicitation of votes under section1126 of the Bankruptcy Code, and they do not require that holders of Claims or Interests beafforded an opportunity to change previously cast acceptances or rejections of the Plan.Accordingly, the Plan is properly before this Court and all votes cast with respect to the Plan priorto such modification shall be binding and shall apply with respect to the Plan.CCaassee 2 244-9-900557755 D Dooccuummeennt t2 29663-2 F Filieledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 8 9 o of f1 133459J. Objections Overruled.11. Any resolution or disposition of objections to Confirmation explained orotherwise ruled upon by the Court on the record at the Confirmation Hearing is herebyincorporated by reference. All unresolved objections, statements, joinders, informal objections,and reservations of rights are hereby overruled on the merits.K. Burden of Proof.12. The Debtors, as proponents of the Plan, have met their burden of provingthe elements of sections 1129(a) and 1129(b) of the Bankruptcy Code by a preponderance of theevidence, the applicable evidentiary standard for Confirmation. Further, the Debtors have proventhe elements of sections 1129(a) and 1129(b) by clear and convincing evidence. Each witness whotestified on behalf of the Debtors in connection with the Confirmation Hearing was credible,reliable, and qualified to testify as to the topics addressed in his testimony.L. Compliance with the Requirements of Section 1129 of the BankruptcyCode.13. The Plan complies with all applicable provisions of section 1129 of theBankruptcy Code as follows:a. Section 1129(a)(1) – Compliance of the Plan with Applicable Provisions of theBankruptcy Code.14. The Plan complies with all applicable provisions of the Bankruptcy Code,including sections 1122 and 1123, as required by section 1129(a)(1) of the Bankruptcy Code.i. Section 1122 and 1123(a)(1) – Proper Classification.15. The classification of Claims and Interests under the Plan is proper under theBankruptcy Code. In accordance with sections 1122(a) and 1123(a)(1) of the Bankruptcy Code,Article III of the Plan provides for the separate classification of Claims and Interests at each Debtorinto Classes, based on differences in the legal nature or priority of such Claims and Interests (otherCaCsaes e2 42-49-09507557 5 D oDcoucmumenetn 2t 9266-32 FFiilleedd iinn TTXXSSBB oonn 1021//3113//2245 PPaaggee 91 0o fo 1f 3143510than Administrative Claims, Professional Fee Claims, and Priority Tax Claims, which areaddressed in Article II of the Plan and Unimpaired, and are not required to be designated asseparate Classes in accordance with section 1123(a)(1) of the Bankruptcy Code). Valid business,factual, and legal reasons exist for the separate classification of the various Classes of Claims andInterests created under the Plan, the classifications were not implemented for any improperpurpose, and the creation of such Classes does not unfairly discriminate between or among holdersof Claims or Interests.16. In accordance with section 1122(a) of the Bankruptcy Code, each Class ofClaims or Interests contains only Claims or Interests substantially similar to the other Claims orInterests within that Class. Accordingly, the Plan satisfies the requirements of sections 1122(a),1122(b), and 1123(a)(1) of the Bankruptcy Codeii. Section 1123(a)(2) – Specifications of Unimpaired Classes.17. Article III of the Plan specifies that Claims and Interests in the classesdeemed to accept the Plan are Unimpaired under the Plan. Holders of Intercompany Claims andIntercompany Interests are either Unimpaired and conclusively presumed to have accepted thePlan, or are Impaired and deemed to reject (the “Deemed Rejecting Classes”) the Plan, and, ineither event, are not entitled to vote to accept or reject the Plan. In addition, Article II of the Planspecifies that Administrative Claims and Priority Tax Claims are Unimpaired, although the Plandoes not classify these Claims. Accordingly, the Plan satisfies the requirements of section1123(a)(2) of the Bankruptcy Code.CCaassee 2 244-9-900557755 D Dooccuummeennt t2 29663-2 F Fileiledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 1 101 o of f1 1334511iii. Section 1123(a)(3) – Specification of Treatment of Voting Classes18. Article III.B of the Plan specifies the treatment of each Voting Class underthe Plan – namely, Class 3 and Class 5. Accordingly, the Plan satisfies the requirements of section1123(a)(3) of the Bankruptcy Code.iv. Section 1123(a)(4) – No Discrimination.19. Article III of the Plan provides the same treatment to each Claim or Interestin any particular Class, as the case may be, unless the holder of a particular Claim or Interest hasagreed to a less favorable treatment with respect to such Claim or Interest. Accordingly, the Plansatisfies the requirements of section 1123(a)(4) of the Bankruptcy Code.v. Section 1123(a)(5) – Adequate Means for Plan Implementation.20. The Plan and the various documents included in the Plan Supplementprovide adequate and proper means for the Plan's execution and implementation, including: (a)the general settlement of Claims and Interests; (b) the restructuring of the Debtors' balance sheetand other financial transactions provided for by the Plan; (c) the consummation of the transactionscontemplated by the Plan, the Lock-Up Agreement, the Restructuring Implementation Deed andthe Agreed Steps Plan and other documents Filed as part of the Plan Supplement; (d) the issuanceof Exchange Notes, the New Money Notes, and the Noteholder Ordinary Shares pursuant to thePlan; (e) the amendment of the Intercreditor Agreement; (f) the amendment of the FacilityAgreement; (g) the amendment of the Senior Secured Term Loan Agreement; (h) theconsummation of the Rights Offering in accordance with the Plan, Rights Offering Documentsand the Lock-Up Agreement; (i) the granting of all Liens and security interests granted orconfirmed (as applicable) pursuant to, or in connection with, the Facility Agreement, the ExchangeNotes Indenture, the New Money Notes Indenture, the amended Intercreditor Agreement and theCCaassee 2 244-9-900557755 D Dooccuummeennt t2 29663-2 F Fileiledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 1 112 o of f1 1334512Senior Secured Term Loan Agreement pursuant to the New Security Documents (including anyLiens and security interests granted or confirmed (as applicable) on the Reorganized Debtors'assets); (j) the vesting of the assets of the Debtors' Estates in the Reorganized Debtors; (k) theconsummation of the corporate reorganization contemplated by the Plan, the Lock-Up Agreement,the Agreed Steps Plan and the Master Reorganization Agreement (as defined in the RestructuringImplementation Deed); and (l) the execution, delivery, filing, or recording of all contracts,instruments, releases, and other agreements or documents in furtherance of the Plan. Accordingly,the Plan satisfies the requirements of section 1123(a)(5) of the Bankruptcy Codevi. Section 1123(a)(6) – Non-Voting Equity Securities.21. The Company's organizational documents in accordance with the SwedishCompanies Act, Ch. 4, Sec 5 and the Plan prohibit the issuance of non-voting securities as of theEffective Date to the extent required to comply with section 1123(a)(6) of the Bankruptcy Code.Accordingly, the Plan satisfies the requirements of section 1123(a)(6) of the Bankruptcy Code.vii. Section 1123(a)(7) – Directors, Officers, and Trustees.22. The manner of selection of any officer, director, or trustee (or any successorto and such officer, director, or trustee) of the Reorganized Debtors will be determined inaccordance with the existing organizational documents, which is consistent with the interests ofcreditors and equity holders and with public policy. Accordingly, the Plan satisfies therequirements of section 1123(a)(7) of the Bankruptcy Code.b. Section 1123(b) – Discretionary Contents of the Plan23. The Plan contains various provisions that may be construed as discretionarybut not necessary for Confirmation under the Bankruptcy Code. Any such discretionary provisionCCaassee 2 244-9-900557755 D Dooccuummeennt t2 29663-2 F Fileiledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 1 123 o of f1 1334513complies with section 1123(b) of the Bankruptcy Code and is not inconsistent with the applicableprovisions of the Bankruptcy Code. Thus, the Plan satisfies section 1123(b).i. Section 1123(b)(1) – Impairment/Unimpairment of Any Class of Claims orInterests24. Article III of the Plan impairs or leaves unimpaired, as the case may be,each Class of Claims or Interests, as contemplated by section 1123(b)(1) of the Bankruptcy Code.ii. Section 1123(b)(2) – Assumption and Rejection of Executory Contracts andUnexpired Leases25. Article V of the Plan provides for the assumption of the Debtors' ExecutoryContracts and Unexpired Leases as of the Effective Date unless such Executory Contract orUnexpired Lease: (a) is identified on the Rejected Executory Contract and Unexpired Lease List;(b) has been previously rejected by a Final Order; (c) is the subject of a motion to reject ExecutoryContracts or Unexpired Leases that is pending on the Confirmation Date; or (4) is subject to amotion to reject an Executory Contract or Unexpired Lease pursuant to which the requestedeffective date of such rejection is after the Effective Date. Thus, the Plan satisfies section1123(b)(2).iii. Compromise and Settlement26. In accordance with section 1123(b)(3)(A) of the Bankruptcy Code andBankruptcy Rule 9019, and in consideration for the distributions and other benefits provided underthe Plan, the provisions of the Plan constitute a good-faith compromise of all Claims, Interests,and controversies relating to the contractual, legal, and subordination rights that all holders ofClaims or Interests may have with respect to any Allowed Claim or Interest or any distribution tobe made on account of such Allowed Claim or Interest. Such compromise and settlement is theproduct of extensive arm's-length, good faith negotiations that, in addition to the Plan, resulted inCCaassee 2 244-9-900557755 D Dooccuummeennt t2 29663-2 F Fileiledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 1 134 o of f1 1334514the execution of the Lock-Up Agreement, which represents a fair and reasonable compromise ofall Claims, Interests, and controversies and entry into which represented a sound exercise of theDebtors' business judgment. Such compromise and settlement is fair, equitable, and reasonableand in the best interests of the Debtors and their Estates.27. The releases of the Debtors' directors and officers are an integral componentof the settlements and compromises embodied in the Plan. The Debtors' directors and officers: (a)made a substantial and valuable contribution to the Debtors' restructuring, including extensive preandpost-Petition Date negotiations with stakeholder groups, and ensured the uninterruptedoperation of the Debtors' businesses during the Chapter 11 Cases; (b) invested significant timeand effort to make the restructuring a success and maximize the value of the Debtors' businessesin a challenging operating environment; (c) attended and, in certain instances, testified atdepositions and Court hearings; (d) attended and participated in numerous stakeholder meetings,management meetings, and board meetings related to the restructuring; (e) are entitled toindemnification from the Debtors under applicable non-bankruptcy law, organizationaldocuments, and agreements; (f) invested significant time and effort in the preparation of the Lock-Up Agreement, the Plan, Disclosure Statement, all supporting analyses, and the numerous otherpleadings Filed in the Chapter 11 Cases, thereby ensuring the smooth administration of the Chapter11 Cases; and (g) are entitled to all other benefits under any employment contracts existing as ofthe Petition Date. Litigation by the Debtors or other Releasing Parties against the Debtors'directors and officers would be a distraction to the Debtors' business and restructuring and woulddecrease rather than increase the value of the estates. The releases of the Debtors' directors andofficers contained in the Plan have the consent of the Debtors and the Releasing Parties and are inthe best interests of the estates.CCaassee 2 244-9-900557755 D Dooccuummeennt t2 29663-2 F Fileiledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 1 145 o of f1 1334515iv. Debtor Release28. The releases of claims and Causes of Action by the Debtors, ReorganizedDebtors, and their Estates described in Article VIII.C of the Plan in accordance with section1123(b) of the Bankruptcy Code (the “Debtor Release”) represent a valid exercise of the Debtors'business judgment under Bankruptcy Rule 9019. The Debtors' or the Reorganized Debtors' pursuitof any such claims against the Released Parties is not in the best interests of the Estates' variousconstituencies because the costs involved would outweigh any potential benefit from pursuingsuch claims. The Debtor Release is fair and equitable and complies with the absolute priority rule.29. The Debtor Release is (a) an integral part of the Plan, and a component ofthe comprehensive settlement implemented under the Plan; (b) in exchange for the good andvaluable consideration provided by the Released Parties; (c) a good faith settlement andcompromise of the claims and Causes of Action released by the Debtor Release; (d) materiallybeneficial to, and in the best interests of, the Debtors, their Estates, and their stakeholders, and isimportant to the overall objectives of the Plan to finally resolve certain Claims among or againstcertain parties in interest in the Chapter 11 Cases; (e) fair, equitable, and reasonable; (f) given andmade after due notice and opportunity for hearing; and (g) a bar to any Debtor asserting any claimor Cause of Action released by the Debtor Release against any of the Released Parties. Theprobability of success in litigation with respect to the released claims and Causes of Action, whenweighed against the costs, supports the Debtor Release. With respect to each of these potentialCauses of Action, the parties could assert colorable defenses and the probability of success isuncertain. The Debtors' or the Reorganized Debtors' pursuit of any such claims or Causes ofAction against the Released Parties is not in the best interests of the Estates or the Debtors' variousCCaassee 2 244-9-900557755 D Dooccuummeennt t2 29663-2 F Fileiledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 1 156 o of f1 1334516constituencies because the costs involved would likely outweigh any potential benefit frompursuing such claims or Causes of Action30. Holders of Claims and Interests entitled to vote have overwhelmingly votedin favor of the Plan, including the Debtor Release. The Plan, including the Debtor Release, wasnegotiated before and after the Petition Date by sophisticated parties represented by able counseland advisors, including the Consenting Creditors. The Debtor Release is therefore the result of ahard fought and arm's-length negotiation process conducted in good faith.31. The Debtor Release appropriately offers protection to parties thatparticipated in the Debtors' restructuring process, including the Consenting Creditors, whoseparticipation in the Chapter 11 Cases is critical to the Debtors' successful emergence frombankruptcy. Specifically, the Released Parties, including the Consenting Creditors, madesignificant concessions and contributions to the Chapter 11 Cases, including, entering into theLock-Up Agreement and related agreements, supporting the Plan and the Chapter 11 Cases, andwaiving or agreeing to impair substantial rights and Claims against the Debtors under the Plan (aspart of the compromises composing the settlement underlying the revised Plan) in order tofacilitate a consensual reorganization and the Debtors' emergence from chapter 11. The DebtorRelease for the Debtors' directors and officers is appropriate because the Debtors' directors andofficers share an identity of interest with the Debtors and, as previously stated, supported and madesubstantial contributions to the success of the Plan, the Chapter 11 Cases, and operation of theDebtors' business during the Chapter 11 Cases, actively participated in meetings, negotiations, andimplementation during the Chapter 11 Cases, and have provided other valuable consideration tothe Debtors to facilitate the Debtors' successful reorganization and continued operation.CCaassee 2 244-9-900557755 D Dooccuummeennt t2 29663-2 F Fileiledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 1 167 o of f1 133451732. The scope of the Debtor Release is appropriately tailored under the factsand circumstances of the Chapter 11 Cases. In light of, among other things, the value provided bythe Released Parties to the Debtors' Estates and the critical nature of the Debtor Release to thePlan, the Debtor Release is appropriate.v. Release by Holders of Claims and Interests33. The release by the Releasing Parties (the “Third-Party Release”), set forthin Article VIII.D of the Plan, is an essential provision of the Plan. The Third-Party Release is: (a)consensual as to those Releasing Parties that did not specifically and timely object or properly optout from the Third-Party Release; (b) within the jurisdiction of the Bankruptcy Court pursuant to28 U.S.C. § 1334; (c) in exchange for the good and valuable consideration provided by theReleased Parties; (d) a good faith settlement and compromise of the claims and Causes of Actionreleased by the Third-Party Release; (e) materially beneficial to, and in the best interests of, theDebtors, their Estates, and their stakeholders, and is important to the overall objectives of the Planto finally resolve certain Claims among or against certain parties in interest in the Chapter 11Cases; (f) fair, equitable, and reasonable; (g) given and made after due notice and opportunity forhearing; (h) appropriately narrow in scope given that it expressly excludes, among other things,any Cause of Action that is judicially determined by a Final Order to have constituted actual fraud,willful misconduct, or gross negligence; (i) a bar to any of the Releasing Parties asserting anyclaim or Cause of Action released by the Third-Party Release against any of the Released Parties;and (j) consistent with sections 105, 524, 1123, 1129, and 1141 and other applicable provisions ofthe Bankruptcy Code.34. The Third-Party Release is an integral part of the agreement embodied inthe Plan among the relevant parties in interest. Like the Debtor Release, the Third-Party ReleaseCCaassee 2 244-9-900557755 D Dooccuummeennt t2 29663-2 F Fileiledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 1 178 o of f1 1334518facilitated participation in both the Debtors' Plan and the chapter 11 process generally. The Third-Party Release is instrumental to the Plan and was critical in incentivizing parties to support thePlan and preventing significant and time-consuming litigation regarding the parties' respectiverights and interests. The Third-Party Release was a core negotiation point in connection with thePlan and instrumental in developing the Plan that maximized value for all of the Debtors'stakeholders and kept the Debtors intact as a going concern. As such, the Third-Party Releaseappropriately offers certain protections to parties who constructively participated in the Debtors'restructuring process—including the Consenting Creditors (as set forth above)—by, among otherthings, facilitating the negotiation and consummation of the Plan, supporting the Plan and, in thecase of the Backstop Providers, committing to provide new capital to facilitate the Debtors'emergence from chapter 11. Specifically, the Notes Ad Hoc Group proposed and negotiated thepari passu transaction that is the basis of the restructuring proposed under the Plan and provideda much-needed deleveraging to the Debtors' business while taking a discount on their Claims (inexchange for other consideration).35. Furthermore, the Third-Party Release is consensual as to all parties ininterest, including all Releasing Parties, and such parties in interest were provided notice of thechapter 11 proceedings, the Plan, the deadline to object to confirmation of the Plan, and theCombined Hearing and were properly informed that all holders of Claims against or Interests inthe Debtors that did not file an objection with the Court in the Chapter 11 Cases that included anexpress objection to the inclusion of such holder as a Releasing Party under the provisionscontained in Article VIII of the Plan would be deemed to have expressly, unconditionally,generally, individually, and collectively consented to the release and discharge of all claims andCauses of Action against the Debtors and the Released Parties. Additionally, the release provisionsCCaassee 2 244-9-900557755 D Dooccuummeennt t2 29663-2 F Fileiledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 1 189 o of f1 1334519of the Plan were conspicuous, emphasized with boldface type in the Plan, the DisclosureStatement, the Ballots, and the applicable notices. Except as set forth in the Plan, all ReleasingParties were properly informed that unless they (a) checked the “opt out” box on the applicableBallot or opt-out form and returned the same in advance of the Voting Deadline, as applicable, or(b) timely Filed an objection to the releases contained in the Plan that was not resolved beforeentry of this Confirmation Order, they would be deemed to have expressly consented to the releaseof all Claims and Causes of Action against the Released Parties.36. The Ballots sent to all holders of Claims and Interests entitled to vote, aswell as the notice of the Combined Hearing sent to all known parties in interest (including thosenot entitled to vote on the Plan), unambiguously provided in bold letters that the Third-PartyRelease was contained in the Plan.37. The scope of the Third-Party Release is appropriately tailored under thefacts and circumstances of the Chapter 11 Cases, and parties in interest received due and adequatenotice of the Third-Party Release. Among other things, the Plan provides appropriate and specificdisclosure with respect to the claims and Causes of Action that are subject to the Third-PartyRelease, and no other disclosure is necessary. The Debtors, as evidenced by the VotingDeclaration and Certificate of Publication, including by providing actual notice to all knownparties in interest, including all known holders of Claims against, and Interests in, any Debtor andpublishing notice in international and national publications for the benefit of unknown parties ininterest, provided sufficient notice of the Third-Party Release, and no further or other notice isnecessary. The Third-Party Release is designed to provide finality for the Debtors, theReorganized Debtors and the Released Parties regarding the parties' respective obligations underthe Plan. For the avoidance of doubt, and notwithstanding anything to the contrary, anyparty who timely opted-out of the Third-Party Release is not bound by the Third-PartyRelease.CCaassee 2 244-9-900557755 D Dooccuummeennt t2 29663-2 F Fileiledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 1 290 o of f1 133452038. The Third-Party Release is specific in language, integral to the Plan, andgiven for substantial consideration. The Releasing Parties were given due and adequate notice ofthe Third-Party Release, and thus the Third-Party Release is consensual under controllingprecedent as to those Releasing Parties that did not specifically and timely object. In light of,among other things, the value provided by the Released Parties to the Debtors' Estates and theconsensual and critical nature of the Third-Party Release to the Plan, the Third-Party Release isappropriatevi. Exculpation.39. The exculpation described in Article VIII.E of the Plan (the “Exculpation”)is appropriate under applicable law, including In re Highland Capital Mgmt., L.P., 48 F. 4th 419(5th Cir. 2022), because it was supported by proper evidence, proposed in good faith, wasformulated following extensive good-faith, arm's-length negotiations with key constituents, and isappropriately limited in scope.40. No Entity or Person may commence or continue any action, employ anyprocess, or take any other act to pursue, collect, recover or offset any Claim, Interest, debt,obligation, or Cause of Action relating or reasonably likely to relate to any act or commission inconnection with, relating to, or arising out of a Covered Matter (including one that alleges theactual fraud, gross negligence, or willful misconduct of a Covered Entity), unless expresslyauthorized by the Bankruptcy Court after (1) it determines, after a notice and a hearing, such Claim,Interest, debt, obligation, or Cause of Action is colorable and (2) it specifically authorizes suchEntity or Person to bring such Claim or Cause of Action. The Bankruptcy Court shall have soleand exclusive jurisdiction to determine whether any such Claim, Interest, debt, obligation or Causeof Action is colorable and, only to the extent legally permissible and as provided for in Article XI,CCaassee 2 244-9-900557755 D Dooccuummeennt t2 29663-2 F Fileiledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 2 201 o of f1 1334521shall have jurisdiction to adjudicate such underlying colorable Claim, Interest, debt, obligation, orCause of Action.vii. Injunction.41. The injunction provisions set forth in Article VIII.F of the Plan are essentialto the Plan and are necessary to implement the Plan and to preserve and enforce the discharge,Debtor Release, the Third-Party Release, and the Exculpation provisions in Article VIII of thePlan. The injunction provisions are appropriately tailored to achieve those purposes.viii. Preservation of Claims and Causes of Action.42. Article IV.L of the Plan appropriately provides for the preservation by theDebtors of certain Causes of Action in accordance with section 1123(b) of the Bankruptcy Code.Causes of Action not released by the Debtors or exculpated under the Plan will be retained by theReorganized Debtors as provided by the Plan. The Plan is sufficiently specific with respect to theCauses of Action to be retained by the Debtors, and the Plan and Plan Supplement providemeaningful disclosure with respect to the potential Causes of Action that the Debtors may retain,and all parties in interest received adequate notice with respect to such retained Causes of Action.The provisions regarding Causes of Action in the Plan are appropriate and in the best interests ofthe Debtors, their respective Estates, and holders of Claims or Interests. For the avoidance of anydoubt, Causes of Action released or exculpated under the Plan will not be retained by theReorganized Debtors.c. Section 1123(d) – Cure of Defaults43. Article V.D of the Plan provides for the satisfaction of Cure Claimsassociated with each Executory Contract and Unexpired Lease to be assumed in accordance withsection 365(b)(1) of the Bankruptcy Code. Any monetary defaults under each assumed ExecutoryCCaassee 2 244-9-900557755 D Dooccuummeennt t2 29663-2 F Fileiledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 2 212 o of f1 1334522Contract or Unexpired Lease shall be satisfied, pursuant to section 365(b)(1) of the BankruptcyCode, by payment of the default amount in Cash on the Effective Date, subject to the limitationsdescribed in Article V.D of the Plan, or on such other terms as the parties to such ExecutoryContracts or Unexpired Leases may otherwise agree. Any Disputed Cure Amounts will bedetermined in accordance with the procedures set forth in Article V.D of the Plan, and applicablebankruptcy and nonbankruptcy law. As such, the Plan provides that the Debtors will Cure, orprovide adequate assurance that the Debtors will promptly Cure, defaults with respect to assumedExecutory Contracts and Unexpired Leases in accordance with section 365(b)(1) of theBankruptcy Code. Thus, the Plan complies with section 1123(d) of the Bankruptcy Code.d. Section 1129(a)(2) – Compliance of the Debtors and Others with the ApplicableProvisions of the Bankruptcy Code.44. The Debtors, as proponents of the Plan, have complied with all applicableprovisions of the Bankruptcy Code as required by section 1129(a)(2) of the Bankruptcy Code,including sections 1122, 1123, 1124, 1125, 1126, and 1128, and Bankruptcy Rules 3017, 3018,and 3019.e. Section 1129(a)(3) – Proposal of Plan in Good Faith.45. The Debtors have proposed the Plan in good faith, in accordance with theBankruptcy Code requirements, and not by any means forbidden by law. In determining that thePlan has been proposed in good faith, the Court has examined the totality of the circumstancesfiling of the Chapter 11 Cases, including the formation of Intrum AB of Texas LLC (“IntrumTexas”), the Plan itself, and the process leading to its formulation. The Debtors' good faith isevident from the facts and record of the Chapter 11 Cases, the Disclosure Statement, and the recordof the Combined Hearing and other proceedings held in the Chapter 11 CasesCCaassee 2 244-9-900557755 D Dooccuummeennt t2 29663-2 F Fileiledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 2 223 o of f1 133452346. The Plan (including the Plan Supplement and all other documents necessaryto effectuate the Plan) is the product of good faith, arm's-length negotiations by and among theDebtors, the Debtors' directors and officers and the Debtors' key stakeholders, including theConsenting Creditors and each of their respective professionals. The Plan itself and the processleading to its formulation provide independent evidence of the Debtors' and such other parties'good faith, serve the public interest, and assure fair treatment of holders of Claims or Interests.Consistent with the overriding purpose of chapter 11, the Debtors Filed the Chapter 11 Cases withthe belief that the Debtors were in need of reorganization and the Plan was negotiated and proposedwith the intention of accomplishing a successful reorganization and maximizing stakeholder value,and for no ulterior purpose. Accordingly, the requirements of section 1129(a)(3) of the BankruptcyCode are satisfied.f. Section 1129(a)(4) – Court Approval of Certain Payments as Reasonable.47. Any payment made or to be made by the Debtors, or by a person issuingsecurities or acquiring property under the Plan, for services or costs and expenses in connectionwith the Chapter 11 Cases, or in connection with the Plan and incident to the Chapter 11 Cases,has been approved by, or is subject to the approval of, the Court as reasonable. Accordingly, thePlan satisfies the requirements of section 1129(a)(4).g. Section 1129(a)(5)—Disclosure of Directors and Officers and Consistency with theInterests of Creditors and Public Policy.48. The identities of or process for appointment of the Reorganized Debtors'directors and officers proposed to serve after the Effective Date were disclosed in the PlanSupplement in advance of the Combined Hearing. Accordingly, the Debtors have satisfied therequirements of section 1129(a)(5) of the Bankruptcy Code.CCaassee 2 244-9-900557755 D Dooccuummeennt t2 29663-2 F Fileiledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 2 234 o of f1 1334524h. Section 1129(a)(6)—Rate Changes.49. The Plan does not contain any rate changes subject to the jurisdiction of anygovernmental regulatory commission and therefore will not require governmental regulatoryapproval. Therefore, section 1129(a)(6) of the Bankruptcy Code does not apply to the Plan.i. Section 1129(a)(7)—Best Interests of Holders of Claims and Interests.50. The liquidation analysis attached as Exhibit D to the Disclosure Statementand the other evidence in support of the Plan that was proffered or adduced at the CombinedHearing, and the facts and circumstances of the Chapter 11 Cases are (a) reasonable, persuasive,credible, and accurate as of the dates such analysis or evidence was prepared, presented orproffered; (b) utilize reasonable and appropriate methodologies and assumptions; (c) have not beencontroverted by other evidence; and (d) establish that each holder of Allowed Claims or Interestsin each Class will recover as much or more value under the Plan on account of such Claim orInterest, as of the Effective Date, than the amount such holder would receive if the Debtors wereliquidated on the Effective Date under chapter 7 of the Bankruptcy Code or has accepted the Plan.As a result, the Debtors have demonstrated that the Plan is in the best interests of their creditorsand equity holders and the requirements of section 1129(a)(7) of the Bankruptcy Code are satisfied.j. Section 1129(a)(8)—Conclusive Presumption of Acceptance by UnimpairedClasses; Acceptance of the Plan by Certain Voting Classes.51. The classes deemed to accept the Plan are Unimpaired under the Plan andare deemed to have accepted the Plan pursuant to section 1126(f) of the Bankruptcy Code. EachVoting Class voted to accept the Plan. For the avoidance of doubt, however, even if section1129(a)(8) has not been satisfied with respect to all of the Debtors, the Plan is confirmable becausethe Plan does not discriminate unfairly and is fair and equitable with respect to the Voting Classesand thus satisfies section 1129(b) of the Bankruptcy Code with respect to such Classes as describedCCaassee 2 244-9-900557755 D Dooccuummeennt t2 29663-2 F Fileiledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 2 245 o of f1 1334525further below. As a result, the requirements of section 1129(b) of the Bankruptcy Code are alsosatisfied.k. Section 1129(a)(9)—Treatment of Claims Entitled to Priority Pursuant to Section507(a) of the Bankruptcy Code.52. The treatment of Administrative Claims, Professional Fee Claims, andPriority Tax Claims under Article II of the Plan satisfies the requirements of, and complies in allrespects with, section 1129(a)(9) of the Bankruptcy Code.l. Section 1129(a)(10)—Acceptance by at Least One Voting Class.53. As set forth in the Voting Declaration, all Voting Classes overwhelminglyvoted to accept the Plan. As such, there is at least one Voting Class that has accepted the Plan,determined without including any acceptance of the Plan by any insider (as defined by theBankruptcy Code), for each Debtor. Accordingly, the requirements of section 1129(a)(10) of theBankruptcy Code are satisfied.m. Section 1129(a)(11)—Feasibility of the Plan.54. The Plan satisfies section 1129(a)(11) of the Bankruptcy Code. Thefinancial projections attached to the Disclosure Statement as Exhibit D and the other evidencesupporting the Plan proffered or adduced by the Debtors at or before the Combined Hearing: (a)is reasonable, persuasive, credible, and accurate as of the dates such evidence was prepared,presented, or proffered; (b) utilize reasonable and appropriate methodologies and assumptions; (c)has not been controverted by other persuasive evidence; (d) establishes that the Plan is feasibleand Confirmation of the Plan is not likely to be followed by liquidation or the need for furtherfinancial reorganization; (e) establishes that the Debtors will have sufficient funds available tomeet their obligations under the Plan and in the ordinary course of business—including sufficientamounts of Cash to reasonably ensure payment of Allowed Claims that will receive CashCCaassee 2 244-9-900557755 D Dooccuummeennt t2 29663-2 F Fileiledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 2 256 o of f1 1334526distributions pursuant to the terms of the Plan and other Cash payments required under the Plan;and (f) establishes that the Debtors or the Reorganized Debtors, as applicable, will have thefinancial wherewithal to pay any Claims that accrue, become payable, or are allowed by FinalOrder following the Effective Date. Accordingly, the Plan satisfies the requirements of section1129(a)(11) of the Bankruptcy Code.n. Section 1129(a)(12)—Payment of Statutory Fees.55. Article XII.C of the Plan provides that all fees payable pursuant to section1930(a) of the Judicial Code, as determined by the Court at the Confirmation Hearing inaccordance with section 1128 of the Bankruptcy Code, will be paid by each of the applicableReorganized Debtors for each quarter (including any fraction of a quarter) until the Chapter 11Cases are converted, dismissed, or closed, whichever occurs first. Accordingly, the Plan satisfiesthe requirements of section 1129(a)(12) of the Bankruptcy Code.o. Section 1129(a)(13)—Retiree Benefits.56. Pursuant to section 1129(a)(13) of the Bankruptcy Code, and as provided inArticle IV.K of the Plan, the Reorganized Debtors will continue to pay all obligations on accountof retiree benefits (as such term is used in section 1114 of the Bankruptcy Code) on and after theEffective Date in accordance with applicable law. As a result, the requirements of section1129(a)(13) of the Bankruptcy Code are satisfied.p. Sections 1129(a)(14), (15), and (16)—Domestic Support Obligations, Individuals,and Nonprofit Corporations.57. The Debtors do not owe any domestic support obligations, are notindividuals, and are not nonprofit corporations. Therefore, sections 1129(a)(14), 1129(a)(15), and1129(a)(16) of the Bankruptcy Code do not apply to the Chapter 11 Cases.CCaassee 2 244-9-900557755 D Dooccuummeennt t2 29663-2 F Fileiledd i nin T TXXSSBB o onn 1 021/3/113/2/245 P Paaggee 2 267 o of f1 1334527q. Section 1129(b)—Confirmation of the Plan Over Nonacceptance of VotingClasses.58. No Classes rejected the Plan, and section 1129(b) is not applicable here,but even if it were, the Plan may be confirmed pursuant to section 1129(b)(1) of the BankruptcyCode because the Plan is fair and equitable with respect to the Deemed Rejecting Classes. ThePlan has been proposed in good faith, is reasonable, and meets the requirements and all VotingClasses have voted to accept the Plan. The treatment of Intercompany Claims and IntercompanyInterests under the Plan provides for administrative convenience does not constitute a distributionunder the Plan on account of suc

In this episode of the Concrete Logic Podcast, host Seth Tandett is joined by Rich Szecsy and Dr. Jon Belkowitz to discuss the recently released ACI 323 code on low carbon concrete. The trio dig into the significance of the code, the confusion surrounding its implementation, and the challenges it poses for ready-mix producers and construction practices. The hosts explore the implications of the new code on concrete pumping, the role of authorities in code adoption, and the need for future updates to adapt to evolving industry standards. The episode concludes with reflections on the potential impact of the code and the importance of ongoing dialogue in the concrete industry. Takeaways ACI 323 represents a significant shift in concrete standards. The code's implementation may create confusion for industry professionals. Ready-mix producers face challenges in meeting new low carbon requirements. There is a need for clarity on the authority of jurisdiction in code adoption. Frequent updates to the code will be necessary as more data becomes available. The relationship between contractors and ready-mix suppliers is crucial for compliance. Concrete pumping practices may be adversely affected by the new standards. Policymakers will likely default to adopting ACI 323 without fully understanding its implications. Ongoing discussions are essential to navigate the complexities of low carbon concrete. Chapters 00:00 Introduction to the Concrete Logic Podcast 03:17 Overview of ACI 323 and Its Significance 06:47 Confusion Surrounding Low Carbon Concrete Standards 09:21 Challenges in the Concrete Supply Chain 12:51 The Role of Authorities in Code Adoption 20:42 Impact of Low Carbon Concrete on Local Regulations 28:35 Future Updates and Adaptations of ACI 323 30:01 The Need for Frequent Updates in Concrete Codes 32:02 The Evolution of Low Carbon Concrete Standards 33:50 Challenges in Concrete Production and Compliance 38:55 Confusion Surrounding Concrete Codes and Specifications 48:59 The Impact of Policy on Concrete Standards 51:58 Looking Ahead: Future of Concrete Codes and Practices*** Did you learn something from this episode? Would you like to support the concrete industry's favorite podcast? If so, donate at https://www.concretelogicpodcast.com/support/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ . When YOU donate to the show, you will be listed as a producer of the next episode that is released! Join the Concrete Logic Academy! Enhance your learning from our podcast with engaging quizzes that test your knowledge and help you earn Professional Development Hours (PDHs). Support Concrete Logic and take your education to the next level!

In June 2024, TTI's Roadside Safety and Physical Security Team crashed a Tesla Model 3 electric vehicle (EV) into a heavy-duty guardrail at 62 miles per hour. When the EV blew right through the barrier, researchers were stunned. TTI Senior Research Engineer Roger Bligh, whose 38 years of roadside safety barrier testing experience oversaw the test, joins guest host and TTI Agency Director Greg Winfree to discuss the results of the testing and the broader implications for standards governing the development and deployment of roadside safety devices. | View the Crash Test

Welcome to the last episode of 2024 where hosts Trey and Mike Farley provide practical insights into designing and bringing to life a backyard paradise, discuss the difference between conceptual and working plans, detailing specifications, and highlighting the importance of comprehensive planning to avoid costly change orders. The episode also reviews key lessons from past projects and emphasizes the value of detailed planning in creating luxury outdoor spaces. Through their thorough discussion, homeowners can understand the various bidding processes, the importance of specifications, and the potential pitfalls in pool and outdoor living construction. Special segments on outdoor kitchen maintenance and reflections on notable episodes from 2024 add a rich layer of practical advice and entertainment. Please follow us on YouTube to see the Videos, BBQ Bits segment and other features of the episodes. https://www.youtube.com/@PoolsidePerspectivesPodcast You can also follow us on Instagram to see pics, snippets and catch previews of episodes: https://www.instagram.com/poolsideperspectivespodcast/   00:00 Introduction to Poolside Perspectives 01:08 End of Year Reflections and Upcoming Plans 02:38 The Importance of Having a Plan 03:10 Conceptual Plans vs. Working Drawings 07:38 The Role of Specifications in Pool Building 08:07 Challenges in Pool Building Bids 17:57 BBQ Bits: Cleaning Tips 19:29 Understanding the Value of Detailed Plans 22:18 The Role of Salespeople in Project Documentation 23:16 Importance of Detailed Plans and Specifications 24:34 Engineering and Permits: A Necessary Step 25:42 The Layout Meeting: Ensuring Clarity Before Construction 27:34 Transparency in Pricing and Its Long-Term Benefits 30:32 Common Pitfalls in Pool Construction 38:26 The Value of Comprehensive Planning 40:42 Reflections on 2024 and Looking Ahead 44:23 Encouraging Industry Growth and Knowledge Sharing 46:31 Conclusion and Future Goals    

In this episode of the Concrete Logic Podcast, Seth Tandett interviews Colin Lobo, the Executive Vice President and Division Head of Engineering at NRMCA. They delve into the differences between prescriptive and performance specifications in concrete, discussing the implications of each on responsibility, compliance, and industry practices. Colin explains the evolution from prescriptive to performance specifications, the challenges of hybrid specifications, and the importance of accurate documentation in concrete mixing. The conversation highlights the challenges faced in job site testing, the importance of density measurement, and the need for improved testing standards to ensure safety and sustainability. The discussion also touches on the shift towards performance-based specifications and the confidentiality issues surrounding mix designs.Takeaways • Prescriptive specifications dictate how to mix concrete. • Performance specifications focus on the desired outcomes. • Responsibility shifts to the concrete producer with performance specs. • Hybrid specifications can create contradictions in requirements. • Water quality is a significant concern in concrete mixing. • Testing specimens often get compromised, affecting strength measurements. • Current testing standards are inadequate and need improvement. • Sustainability efforts could be increasing the carbon footprint of concrete. • Industry standards must evolve to reflect practical realities. • Collaboration is needed to improve testing and standards. • Engagement in standards committees is vital for industry progress. Chapters 00:00 Introduction to Concrete Specifications 03:25 Understanding Prescriptive vs Performance Specifications 07:30 The Shift in Responsibility 09:50 Hybrid Specifications and Their Challenges 11:46 The Role of Legal in Specification Acceptance 13:24 Concrete Producer's Perspective on Specifications 15:09 Documenting Compliance in Concrete Mixing 16:40 Typical Prescriptive Requirements 19:24 Evolution from Prescriptive to Performance Specifications 21:20 Challenges in Concrete Testing 24:29 Mix Design and Performance Expectations 27:27 The Importance of Density Measurement 29:52 Addressing Testing Standards and Sustainability 32:19 Evolving Towards Performance-Based Specifications 35:18 Confidentiality and Industry Standards***Did you learn something from this episode? Would you like to support the concrete industry's favorite podcast? If so, donate at https://www.concretelogicpodcast.com/support/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ . When YOU donate to the show, you will be listed as a producer of the next episode that is released! Join the Concrete Logic Academy! Enhance your learning from our podcast with engaging quizzes that test your knowledge and help you earn Professional Development Hours (PDHs). Support Concrete Logic and take your education to the next level!

Guy Podjarny is the founder of Tessl - a startup that is rethinking how we build software.Guy previously founded Snyk - a dependency scanning tool worth billions of dollars. Before Snyk, Guy founded Blaze, which he sold to Akamai.This episode is brought to you by WorkOS. If you're thinking about selling to enterprise customers, WorkOS can help you add enterprise features like Single Sign On and audit logs. In this conversation, we talk about the future of programming and the future of DevTools. The future of programming will focus on writing specifications.Trust in AI toolsSnyk is an example of how tools can integrate into existing workflows.Code can become disposable, allowing for flexibility in development.Specifications will serve as repositories of truth in software development.Developers will need to adapt their skills to leverage AI tools effectively.Community collaboration is essential for the evolution of AI development tools.AI simplifies and democratizes the process of software creationThanks to Anna Debenham for making this happen. 

As Russian artist, Wassily Kandinsky, said: “Colour is a power which directly influences the soul.” As designers of retirement, care or dementia facilities we know that some older people may spend a great deal of time indoors, therefore colour and associated finishes become a critical tool in the development of uplifting and enjoyable environments. Join Lori and her guests Tony Westgarth and Dawn Scott from Akzo Nobel, one of the world's largest paint companies, as they discuss paint colour palettes and finishes recommended for older people…and why! For links to resources related to this episode, please visit us at thirdage.design/s5e01 - and while you're there, hit the Join Us button! We'll show our thanks for your interest by sending you our periodic, exclusive - and free! - TAD Extra.

World Oil sat down with Hamza Hallal, Senior Manager, Monogram/APIQR, American Petroleum Institute (API), to discuss API's Monogram Program, and how the association monitors and engages with users to ensure that they are following API standards and specifications.

Join us as we chat with Erick Gama, a strategic RFP specialist at BOS in Chicago, about his unique journey in the design world. From his college days studying interior design to becoming an integral part of a specialized response team, Eric shares how he carved out his career path. He opens up about the challenges of working on RFPs, the lessons he's learned along the way, and his advice for emerging designers eager to make their mark. Eric's story is a testament to the power of teamwork, personal growth, and staying open to unexpected opportunities in the design industry.Sign up for The Design POP's Monthly webinar as we continue to learn existing design technologies and explore new ones too! https://www.thedesignpop.com/webinarThe Design Pop is an Imagine a Place Production (presented by OFS)Connect with Alexandra on LinkedInFollow The Design Pop on LinkedInConnect with Alexandra Tseffos and The Design Pop

Check out Elecosoft here: https://elecosoft.com/us/Follow Daniel here

Follow Sadanand hereCheck out ConstructivIQ here: https://constructiviq.com/ 

In this episode, Steve talks with Farhad Sadeghi, the founder and lead polymer scientist at Analytical Polymers. They dive deep into the world of biomedical balloon tubing and explore the nuances of non-compliant, semi-compliant, and compliant balloons. Farhad sheds light on why precise tube sizing is essential for optimal performance and then gets in to how factors like resin selection, extrusion techniques, the balloon-forming process, and tensile specification can affect balloon tubing.Host/ Producer: Steve Maxson | Innovation & Business Development Manager | US ExtrudersGuest: Farhad Sadeghi| Founder and Lead Polymer Scientist| Analytical PolymersAnnouncer: Bill Kramer | President | US ExtrudersEditor/ Original Music: Eric Adair | Marketing/ Business Development | US ExtrudersFor video episodes visitwww.us-extruders.com/podcasts

In this episode of the Concrete Logic Podcast, Seth and Dr. Jon Belkowitz delve into the complexities of cement testing, particularly focusing on Type 1L cement and the challenges posed by blended cements. They discuss the importance of establishing a proactive quality management system to ensure the integrity of concrete mixes, emphasizing the need for rigorous testing and quality control measures. The conversation highlights the financial implications of poor quality control and the potential for significant cost savings through proactive measures. Dr. Jon shares insights from his experiences in the industry, advocating for a shift towards more reliable testing practices to enhance the overall quality of concrete production. Takeaways Quality management systems are essential for concrete producers. Type 1L cement is often misunderstood in the industry. Blended cements can lead to unexpected challenges. Proactive testing can prevent costly mistakes. Understanding ASTM standards is crucial for compliance. Quality control can significantly reduce legal liabilities. Investing in quality management can save money in the long run. Communication between teams is vital for quality assurance. Testing frequency should increase with new cement deliveries. The concrete industry must adapt to changing materials and standards. Chapters 00:00 Introduction and Podcast Support 02:22 Donations and Guest Suggestions 08:35 Testing Cement: Ensuring Quality and Specifications 12:09 Understanding the Differences: Type 1L Cement vs. Type 1 Cement 19:58 The Need for a Quality Management System in the Concrete Industry 21:52 Implementing a Vetting Process for Cement: Benefits and Challenges 27:27 Testing Methods and Resources 36:17 The misconception of already doing quality control 41:33 The potential cost savings of proactive quality control 45:31 Avoiding issues by investing in proactive quality control 47:15 The simple steps to improve quality control 49:19 Conclusion and invitation to further discussion***Did you learn something from this episode? Would you like to support the concrete industry's favorite podcast? If so, donate at https://www.concretelogicpodcast.com/support/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ . When YOU donate to the show, you will be listed as a producer of the next episode that is released!***Episode References Guest: Dr. Jon Belkowitz | Intelligent Concrete | Jon@intelligent-concrete.com Guest Website:⁠ https://www.intelligent-concrete.com/Producers: Jodi Tandett Donate & Become a Producer: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.concretelogicpodcast.com/support/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Music: Mike Dunton | ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.mikeduntonmusic.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠mikeduntonmusic@gmail.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | Instagram ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠@Mike_Dunton⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Host: Seth Tandett, ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠seth@concretelogicpodcast.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Host LinkedIn: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/seth-tandett/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Website: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.concretelogicpodcast.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ LinkedIn: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/company/concrete-logic-podcast*** Elevate your concrete expertise and join a community of passionate professionals who drive industry innovation at the Concrete Logic Academy! Learn more at https://www.concretelogicacademy.com/***

Welcome to a new episode of Get Creative! In this episode, we delve into a compelling real estate strategy that netted a $300,000 return simply by connecting the right people. Join Pace as he breaks down a recent deal involving a 1031 exchange and explains how aligning resources and networking within the real estate community can lead to significant profits. Whether you're a seasoned investor or new to the field, this story offers invaluable insights into creative finance and real estate investment.   Highlights: "The key to massive profits in real estate is not just finding deals, but creating them." "If you're not learning how to solve problems for others, you're leaving money on the table." "1031 exchanges can be complex, but they're gold mines if you know how to navigate them."  "Investing in yourself and learning to connect the dots will set you apart in any business."    Timestamps: 00:00 - Introduction: The Potential of Creative Real Estate  00:31 - Discussing Client Needs with Olivia  01:06 - Pace's Community and Experience with Single Family Homes  02:01 - Challenges of 1031 Exchanges  03:07 - Discussing the Financial Aspects of the Deal  04:17 - Specifications on Property Requirements  06:15 - Strategy for Finding Deals Outside of MLS  07:40 - Structuring Wholesale Deals Creatively  09:49 - The Importance of Being a Deal Finder  12:25 - Closing Remarks: The Power of Networking and Making Money in Real Estate   ► Join The Subto Community & Learn Creative Finance Directly from Pace:  https://paceapproves.com/subto-gc    ► Want to Become a Private Money Lender? Join Us For The Upcoming LIVE Training this Saturday to Learn How to Lend Money on Real Estate Deals: http://joingatortribe.com/yt    ► Join Our Free Facebook Group to Connect with Pace and his Students: https://paceapproves.com/freefb-yt    ► Become a Top Tier Transaction Coordinator and Make Money Doing The Paperwork For Real Estate Transactions: https://paceapproves.com/tttc-gc    ► Listen To Pace and His Students Share Insider Secrets To Real Estate Investor Success: https://getcreativepodcast.com/    PLUG IN & SUBSCRIBE Instagram: https://www.instagram.com/pacemorby/  TikTok: https://www.tiktok.com/@pacemorby 

In this episode of the Mr. Beacon podcast, Damon Barnes from Bluetooth SIG discusses the groundbreaking features of Bluetooth Core Specification version 6.0, including channel sounding, which offers precise range finding with centimeter-level accuracy. Learn how this innovation, along with other Bluetooth Core Specification version 6.0 updates, is set to transform industries like automotive and IoT, enabling accurate, cost-effective distance measurement. A must-listen for tech enthusiasts and anyone curious about the future of Bluetooth and wireless communication.Damon's Favorite Songs:“Exile” by Taylor Swift (feat. Bon Iver): https://www.youtube.com/watch?v=osdoLjUNFnA“Bleeding Out” by Imagine Dragons: https://www.youtube.com/watch?v=QFKHScAStsU“Start Me Up” by The Rolling Stones: https://www.youtube.com/watch?v=7JR10AThY8M Hosted on Acast. See acast.com/privacy for more information.

Check out Mancini Duffy on Linkedin hereFollow Bill Mandara hereCheck out Mancini Duffy's website: https://manciniduffy.com/

Check out Phil here: https://getphil.app/Follow Bryan here: https://www.linkedin.com/in/bryankerr/ 

Today we are joined by Susan Fasoli. In addition to being an active member of AOTA and the American Congress of Rehabilitation Medicine, Susan is a Professor Emerita of occupational therapy at MGH institute of health professions where she has conducted, published, and disseminated research related to robot assisted therapy and cognitive skills training, the importance of interprofessional collaboration, and the rehabilitation treatment specification system (RTSS). She shares information related to RTSS and gives recommendations on how students, practitioners, educators, and researchers can enhance their practice by applying the RTSS.  Additional Resources: American Congress of Rehabilitation Medicine: Improving Lives Through Interdisciplinary Rehabilitation Research | ACRM ACRM Rehabilitation Treatment Specification Networking Group (RTS-NG)  Follow ACRM on X at @ACRMRTS

JVM summit, virtual threads, stacks applicatives, licences, déterminisme et LLMs, quantification, deux outils de l'épisode et bien plus encore. Enregistré le 13 septembre 2024 Téléchargement de l'épisode LesCastCodeurs-Episode–315.mp3 News Langages Netflix utilise énormément Java et a rencontré un problème avec les Virtual Thread dans Java 21. Les ingénieurs de Netflix analysent ce problème dans cet article : https://netflixtechblog.com/java–21-virtual-threads-dude-wheres-my-lock–3052540e231d Les threads virtuels peuvent améliorer les performances mais posent des défis. Un problème de locking a été identifié : les threads virtuels se bloquent mutuellement. Cela entraîne des performances dégradées et des instabilités. Netflix travaille à résoudre ces problèmes et à tirer pleinement parti des threads virtuels. Une syntax pour indiquer qu'un type est nullable ou null-restricted arriverait dans Java https://bugs.openjdk.org/browse/JDK–8303099 Foo! interdirait null Foo? indiquerait que null est accepté Foo?[]! serait un tableau non-null de valeur nullable Il y a aussi des idées de syntaxe pour initialiser les tableaux null-restricted JEP: https://openjdk.org/jeps/8303099 Les vidéos du JVM Language Summit 2024 sont en ligne https://www.youtube.com/watch?v=OOPSU4LnKg0&list=PLX8CzqL3ArzUEYnTa6KYORRbP3nhsK0L1 Project Leyden Update Project Babylon - Code Reflection Valhalla - Where Are We? An Opinionated Overview on Static Analysis for Java Rethinking Java String Concatenation Code Reflection in Action - Translating Java to SPIR-V Java in 2024 Type Specialization of Java Generics - What If Casts Have Teeth ? (avec notre Rémi Forax national !) aussi tip or tail pour tout l'ecosysteme quelques liens sur Babylon: Code reflection pour exprimer des langages etranger (SQL) dans Java: https://openjdk.org/projects/babylon/ et sont example en emulation de LINQ https://openjdk.org/projects/babylon/articles/linq Librairies Micronaut sort sa version 4.6 https://micronaut.io/2024/08/26/micronaut-framework–4–6–0-released/ essentiellement une grosse mise à jour de tonnes de modules avec les dernières versions des dépendances Microprofile 7 faire quelques changements et evolution incompatibles https://microprofile.io/2024/08/22/microprofile–7–0-release/#general enleve Metrics et remplace avec Telemetry (metrics, log et tracing) Metrics reste une spec mais standalone Microprofile 7 depende de Jakarta Core profile et ne le package plus Microprofile OpenAPI 4 et Telemetry 2 amenent des changements incompatibles Quarkus 3.14 avec LetsEncrypt et des serialiseurs JAckson sans reflection https://quarkus.io/blog/quarkus–3–14–1-released/ Hibernate ORM 6.6 Serialisateurs JAckson sans reflection installer des certificats letsencrypt simplement (notamment avec la ligne de commande qui aide sympa notamment avec ngrok pour faire un tunnel vers son localhost retropedalage sur @QuarkusTestResource vs @WithTestResource suite aux retour de OOME et lenteur des tests mieux isolés Les logs structurées dans Spring Boot 3.4 https://spring.io/blog/2024/08/23/structured-logging-in-spring-boot–3–4 Les logs structurées (souvent en JSON) vous permettent de les envoyer facilement vers des backends comme Elastic, AWS CloudWatch… Vous pouvez les lier à du reporting et de l'alerting. Spring Boot 3.4 prend en charge la journalisation structurée par défaut. Il prend en charge les formats Elastic Common Schema (ECS) et Logstash, mais il est également possible de l'étendre avec vos propres formats. Vous pouvez également activer la journalisation structurée dans un fichier. Cela peut être utilisé, par exemple, pour imprimer des journaux lisibles par l'homme sur la console et écrire des journaux structurés dans un fichier pour l'ingestion par machine. Infrastructure CockroachDB qui avait une approche Business Software License (source available puis ALS 3 ans apres), passe maintenant en license proprietaire avec source available https://www.cockroachlabs.com/blog/enterprise-license-announcement/ Polyform project offre des licences standardisees selon les besoins de gratuit vs payant https://polyformproject.org/ Cloud Azure fonctions, comment le demarrage a froid est optimisé https://www.infoq.com/articles/azure-functions-cold-starts/?utm_campaign=infoq_content&utm_source=twitter&utm_medium=feed&utm_term=Cloud fonctions ont une latence naturelle forte toutes les lantences longues ne sont aps impactantes pour le business les demarrages a froid peuvent etre mesures avec les outils du cloud provider donc faites en usage faites des decentilers de latences experience 381 ms cold et 10ms apres tracing pour end to end latence les strategies keep alive pings: reveiller la fonctione a intervalles reguliers pour rester “warm” dans le code de la fonction: initialiser les connections et le chargement des assemblies dans l'initialization configurer dans host.json le batching, desactiver file system logging etc deployer les fonctions as zips reduire al taille du code et des fichiers (qui sont copies sur le serveur froid) sur .net activer ready to run qui aide le JIT compiler instances azure avec plus de CPU et memoire sont plus cher amis baissent le cold start dedicated azure instances pour vos fonctions (pas aprtage avec les autres tenants) ensuite montre des exemples concrets Web Sortie de Vue.js 3.5 https://blog.vuejs.org/posts/vue–3–5 Vue.JS 3.5: Nouveautés clés Optimisations de performance et de mémoire: Réduction significative de la consommation de mémoire (–56%). Amélioration des performances pour les tableaux réactifs de grande taille. Résolution des problèmes de valeurs calculées obsolètes et de fuites de mémoire. Nouvelles fonctionnalités: Reactive Props Destructure: Simplification de la déclaration des props avec des valeurs par défaut. Lazy Hydration: Contrôle de l'hydratation des composants asynchrones. useId(): Génération d'ID uniques stables pour les applications SSR. data-allow-mismatch: Suppression des avertissements de désynchronisation d'hydratation. Améliorations des éléments personnalisés: Prise en charge de configurations d'application, d'API pour accéder à l'hôte et au shadow root, de montage sans Shadow DOM, et de nonce pour les balises. useTemplateRef(): Obtention de références de modèle via l'API useTemplateRef(). Teleport différé: Téléportation de contenu vers des éléments rendus après le montage du composant. onWatcherCleanup(): Enregistrement de callbacks de nettoyage dans les watchers. Data et Intelligence Artificielle On entend souvent parler de Large Language Model quantisés, c'est à dire qu'on utilise par exemple des entiers sur 8 bits plutôt que des floatants sur 32 bits, pour réduire les besoins mémoire des GPU tout en gardant une précision proche de l'original. Cet article explique très visuellement et intuitivement ce processus de quantisation : https://newsletter.maartengrootendorst.com/p/a-visual-guide-to-quantization Guillaume continue de partager ses aventures avec le framework LangChain4j. Comment effectuer de la classification de texte : https://glaforge.dev/posts/2024/07/11/text-classification-with-gemini-and-langchain4j/ en utilisant la classe TextClassification de LangChain4j, qui utilise une approche basée sur les vector embeddings pour comparer des textes similaires en utilisant du few-shot prompting, sous différentes variantes, dans cet autre article : https://glaforge.dev/posts/2024/07/30/sentiment-analysis-with-few-shots-prompting/ et aussi comment faire du multimodal avec LangChain4j (avec le modèle Gemini) pour analyser des textes, des images, mais également des vidéos, du contenu audio, ou bien des fichiers PDFs : https://glaforge.dev/posts/2024/07/25/analyzing-videos-audios-and-pdfs-with-gemini-in-langchain4j/ Pour faire varier la prédictibilité ou la créativité des LLMs, certains hyperparamètres peuvent être ajustés, comme la température, le top-k et le top-p. Mais est-ce que vous savez vraiment comment fonctionnent ces paramètres ? Deux articles très clairs et intuitifs expliquent leur fonctionnement : https://medium.com/google-cloud/is-a-zero-temperature-deterministic-c4a7faef4d20 https://medium.com/google-cloud/beyond-temperature-tuning-llm-output-with-top-k-and-top-p–24c2de5c3b16 la tempoerature va ecraser la probabilite du prochain token mais il reste des variables: approximnation des calculs flottants, stacks differentes effectuants ces choix differemment, que faire en cas d'egalité de probabilité entre deux tokens mais il y a d'atures apporoches de configuiration des reaction du LLM: top-k (qui evite les tokens peu frequents), top-p pour avoir les n des tokens qui totalient p% des probabilités temperature d'abord puis top-k puis top-p explique quoi utiliser quand OSI propose une definition de l'IA open source https://www.technologyreview.com/2024/08/22/1097224/we-finally-have-a-definition-for-open-source-ai/ gros debats ces derniers mois utilisable pour tous usages sans besoin de permission chercheurs peuvent inspecter les components et etudier comment le system fonctionne systeme modifiable pour tout objectif y compris chager son comportement et paratger avec d'autres avec ou sans modification quelque soit l'usage Definit des niveaux de transparence (donnees d'entranement, code source, poids) Une longue rétrospective de PostgreSQL a des volumes de malades et les problèmes de lock https://ardentperf.com/2024/03/03/postgres-indexes-partitioning-and-lwlocklockmanager-scalability/ un article pour vous rassurer que vous n'aurez probablement jamais le problème histoire sous forme de post mortem des conseils pour éviter ces falaises Outillage Un premier coup d'oeil à la future notation déclarative de Gradle https://blog.gradle.org/declarative-gradle-first-eap un article qui explique à quoi ressemble cette nouvelle syntaxe déclarative de Gradle (en plus de Groovy et Kotlin) Quelques vidéos montrent le support dans Android Studio, pour le moment, ainsi que dans un outil expérimental, en attendant le support dans tous les IDEs L'idée est d'éviter le scripting et d'avoir vraiment qu'une description de son build Cela devrait améliorer la prise en charge de Gradle dans les IDEs et permettre d'avoir de la complétion rapide, etc c'est moi on on a Maven là? Support de Firefox dans Puppeteer https://hacks.mozilla.org/2024/08/puppeteer-support-for-firefox/ Puppeteer, la bibliothèque d'automatisation de navigateur, supporte désormais officiellement Firefox dès la version 23. Cette avancée permet aux développeurs d'écrire des scripts d'automatisation et d'effectuer des tests de bout en bout sur Chrome et Firefox de manière interchangeable. L'intégration de Firefox dans Puppeteer repose sur WebDriver BiDi, un protocole inter-navigateurs en cours de standardisation au W3C. WebDriver BiDi facilite la prise en charge de plusieurs navigateurs et ouvre la voie à une automatisation plus simple et plus efficace. Les principales fonctionnalités de Puppeteer, telles que la capture de journaux, l'émulation de périphériques, l'interception réseau et le préchargement de scripts, sont désormais disponibles pour Firefox. Mozilla considère WebDriver BiDi comme une étape importante vers une meilleure expérience de test inter-navigateurs. La prise en charge expérimentale de CDP (Chrome DevTools Protocol) dans Firefox sera supprimée fin 2024 au profit de WebDriver BiDi. Bien que Firefox soit officiellement pris en charge, certaines API restent non prises en charge et feront l'objet de travaux futurs. Guillaume a créé une annotation @Retry pour JUnit 5, pour retenter l'exécution d'un test qui est “flaky” https://glaforge.dev/posts/2024/09/01/a-retryable-junit–5-extension/ Guillaume n'avait pas trouvé d'extension par défaut dans JUnit 5 pour remplacer les Retry rules de JUnit 4 Mais sur les réseaux sociaux, une discussion intéressante s'ensuit avec des liens sur des extensions qui implémentent cette approche Comme JUnit Pioneer qui propose plein d'extensions utiles https://junit-pioneer.org/docs/retrying-test/ Ou l'extension rerunner https://github.com/artsok/rerunner-jupiter Arnaud a aussi suggéré la configuration de Maven Surefire pour relancer automatiquement les tests qui ont échoué https://maven.apache.org/surefire/maven-surefire-plugin/examples/rerun-failing-tests.html la question philosophique est: est-ce que c'est tolerable les tests qui ecouent de façon intermitente Architecture Un ancien fan de GraphQL en a fini avec la technologie GraphQL et réfléchit aux alternatives https://bessey.dev/blog/2024/05/24/why-im-over-graphql/ Problèmes de GraphQL: Sécurité: Attaques d'autorisation Difficulté de limitation de débit Analyse de requêtes malveillantes Performance: Problème N+1 (récupération de données et autorisation) Impact sur la mémoire lors de l'analyse de requêtes invalides Complexité accrue: Couplage entre logique métier et couche de transport Difficulté de maintenance et de tests Solutions envisagées: Adoption d'API REST conformes à OpenAPI 3.0+ Meilleure documentation et sécurité des types Outils pour générer du code client/serveur typé Deux approches de mise en œuvre d'OpenAPI: “Implementation first” (génération de la spécification à partir du code) “Specification first” (génération du code à partir de la spécification) retour interessant de quelqu'un qui n'utilise pas GraphQL au quotidien. C'était des problemes qui devaient etre corrigés avec la maturité de l'ecosysteme et des outils mais ca a montré ces limites pour cette personne. Prensentation de Grace Hoper en 1980 sur le future des ordinateurs. https://youtu.be/AW7ZHpKuqZg?si=w_o5_DtqllVTYZwt c'est fou la modernité de ce qu'elle décrit Des problèmes qu'on a encore aujourd'hui positive leadership Elle décrit l'avantage de systèmes fait de plusieurs ordinateurs récemment declassifié Leader election avec les conditional writes sur les buckets S3/GCS/Azure https://www.morling.dev/blog/leader-election-with-s3-conditional-writes/ L'élection de leader est le processus de choisir un nœud parmi plusieurs pour effectuer une tâche. Traditionnellement, l'élection de leader se fait avec un service de verrouillage distribué comme ZooKeeper. Amazon S3 a récemment ajouté le support des écritures conditionnelles, ce qui permet l'élection de leader sans service séparé. L'algorithme d'élection de leader fonctionne en faisant concourir les nœuds pour créer un fichier de verrouillage dans S3. Le fichier de verrouillage inclut un numéro d'époque, qui est incrémenté à chaque fois qu'un nouveau leader est élu. Les nœuds peuvent déterminer s'ils sont le leader en listant les fichiers de verrouillage et en vérifiant le numéro d'époque. attention il peut y avoir plusieurs leaders élus (horloges qui ont dérivé) donc c'est à gérer aussi Méthodologies Guillaume Laforge interviewé par Sfeir, où il parle de l'importance de la curiosité, du partage, de l'importance de la qualité du code, et parsemé de quelques photos des Cast Codeurs ! https://www.sfeir.dev/success-story/guillaume-laforge-maestro-de-java-et-esthete-du-code-propre/ Sécurité Comment crowdstrike met a genoux windows et de nombreuses entreprises https://next.ink/144464/crowdstrike-donne-des-details-techniques-sur-son-fiasco/ l'incident vient de la mise à jour de la configuration de Falcon l'EDR de crowdstrike https://www.crowdstrike.com/blog/falcon-update-for-windows-hosts-technical-details/ qu'est ce qu'un EDR? Un système Endpoint Detection and Response a pour but de surveiller votre machine ( access réseaux, logs, …) pour detecter des usages non habituels. Cet espion doit interagir avec les couches basses du système (réseau, sockets, logs systems) et se greffe donc au niveau du noyau du système d'exploitation. Il remonte les informations en live à une plateforme qui peut ensuite adapter les réponse en live si l'incident a duré moins de 1h30 coté crowdstrike plus de 8 millions de machines se sont retrouvées hors service bloquées sur le Blue Screen Of Death selon Microsoft https://blogs.microsoft.com/blog/2024/07/20/helping-our-customers-through-the-crowdstrike-outage/ cela n'est pas la première fois et était déjà arrivé il y a quelques mois sur Linux. Comme il s'agissait d'une incompatibilité de kernel il avait été moins important car les services ITs gèrent mieux ces problèmes sous Linux https://stackdiary.com/crowdstrike-took-down-debian-and-rocky-linux-a-few-months-ago-and-no-one-noticed/ Les benchmarks CIS, un pilier pour la sécurité de nos environnements cloud, et pas que ! (Katia HIMEUR TALHI) https://blog.cockpitio.com/security/cis-benchmarks/ Le CIS est un organisme à but non lucratif qui élabore des normes pour améliorer la cybersécurité. Les référentiels CIS sont un ensemble de recommandations et de bonnes pratiques pour sécuriser les systèmes informatiques. Ils peuvent être utilisés pour renforcer la sécurité, se conformer aux réglementations et normaliser les pratiques. Loi, société et organisation Microsoft signe un accord avec OVHCloud pour qu'il arretent leur plaine d'antitrust https://www.politico.eu/article/microsoft-signs-antitrust-truce-with-ovhcloud/ la plainte était en Europe mermet a des clients de plus facilement deployer les solutions Microsoft dans le fournisseur de cloud de leur choix la plainte avait ete posé à l'été 2021 ca rendait faire tourner les solutions MS plus cheres et non competitives vs MS ElasticSearch et Kibana sont de nouveau Open Source, en ajoutant la license AGPL à ses autres licences existantes https://www.elastic.co/fr/blog/elasticsearch-is-open-source-again le marché d'il y a trois ans et maintenant a changé AWS est une bon partenaire le flou Elasticsearch vs le produit d'AWS s'est clarifié donc retour a l'open source via AGPL Affero GPL Elastic n'a jamais cessé de croire en l'open source d'après Shay Banon son fondateur Le changement vers l'AGPL est une option supplémentaire, pas un remplacement d'une des autres licences existantes et juste apres, Elastic annonce des resultants decevants faisant plonger l'action de 25% https://siliconangle.com/2024/08/29/elastic-shares-plunge–25-lower-revenue-projections-amid-slower-customer-commitments/ https://unrollnow.com/status/1832187019235397785 et https://www.elastic.co/pricing/faq/licensing pour un résumé des licenses chez elastic Outils de l'épisode MailMate un client email Markdown et qui gere beaucoup d'emails https://medium.com/@nicfab/mailmate-a-powerful-client-email-for-macos-markdown-integrated-email-composition-e218fe2accf3 Emmanuel l'utilise sur les boites email secondaires un peu lent a demarrer (synchro) et le reste est rapide boites virtuelles (par requete) SpamSieve Que macOS je crois Trippy, un analyseur de réseau https://github.com/fujiapple852/trippy Il regroupe dans une CLI traceroute et ping Conférences La liste des conférences provenant de Developers Conferences Agenda/List par Aurélie Vache et contributeurs : 17 septembre 2024 : We Love Speed - Nantes (France) 17–18 septembre 2024 : Agile en Seine 2024 - Issy-les-Moulineaux (France) 19–20 septembre 2024 : API Platform Conference - Lille (France) & Online 20–21 septembre 2024 : Toulouse Game Dev - Toulouse (France) 25–26 septembre 2024 : PyData Paris - Paris (France) 26 septembre 2024 : Agile Tour Sophia-Antipolis 2024 - Biot (France) 2–4 octobre 2024 : Devoxx Morocco - Marrakech (Morocco) 3 octobre 2024 : VMUG Montpellier - Montpellier (France) 7–11 octobre 2024 : Devoxx Belgium - Antwerp (Belgium) 8 octobre 2024 : Red Hat Summit: Connect 2024 - Paris (France) 10 octobre 2024 : Cloud Nord - Lille (France) 10–11 octobre 2024 : Volcamp - Clermont-Ferrand (France) 10–11 octobre 2024 : Forum PHP - Marne-la-Vallée (France) 11–12 octobre 2024 : SecSea2k24 - La Ciotat (France) 15–16 octobre 2024 : Malt Tech Days 2024 - Paris (France) 16 octobre 2024 : DotPy - Paris (France) 16–17 octobre 2024 : NoCode Summit 2024 - Paris (France) 17–18 octobre 2024 : DevFest Nantes - Nantes (France) 17–18 octobre 2024 : DotAI - Paris (France) 30–31 octobre 2024 : Agile Tour Nantais 2024 - Nantes (France) 30–31 octobre 2024 : Agile Tour Bordeaux 2024 - Bordeaux (France) 31 octobre 2024–3 novembre 2024 : PyCon.FR - Strasbourg (France) 6 novembre 2024 : Master Dev De France - Paris (France) 7 novembre 2024 : DevFest Toulouse - Toulouse (France) 8 novembre 2024 : BDX I/O - Bordeaux (France) 13–14 novembre 2024 : Agile Tour Rennes 2024 - Rennes (France) 16–17 novembre 2024 : Capitole Du Libre - Toulouse (France) 20–22 novembre 2024 : Agile Grenoble 2024 - Grenoble (France) 21 novembre 2024 : DevFest Strasbourg - Strasbourg (France) 21 novembre 2024 : Codeurs en Seine - Rouen (France) 27–28 novembre 2024 : Cloud Expo Europe - Paris (France) 28 novembre 2024 : Who Run The Tech ? - Rennes (France) 2–3 décembre 2024 : Tech Rocks Summit - Paris (France) 3 décembre 2024 : Generation AI - Paris (France) 3–5 décembre 2024 : APIdays Paris - Paris (France) 4–5 décembre 2024 : DevOpsRex - Paris (France) 4–5 décembre 2024 : Open Source Experience - Paris (France) 5 décembre 2024 : GraphQL Day Europe - Paris (France) 6 décembre 2024 : DevFest Dijon - Dijon (France) 22–25 janvier 2025 : SnowCamp 2025 - Grenoble (France) 30 janvier 2025 : DevOps D-Day #9 - Marseille (France) 6–7 février 2025 : Touraine Tech - Tours (France) 3 avril 2025 : DotJS - Paris (France) 16–18 avril 2025 : Devoxx France - Paris (France) Nous contacter Pour réagir à cet épisode, venez discuter sur le groupe Google https://groups.google.com/group/lescastcodeurs Contactez-nous via twitter https://twitter.com/lescastcodeurs Faire un crowdcast ou une crowdquestion Soutenez Les Cast Codeurs sur Patreon https://www.patreon.com/LesCastCodeurs Tous les épisodes et toutes les infos sur https://lescastcodeurs.com/

Follow Lucas hereCheck out Building Ventures here

Follow Roger hereCheck out FullStack Modular here: https://www.fullstackmodular.com/

3 mishnayot! Each about selling different properties, where the details of the sale are not specified. First, a courtyard. (if the details are specified, or if the seller says: "I'm selling you everything that is therein," then those sales are simpler, as per the stipulation). Second, an olive press, and third, a bath house. Without specification, the attached portions are all part of the sale, and the movable items are not.

Follow Romey hereCheck out LMRE here: https://www.lmre.tech/lmre-north-america/

EIP-2537 is a proposal to adds operation on BLS12-381 curve as a precompile in a set necessary to efficiently perform operations such as BLS signature verification. Resources: ----------------- Presentation: EIP - https://eips.ethereum.org/EIPS/eip-2537 Discussion - Other Resources: https://youtu.be/GriLSj37RdI https://youtu.be/SfDC_qUZaos https://youtu.be/CcL9RJBljUs https://youtu.be/-xY1EEzcp0s https://youtu.be/KdhHJa2SEwY Check out upcoming EIPs in Peep an EIP series at https://github.com/ethereum-cat-herders/PM/projects/2 PEEPanEIP - https://www.youtube.com/playlist?list=PL4cwHXAawZxqu0PKKyMzG_3BJV_xZTi1F Follow at Twitter: -------------------------- Alex Stokes - https://twitter.com/ralexstokes Pooja Ranjan - https://twitter.com/poojaranjan19 Topics covered: ------------------------- 00:23 - About EIP - 2537 01:34 - About Alex Stokes 02:19 - Alex's Introduction 04:44 - Presentation 04:54 - History of EIP - 2537 06:30 - What EIP - 2537 do? 11:21 - What EIP-2537 brings? 13:05 - Who need this EIP? 17:05 - What is Done? 18:36 - What's new since then? 23:03 - Presentation End 24:27 - Q&A 24:36 - What is Alex thought on Major Changes to the Specification? & Why Trade-offs of security vs Expensive changes necessary and how that improve this proposal? 26:55 - What challenges faced by Alex during inclusion in the Ethereum Network Upgrade? & What changes between 2020 to 2024 it being included in Pectra Upgrade? 31:15 - What are the real-life use cases of EIP - 2537? 35:54 - Is EIP- 2537 & EIP - 7212 are related in anyways? 36:49 - Is Proposal 2537 replace or get addition to existing curve? 38:02 - Alex talked about Gas cost consideration and how they address. 41:03 - Are BLS-12 GTADD, BLS-12 GTMUL already include in 2537 or planning to include in future? 44:54 - Alex feedback on PEEPanEIP Series 46:05 - Alex final thought

Want to add strategic pricing to your marketing tool box? Go to InteliChek or call 877-827-7273 and ask about our InteliShare Series!   InteliShare  contains all of our promotional tools that you can use to promote your favorable prices, including our InteliAds, the printable flyers that you can show off in easel displays, InteliMedia, for your Digital Media Boards AND InteliWidgets, so you can show off price comparisons on your website and even let your customers schedule from the widget.     Summary In this episode, Brandon, Ed, and Tom discuss the Right to Repair Act and its implications for dealerships. They explore the key provisions of the act, including the requirement for manufacturers to provide specifications to third parties and the disclosure of vehicle information captured in telematics. The conversation also touches on the potential impact on warranties, patents, and personal data. The hosts debate the need for regulation in the automotive industry and the balance between consumer choice and intellectual property rights. They also discuss the history and future of the repair act and its potential effects on the industry. The conversation discusses the impact of proposed legislation on the use of aftermarket parts in vehicle repairs. The speakers explore the history of aftermarket parts, the role of certifications, and the potential consequences of the legislation. They also touch on the influence of insurance companies and the importance of educating customers about their repair options. The conversation concludes with a discussion on data privacy and the need for consumers to be informed and make their own decisions.   Takeaways The Right to Repair Act is an attempt by Congress to level the playing field between dealerships and manufacturers, but it may put dealers and manufacturers at a disadvantage. The act requires manufacturers to provide specifications to third parties and disclose all vehicle information captured in telematics, which raises concerns about intellectual property rights and personal data privacy. Dealerships are already heavily regulated, and the act adds another layer of complexity and cost, potentially driving up prices for consumers. The act may lead to more subscription services and increased prices for vehicles, as manufacturers find alternative ways to recoup costs. The future of the repair act is uncertain, with different states passing their own legislation and the potential for changes depending on the political landscape. The quality of aftermarket parts has improved over time, and they can be a cost-effective alternative to OEM parts. The proposed legislation would require OEMs to share their patents and information with aftermarket manufacturers, potentially impacting competition and innovation. Insurance companies may prefer the use of aftermarket parts to keep costs down, but customers should be educated about their repair options. Data privacy is a concern, and consumers should have the choice to share their vehicle data or not.   Clips: Mass Law 2012 2014 Agreement (National Standard) 2020 Ballot Measure 2023 Neal Dunn 2023 Darryl Issa-SMART ACT NHTSA-Do Not Comply NHTSA-Reverse Course   Music: Wild Wonder-The Last Reveille-Night Visions Lone Canyon-Another Moment Quiet Lake-Into The Abyss Alsever Lake-Shine Your Light   Guests: Tom Kline-Better Vantage Point Ed Roberts-Mile One Leadership

Want to add strategic pricing to your marketing tool box? Go to InteliChek or call 877-827-7273 and ask about our InteliShare Series!   InteliShare  contains all of our promotional tools that you can use to promote your favorable prices, including our InteliAds, the printable flyers that you can show off in easel displays, InteliMedia, for your Digital Media Boards AND InteliWidgets, so you can show off price comparisons on your website and even let your customers schedule from the widget.     Summary In this episode, Brandon, Ed, and Tom discuss the Right to Repair Act and its implications for dealerships. They explore the key provisions of the act, including the requirement for manufacturers to provide specifications to third parties and the disclosure of vehicle information captured in telematics.   The conversation also touches on the potential impact on warranties, patents, and personal data. The hosts debate the need for regulation in the automotive industry and the balance between consumer choice and intellectual property rights. They also discuss the history and future of the repair act and its potential effects on the industry. The conversation discusses the impact of proposed legislation on the use of aftermarket parts in vehicle repairs.   The speakers explore the history of aftermarket parts, the role of certifications, and the potential consequences of the legislation. They also touch on the influence of insurance companies and the importance of educating customers about their repair options. The conversation concludes with a discussion on data privacy and the need for consumers to be informed and make their own decisions.   Takeaways The Right to Repair Act is an attempt by Congress to level the playing field between dealerships and manufacturers, but it may put dealers and manufacturers at a disadvantage. The act requires manufacturers to provide specifications to third parties and disclose all vehicle information captured in telematics, which raises concerns about intellectual property rights and personal data privacy. Dealerships are already heavily regulated, and the act adds another layer of complexity and cost, potentially driving up prices for consumers. The act may lead to more subscription services and increased prices for vehicles, as manufacturers find alternative ways to recoup costs. The future of the repair act is uncertain, with different states passing their own legislation and the potential for changes depending on the political landscape. The quality of aftermarket parts has improved over time, and they can be a cost-effective alternative to OEM parts. The proposed legislation would require OEMs to share their patents and information with aftermarket manufacturers, potentially impacting competition and innovation. Insurance companies may prefer the use of aftermarket parts to keep costs down, but customers should be educated about their repair options. Data privacy is a concern, and consumers should have the choice to share their vehicle data or not.   Clips: Mass Law 2012 2014 Agreement (National Standard) 2020 Ballot Measure 2023 Neal Dunn 2023 Darryl Issa-SMART ACT NHTSA-Do Not Comply NHTSA-Reverse Course   Music: Wild Wonder-The Last Reveille-Night Visions Lone Canyon-Another Moment Quiet Lake-Into The Abyss Alsever Lake-Shine Your Light   Guests: Tom Kline-Better Vantage Point Ed Roberts-Mile One Leadership

Sponsors:• ◦ Visit Buildertrend to get a 60-day money-back guarantee on your Buildertrend account!• ◦ Design Camp• ◦ Pella Windows & Doors• ◦ Sub-Zero Wolf Cove Showroom PhoenixConnect with Jamie Gasparovic:Studio Gaspo WebsiteConnect with Brad Leavitt:Website | Instagram | Facebook | Houzz | Pinterest | YouTube

A physical therapy clinic is planning to install a new wheelchair ramp that incorporates a switchback for space efficiency. According to ADA guidelines, what is the MINIMUM required landing size at the switchback to ensure compliance and safety?A) 36 inches by 36 inchesB) 48 inches by 48 inchesC) 60 inches by 60 inchesD) 72 inches by 72 inches LINKS MENTIONED: Did you get this question wrong?! If you were stuck between two answers and selected the wrong one, then you need to visit www.NPTEPASS.com, to learn about the #1 solution to STOP getting stuck. Get Your Episode Cheatsheet here: https://www.nptecheatsheet.com/wheelchairs Check out our Instagram account: www.nptegroup.com --- Support this podcast: https://podcasters.spotify.com/pod/show/thepthustle/support