Podcasts about pattern language

Architecture is HumanArchitecture is more than just buildings—it's a reflection of humanity itself. In this episode, architect, writer, and educator Duo Dickinson shares his insights on how architecture shapes our values, communities, and experiences. He discusses the delicate balance between honoring history and pushing design forward, emphasizing the importance of context and connection.With over 30 years of experience and a deep commitment to pro bono work, Duo offers a unique perspective on architecture's responsibility to serve people, not just projects. He explores how thoughtful design can transform spaces, revitalize communities, and enhance everyday life. The conversation also delves into his philosophy on fees, the human element in architecture, and the importance of truly listening to clients.Through real-world examples and decades of expertise, Duo makes the case that great architecture is not just about aesthetics—it's about understanding people and creating places that resonate with them.This week at EntreArchitect Podcast, Architecture is Human with Duo Dickerson.Want to watch this HWS session? Check it out on YouTube! Want to hear more conversations like this? Check out the EntreArchitect Network!Learn more about Duo online at DuoDickinson.com, and connect with him on Instagram.Referenced in this EpisodeBuilding BeautyChristopher Alexander's "A Pattern Language" and "The Nature of Order"Common Edge CollaborativeWPKN RadioPlease visit Our Platform SponsorsArcatemy is Arcat's Continuing Education Program. Listen to Arcat's Detailed podcast and earn HSW credits. As a trusted provider, Arcat ensures you earn AIA CE credits while advancing your expertise and career in architecture. Learn more at Arcat.com/continuing-education.Visit our Platform Sponsors today and thank them for supporting YOU... The EntreArchitect Community of small firm architects.

On this episode of Powered By Her, we sit down with Lisa Uhrik to dive into The Pattern Language by Christopher Alexander. Together, we explore how designing your personal and professional spaces with intention can transform your life. Lisa also shares her passion for creating retail spaces that feel like community hubs, explaining the big benefits of bringing people together in meaningful ways. If you're curious about how the spaces around you can inspire connection and creativity, this conversation is for you! Tune in and discover practical tips and fresh ideas to apply to your life and business today. Thanks to our partners: Plenty Downtown Bookshop The Biz Foundry Miss Sallie's Market

In this episode of Trending in Education, Kumar Garg, President of Renaissance Philanthropy, rejoins host Mike Palmer for his second appearance after first appearing in the Spring of 2021. The conversation delves into Garg's evolution from Schmidt Futures to launching Renaissance Philanthropy, and their work at the intersection of AI and learning science. We discuss the historical underfunding of education R&D compared to other sectors and explore the immense potential of AI in transforming learning experiences. The conversation covers the Learning Engineering Virtual Institute, the importance of interdisciplinary expertise, recent research with the Walton Family Foundation, and future ambitions for integrating cutting-edge technology into education. We also reference Renaissance's Pattern Language for High Impact Philanthropic Giving. Subscribe where you get your podcasts. Video versions now available on Youtube and Spotify. TIMESYAMPS 00:00 Welcome and Introduction 00:38 Kumar Garg's Journey and Renaissance Philanthropy 02:39 The Intersection of AI and Learning Science 05:45 Building "Bilingual" Teams for Educational Innovation 06:55 Renaissance's Bold Goals and Partnerships 08:44 Recent Initiatives and Future Directions 13:09 Challenges and Opportunities in AI for Education 27:34 The Importance of Trust and Equity in Educational Technology 33:22 Conclusion and Call to Action

In this episode, Madeline chats with her friend Hannah Bernstein, a landscape architecture student at the University of Illinois at Urbana-Champaign During their conversation, they discuss the Pacific Northwest and Spain, UIUC's Newman Center, what landscape architecture is, how our expertise gets embedded in us, living at a residential Newman Center, American accents, her study abroad and research trip, Dominican cloister gardens, going beyond the surface level, the King of Itineraries, and so much more!-links: the not so big house, A Pattern LanguageDuring the course of their conversation, they make many references which you can explore. Some of these references include The Not So Big House by Susan Susanna and A Pattern Language by Christopher W. Alexander.Feel free to like, subscribe, and share the episode! Follow us on Instagram! @sbltfpodcastDon't forget to go out there, and be a light to this world!

Work for Humans has always been about designing with the employee in mind, but many designers mistakenly focus on objects rather than the actions those objects should create. This leads to falling back on traditional roles and routines when there is actually more choice out there. Inspired by the power of designing for action instead of things, WFH connected with Stephanie Goia and Melanie Kahl—two design strategists dedicated to human-centered organizational design. Together, they're creating a pattern language library, offering a resource that encourages more choice and innovation to all designers.In this episode, Dart, Stephanie, and Melanie discuss:- Human-centered organizational design practice- Pattern language in design- Designing for verbs instead of things- What is designable and what isn't- 5 key categories of pattern language- Design lessons from education and biological systems- Holding spaces for participatory design- And other topics…Stephanie Goia is a partner and lead design strategist at Future Work Design, a firm dedicated to transforming workplaces through innovative design. With over 15 years of experience in consulting and education, she specializes in organizational design and human-centered practices. Stephanie also serves as the Lab Director of EitherOrg and as an Executive MBA instructor at the University of Oregon, where she furthers her commitment to participatory design and systemic change. Melanie Kahl is an innovation leader and strategist with over 15 years of experience designing programs and spaces that foster human flourishing. She previously launched Meta's first Community-in-Residence program and led projects with global organizations like the Gates Foundation and USAID. Melanie holds a degree from Northwestern University and is an adjunct professor at the School of Visual Arts and the Copenhagen Institute of Interaction Design.Resources mentioned:Seeing Like a State, by James Scott: https://www.amazon.com/Seeing-like-State-Certain-Condition/dp/0300078153 A Pattern Language, by Christopher Alexander: https://www.amazon.com/Pattern-Language-Buildings-Construction-Environmental/dp/0195019199 Dark Matter Labs: https://darkmatterlabs.org/ The Edge of the Sea, by Rachel Carson: https://www.amazon.com/Edge-Sea-Rachel-Carson/dp/0395924960 Connect with Stephanie & Melanie:www.futurework.designwww.eitherorg.orgStephanie LinkedIn: https://www.linkedin.com/in/stephaniegioia/www.MelanieKahl.comMelanie's Instagram: @melanie_kahlMelanie's X: @melaniekahl

In this episode, Conor and Bryce chat with Kevlin Henney about the top recommendation from 97 Things Every Programmer Should Know.Link to Episode 194 on WebsiteDiscuss this episode, leave a comment, or ask a question (on GitHub)TwitterADSP: The PodcastConor HoekstraBryce Adelstein LelbachAbout the GuestKevlin Henney is an independent consultant, speaker, writer and trainer. His software development interests are in programming, practice and people. He has been a columnist for various magazines and websites. He is the co-author of A Pattern Language for Distributed Computing and On Patterns and Pattern Languages, two volumes in the Pattern-Oriented Software Architecture series, and editor of 97 Things Every Programmer Should Know and co-editor of 97 Things Every Java Programmer Should Know.Show NotesDate Recorded: 2024-07-11Date Released: 2024-08-0997 Things Every Programmer Should Know (GitHub)97 Things Every Programmer Should KnowPattern-Oriented Software Architecture: A Pattern Language for Distributed Computing, 4th VolumePattern Oriented Software Architecture Volume 5: On Patterns and Pattern LanguagesEffective C++ Series by Scott MeyersBeautiful C++: 30 Core Guidelines for Writing Clean, Safe, and Fast CodeIntro Song InfoMiss You by Sarah Jansen https://soundcloud.com/sarahjansenmusicCreative Commons — Attribution 3.0 Unported — CC BY 3.0Free Download / Stream: http://bit.ly/l-miss-youMusic promoted by Audio Library https://youtu.be/iYYxnasvfx8

In this episode, Bryce chats with Kevlin Henney about Kevlin Henneys.Link to Episode 193 on WebsiteDiscuss this episode, leave a comment, or ask a question (on GitHub)TwitterADSP: The PodcastConor HoekstraBryce Adelstein LelbachAbout the GuestKevlin Henney is an independent consultant, speaker, writer and trainer. His software development interests are in programming, practice and people. He has been a columnist for various magazines and websites. He is the co-author of A Pattern Language for Distributed Computing and On Patterns and Pattern Languages, two volumes in the Pattern-Oriented Software Architecture series, and editor of 97 Things Every Programmer Should Know and co-editor of 97 Things Every Java Programmer Should Know.Show NotesDate Recorded: 2024-07-11Date Released: 2024-08-02HPXIntro Song InfoMiss You by Sarah Jansen https://soundcloud.com/sarahjansenmusicCreative Commons — Attribution 3.0 Unported — CC BY 3.0Free Download / Stream: http://bit.ly/l-miss-youMusic promoted by Audio Library https://youtu.be/iYYxnasvfx8

In this episode, Bryce chats with Kevlin Henney about systems programming and more.Link to Episode 192 on WebsiteDiscuss this episode, leave a comment, or ask a question (on GitHub)TwitterADSP: The PodcastConor HoekstraBryce Adelstein LelbachAbout the GuestKevlin Henney is an independent consultant, speaker, writer and trainer. His software development interests are in programming, practice and people. He has been a columnist for various magazines and websites. He is the co-author of A Pattern Language for Distributed Computing and On Patterns and Pattern Languages, two volumes in the Pattern-Oriented Software Architecture series, and editor of 97 Things Every Programmer Should Know and co-editor of 97 Things Every Java Programmer Should Know.Show NotesDate Recorded: 2024-07-11Date Released: 2024-07-26Kevlin Henney ACCU 2024 TalkIntro Song InfoMiss You by Sarah Jansen https://soundcloud.com/sarahjansenmusicCreative Commons — Attribution 3.0 Unported — CC BY 3.0Free Download / Stream: http://bit.ly/l-miss-youMusic promoted by Audio Library https://youtu.be/iYYxnasvfx8

In this episode, Conor and Bryce chat with Kevlin Henney about algorithms, libraries and many programming languages!Link to Episode 191 on WebsiteDiscuss this episode, leave a comment, or ask a question (on GitHub)TwitterADSP: The PodcastConor HoekstraBryce Adelstein LelbachAbout the GuestKevlin Henney is an independent consultant, speaker, writer and trainer. His software development interests are in programming, practice and people. He has been a columnist for various magazines and websites. He is the co-author of A Pattern Language for Distributed Computing and On Patterns and Pattern Languages, two volumes in the Pattern-Oriented Software Architecture series, and editor of 97 Things Every Programmer Should Know and co-editor of 97 Things Every Java Programmer Should Know.Show NotesDate Recorded: 2024-07-11Date Released: 2024-07-19FortranCoarray FortranPascal LanguagepytestNumPyPython pipRust cargoRust crates.ioIntro Song InfoMiss You by Sarah Jansen https://soundcloud.com/sarahjansenmusicCreative Commons — Attribution 3.0 Unported — CC BY 3.0Free Download / Stream: http://bit.ly/l-miss-youMusic promoted by Audio Library https://youtu.be/iYYxnasvfx8

In this episode, Conor and Bryce chat with Kevlin Henney about C++, Python and more!Link to Episode 190 on WebsiteDiscuss this episode, leave a comment, or ask a question (on GitHub)TwitterADSP: The PodcastConor HoekstraBryce Adelstein LelbachAbout the GuestKevlin Henney is an independent consultant, speaker, writer and trainer. His software development interests are in programming, practice and people. He has been a columnist for various magazines and websites. He is the co-author of A Pattern Language for Distributed Computing and On Patterns and Pattern Languages, two volumes in the Pattern-Oriented Software Architecture series, and editor of 97 Things Every Programmer Should Know and co-editor of 97 Things Every Java Programmer Should Know.Show NotesDate Recorded: 2024-07-11Date Released: 2024-07-12When zombies attack! Bristol city council ready for undead invasionACCU Conference97 Things Every Programmer Should Know (GitHub)97 Things Every Programmer Should Know97 Things Every Java Programmer Should KnowC++Now 2018: Ben Deane “Easy to Use, Hard to Misuse: Declarative Style in C++”When to Use a List Comprehension in PythonIntro Song InfoMiss You by Sarah Jansen https://soundcloud.com/sarahjansenmusicCreative Commons — Attribution 3.0 Unported — CC BY 3.0Free Download / Stream: http://bit.ly/l-miss-youMusic promoted by Audio Library https://youtu.be/iYYxnasvfx8

Renowned herbalists Chanchal Cabrera and Kat Maier are hosting a couple of INCREDIBLE events this summer. The events take place between July 31 to August 4, 2024. LEARN MORE & REGISTER | https://chanchalcabrera.com/events/ Tune into today's episode of the HerbRally Podcast to learn more about both events.  Advanced Clinical Practicum – Putting Theory into Practice July 31 - August 2, 2024 Innisfree Farm, Courtenay BC LEARN MORE & REGISTER Energetic Herbalism – Reading the Pattern Language of our Landscapes and our Selves August 3 - 4, 2024 LEARN MORE & REGISTER I am always so incredibly impressed by the brilliance and wisdom of these two herbalists. These events are going to be absolutely amazing, I have no doubt.  Thanks to Chanchal and Kat for creating these opportunities for the herbal community, as well as for taking the time to record this podcast episode.  And thanks to you dear listener for tuning in!  See you in the next episode, ~Mason LINKS & RESOURCES Chanchal Cabrera | ChanchalCabrera.com Kat Maier | SacredPlantTraditions.com BOOK: Energetic Herbalism | BUY THE BOOK

Stephanie shares an intriguing discovery about the origins of design patterns in software, tracing them back to architect Christopher Alexander's ideas in architecture. Joël is an official member of the Boston bike share system, and he loves it. He even got a notification on the app this week: "Congratulations. You have now visited 10% of all docking stations in the Boston metro area." #AchievementUnlocked, Joël! Joël and Stephanie transition into a broader discussion on data modeling within software systems, particularly how entities like companies, employees, and devices interconnect within a database. They debate the semantics of database relationships and the practical implications of various database design decisions, providing insights into the complexities of backend development. Christopher Alexander and Design Patterns (https://www.designsystems.com/christopher-alexander-the-father-of-pattern-language/) Rails guide to choosing between belongsto and hasone (https://edgeguides.rubyonrails.org/association_basics.html#choosing-between-belongs-to-and-has-one) Making impossible states impossible (https://www.youtube.com/watch?v=IcgmSRJHu_8) Transcript: We're excited to announce a new workshop series for helping you get that startup idea you have out of your head and into the world. It's called Vision to Value. Over a series of 90-minute working sessions, you'll work with a thoughtbot product strategist and a handful of other founders to start testing your idea in the market and make a plan for building an MVP. Join for all seven of the weekly sessions, or pick and choose the ones that address your biggest challenge right now. Learn more and sign up at tbot.io/visionvalue. JOËL: Hello and welcome to another episode of The Bike Shed, a weekly podcast from your friends at thoughtbot about developing great software. I'm Joël Quenneville. STEPHANIE: And I'm Stephanie Minn. And together, we're here to share a bit of what we've learned along the way. JOËL: So, Stephanie, what's new in your world? STEPHANIE: So, I learned a very interesting tidbit. I don't know if it's historical; I don't know if I would label it that. But, I recently learned about where the idea of design patterns in software came from. Are you familiar with that at all? JOËL: I read an article about that a while back, and I forget exactly, but there is, like, a design patterns movement, I think, that predates the software world. STEPHANIE: Yeah, exactly. So, as far as I understand it, there is an architect named Christopher Alexander, and he's kind of the one who proposed this idea of a pattern language. And he developed these ideas from the lens of architecture and building spaces. And he wrote a book called A Pattern Language that compiles, like, all these time-tested solutions to how to create spaces that meet people's needs, essentially. And I just thought that was really neat that software design adopted that philosophy, kind of taking a lot of these interdisciplinary ideas and bringing them into something technical. But also, what I was really compelled by was that the point of these patterns is to make these spaces comfortable and enjoyable for humans. And I have that same feeling evoked when I'm in a codebase that's really well designed, and I am just, like, totally comfortable in it, and I can kind of understand what's going on and know how to navigate it. That's a very visceral feeling, I think. JOËL: I love the kind of human-centric approach that you're using and the language that you're using, right? A place that is comfortable for humans. We want that for our homes. It's kind of nice in our codebases, too. STEPHANIE: Yeah. I have really enjoyed this framing because instead of just saying like, "Oh, it's quote, unquote, "best practice" to follow these design patterns," it kind of gives me more of a reason. It's more of a compelling reason to me to say like, "Following these design patterns makes the codebase, like, easier to navigate, or easier to change, or easier to work with." And that I can get kind of on board with rather than just saying, "This way is, like, the better way, or the superior way, or the way to do things." JOËL: At the end of the day, design patterns are a means to an end. They're not an end in of itself. And I think that's where it's very easy to get into trouble is where you're just sort of, I don't know, trying to rack up engineering points, I guess, for using a lot of design patterns, and they're not necessarily in service to some broader goal. STEPHANIE: Yeah, yeah, exactly. I like the way you put that. When you said that, for some reason, I was thinking about catching Pokémon or something like filling your Pokédex [laughs] with all the different design patterns. And it's not just, you know, like you said, to check off those boxes, but for something that is maybe a little more meaningful than that. JOËL: You're just trying to, like, hit the completionist achievement on the design patterns. STEPHANIE: Yeah, if someone ever reaches that, you know, gets that achievement trophy, let me know [laughs]. JOËL: Can I get a badge on GitHub for having PRs that use every single Gang of Four pattern? STEPHANIE: Anyway, Joël, what's new in your world? JOËL: So, on the topic of completing things and getting badges for them, I am a part of the Boston bike share...project makes it sound like it's a, I don't know, an exclusive club. It's Boston's bike share system. I have a subscription with them, and I love it. It's so practical. You can go everywhere. You don't have to worry about, like, a bike getting stolen or something because, like, you drop it off at a docking station, and then it's not your responsibility anymore. Yeah, it's very convenient. I love it. I got a notification on the app this week that said, "Congratulations. You have now visited 10% of all docking stations in the Boston metro area." STEPHANIE: Whoa, that's actually a pretty cool accomplishment. JOËL: I didn't even know they tracked that, and it's kind of cool. And the achievement shows me, like, here are all the different stations you've visited. STEPHANIE: You know what I think would be really fun? Is kind of the equivalent of a Spotify Wrapped, but for your biking in a year kind of around the city. JOËL: [laughs] STEPHANIE: That would be really neat, I think, just to be like, oh yeah, like, I took this bike trip here. Like, I docked at this station to go meet up with a friend in this neighborhood. Yeah, I think that would be really fun [laughs]. JOËL: You definitely see some patterns come up, right? You're like, oh yeah, well, you know, this is my commute into work every day. Or this is that one friend where, you know, every Tuesday night, we go and do this thing. STEPHANIE: Yeah, it's almost like a travelogue by bike. JOËL: Yeah. I'll bet there's a lot of really interesting information that could surface from that. It might be a little bit disturbing to find out that a company has that data on you because you can, like, pick up so much. STEPHANIE: That's -- JOËL: But it's also kind of fun to look at it. And you mentioned Spotify Wrapped, right? STEPHANIE: Right. JOËL: I love Spotify Wrapped. I have so much fun looking at it every year. STEPHANIE: Yeah. It's always kind of funny, you know, when products kind of track that kind of stuff because it's like, oh, like, it feels like you're really seen [laughs] in terms of what insights it's able to come up with. But yeah, I do think it's cool that you have this little badge. I would be curious to know if there's anyone who's, you know, managed to hit a hundred percent of all the docking stations. They must be a Boston bike messenger or something [laughs]. JOËL: Now that I know that they track it, maybe I should go for completion. STEPHANIE: That would be a very cool flex, in my opinion. JOËL: [laughs] And, you know, of course, they're always expanding the network, which is a good thing. I'll bet it's the kind of thing where you get, like, 99%, and then it's just really hard to, like, keep up. STEPHANIE: Yeah, nice. JOËL: But I guess it's very appropriate, right? For a podcast titled The Bike Shed to be enthusiastic about a bike share program. STEPHANIE: That's true. So, for today's topic, I wanted to pick your brain a little bit on a data modeling question that I posed to some other developers at thoughtbot, specifically when it comes to associations and associations through other associations [laughs]. So, I'm just going to kind of try to share in words what this data model looks like and kind of see what you think about it. So, if you had a company that has many employees and then the employee can also have many devices and you wanted to be able to associate that device with the company, so some kind of method like device dot company, how do you think you would go about making that association happen so that convenience method is available to you in the code? JOËL: As a convenience for not doing device dot employee dot company. STEPHANIE: Yeah, exactly. JOËL: I think a classic is, at least the other way, is that it has many through. I forget if you can do a belongs to through or not. You could also write, effectively, a delegation method on the device to effectively do dot employee dot company. STEPHANIE: Yeah. So, I had that same inkling as you as well, where at first I tried to do a belongs to through, but it turns out that belongs to does not support the through option. And then, I kind of went down the next path of thinking about if I could do a has one, a device has one company through employee, right? But the more I thought about it, the kind of stranger it felt to me in terms of the semantics of saying that a device has a company as opposed to a company having a device. It made more sense in plain English to think about it in terms of a device belonging to a company. JOËL: That's interesting, right? Because those are ways of describing relationships in sort of ActiveRecord's language. And in sort of a richer situation, you might have all sorts of different adjectives to describe relationships. Instead of just belongs to has many, you have things like an employee owns a device, an employee works for a company, you know because an employee doesn't literally belong to a company in the literal sense. That's kind of messed up. So, I think what ActiveRecord's language is trying to use is less trying to, like, hit maybe, like, the English domain language of how these things relate to, and it's more about where the foreign keys are in the database. STEPHANIE: Yeah. I like that point where even though, you know, these are the things that are available to us, that doesn't actually necessarily, you know, capture what we want it to mean. And I had gone to see what Rails' recommendation was, not necessarily for the situation I shared. But they have a section for choosing between which model should have the belongs to, as opposed to, like, it has one association on it. And it says, like you mentioned, you know, the distinction is where you place the foreign key, but you should kind of think about the actual meaning of the data. And, you know, we've talked a lot about, I think, domain modeling [chuckles] on the show. But their kind of documentation says that...the has something relationship says that one of something is yours, that it can, like, point back to you. And in the example I shared, it still felt to me like, you know, really, the device wanted to point to the company that it is owned by. And if we think about it in real-world terms, too, if that device, like, is company property, for example, then that's a way that that does make sense. But the couple of paths forward that I saw in front of me were to rework that association, maybe add a new column onto the device, and go down that path of codifying it at the database level. Or kind of maybe something as, like, an in-between step is delegating the method to the employee. And that's what I ended up doing because I wasn't quite ready to do that data migration. JOËL: Adding more columns is interesting because then you can run into sort of data consistency issues. Let's say on the device you have a company ID to see who the device belongs to. Now, there are sort of two different independent paths. You can ask, "Which company does this device belong to?" You can either check the company ID and then look it up in the company table. Or you can join on the employee and join the employee back under company. And those might give you different answers and that can be a problem with data consistency if those two need to stay in sync. STEPHANIE: Yeah, that is a good point. JOËL: There could be scenarios where those two are allowed to diverge, right? You can imagine a scenario where maybe a company owns the device, but an employee of a potentially different company is using the device. And so, now it's okay to have sort of two different chains because the path through the employee is about what company is using our devices versus which company actually owns them. And those are, like, two different kinds of relationships. But if you're trying to get the same thing through two different paths of joining, then that can set you up for some data inconsistency issues. STEPHANIE: Wow. I really liked what you said there because I don't think enough thought goes into the emergent relationships between models after they've been introduced to a codebase. At least in my experience, I've seen a lot of thought go up front into how we might want to model an ActiveRecord, but then less thought into seeing what patterns kind of show up over time as we introduce more functionality to these models, and kind of understand how they should exist in our codebase. Is that something that you find yourself kind of noticing? Like, how do you kind of pick up on the cue that maybe there's some more thought that needs to happen when it comes to existing database tables? JOËL: I think it's something that definitely is a bit of a red flag, for me, is when there are multiple paths to connect to sort of establish a relationship. So, if I were to draw out some sort of, like, diagram of the models, boxes, and arrows or something like that, and then I could sort of overlay different paths through that diagram to connect two models and realize that those things need to be in sync, I think that's when I started thinking, ooh, that's a potential danger. STEPHANIE: Yeah, that's a really great point because, you know, the example I shared was actually a kind of contrived one based on what I was seeing in a client codebase, not, you know, I'm not actually working with devices, companies, and employees [laughs]. But it was encoded as, essentially, a device having one company. And I ended up drawing it out because I just couldn't wrap my head around that idea. And I had, essentially, an arrow from device pointing to company when I could also see that you could go take the path of going through employee [laughs]. And I was just curious if that was intentional or was it just kind of a convenient way to have that direct method available? I don't currently have enough context to determine but would be something I want to pay attention to. Like you said, it does feel like, if not a red flag, at least an orange one. JOËL: And there's a whole kind of science to some of this called database normalization, where they're sort of, like, they all have rather arcane names. They're the first normal form, the second normal form, the third normal form, you know, it goes on. If you look at the definition, they're all also a little bit arcane, like every element in a relation must depend solely upon the primary key. And you're just like, well, what does that mean? And how do I know if my table is compliant with that? So, I think it's worth, if you're Googling for some of these, find an article that sort of explains these a little bit more in layman's terms, if you will. But the general idea is that there are sort of stricter and stricter levels of the amount of sort of duplicate sources of truth you can have. In a sense, it's almost like DRY but for databases, and for your database schema in particular. Because when you have multiple sources of truth, like who does this device belong to, and now you get two different answers, or three different answers, now you've got a data corruption issue. Unlike bugs in code where it's, you know, it can be a problem because the site is down, or users have incorrect behavior, but then you can fix it later, and then go to production, and disruption to your clients is the worst that happened, this sort of problem in data is sometimes unrecoverable. Like, it's just, hey, -- STEPHANIE: Whoa, that sounds scary. JOËL: Yeah, no, data problems scare me in a way that code problems don't. STEPHANIE: Whoa. Could you...I think I interrupted you. But where were you going to go about once you have corrupted data? Like, it's unrecoverable. What happens then? JOËL: Because, like, if I look at the database, do I know who the real owner of this...if I want to fix it, let's say I fix my schema, but now I've got all this data where I've got devices that have two different owners, and I don't know which one is the real one. And maybe the answer is, I just sort of pick one and say, "Oh, the one that was through this association is sort of the canonical one, and we can just sort of ignore the other one." Do I have confidence in that decision? Well, maybe depending on some of the other context maybe, I'm lucky that I can have that. The doomsday scenario is that it's a little bit of one, a little bit of the other because there were different code paths that would write to one way or another. And there's no real way of knowing. If there's not too many devices, maybe I do an audit. Maybe I have to, like, follow up with all of my customers and say, "Hey, can you tell me which ones are really your devices?" That's not going to scale. Like, real worst case scenario, you almost have to do, like, a bit of a bankruptcy, where you say, "Hey, all the data prior to this date there's a bit of a question mark on it. We're not a hundred percent sure about it." And that does not feel great. So, now you're talking about mitigation strategies. STEPHANIE: Oof. Wow. Yeah, you did make it sound [laughs] very scary. I think I've kind of been on the periphery of a situation like this before, where it's not just that we couldn't trust the code. It's that we couldn't trust the data in the database either to tell us how things work, you know, for our users and should work from a product perspective. And I was on a previous client project where they had to, yeah, like, hire a bunch of people to go through that data and kind of make those determinations, like you said, to kind of figure out it out for, you know, all of these customers to determine the source of truth there. And it did not sound like an easy feat at all, right? That's so much time and investment that you have to put into that once you get to that point. JOËL: And there's a little bit of, like, different problems at different layers. You know, at the database layer, generally, you want all of that data to be really in a sort of single source of truth. Sometimes that makes it annoying to query because you've got to do all these joins. And so, there are various denormalization strategies that you can use to make that. Or sometimes it's a risk you're going to take. You're going to say, "Look, this table is not going to be totally normalized. There's going to be some amount of duplication, and we're comfortable with the risk if that comes up." Sometimes you also build layers of abstractions on top, so you might have your data sort of at rest in database tables fully normalized and separated out, but it's really clunky to query. So, you build out a database view on top of that that returns data in sort of denormalized fashion. But that's okay because you can always get your correct answer by querying the underlying tables. STEPHANIE: Wow. Okay. I have a lot of thoughts about this because I feel like database normalization, and I guess denormalization now, are skills that I am certainly not an expert at. And so, when it comes to, like, your average developer, how much do you think that people need to be thinking about this? Or what strategies do you have for, you know, a typical Rails dev in terms of how deep they should go [laughs]? JOËL: So, the classic advice is you probably want to go to, like, third to fourth normal form, usually three. There's also like 3.5 for some reason. That's also, I think, sometimes called BNF. Anyway, sort of levels of how much you normalize. Some of these things are, like, really, really basic things that Rails just builds into its defaults with that convention over configuration, so things like every table should have a primary key. And that primary key should be something that's fixed and unique. So, don't use something like combination of first name, last name as your primary key because there could be multiple people with the same name. Also, people change their names, and that's not great. But it's great that people can change their names. It's not great to rely on that as a primary key. There are things like look for repeating columns. If you've got columns in your schema with a number prefix at the end, that's probably a sign that you want to extract a table. So, I don't know, you have a movie, and you want to list the actors for a movie. If your movie table has actor 1, actor 2, actor 3, actor 4, actor 5, you know, like, all the way up to actor 20, and you're just like, "Yeah, no, we fill, like, actor 1 through N, and if there's any space left over, we just put nulls in those columns," that's a pretty big sign that, hey, why don't you instead have a, like, actor's table, and then make a, like, has many association? So, a lot of the, like, really basic normalization things, I think, are either built into Rails or built into sort of best practices around Rails. I think something that's really useful for developers to get as a sense beyond learning the actual different normal forms is think about it like DRY for your schema. Be wary of sort of multiple sources of truth for your data, and that will get you most of the way there. When you're designing sort of models and tables, oftentimes, we think of DRY more in terms of code. Do you ever think about that a little bit in terms of your tables as well? STEPHANIE: Yeah, I would say so. I think a lot of the time rather than references to another table just starting to grow on a certain model, I would usually lean towards introducing a join table there, both because it kind of encapsulates this idea that there is a connection, and it makes the space for that idea to grow if it needs to in the future. I don't know if I have really been disciplined in thinking about like, oh, you know, there should really...every time I kind of am designing my database tables, thinking about, like, there should only be one source of truth. But I think that's a really good rule of thumb to follow. And in fact, I can actually think of an example right now where we are a little bit tempted to break that rule. And you're making me reconsider [laughter] if there's another way of doing so. One thing that I have been kind of appreciative of lately is on my current client project; there's just, like, a lot of data. It's a very data-intensive and sensitive application. And so, when we introduce migrations, those PRs get tagged for review by someone over from the DevOps side, just to kind of provide some guidance around, you know, making sure that we're setting up our models to scale well. One of the things that he's been asking me on my couple of code changes I introduced was, like, when I introduced an index, like, it happened to be, like, a composite index with a couple of different columns, and the particular order of those columns mattered. And he kind of prompted me to, like, share what my use cases for this index were, just to make sure that, like, some thought went into it, right? Like, it's not so much that the way that I had done it was wrong, but just that I had, like, thought about it. And I like that as a way of kind of thinking about things at the abstraction that I need to to do my dev work day to day and then kind of mapping that to, like you were saying, those best practices around keeping things kind of performant at the database level. JOËL: I think there's a bit of a parallel world that people could really benefit from dipping a toe in, and that's sort of the typed programming world, this idea of making impossible states impossible or making illegal states unrepresentable. That in the sort of now it's not schemas of database tables or schemas of types that you're creating but trying to prevent data coming into a state where someone could plausibly construct an instance of your object or your type that would be nonsensical in the context of your app, kind of trying to lock that down. And I think a lot of the ways that people in those communities think about...in a sense, it's kind of like database normalization for developers. So, if you're not wanting to, like, dip your toe in more of the sort of database-centric world and, like, read an article from a DBA, it might be worthwhile to look at some of those worlds as well. And I think a great starting point for that is a talk by Richard Feldman called Making Impossible States Impossible. It's for the Elm language. And there are equivalents, I think, in many others as well. STEPHANIE: That's really cool that you are making that connection. I know we've kind of briefly talked about workshops in the past on the show. But if there were a workshop for, you know, that kind of database normalization for developers, I would be the first to sign up [laughs]. JOËL: Hint, hint, RailsConf idea. There's something from your original question that I think is interesting to circle back to, and that's the fact that it was awkward to work through in Ruby to do the work that you wanted to do because the tables were laid out in a certain way. And sometimes, there's certain ways that you need the tables to be in order to be sort of safe to represent data, but they're not the optimal way that we would like to interact with them at the Ruby level. And I think it's okay for not everything in Ruby to be 100% reflective of the structure of the tables underneath. ActiveRecord gives us a great pattern, but everything is kind of one-to-one. And it's okay to layer on some things on top, add some extra methods to build some, like, connections in Ruby that rely on this normalized data underneath but that make life easier for you, or they better just represent or describe the relationships that you have. STEPHANIE: 100%. I was really compelled by your idea of introducing helpers that use more descriptive adjectives for what that relationship is like. We've talked about how Rails abstracted things from the database level, you know, for our convenience, but that should not stop us from, like, leaning on that further, right? And kind of introducing our own abstractions for those connections that we see in our domain. So, I feel really inspired. I might even kind of reconsider the way I handled the original example and see what I can make of it. JOËL: And I think your original solution of doing the delegation is a great example of this as well. You want the idea that a device belongs to a company or has an association called company, and you just don't want to go through that long chain, or at least you don't want that to be visible as an implementation detail. So, in this case, you delegate it through a chain of methods in Ruby. It could also be that you have a much longer chain of tables, and maybe they don't all have associations in Rails and all that. And I think it would be totally fine as well to define a method on an object where, I don't know, a device, I don't know, has many...let's call it technicians, which is everybody who's ever touched this device or, you know, is on a log somewhere for having done maintenance. And maybe that list of technicians is not a thing you can just get through regular Rails associations. Maybe there's a whole, like, custom query underlying that, and that's okay. STEPHANIE: Yeah, as you were saying that, I was thinking about that's actually kind of, like, active models are the great spot to put those methods and that logic. And I think you've made a really good case for that. JOËL: On that note, shall we wrap up? STEPHANIE: Let's wrap up. Show notes for this episode can be found at bikeshed.fm. JOËL: This show has been produced and edited by Mandy Moore. STEPHANIE: If you enjoyed listening, one really easy way to support the show is to leave us a quick rating or even a review in iTunes. It really helps other folks find the show. JOËL: If you have any feedback for this or any of our other episodes, you can reach us @_bikeshed, or you can reach me @joelquen on Twitter. STEPHANIE: Or reach both of us at hosts@bikeshed.fm via email. JOËL: Thanks so much for listening to The Bike Shed, and we'll see you next week. ALL: Byeeeeeeee!!!!!!!!!! AD: Did you know thoughtbot has a referral program? If you introduce us to someone looking for a design or development partner, we will compensate you if they decide to work with us. More info on our website at: tbot.io/referral. Or you can email us at: referrals@thoughtbot.com with any questions.

Our intrepid heroes visit the New York Public Library to meet up with visiting literary scholar Merrill Malone, an eccentric and the foremost expert on Virginia Gaskell's life and work, to get, once and for all, all the answers about the portals. What they don't realize is that shocking personal revelations and the very ground beneath their feet will alter forever within the library's seemingly pristine walls. Learn more about your ad choices. Visit megaphone.fm/adchoices

Our intrepid heroes visit the New York Public Library to meet up with visiting literary scholar Merrill Malone, an eccentric and the foremost expert on Virginia Gaskell's life and work, to get, once and for all, all the answers about the portals. What they don't realize is that shocking personal revelations and the very ground beneath their feet will alter forever within the library's seemingly pristine walls. Learn more about your ad choices. Visit megaphone.fm/adchoices

Emily McCorkle has landed the media appearance of a lifetime: a guest spot on the most respected talk show in America. But why is the host so concerned with her private details? And why are so many skeletons from her past making guest appearances? And who is the strange man with the hot dogs? Learn more about your ad choices. Visit megaphone.fm/adchoices

Emily McCorkle has landed the media appearance of a lifetime: a guest spot on the most respected talk show in America. But why is the host so concerned with her private details? And why are so many skeletons from her past making guest appearances? And who is the strange man with the hot dogs? Learn more about your ad choices. Visit megaphone.fm/adchoices

Months after the events of “Paths Not Taken,” Chelsea is working hard to turn a corner and improve her life. But when Emily McCorkle, the smear merchant journalist who severely damaged her reputation, returns to write a followup piece, Chelsea is thrown into a jarring maelstrom that involves demons, people from her past, and the possibility of redemption. Learn more about your ad choices. Visit megaphone.fm/adchoices

Months after the events of “Paths Not Taken,” Chelsea is working hard to turn a corner and improve her life. But when Emily McCorkle, the smear merchant journalist who severely damaged her reputation, returns to write a followup piece, Chelsea is thrown into a jarring maelstrom that involves demons, people from her past, and the possibility of redemption. Learn more about your ad choices. Visit megaphone.fm/adchoices

Pat Goras and Lucy Didas are a happy couple living in a fantastical suburban realm preparing for a delightful dragon brisket barbeque with their neighbors. But when a strange portal opens in their backyard, their lives and roles become permanently altered within the very Gray Area itself! Learn more about your ad choices. Visit megaphone.fm/adchoices

Pat Goras and Lucy Didas are a happy couple living in a fantastical suburban realm preparing for a delightful dragon brisket barbeque with their neighbors. But when a strange portal opens in their backyard, their lives and roles become permanently altered within the very Gray Area itself! Learn more about your ad choices. Visit megaphone.fm/adchoices

Light is an essential human nutrient. So much of our modern built environment is built without regard to orienting and integrating natural light, and our health - physical, mental, spiritual, emotional and communal - suffers for it. The good news is that you can design your structures (or retrofit them) to bring natural light back into them and create buildings and places within them that support human thriving because they are well integrated with natural light. Join me for a dive into the patterns of human habitation design that enhance our relationship with light from Christopher Alexander's A Pattern Language: 105 - South Facing Outdoors 107 - Wings of Light 112 - Entrance Transition 128 - Indoor Sunlight 135 - Tapestry of Light and Dark 159 - Light On Two Sides Of Every Room 161 - Sunny Place 162 - North Face 163 - Outdoor Room 180 - Window Place 181 - The Fire (there is NO substitute for fire!) 182 - Eating Atmosphere 199 - Sunny Counter 223 - Deep Reveals 238 - Filtered Light 252 - Pools of Light Resources A Pattern Language [WHOLE TEXT PDF DOWNLOAD]: PatternLanguage.com – website for the book and Alexander's works Zone 0 Pattern Language Fundamentals - Designing Your Permaculture Kitchen ~Epi-076 Light, Water, Soil and Life - The Four Pillars Of A Productive And Profitable Homestead - Epi-005     ____________________________________________________________________________ WHAT I DO: Design: On-Site Consultation Online Site/Project Consultation Holistic Ecosystem Design   Implementation: Water Harvesting Earthworks High-function, Low-Maintenance Access Living Systems Spring Development   Courses: Minimum Holistic Goal Building Your Sovereign Homestead   Media: The Sovereign Homestead Podcast YouTube Instagram      

Join me today as we discuss designing functional kitchen spaces that people want to be in. Lots of people are inheriting kitchens designed more for magazine covers than for function - and where there is a lack of function there is a concommitant increase in friction, which means more stress and less joy. Kitchens are the Zone 1 of Zone 0 - Zone 0 referring to the space inside the home. Kitchens are the heart of human life - communion over shared food, shared work, a space for being together, conversing, and generally connecting over the daily activities that make up life. Poorly designed kitchens discourage healthy human interaction and bonding, and thus are a huge lost opportunity for not only creating a thriving, functional homestead, but can actively undermine human thriving. In today's show we discuss some of the fundamental emergent patterns detailed by Christoper Alexander and company  A Pattern Language - a seminal work on the patterns of human habitation that support and promote human well being. This book belongs on your shelf if you're serious about creating healthy human habitats. It is guaranteed to spark fresh ideas and perspectives for examining your space, even if you've been there for decades, and give you actual tangible design guidelines if you're starting from scratch or remodeling to build functional, beautiful places for life to happen. In this episode we will discuss the following patterns as they pertain to permaculture kitchens specifically and Zone 0 home design generally: 127 - Intimacy Gradients 129 - Common Areas At The Heart 159 - Light On Two Sides 139 - Farmhouse Kitchen 184 - Cooking Layout 182 - Eating Atmosphere Show Resources A Pattern Language [WHOLE TEXT PDF DOWNLOAD]: PatternLanguage.com - website for the book and Alexander's works   ____________________________________________________________________________ WHAT I DO: Design: On-Site Consultation Online Site/Project Consultation Holistic Ecosystem Design   Implementation: Water Harvesting Earthworks High-function, Low-Maintenance Access Living Systems Spring Development   Courses: Minimum Holistic Goal Building Your Sovereign Homestead   Media: The Sovereign Homestead Podcast YouTube Instagram      

Two questions that pop up regularly in my world are, “I want to take my Feng Shui deeper – what resources do you recommend?” and, “How do I prepare for a Feng Shui consultation?” Both excellent Qs, so let's unpack them!   RESOURCES: join the conversation | *Become Your Own Feng Shui Consultant* course become certified | House Therapy Certification buy the book | Simple Shui for Every Day: 365 Ways to Feng Shui Your Life subscribe to the newsletter | Simple Shui follow along | Instagram   House Therapy | graduate directory read the book | A Pattern Language

With decades of experience in education, Dr. Peter Liljedahl realized that classrooms and workspaces have long been failing to engage those within them. He began a push to shift the paradigm of learning by challenging every classroom norm he could find - and it worked. Dr. Liljedahl was able to increase student thinking and engagement, and his revolutionary ideas are now able to be applied to work around the world.Dr. Peter Liljedahl is an author, researcher, and Professor of Faculty Education at Simon Fraser University in Vancouver, Canada. He has authored or co-authored 38 journal articles, over 50 conference papers, and 12 books including Building Thinking Classrooms. Working within education for decades, Peter consults regularly with schools, school districts, and ministries of education on issues of teaching and learning, assessment, and numeracy. In this episode, Dart and Peter discuss:- Peter's redesign of the classroom and how it can be applied to work- How to create an environment that cultivates thinking- Transforming norms to achieve better results- The importance of collaboration in work and learning- The best ways to evaluate employee performance- Deconstructing ideas into actionable points- What creates “Aha!” moments- The structure of a good task- And other topics…Dr. Peter Liljedahl is an author, researcher, and Professor of Faculty Education at Simon Fraser University in Vancouver, Canada. He has authored or co-authored over 38 book chapters, 38 journal articles, over 50 conference papers, and 12 books including Building Thinking Classrooms. Working within education for decades, Peter consults regularly with schools, school districts, and ministries of education on issues of teaching and learning, assessment, and numeracy. Peter is the current president of the Canadian Mathematics Education Study Group (CMESG) and the International Group for the Psychology of Mathematics Education (PME). He also serves on various editorial boards and is a senior editor of IJSME. Dr. Liljedahl recently received the Cmolik Prize for the enhancement of public education in BC as well as the Margaret Sinclair Memorial Award for innovation and excellence in mathematics education.Resourced mentioned:Building Thinking Classrooms in Mathematics, Grades K-12, by Peter Liljedahl: https://www.amazon.com/Building-Thinking-Classrooms-Mathematics-Grades/dp/1544374836Weapons of the Weak, by James Scott: https://www.amazon.com/Weapons-Weak-Everyday-Peasant-Resistance/dp/0300036418 A Pattern Language, by Christopher Alexander: https://www.amazon.com/Pattern-Language-Buildings-Construction-Environmental/dp/0195019199Connect with Peter:https://buildingthinkingclassrooms.com/Facebook Groups: Thinking Classrooms

Freddi und Adrian sprechen über Dominik Eulberg, A Pattern Language und darüber warum Musik uns glücklich macht. Empfehlungen aus der Folge: einemustersprache.de https://www.youtube.com/watch?v=W1PBem0xjQs&list=PLxrWmu4Of0cCmsdrspyGhKgqsItksOR https://www.instagram.com/am_draht/

Andrew has been a community development worker, mechanic, small business owner, and now co-founder of Eco Villages Australia - an organisation that helps people live collaboratively. Co-founder and resident of the Maleny Eco Village, he strives to live a life of economic, cultural, social and ecological regeneration.  "Social disconnection has hit epidemic proportions. Now is the time to find a way to connect with self, each other and the earth." In this episode, Andrew speaks to the importance of valuing native plants and medicines and the wisdom of first nations people to learn about relationships and reciprocal living. From sacred economics to his perspective of the eight forms of capital/wealth, Andrew shares how he financially co-seeded an eco-village with 0% interest to remodel housing loans and trust. He gives some insight into life in the village and how they consider individual capacity, the gift economy and how 'working together' is their superpower. Andrew now travels to offer free forums to anyone interested in learning how to start or be part of a small-scale village that cares for the earth, people and economic equality in the face of the current housing crisis. He calls himself 'a busker of ideas' and discusses his unique perspective of 'social healing' as a form of medicine and advocates for confronting trauma collectively within the support of a village, rather than in isolation." Claire (also co-founder) from Maleny Eco-village offers free Intentional Healing Therapy and invites bookings via text to 0439 532 299. CONNECT: Website: https://www.ecovillages.au/ Facebook: https://www.facebook.com/ecovillagesaustralia Youtube: @ecovillagesaustralia8549 SHOW NOTES: Video Intro to Eco Villages Australia: ⁠https://youtu.be/zs_l6QEHuo0⁠ Sacred Economics by Charles Eisenstein: https://sacred-economics.com/ Dark Emu by Bruce Pascoe: https://iview.abc.net.au/show/dark-emu-story Platform Cooperativism by Douglass Rushkoff: https://youtu.be/twUcIuetL4Y?t=599 Retro Suburbia by David Holmgren: https://retrosuburbia.com/ Pattern Language & The Timeless Way of Building: https://www.patternlanguage.com/ CSIRO Australian Food Systems: https://www.csiro.au/en/work-with-us/services/consultancy-strategic-advice-services/CSIRO-futures/Agriculture-and-Food/Reshaping-Australian-Food-Systems Do we only have 60 harvests left?: https://ourworldindata.org/soil-lifespans Learn more about permaculture & home-grown edible gardening: www.earthmumma.co To learn more about The Elder Tree, visit the website at ⁠www.theeldertree.org⁠ and donate to the crowdfunding campaign ⁠here⁠. You can also follow The Elder Tree on ⁠Facebook⁠ and ⁠Instagram⁠ and ⁠sign up to the newsletter⁠. Find out more about this podcast and the presenters ⁠here⁠. Get in touch with The Elder Tree at:  ⁠asktheeldertree@gmail.com⁠ The intro and outro song is "⁠Sing for the Earth⁠" and was kindly donated by Chad Wilkins.  You can find Chad's music ⁠here⁠ and ⁠here⁠.

I was a core member of what Farrell would call a collaborative circle: the four people who codified Context-Driven Testing. That makes me think I can supplement Farrell's account with what it feels like to be inside a circle. I try to be "actionable", not just some guy writing a memoir.My topics are: what the context-driven circle was reacting against; the nature of the reaction and the resulting shared vision; how geographically-distributed circles work (including the first-wave feminist Ultras and the Freud/Fleiss collaboration); two meeting formats you may want to copy; why I value shared techniques over shared vision; how circles develop a shared tone and stereotyped reactions, not just a shared vision; and, the nature of “going public” with the vision. MentionedMichael P. Farrell, Collaborative Circles: Friendship Dynamics and Creative Work, 2001.Cem Kaner, Jack Falk, and Hung Quoc Nguyen, Testing Computer Software, 1993.Édouard Manet, Le Déjeuner sur l'herbe (The Luncheon on the Grass), 1863.context-driven-testing.com (including the principles of context-driven testing), 2001?Cem Kaner, James Bach, Bret Pettichord, Lessons Learned in Software Testing: a Context-Driven Approach, 2002.Association for Software Testing.Elisabeth Hendrickson, Explore It! Reduce Risk and Increase Confidence with Exploratory Testing, 2012.Jonathan Bach, "Session-Based Test Management", 2000.Patrick O'Brian, Post Captain, 1972. (It's the second in a series that begins with Master and Commander.)Four articles that demonstrate personal style:James Bach, “Enough About Process, What We Need Are Heroes”, IEEE Software, March 1995.Brian Marick, "New Models for Test Development", 1999.Bret Pettichord, "Testers and Developers Think Differently", 2000.James Bach, "Explaining Testing to THEM", 2001.Los Altos Workshop on Software Testing and related:Cem Kaner, "Improving the Maintainability of Automated Test Suites", 1997. (This contains the conclusions of LAWST 1 as an appendix.)The LAWST Handbook (1999) and LAWST Format (1997?) describe the meeting format.The "Pattern Writers' Workshop" style is most fully explained in Richard P. Gabriel, Writers' Workshops & the Work of Making Things: Patterns, Poetry... (2002). James Coplien, "A Pattern Language for Writer's Workshops" (1997), describes writers' workshops in the "Alexandrian style" of pattern description (the one used in the seminal A Pattern Language). "Writers Workshop Guidelines" is a terse description.Image creditThe image is the painting Le Déjeuner sur l'herbe.

Jesse chats with Josh Thompson 1701 BE Alum about his Turing story, Mythical Creatures, blogging, writing, TIL workflow, Scooters, traffic, urban design, and what's next. Some books mentioned are The Power Broker by Robert Caro, A Pattern Language by Christopher Alexander, The Color of Law by Richard Rothstein, and Streetfight by Janette Sadik-Khan.  You can read more from Josh at josh.works including his Turing guide at https://josh.works/turing-backend-prep-01-intro and his Robert Moses post at https://josh.works/robert-moses. You can learn more about Josh's traffic work at https://www.tiktok.com/@josh_exists If you or someone you know are code curious, we encourage you to attend a Turing Try Coding Event. You can register for a free Try Coding class at turing.edu/try-coding.

Jim talks with Carlos Perez about the ideas in his new book A Pattern Language for Generative AI: A Self-Generating GPT-4 Blueprint. They discuss GPT-4's ability to introspect on its capabilities, Christopher Alexander's idea of a pattern language, pattern language design, Jim's script-writing program, moving beyond ChatGPT to the OpenAI API, managing the context window, chain of thought prompting, the skyhook effect, the value of using tables, creation patterns, input-output pairs, the power of examples, punctuation, cloze prompts, compressing text, the mystery of LLM capabilities, an explanation for state emulation, the system prompt, explainability patterns, meta-levels of language, procedural patterns, design thinking prompts, the idea of a GPTpedia, composite patterns, in-painting vs out-painting, corrective patterns, 6 thinking hats, attribute listing prompts, problem restatements, inverted interaction, multiple-discipline prompts, modularity patterns, ChatGPT plugins, katas & meditations, and much more. Episode Transcript A Pattern Language for Generative AI: A Self-Generating GPT-4 Blueprint, by Carlos Perez "ScriptHelper-001: an experimental GPT-4 based Movie Script Writing Program," by Jim Rutt Artificial Intuition: The Improbable Deep Learning Revolution, by Carlos Perez Deep Learning AI Playbook: Strategy for Disruptive Artificial Intelligence, by Carlos Perez Artificial Empathy: A Roadmap for Human-Aligned Artificial Intelligence, by Carlos Perez Carlos E. Perez is a seasoned software architect and developer with 30 years of experience in bringing software systems from concept to production. He has authored books on Artificial Intuition, Fluency, and Empathy, with a primary focus on applying semiotic methods in Deep Learning. Carlos holds a Master's degree in Computer Science from the University of Massachusetts and has U.S. patents in expert systems and social networks.

Transcript: Joe Krebs 0:10 Agile FM radio for the Agile community.www agile.fm.Welcome to another podcast episode here of agile fm, I have Jurgen Appelo creator of unfix, which is a topic we want to talk about here today is unfix.com. That's where you can learn more about this topic. But we want to talk a little bit of what unfix is, where it came from, how old it is, how new it is, and what it can do for organizations out there. A super interesting pattern which I which is important. We want to explore what patterns are everywhere and also talk about what unfix is not. Welcome to the podcast for you. How you doing today?Jurgen Appelo 1:05 I am great. The weather is awesome here in my in my city in Rotterdam in the Netherlands. Looking forward to the trip tomorrow to Lima, Peru, which, which is something that I have been looking forward to quite a few weeks already. So longest trip and those are nice to have every now and then. And yeah, lots of things happening.Joe Krebs 1:29 Lima is are they interested in unfix? Or is this for pleasureJurgen Appelo 1:32 of course. That's what I'll be talking about. That's my keynotes agile, lean agile event. Yeah.Joe Krebs 1:41 All right. unfix is not another scaling framework. It's not a method. It's not a framework. What is it?Jurgen Appelo 1:49 It's a pattern library. That's that's how I call it. There are other pattern libraries such as sociocracy, triolo, and team topologies. And, and so on liberating structures, they are not frameworks, because you don't install them. That's the idea of a framework that you have something to implement. And then you can validate or verify that you did the implementation correctly. You can certify people with in the implementation roadmap, that is not what you do with a pattern library, all of the suggestions are options, there's nothing mandatory with a pattern library. So the best metaphor that I have is Lego. There is not a single block in the Lego box that is mandatory for you. All of them are optional. Some of the blocks are more obvious, then the others, so you will use them more often. Maybe nearly always. Some are more rare for special cases, but not a single part of the Lego toolbox is is mandatory. And that's that's how I see pattern languages. That's the real word that specialists use sometimes Pattern Language. Yeah. And yeah, that's that's what the unfix model is, as well.That is interesting, because in lego, a round shaped kind of piece could be a wheel on the car, or could be a pizza on the table. Right? Exactly. Joe Krebs 2:49 Creative creativity here, right? It's also interesting, because you are, sometimes you build with LEGO not that I have worked on with Lego in a long time. But you could build a house, you can build a street of houses or like a road or alignment, you could build a city. You know, there are some exercises out there in the Agile community where things are being built in isolation and put together there are there is a guy called Christopher Alexander I was exposed to, in the beginning of my career with is an architect where I'm nothing really in the Agile space, but he has influenced a lot of people in that how did how do these people like Christopher Alexander or Gang of Four, and others, there's many, many people out there in the community. How did they influence you? Or unfix?Jurgen Appelo 4:10 Yeah, I have the book actually here, one or two meters behind me the Pattern Language of Christopher Alexander where he published, I think in the 70s or something. He was the first one to recognize the benefits of micro solutions, small solutions to known problems that you have to combine to come up with larger custom made context dependent structures. And that is what cities are. So in the book Pattern Language, you find the public square as a pattern. Anyone knows what a public square is. You have public squares in New York City. I know quite a few famous ones. We have public squares here in Rotterdam. But the cities are completely different. Same with the the promenade as a pattern there are promenades in, in New York and also promenades in Rotterdam, and so on. So this book has 253 patterns that is quite a lot. But then it's up to you as an urban planner, a city designer to come up with ways of combining them that makes sense, within the context of the city, because some cities have mountains, others have lakes and rivers, and whatever, you have to work with the environment that you have. But then, within that environment, you're gonna use the familiar patterns that everyone is using that principle, you also find in while you mentioned it, design patterns are the Gang of Four and then book came out in the 90s, where they came up with familiar patterns in programming, the facade, the singleton, the model view controller, I'm sure many programmers listening to this know what I'm talking about. And it is up to you as an architect to use those patterns and combine them in any way you want, depending on what the software is supposed to do. The interesting thing is, I remember back then that some people implemented all those patterns as a framework that you could literally buy frameworks, like the dotnet implementation of all the patterns that you could then install on your computer. And, and I thought, that's, that's totally not what they meant. With the book, you should not turn those patterns into a framework that you can then install, because you're not supposed to do all of them. You only pick and choose, depending on context, what you need. And I think that is my main problem that I have with frameworks in the Agile community, where you have these rigid structures where something needs to be installed, like well, let's name the big one, the Scaled Agile Framework SAFe, they literally call the smallest version essential safe, it is in the name itself. That part is essential, it is mandatory. If you do not have an agile release, train, you do not have SAFe. So you must have an art, you must have PI planning, you must have quite a few other things that those are together the framework that needs to be installed. I do not believe in that approach. I do believe that the frameworks have lots of good patterns in them. But we have to break them down. We have to decompose them deconstruct into the smaller building blocks. And then let you in your organization, do the recombination, figure out how to combine the different patterns from different toolboxes SAFe. LESS team apologies, whatever. They all have practices that you can combine. And that's what I tried to do with the unfixed model. I just borrowed the good stuff that is already out there. Just as Christopher Alexander has done, cities existed before the book, surprisingly, good organizations that do common sense, good stuff already existed before unfix came out, I just capture the good stuff, I give it a name, I give it a visual say, well, this is what we've seen, that seems to make sense as a micro solution. We add it to the box, the little box as one of the options. And then you take it out when you think you can apply it. And the box is getting larger and larger. Because we need more options, so that you can build more stuff with the, with the pattern language. Joe Krebs 9:02 So this is very interesting, right? Because what you just mentioned about the essential piece of in your example was SAFe, but we could probably take any, any other framework as well. Right? But when we're looking at the essential piece that does not consider the environment you're in right. So we're coming back to Christopher Alexander, he does not see that. What is what is the environment you're in? What's your view of mountains? Do you have lakes Do you have how do we build around it right, you come in with the essential piece and it might not work for that environment right to have a little bit more of a flexible approach I think that is that's a good point now is unfix like buffet style, is that what people are they have to see is like there's a collection of patterns and people go out and says I'm gonna grab this I'm gonna grab this and grab this and I get confidence in the individual pattern, but I need the skills to combine them that they make sense togetherJurgen Appelo 9:55 exactly. I like the metaphor that you're using buffet style that might make it harder to sell things to people because I'm making them do work, I have to convince people that they have to do the thinking themselves don't do just a stupid implementation or something off the shelf. That is not going to work, you have to do your own thinking, according to your context to make things work, interestingly enough, I just read a couple of weeks ago, in a very different context, the scientific results of research into body weight, or body loss or body weight loss, what is the weight loss, weight loss? Weight loss programs?Joe Krebs 10:47 Weight loss? Yeah,Jurgen Appelo 10:48 yeah, that was the term I was looking for. And the evidence is in none of them work. None of the standard programs work. They already know that there is scientific evidence that the only thing that works if you create your own program, out of the common sense suggestions that are captured in all those other programs, the standard programs out there, but it is so context specific, a weight loss program that you have to customize it to who you are, what kind of body you have, what kind of lifestyle you have, et cetera, et cetera. So the following any standard program is, is is going to it's going to fail. Yeah, and that is the equivalent of following a standard standard framework, it's not going to work, you have to break it apart and use the individual components good. There is a lot of good advice in there is just the whole package that is sold that you have to get rid of.Joe Krebs 11:54 So some of the listeners, not fully familiar with with unfix might now think, throw everything out and use unfix that's not what you're saying. Right. So this is also important, because we are talking about SAFe and possibly other frameworks here right now, that does not mean that unfix is replacing these these kinds of things, right? How would they be? How do these coexist? And how to how do you envision to go into an organization say, hey, we'll, let's say there's an organization using a framework of any kind, but as unfix pair up with that approach.Jurgen Appelo 12:33 Now, yeah, I would like to help people stop thinking in terms of frameworks. And how do we implement it well, some suggest that there could be good starting points for customization. I think the jury's out on that argument, I'm not fully convinced that they are a good starting point, I think starting from scratch might sometimes be easier than starting from a framework implementation and then adapting it. But let's give them the benefit of the doubt people who have a framework and want to customize it, they could look at what the unfix model offers in this, and then see what else is in the Lego box that we can use to start changing this implementation that we have here with continuous improvement and, and small step experiments, to turn it into something completely different. So it would be similar to beginning with a standard weight loss program, but then realizing on day one, that there's not going to help, you'll have to you'll have to change the exact diet, the exact exercises and so on to start making it work for you. That I can agree that that might my approach.Joe Krebs 14:02 Yeah. So So that's, that's interesting. Like I for example, I teach a lot of adaptive org design courses, for example, how organizations shift, make the switch towards agility and kind of things to consider. There's a lot of talk about self management and self organization, obviously, in these courses and how to get to states like that does unfix if somebody listens now more from a leadership and managerial role, prior to this podcast is this unfix demand like a full self organized self managed like it's a radical name, right unfix? It's provocative, nice, nicely provocative, right? And it makes you think, does that also mean like we're going to the extremes with adaptive org design? How does a company steer that transition? Not necessarily top down structure, but even like any kind of structure in an organization how does unfix change that? Um, I think What I want to achieve here is to plant a flag on the horizon and show people, this is the direction that we want to be going. And I don't expect you to be here tomorrow. But I want you to move in that direction. And that direction is being a networked organization with a fractal or design. There are some companies, not many, but a few that have evolved quite far in that in that direction, famous one is Haier, the Chinese company where it was 10,12 years ago, where they reorganized themselves into a network of 4,000 micro enterprises was a 4,000 tiny little companies that that collaborate horizontally without big fat middle management layers, no matrix structure, whatever. And they are incredibly adaptive, they are super fast in in responding to opportunities. For example, when COVID hit the Chinese economy Haier was the was the first one to start making masks or a face mask for half the country, basically, because there was an opportunity, and they could respond incredibly fast to this to this new thing emerging. While normally they make vacuum cleaners and and and fridges and whatever, but they switched to face masks short, why not? Why not? Yeah. And so this is a very inspiring company as that shows what you can do as a network company instead of a hierarchical matrix organization. And that is, as I said, the flag on the horizon that I want to offer people try and go in this direction. But I do agree that it is a step by step thing, you'll first want to move into the adjacent possible as some complexity thinkers would would say, you open up opportunities in a new direction, by making small steps, and that unlocks other doors, and then you go through that door. And if something doesn't work out, you make a step back and you move in another direction. I'm sure that is also what Haier has done that local experimentation before they did the big radical change of firing all the middle managers basically, because that was quite a revolutionary thing. That was Kaikaku not Kaizen them at that time, but I'm sure they did some Kaizen before they were sure about the big step they wanted to make. I keep telling everyone started with small experimentation. I have already 150 patterns in the in the pattern language in the model, and more are coming. And there's plenty to experiment with very small things that will harm nobody. So just start playing, get some experience. And then when something seems to be working well, you could make some more radical steps. With your org design,assemble your city, right? Build your city like start small somewhere, right?Jurgen Appelo 18:14 Exactly. And by the way, it's not only about organization design, about crew types, Team types and so on. There's also decision making methods. Also about goal setting patterns are coming out in the next couple of months. So more advanced version of OKRs (objecetves and key results) basically the whole OKRs and MBO (management by objectives) KPI stuff, I have deconstructed into patterns. And that's going to be awesome, I think,for people to playwith and make their own OKRs like approach with the individual patterns that we're going to offer. So yeah, organization structure, business processes and collaboration. There's lots of different angles on on the pattern library. You can start anywhere, whatever is the lowest hanging fruit the smallest pain that you can address. Start playing like with a Lego box. There are 4,000 different types of Lego pieces. Did you know that Joe 4,000 Neither did I. Yes, that's quite a lot of options that but nobody starts with with 4,000 pieces on the table now doesn't that doesn't make sense. You start with a subset of the more obvious ones and then you will dig into the rest later on with when you gained a bit of experience. Joe Krebs 19:44 Before we go into one of the maybe we can explore one of those patterns is one thing I noticed and I just want to follow up on this because we just talked about you know, leadership etc. and organizational change. These are this is a bottom up kind of approach, right? And you just mentioned like some form of middle management and that was reduced or removed. You're not saying unfix we're not have any managers or leaders? And I think we were very clear about this. What is the role of though of leadership? If it's a bottom up movement? How can leadership support unfix? within an organization? If we're seeing on one side, there is some form of streamlining going on within an organization, which I think many organizations would benefit from, as well. Right. But on the other side, it might be the the the question of a leader that says, I don't know what my role is, in all this. How can I support unfix to make the organization a better place?Jurgen Appelo 20:46 So well, that's where my previous work on management 3.0, comes in, I always say manage the system and not the people. And the very same thing, I suggest with the unfix model, where we have the governance crew, which is the team of chiefs, Chief Executive Officer, Chief Information Officer chief whatever. At the base level, and the base is what I'd hire would be the micro enterprise, some might call it a tribe, a self sustaining business unit, whatever small units of, of maybe up to 100, people maybe a little more, but not much, much more than that, that is the unit that we're looking at, that should be autonomous self managing, with a very specific business model proposition that they offer to either the world outside to customers or users or to other parts of the network in within the company. And that unit needs to be managed, that someone has to take responsibility for the success of that unit. All of those 4,000 micro enterprises hat Haier are managed by a chief. And actually, the fascinating thing at hire is that if the chief is not doing well, for three months, there's an automatic re-election triggered, where other people can volunteer to take up the role of the chief and see if they can do better that is interesting. But I will not go there yet with my suggestions because that makes some managers very scared of their of their job. But the fact is, the unit needs management but management of the unit of the system, how does that system work because you need to put some constraints in place on on how those 20 50,100 people in that base, collaborate with each other. And we want to make and that's what the name is about unfix we want to keep that unit as flexible as versatile as possible with its organization structure. That means that you should try and not have managers on teams. So no manager on a scrum team, no manager on a team of coaches, no manager on a platform team or anything because as soon as you have a manager to the air, you create territories, I know from personal experience, how hard it is to change those territories when you put someone there, this is this is now the place that you are going to manage and you will decide how much people get paid within this part of the organization. Then you you just put into in cement a part of your organization, you you should try and not do that. You can have a captain, on on on a crew, for example, that is something else that is like a pilot on a plane. That is a person who has the responsibility for the mission. But the pilot does not decide how much the stewards and stewardesses get paid. They don't have HR responsibility. They do report to the Chiefs how well the mission has gone and who deserves some extra credits or compliments or whatever it is they know everything that goes on, on that mission, but they do not have management responsibility. They are leaders of course captains are leaders that so we offer a captain role and what we call crews as an option, you don't need a captain maybe but it is an option that you can consider and I know companies have great success with Mission leads as they call them. For example, well I call him Captain but that's the same thing. We call that pattern the captain role. But as long as you keep that management responsibility out of it and with management I mean people management HR responsibility and desirable gets paid and career Development and so on, remove that out on the teams put that in the governance crew level, so that the rest of the bases stays flexible.Joe Krebs 25:11 Very, that's very interesting. And I think when you just said that, and you had a smile on your face about exactly like the managing the pay and managing promotions, etc. And I think everybody out there who's listening to this right now might say, that's true in my organization that is a blocker, if we're removing that, that might change the environment. And that makes it a case for a pattern has proven micro solution for a common for a common problem. So this is, this is really cool. What I want to touch on one thing you just mentioned the word crew. What I like about the flexibility of these patterns is that you it's almost like you have name suggestions for these patterns. But you always make the link to alternatives where we say like you might have heard this word before. And this is really what it means over here. So it's like the name of the pattern, right? The same in a cookbook, where it could be a Sicilian tomato sauce, and we could be Northern Italian Italian sauce, but at the end of the day, there will be a tomato in it right? In either or, with subtle nuances in it, but you do speak about a crew. And I think that's like one example I want to take you just mentioned that. I don't know them all from the top of my head. But there are different crews, you just set the governance crew, there's I think there's a platform crew. This might be a lot of crews for somebody who looks at unfix. In the beginning. I like your approach of starting somewhere lowest hanging fruit you mentioned when but why are there different crews? What's What's the benefit of looking at the crews in different ways from different angles?Jurgen Appelo 26:53 Well, let's let's take the two topics. separately first, naming is important. So indeed, I've used the word crew instead of team because the word team is overloaded these days people use the word team for anything. Basically, crew is a bit more specific. I use word base for what other people would call a tribe. Some people complain about cultural appropriation and things like that. So I've tried to steer away from the tribe word. Base is the home the place where people return to I like that word. And we use forum instead of Guild because by default, people assume that guilds are things that emerge bottom up that it always volunteers, that is possible. But a forum could be more formal. So it could be something bottom up. But a forum could also be installed by managers, for example, where they say we want alignment across bases on a certain technology, like we don't want five different testing platforms, we will not one, because that's cheaper. Now you go and figure out with each other which one it is going to be and we want a forum to take care of that. So language is important. But indeed, people can use their own words in the pattern language, you need words to identify things. And I think about what is the best word that comes with as little baggage as possible. But I leave it to people to use their own words in their own organization. If you like the word, pod or squad, instead of crew, go ahead, knock yourself out. The second part of the question was indeed the different crew types I borrow for from Team topologies. Actually, they simply identified 4 patterns before I did, and I credit them for that, which is the typical value stream team, Scrum Kanban. Team, whatever, we know how that works. And then the three exceptions which they call the enabling team, the complicated subsistent team and the platform team. Those are three different kinds of teams that are inward facing. And I borrowed the same ones I changed the name a little bit maybe too off topic to discuss all the reasoning behind it, but I just borrowed the same four and they added three other times that I thought were useful, which is experienced crew partnership crew and the governance crew and we just talked about so the set is seven, seven kinds of crews are teams within the base and they are like Lego blocks you use them as you want. I always tell people I hope you have as many value stream grooves as possible because that is like the most popular block. The Lego block the most beneficial ones I hope seventy percent of your teams aren't that type. But an enterprise of 100,000 people is not 20,000 Scrum teams, that doesn't work, you need some other kinds of teams to hold it all together. And that is why team topologies identify the different kinds. Because not everyone is offering value to a customer, some people are offering value internally to the other employees. And there are different kinds of behaviors that you can identify like a platform, through, as I call them, they offer a value to others on a self service basis, almost like an API, or sometimes literally through an API, in terms of technical infrastructure, or in DevOps capabilities, whatever. But I have seen kindergarten on site at a company where I was a couple of years ago. And you could bring your baby and toddler and throw them in the basement. And by the end of the day, you could pick them up. That's an API as well. That is that is also a platform crew, the kindergarten team. So that's that's that's one kind of platform crew. And then there's others the facilitation crew and capabilities. Again, alternative exceptions to the rule, you could say,Joe Krebs 31:25 but but I do want to reiterate and get your confirmation, this is not something you would be setting up all these crews up front, right, this is you're building piece by piece, you're starting somewhere start small. So this is not completing the picture. And having a crew everywhere, this is not installing unfix, you might start with the value stream crew. AndJurgen Appelo 31:46 I know it sometimes it's more clarifying what people are already doing, or giving it a name to something that seemed sensible. Actually, I had people reach out to me literally, when I published the unfix model for the first time where people said finally now, now we have a language for what we have already been doing for several years. And it seemed natural to us only we didn't we didn't see this visualized in other frameworks like like that. Yeah, so there are several case studies like that, on the unfix website web page already use the patterns, they they didn't have the names yet, I was just giving it a name and a color and that's it. But um, so what what can help is with a pattern language is it helps people to have a conversation, like, Okay, we have a couple of Scrum teams here. That is obvious or Kanban teams, whatever your preferred, agile approach, but a few of the other people are inward facing with the things that they do instead of outward facing what, what are they? Well, that depends on how they behave, do they literally sit with the others? Are they facilitating like agile coaches and so on then they would be facilitation crew, that's a different kind, but that gives you a name it gives you it gives those people recognition like that. So we we are this we are this pattern the facilitation group pattern. And now we we know how to explain what we do to to the others. And if you don't have it, then you might want to consider it like, Okay, you have 10 Scrum teams or something, maybe want to consider facilitation crew because it could offer these benefits. They might be interesting in your in your context. So read up on the available patterns and decide whether this building block is something for you. And then you use it or you don't.Joe Krebs 31:46 Yeah. Awesome. Yeah. So you're talking to a pattern freak, right? I love I love the thinking behind it. I have you know, read all this stuff in the past. And as you mentioned, this started a while back. So really cool stuff. And for everybody out there interested in in unfix obviously on fixed.com is the place to go to learn a little bit about it. As you said, you're on your way to a conference, you're speaking as well as the unfix conferences. What's what's your approach on You know, sharing the wealth of unfix with the world, more conferences is the training programs behind it, etc. How do you how do you multiply Jurgen around the world in a way cloning that your model is sticking?Jurgen Appelo 34:50 I'm glad that we cannot clone ourselves because I'm a difficult enough person as it is. So I wouldn't, I wouldn't want to bother the world where have multiple copies of me. But no kidding kidding, all kidding aside, I do want the word out. And of course, I want people to play with this. I love working on the model and pattern language itself. I'm very, very happy to be doing the research and then pattern analysis and coming up with names and visualizations. I have other people who in their own way try to bring this to an audience. So for example, the unfixcon is organized by other people in Berlin. I know them, well, they use the brand, I am involved, but it is not me doing this. I have a team that is working on partnerships, so people can sign up as a partner and then use the the courseware materials to the unfix foundation classes. And again, I have team for that is not what I do. There's someone else creating an app plotter app that you can use to design on your computer, your org design with the unfixed patterns again, that somebody else so I actually want to enable a lot of people who have an idea of how can I bring this pattern language to certain users customers in any way that that seems sensible, and then enable them to do that. I have someone who creating a webshop with mugs and T shirts, and so on. All right, thumbs up. So and and someone else might be writing books on the topics or creating courseware modules, all of that I delegate to others, I just want to focus on the Patreon side because that makes me happy.Joe Krebs 36:46 Awesome. Well, you're getting to you also speak about it. So have fun with that meet a lot of people. The unfix model is the first thing that's going to strike you when you go to the website is colors, lots of colors, and maybe that is an expression on diversity, diversity and the patterns the approach and maybe the ways of how people approach unfix in in many many different ways.Jurgen Appelo 37:13 true! the colors well actually what I use colors for for 15 years people know me I'm not I consider myself in eternal midlife crisis and I need colors. But at the same time, it gives people a sense of playing with a Lego or having a playful toolbox. It's it should not look boring. I find I find very important. So there is also marketing psychological. It has to be colorful because life is too. Life is too short to use only boring colors. JoeJoe Krebs 37:53 Yeah. Thank you another black T shirt guy. Jurgen thank you so much. Thank you too. And thanks for sharing your thoughts and, and good luck with that. Thank you for listening to Agile FM, the radio for the Agile community. I'm your host Joe Krebs. If you're interested in more programming and additional podcasts, please go to www.agile.fm. Talk to you soon.

On this episode, Kris and David close out their architecture series. We talk: Making documentaries, three years of Lost Xplorers, almost good at podcasts after 400 episodes, beginner's mind, areas unexplored due to ants, constructing unknown areas in the mind, defense mechanisms against derangement, a go master vs. a computer, doing everything wrong, practicing thinking together, a sea change of strangeness, rappers who don't speak, anarchists of mind, thinking hard vs. thinking far, fans running too hot, making peace with hierarchies, suspicion of disorder, houses as machines for living, the children of the machine, the overgrown village, the balkanization of the Atlantic seaboard, the little black pig, technical difficulties, cuckoo clocks, a clear vision for the future of architecture, homelessness as an architectural problem, The Decorated Diagram, A Pattern Language, reading your spouse's thoughts, accuracy as an antidote to the truth, and the reality of dream beings.

We journey to a plant person's garden between the Great Lakes and the Appalachian Mountains, an apartment amid the Palos Borrachos of Buenos Aires and an oak-topped bluff above the Minnesota River Valley. Support the show: https://ko-fi.com/bendarkEpisode links:The trees of Buenos Aires: https://landingpadba.com/buenos-aires-tree-guide/Tsubo-niwa (pocket gardens): https://en.wikipedia.org/wiki/Tsubo-niwaThe Bluet Houstonia caerulea: https://plants.ces.ncsu.edu/plants/houstonia-caerulea/ A Pattern Language: https://en.wikipedia.org/wiki/A_Pattern_LanguageFor copies of Ben's book, The Grove: A Nature Odyssey in 19 ½ Front Gardens go here: https://linktr.ee/deargardenerThe dear gardeners on Instagram:Alicia: https://www.instagram.com/kalijardinJulie: https://www.instagram.com/juliewitmergardensMichael: https://www.instagram.com/sneaky.productions/

Join Visionary Urbanist Michael von Hausen for a broad yet intimate perspective on Vancouver urban design, from the '70s through to the present day.Michael has been laying Vancouver's groundwork since the '80s, as a key designer in the early development of False Creek. His multi-disciplinary perspective on urban design draws from landscape architecture, planning, design, and development, to forge an urban ‘greenfrastructure' to feed our bellies as well as our urban souls.Together Michael and Gord chart the development of Vancouver's design identity, focusing on the evolution of False Creek from '70s Pattern Language, through to Concord Pacific glass-tower mania, to Olympic Village, and consider how False Creek points to the development future, for Sen̓áḵw and the for the Region as a whole. Michael von Hausen is CEO of the Great Communities Institute, which he founded in 2021 to focus on integrating urban design with real estate development and to share progressive ideas. He is Adjunct Professor at Simon Fraser University in the Graduate Urban Studies Program, and Adjunct Professor at Vancouver Island University. ****************************************The Viewpoint Podcast is a production of Viewpoint Vancouver.Visit viewpointvancouver.ca for more Urbanism, Insight, and Evolution.  Please subscribe to the Viewpoint newsletter, or subscribe to the Podcast in all the usual paces.If you like this podcast and want to help shape our region,  please support our labour of love. Cool perks and prizes are at: patreon.com/viewpointvancouverMusic for the VWPT Podcast is by Romina Jones, from her lp Elevation. Hear more from Romina at:  soundcloud.com/andabeatCatch up on Viewpoint Podcasts you might have missed, HERE.    

There are an increasing number of urban jurisdictions that are allowing egg-laying chickens/hens. Arguable, the reasons are clear - chickens provide protein, great fertilizer, pest control and are easy to maintain. But the bigger reason for keeping chickens may be for people to get more control of their food supply, just like growing vegetables etc. Following the past few years of the Covid pandemic, we all know food security should not be taken for granted and urban planning to allow for small scale food production can help many people meet their basic needs. The speakers will argue that urban food production is sustainable and helpful for us to live in this world without depleting its resources. Speakers:                    Gilles Leclair and Kelti Baird Gilles is a founding member and past-president of the Lethbridge Sustainable Living Association. He created the Applefest (an event to promote local food sustainability) and was a long-time executive member of the Unitarian Universalist Fellowship of Lethbridge. Gilles has participated in Toastmasters and is a student of the books Small Is Beautiful: Economics as If People Really Mattered, Nonviolent Communication and A Pattern Language (urban design). He is a self-described Social Entrepreneur with a passion for re-creating urban spaces within a sustainable context. Kelti is a 2012 graduate of the University of Lethbridge with a Bachelor's Degree in History. Her particular focus was architectural history specializing in settlement architecture in Western Canada. She is the founding co-owner of Theoretically Brewing Company, here in the city, as well as an environmental enthusiast. Kelti's short time working for Environment Lethbridge, along with interactions with the Lethbridge Sustainable Living Association and Homestead Show & Market in Fort MacLeod, sprouted an interest in urban agriculture and environmentalism. In September 2018, Kelti introduced a request to City Council for an Urban Hen Pilot project, and is pursuing a change to Bylaw 3383 to allow for the same.

Welcome to Dev Game Club, where this week we complete our series on SimCity 2000. We talk disasters and scenarios and of course, our takeaways. Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary. Sections played: A new beginning and a scenario Issues covered: looking at the scenarios, recovering from disasters, plane crash disaster, choosing what disasters you would use, flooding in particular, kicking down the sandcastle, what it models and what it doesn't, wanting to have a conversation about it with your child if they played it, street-level view of community, a fun-house mirror on urban development, various areas of study referenced in the simulation, the books referenced for further study, sicknesses in the modern sim, needing an influx of cash to keep your villages going, looking at the scenarios, reflecting on Flint Michigan, choosing to reflect a real place, eminent domain, being curious about why that was included, finding compromise, focusing on progress, expose/explore/explain your passions, inherent statements in how you win, the huge scope of this game and the wish fulfillment of that, a simulation can't be everything and as a game you have to be careful, urban renewal and SimCity, the Launch arcologies. Games, people, and influences mentioned or discussed: mysterydip, Doug Bowser, Nintendo of America, Cities: Skylines, The Boys, Roger Ebert, Christopher Alexander, A Pattern Language, David Macauley, Dungeons & Dragons, Wizards of the Coast, Gary Gygax, Dave Arneson, Disney, Five Nights at Freddy's, Call of Duty, American Factory, Roger & Me, SimTown, Will Wright, Raid on Bungeling Bay, Doom, Civilization, Maxis, Midknight22, Shadow of the Colossus, ICO, Chris, Cyberpunk, High Rise, J. G. Ballard, Crash, Dredd, Megaman, Dark Souls, Kirk Hamilton, Aaron Evers, Mark Garcia. Notes: The 5e book list in the DMG is very different from the 1e list. Next time: ...?! Twitch: brettdouville or timlongojr, instagram:timlongojr, Twitter: @timlongojr and @devgameclub DevGameClub@gmail.com

Welcome to Dev Game Club, where this week we begin a new series on that classic sim, SimCity. We very briefly situate it in time and talk a little bit about Will Wright before talking over some of the strangeness that is this game (or toy). Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary. Sections played: Tutorials or A Few Cities Issues covered: which version and why, establishing the SimUniverse, Wright and describing his design process, a good representative for our art form, a simulated ant farm toy, setting it in its time, licensed titles, the origins of the game in practice and in theory, a wide variety of influences, industrial design, where other designers get their influences, working in a space with other designers, picking your battles and choosing conflict, different sims being developed at the same time, legacies, a recognizable space, playing with it like a toy, setting your own goals, differences in the motivation for play, a very Western lens, making assumptions and scope, a Christian church as a statement, designing to constraints, what you're building and what you're not, meeting the citizens' concerns, zoning and pipes and infrastructure, how cities grow in reality and the intersection with history, the newspaper as a conduit for information and setting and feel, the weird content in the newspaper, advisors and the pulse of the people, being grounded, the things that are your concern, budgets and taxes and deficits, audio associated with taxes, "Read my lips: no new taxes," being careful with incentives, replaying MegaMan levels, audio budgets, the names and lore of MegaMan, listening to music when you code, generated art, humans as creators and consumers of art, art as conversation and exploration, enjoying procedurally created levels and worlds, AI assistant tools, kudos to the hosts, being humbled by how our games touch people. Games, people, and influences mentioned or discussed: Will Wright, The Sims (series), MAXIS, Spore, SimAnt, SimCopter, SimTower, SimEarth, MegaMan 2/X, Prince of Persia, Populous, Tetris, GameBoy, Castlevania (series), Star Trek: The Next Generation, Batman (1989), MYST, DOOM, Day of the Tentacle, Star Fox, Secret of Mana, The 7th Guest, Bill Gates, Link's Awakening, Raid on Bungeling Bay, John Romero, Christopher Alexander, A Pattern Language, Urban Dynamics, Star Wars, Alien, June Longo, Shigeru Miyamoto, Pikmin, Legend of Zelda (series), Civilization, Populous, Sid Meier, Black & White, Dungeon Keeper, Cities: Skylines, X-COM, Dark Souls, Mrs Reckis, mysterydip, The2ndQuest, NES, Albert Einstein, Thomas Edison, OCRemix, Metal Gear Solid, Valheim, Minecraft, Parham, Republic Commando, Skyrim, Kirk Hamilton, Aaron Evers, Mark Garcia. Next time: More hours? Hard to know how to schedule this one :) Links: -Mega Man 2 (Original Version) by The Minibosses (metal medley of MM2 tracks) -Mega Man 2: Tickle My Wily by Star Salzman (kind of an epic orchestral/electronica OCRemix piece) -Cataclysmic Clash by Game Over (MM3-inspired, but quotes recurring music from MM2- also has lyrics!) -Mega Man X Guitar Medley by FamilyJules Twitch: brettdouville or timlongojr, instagram:timlongojr, Twitter: @timlongojr and @devgameclub DevGameClub@gmail.com

Sarah Susanka is an architect, prolific author, and visionary thinker credited with starting the tiny house movement. She's changed the way huge amounts of people see the world, but she insists the way to create change is by thinking small and attending to the everyday challenges you see in front of you. I talked to Sarah with a co-host, returning podcast guest Ross Chaplin—creator of “pocket neighborhoods.” This was an incredible opportunity to speak with two highly influential figures in architecture and design who both see their work as being in service to humanity and wellbeing. We spoke about how they were both deeply influenced by the work of Christopher Alexander and his book A Pattern Language, the importance of building with love, the authenticity of designing for human well-being, and how to create change that truly shifts culture. To learn more about Sarah's ideas and work, visit susanka.com and watch her TEDx talk. 

Welcome to the Omni-Win Project Podcast.It's time to upgrade our democracy. If you're fed up with the status quo and want to catalyze political and societal change, you're in the right place. The Omni-Win Project Podcast is ready to shed light on the many opportunities we have to revolutionize our political culture. We're all in this together, so join us in co-creating the future of democracy. "We need to be able to use differences and disturbances creatively."Did you know that activism can't really contend with our current system? While we're slowly improving our democracy with awesome technology and tools, they aren't widely used. But when we use them, we see incredible results: Tom Atlee recounts a ground-breaking story about the power of dialogue. It's time to improve our democracy and how we relate to each other.You'll also learn about pattern language and how it can lead to a wiser democracy. Duncan and Tom talk about the importance of everyone being included in a conversation. Are you ready to discover why climate deniers need to be included in the environment discussion?Highlights in this episode:Tom talks about how we need to out-Gandhi Gandhi.Discover the world of Wise Democracy's pattern languages.Learn how technology is revolutionizing democracy.Uncover why activism isn't working.Learn why we need to include climate deniers in the discussion.Tom recounts an incredible story about dialogue bringing people in conflict together.Understand why we need to focus on the whole.About this episode's guest:Tom Atlee is the creator of the Wise Democracy Project and a lifelong advocate for co-intelligence. Tom researches and promotes ideas and approaches for generating collective wisdom about public affairs, which he presents in an encyclopedic vision called "Wise Democracy".More from Tom Atlee:https://www.youtube.com/channel/UCeOMzv3eQZqdkUs671eDbZgContact Tom Here: https://www.co-intelligence.institute/contact-ushttps://co-intelligence.institutehttp://tomatleeblog.comhttps://co-intelligence.orghttps://wd-pl.comhttps://www.wd-pl.com/prime-directive/Where Else can you find this episode? Watch on YouTube: https://youtu.be/0orktmeC-w4On Substack: https://omniwin.substack.com/p/tom-atleeEpisode Page: https://omniwinproject.com/tom-atlee

Vance sits down for an As the Crowe flies episode to request 2 things from our listeners:1) Ideas for a mural he hopes to have commissioned for his second daughter, Autumn2) A new pattern language that better captures ideas surrounding long term thinking. To view Vance's first mural for Violet: https://www.vancecrowe.com/violets-muralJoin the Articulate Ventures Network | https://network.articulate.ventures/ —We are a patchwork of thinkers that want to articulate ideas in a forum where they can be respectfully challenged, improved and celebrated so that we can explore complex subjects, learn from those we disagree with and achieve our personal & professional goals.Book a Legacy Interview | https://legacyinterviews.com/ —A Legacy Interview is a two-hour recorded interview with you and a host that can be watched now and viewed in the future. It is a recording of what you experienced, the lessons you learned and the family values you want passed down. We will interview you or a loved one, capturing the sound of their voice, wisdom and a sense of who they are. These recorded conversations will be private, reserved only for the people that you want to share it with.Contact Vance for a Talk | https://www.vancecrowe.com/ —Vance delivers speeches that reveal important aspects of human communication.  Audiences are entertained, engaged, and leave feeling empowered to change something about the way they are communicating.  Vance tells stories about his own experiences, discusses theories in ways that make them relatable and highlights interesting people, books, and media that the audience can learn even more from. Join the #ATCF Book Club | https://www.vancecrowe.com/book-club

Jeff Atwood, writer of the computer science classic "A Pattern Language", joins Lexman to talk about the intricacies of football strategy, specifically with regards to René Cruyff's famous "Duralumin" game plan. They also discuss the applicability of computer science concepts to real-world situations, and compare and contrast the mythology and functionality of the Norse gods Jotuns and Hydrons.

The architect Christopher Alexander died recently. As the (surprisingly good) New York Times obituary described him: [Alexander] believed that ordinary people, not just trained architects, should have a hand in designing their houses, neighborhoods and cities, and proposed a method for doing so in writing that could be poetically erudite, frustratingly abstract and breathtakingly simple... Mr. Alexander was a fierce anti-modernist who found traditional and indigenous structures — the beehive-shaped huts of North Africa, for example, or medieval Italian villages — more aesthetically pleasing than highly designed contemporary ones, which he saw as ugly and soulless.Alexander has long been an inspiration here at Current Affairs and his work has been mentioned in a number of articles. (1) (2) (3) (4)In this interview, Nathan talks to his old friend, city engineer and planner Daniel Ohrenstein, about why they both love Alexander's writing and how Alexander can help us think more clearly about what's wrong with contemporary architecture and how to build beautiful places. A transcript of this interview, with lots of photos including some of Alexander's own built work, appears here."What emerges from A Pattern Language is a vision of life and how it should be. A society where people are mixing and aren't isolated. There's a good saying: when the revolution starts, everyone should know where to go. And if you think about your town, what is the public square? Having a center or public square where people gather is part of being in a real city. Having civic life means having these public spaces. And in these spaces, you can have carnivals, you can have old people and young people playing chess outside. What makes an idyllic city? It's certainly one that has social engagement. Another suggestion in A Pattern Language is animals everywhere. I was at Whole Foods the other day and I got startled by a sandhill crane. It came up to me and squawked. That kind of interaction is important. Like: Don't forget there are other beings that inhabit the planet." — Daniel Ohrenstein

Welcome to The Nonlinear Library, where we use Text-to-Speech software to convert the best writing from the Rationalist and EA communities into audio. This is: A Pattern Language For Rationality, published by Vaniver on July 5, 2022 on LessWrong. There's a lens to looking at the rationality project that I've been finding enlivening recently, and I think it's reached the point where more eyes and hands might be useful, while not being anywhere near complete yet. First, some background. Christopher Alexander was a designer and architect; his thinking, and focus on patterns in particular, were influential in programming; wikis were first invented to facilitate the collaborative creation and modification of 'patterns' in the style he described. He wrote lots of books, but I'll focus on this trio: The Timeless Way of Building (about the ‘quality without a name', and good vs. bad buildings) A Pattern Language: Towns, Buildings, Construction (about the 'patterns' they've identified for physical buildings and towns) The Oregon Experiment (about the University of Oregon, and how it could replace a ‘master plan' with principles) The three books, while each on a different subject or layer of 'design', all work together and depend on each other. The first identifies the target, why it would even be good to pursue, and how you know whether or not you've found it. The second is a detailed description of the patterns they've found useful in approaching the target. The third is what it looks like to organize systems to deliberately and durably organize themselves according to this design. Just like this approach was profitably translated to programming (and other areas of design), I think it's worth looking at the 'rationality' project as a way to design decisions, habits, and thinking, and attempting to deliberately incorporate Alexander's approach and strategy. This post is an attempt to get started in each of the three directions, rather than fully lay them out; depending on how things go, I might turn this post into a sequence / flesh out individual sections. The Timeless Way of Living The Tao that can be told is not the eternal Tao; The name that can be named is not the eternal name. [Consider also 'thinking', 'deciding', 'doing', and 'being' in place of 'living', for both this section and the next.] Alexander talks about the “Quality Without A Name”, so-called because no existing English word was a good fit, altho he could point towards it pretty effectively in a few pages; you should read the start of The Timeless Way of Building (Amazon, pdf) to get his sense of it. I think “equilibrium” comes somewhat close–a design has the Quality Without A Name if all of the forces present, both internal and external, are balanced. This isn't the true name because many equilibria we see don't have the Quality Without A Name, because for them only some of the forces are active in determining the level. A house might be at ‘equilibrium' according to the windows and the thermostat, but not according to the human inside who's not happy with the situation and wants to do something about it. When talking about buildings, he talks about whether they're 'alive' or 'dead'. His overall sense is that many design features are 'obvious' or 'natural'; while there might be lots of detail to the model of how to make things that are alive, most of the ability to detect whether or not a building is alive or dead is already 'baked in' to being a human. I think it's relatively easy to point to good buildings and bad buildings, and somewhat harder to point to good lives and bad lives, mostly because we can walk around the inside of building made by others but not their minds. Nevertheless, it seems possible to collect pictures of what it is that makes life worth living, what properties good decisions have, what virtues we might like to embody. This is, historically, a place I think the rationality project has done pretty well. You may try to name the highest princip...

Link to original articleWelcome to The Nonlinear Library, where we use Text-to-Speech software to convert the best writing from the Rationalist and EA communities into audio. This is: A Pattern Language For Rationality, published by Vaniver on July 5, 2022 on LessWrong. There's a lens to looking at the rationality project that I've been finding enlivening recently, and I think it's reached the point where more eyes and hands might be useful, while not being anywhere near complete yet. First, some background. Christopher Alexander was a designer and architect; his thinking, and focus on patterns in particular, were influential in programming; wikis were first invented to facilitate the collaborative creation and modification of 'patterns' in the style he described. He wrote lots of books, but I'll focus on this trio: The Timeless Way of Building (about the ‘quality without a name', and good vs. bad buildings) A Pattern Language: Towns, Buildings, Construction (about the 'patterns' they've identified for physical buildings and towns) The Oregon Experiment (about the University of Oregon, and how it could replace a ‘master plan' with principles) The three books, while each on a different subject or layer of 'design', all work together and depend on each other. The first identifies the target, why it would even be good to pursue, and how you know whether or not you've found it. The second is a detailed description of the patterns they've found useful in approaching the target. The third is what it looks like to organize systems to deliberately and durably organize themselves according to this design. Just like this approach was profitably translated to programming (and other areas of design), I think it's worth looking at the 'rationality' project as a way to design decisions, habits, and thinking, and attempting to deliberately incorporate Alexander's approach and strategy. This post is an attempt to get started in each of the three directions, rather than fully lay them out; depending on how things go, I might turn this post into a sequence / flesh out individual sections. The Timeless Way of Living The Tao that can be told is not the eternal Tao; The name that can be named is not the eternal name. [Consider also 'thinking', 'deciding', 'doing', and 'being' in place of 'living', for both this section and the next.] Alexander talks about the “Quality Without A Name”, so-called because no existing English word was a good fit, altho he could point towards it pretty effectively in a few pages; you should read the start of The Timeless Way of Building (Amazon, pdf) to get his sense of it. I think “equilibrium” comes somewhat close–a design has the Quality Without A Name if all of the forces present, both internal and external, are balanced. This isn't the true name because many equilibria we see don't have the Quality Without A Name, because for them only some of the forces are active in determining the level. A house might be at ‘equilibrium' according to the windows and the thermostat, but not according to the human inside who's not happy with the situation and wants to do something about it. When talking about buildings, he talks about whether they're 'alive' or 'dead'. His overall sense is that many design features are 'obvious' or 'natural'; while there might be lots of detail to the model of how to make things that are alive, most of the ability to detect whether or not a building is alive or dead is already 'baked in' to being a human. I think it's relatively easy to point to good buildings and bad buildings, and somewhat harder to point to good lives and bad lives, mostly because we can walk around the inside of building made by others but not their minds. Nevertheless, it seems possible to collect pictures of what it is that makes life worth living, what properties good decisions have, what virtues we might like to embody. This is, historically, a place I think the rationality project has done pretty well. You may try to name the highest princip...

this sunday read-aloud is a child of the second episode of the journal of small work*, pattern language + permeability. it is concerned particularly with our permeable selves, and our bigger selves, the one that encompasses a whole earth system in perpetual exchange. this tiny piece touches on the exchanging of the possibly toxic for the definitely edible, accepting our microbial-ness, looking to the cycling of this living being we are living within for patterns that lead us to better decisions. all of that. it would be lovely to hear what you think of it. and if you missed a link i posted yesterday to a new interview with sophie from big things little things, you might like to listen in about just these sorts of concerns and approaches.with thanks to the appleturnover radio and film patrons. you make this possible. i like to think of it as a csa, like my regenerative-agrarian friends cultivate; community supported activism. thank you. follow appleturnover on patreon for more. Hosted on Acast. See acast.com/privacy for more information.

On this edition of the Momentom Podcast, join Momentom cofounder John Early (@johntearly) and Sycamore (@ceremonial_chef) on the beach of Nosara, Costa Rica as they dive into the concept of healing inner and outer ecology. Sycamore is a renowned land steward, chef and farm manager – live from the beach of Nosara (so don't mind the ocean sounds in the background). Join the conversation into comprehending structured water, stewardship vs ownership and going beyond the dogma of diets and fasting. For more info on Sycamore visit www.ceremonialchef.com and follow his journey at https://www.instagram.com/ceremonial_chef~Topic Timestamps:1:18 - What is a land steward3:30 - Stewardship VS Ownership6:40 - What is water?9:44 - Carbon cycle VS Water cycle12:15 - What is structured water?15:30 - All illness is dehydration17:00 - Fall back in love, find our source20:05 - Water filtration24:30 – The Truth of Almond milk VS Dairy milk28:35 - Beyond diet and dogma32:30 - Soak and sprout your plant foods39:20 - Gut health & roundup47:25 - The ancient art of fasting55:25 - What is permaculture(Recorded live at Playa Nosara, Costa Rica – March 2022) ~ For more info on our International Artist Residencies visit https://www.momentomcollective.com For more on our Podcast host, John Early visit https://www.johnearly.ca or on Instagram @johntearly Sycamore roots himself at the intersection of ecological and social permaculture, weaving the relationships between gardens and group process, water stewardship and conflict transformation, ceremonial nutrition and body temple restoration. From community song leader to large event chef, from garden whisperer to council circle facilitator, he lives the solutions to our societal crisis, inviting this opportunity for land-based, heart-based creativity amidst the cultural revival. With a decade of experience managing farms, leading kitchens and living in eco-villages throughout Turtle Island, Sycamore brings an embodied awe for agroforestry & chef alchemy as his Pattern Language for The Great Turning.~ For the full playlist of our Video Podcasts on Youtube visit: https://www.youtube.com/playlist?list=PLDfv9P0yDraLxTtiJx6-vo_2hohOE1uu_For the Momentom Collective Podcast on Spotify visit: https://open.spotify.com/show/6Q9g39tyehzZWT75DZHo29?si=72YlmJNxSKuCO59yuX2S6g&nd=1Past episodes include: *Poranguí - The Medicine of Now & The Role Humanity Plays *Amelia Broughton – Creating Connection with Authentic Relating & Human Design* Bodhi Samuel - Understanding Sexual Alchemy

This week on Mondays we talk a lot of different subjects including Christopher Alexander's A Pattern Language and how where you grow up impacts how good you are at directions. Join us for an Idaho Stop won't you? Where you grow up determines your directions - NYT Omaha Plans for the future of Downtown - Omaha World Herald Colorado Could Soon Allow Idaho Stops - Colorado Politics Boomers Tell Millennials there's No Crisis - New Statesman Tire Chemicals are killing fish - Toronto Star Why Christopher Alexander Still Matters - Planetizen     Follow us on twitter @theoverheadwire Support the show on Patreon http://patreon.com/theoverheadwire Buy books on our Bookshop.org Affiliate site! 

TopicWe discuss the recent death of Christopher Alexander, his infamous book A Pattern Language, the newly released The Adam Project movie and architecture as a character, Cormac's big news, and more.LinksThe Adam Project (Netflix)Gimme: The House from ‘The Adam Project'Christopher Alexander (Wikipedia)Pattern Language websiteThe book: A Pattern Language: Towns, Buildings, Construction by Christopher Alexander (Amazon)Fallingwater weekly livestream: A Closer LookEames lounge chair (Wikipedia)SponsorStart implementing powerful systems for the profitability you need and the freedom you want. Join Douglas Tieger, FAIA for the next Designing Your Business Masterclass, brought to you by BQE CORE. Every live masterclass session is free and includes AIA continuing education credit. Register now at bqe.com/masterclass.Listen and Subscribe to Archispeak

Dove mettere la nostra pianta preferita?Come progettare lo spazio del nostro giardino quando c'è un profumo che ci piace particolarmente?Come gestire le piante in spazi piccoli per creare giardini interessanti?Parliamo insieme di viste zen e di "A pattern language" (https://www.patternlanguage.com/bookstore/pattern-language.html), bestseller dell'architettura uscito nel 1977, di profumi e piante amate!__________________________________________Io credo che abbiamo tutti bisogno di un giardino

Amity and Dianne share their personal “three favorite patterns” from Pattern Language.

Our intrepid heroes visit the New York Public Library to meet up with visiting literary scholar Merrill Malone, an eccentric and the foremost expert on Virginia Gaskell's life and work, to get, once and for all, all the answers about the portals. What they don't realize is that shocking personal revelations and the very ground beneath their feet will alter forever within the library's seemingly pristine walls. (Running time: 55 minutes, 43 seconds.) Written, produced, and directed by Edward Champion. CAST: Chelsea: Katrina Clairvoyant Emily McCorkle: Belgys Felix Professor Malone: Robert Garson Jenna: Devony DiMattia Miss Gaskell: Chris Smith Maya: Tanja Milojevic Ed Champion: Edward Champion The Executive: Rachel Matusewicz Audrey: Amanda Rios Romero: David Ault Joe: David Sinkus The Guard: Graham Rowat and Zack Glassman as The Receptionist   Incidental music licensed through Neosounds and MusicFox. Additional music composed by Edward Champion   Sound design, editing, engineering, and mastering by a bald man in Brooklyn who clearly has some corporate identity issues to work out.   Thank you for listening!

Our showrunner Edward Champion discusses Part 3 of "Pattern Language." Subjects discussed include WandaVision, the careful balance between realism and pastiche, the Faulkner short story as a starting point, Love and Rockets, why the memory of an inspiration is often better than closely examining the source text, designing the 1970s announcer voice, using 1970s television effects to create a sound design, being careful with laugh tracks, why Carol Jacobanis is an extraordinary actor, the advantages of recording with Belgys and Carol together in the same room, an abandoned first season script set within a talk show, Eric Bogosian's Talk Radio, avoiding rehashes while writing, inverting the Neil LaBute/David Mamet formula for women, the strange Italian references throughout The Gray Area, Heath Martin, Louis CK's apology, creating walla sounds for the journalists, how Carol struck the perfect balance between realism and stylized voices, the need to know where a story is heading within five minutes, story beats, the candid dialogue, growing up in a prudish household, both-siderism vs. all sides in journalism, statements on the public record, bullies and therapy, young people who talk down at older people, the impossible behavioral ideal in the digital age, Dostoevsky's Crime and Punishment, the fajita demon origin story, why Pompano made an appearance here is an NYC restaurant, fish metaphors, The Shawshank Redemption, meeting Frank Darabont as a young man, behavioral patterns and therapy, paying respectful homage to Richard Russo, the great versatility of Monica Ammerman, how a recording accident created an opportunity for greater authenticity, the Chico State backstory, how his California origins influenced the script, fluid sexuality, ghost writing, why alcoholics keep cropping up in The Gray Area, annoying the audience, animal sounds, Catholicism, why the ukulele was used in a music cue, Jeff Russo's Fargo cue, Tarantino and surf music, balancing demons and humans, Evita and fascism, Argentine history, the disadvantages of being a horror movie fan while doing sound design, beta listener feedback, arriving at natural storytelling beats, the importance of the cart sound effect, electromatter sound design, learning the keyboard and composing primitive music, the high price of music clearance, barking dogs and the "black dog" of depression, being careful with storytelling explanations, wordplay as a source of creative inspiration, double-tracking to get vocal effects, creating ethereal sounds from homegrown recording, how using a keyboard altered the sound design, the responsibility of following up on storytelling points, a minor story problem in "An Iris for Emily," Johnny as Ed's dark half, and overly dramatic performance vs. melodrama. (Running time: 30 minutes, 27 seconds.)

Emily McCorkle has landed the media appearance of a lifetime: a guest spot on the most respected talk show in America. But why is the host so concerned with her private details? And why are so many skeletons from her past making guest appearances? And who is the strange man with the hot dogs? (Running time: 38 minutes, 1 second.) Written, produced, and directed by Edward Champion. CAST: Emily McCorkle: Belgys Felix Ophelia Kakanakis: Carol Jacobanis June: Monica Ammerman The Fajita Demon: Pete Lutz The Cunning Demon: Leanne Troutman Morris Pressman: David Tao Jimmy Markson: Heath Martin Johnson: Hilah Hallaway Emily's Mom: Melissa Medina Emily's Dad: David Sirkus Chelsea: Katrina Clairvoyant Maya: Tanja Milojevic Ed Champion: Edward Champion Reporter #1: Glenn Bulthius Reporter #2: Alice Fox and Zack Glassman as The Receptionist Creature Voices by Samantha Cooper and Rachel Baird Incidental music licensed through Neosounds and MusicFox. Additional music composed by Edward Champion. Sound design, editing, engineering, and mastering by a bald man in Brooklyn who has become a TikTok junkie seemingly against his will. Thank you for listening

We discuss working in a start-up environment, making hard decisions when prioritizing, and the parallels between architecture and software development. Hyper growth (https://www.drift.com/blog/what-is-hypergrowth/) VCR (https://github.com/vcr/vcr) Tweet about architecture (https://twitter.com/KFMolli/status/1419555663982866435) How Buildings Learn (https://www.goodreads.com/book/show/38310.How_Buildings_Learn) by Steward Brand A Pattern Language (https://www.goodreads.com/book/show/79766.A_Pattern_Language) by Christopher Alexander You can reach us via email at hosts@expandingbeyond.it (mailto:hosts@expandingbeyond.it). You can follow us on Twitter at @podcast_eb (https://twitter.com/podcast_eb). Where to find Monica on the internet: Website: monicag.me (https://monicag.me/) Twitter: @KFMolli (https://twitter.com/KFMolli) Github: @nirnaeth (https://github.com/nirnaeth) Blog: dev.to/nirnaeth (https://dev.to/nirnaeth) Where to find Urban on the internet: Twitter: @ujh (https://twitter.com/ujh) Github: @ujh (https://github.com/ujh/) Blog: urbanhafner.com (https://urbanhafner.com/) The intro and outro music is Our Big Adventure (https://freemusicarchive.org/music/Scott_Holmes/Happy_Music/Our_Big_Adventure) by Scott Holmes (https://freemusicarchive.org/music/Scott_Holmes). It's licensed under Attribution-NonCommercial 4.0 International (CC BY-NC 4.0) (https://creativecommons.org/licenses/by-nc/4.0/).

Our showrunner Edward Champions dives into the second chapter of "Pattern Language."  Subjects discussed include creative dissatisfaction, basing the story arc on being personally libeled by a journalist, writing as an act of being peace, resisting the temptation to write from revenge, fantasy as a genre where real-life people incapable of empathy express it as new characters, designing the telephone muttering, invasion of privacy, when culture doesn't allow people to change, how Belgyis Felix landed the role by staying in character as a demon during a play, the Adelphi school of acting, the remarkable acting range of Belgys Felix, how McCorkle's recalcitrance reflected his own arrogant past, the immaturity and narcissism of star journalists, the public profile vs. the private character of a person, the "worst X" as a headline, wishful thinking about editorial standards, Kevin Fogelberg and Dan Fogelberg, allusions to the Hulk Hogan Gawker suit, the New York Times vs. Sullivan standard and libel, advertorial articles and puff pieces in the magazine industry, ideologues who claim to be journalists, basing Morris Pressman on Ben Hecht plays, larger-than-life characters, Slate reporters who manipulate content for white-collar workers, floral allegories, the influence of Twin Peaks: Fire Walk with Me, his tendency to write stylized men, recording subway and New York sounds, tying the many loose strands together, the Ed and Maya conversation as a callback to "Dearer than Earsight," why it's important to cast someone better than you if you appear in your own audio drama, addressing the events of "Fuel to the Fire," why he had to hire a German translator, why Tanja Milojevic is brilliant, scouring for German idioms, why there are so many Receptionists in the main universe, the influence of Stranger than Paradise on music licensing, casting a real estate broker as a corporate tycoon, the parallels between Chelsea and The Wizard of Oz's Dorothy, location audio in Midtown, the tendency to run into random people quite frequently in New York City, coincidental run-ins in stories, clarifying previous story details, chase scenes, the crazed amount of Tony Danza research done for The Gray Area, Christopher Alexander and "pattern language," and demon transformation.  (Running time: 26 minutes, 8 seconds)

Months after the events of “Paths Not Taken,” Chelsea is working hard to turn a corner and improve her life. But when Emily McCorkle, the smear merchant journalist who severely damaged her reputation, returns to write a followup piece, Chelsea is thrown into a jarring maelstrom that involves demons, people from her past, and the possibility of redemption. (Running time: 32 minutes, 22 seconds.) Written, produced, and directed by Edward Champion. CAST: Chelsea: Katrina Clairvoyant Emily McCorkle: Belgys Felix Maya: Tanja Milojevic Morris Pressman: David Tao Ed Champion: Edward Champion Alicia: Elizabeth Rimar Johnson: Hilah Hillaway The Fajita Demon: Pete Lutz The Cunning Demon: Leanne Troutman Lucinda: Emily Carding Mrs. Gelding: Westlake Stark and Zack Glassman as The Receptionist   Creature Voices by Samantha Cooper and Rachel Baird   Incidental music licensed through Neosounds and MusicFox. Additional music composed by Edward Champion.   Sound design, editing, engineering, and mastering by a bald man in Brooklyn who does his best to resist mayonnaise but can't entirely fight the allure for a good tuna sandwich.   Thank you for listening!

Our showrunner Edward Champion discusses the first chapter of "Pattern Language." Subjects discussed include his hesitations about creating, the dangers of revealing too much, Chris Ware, being dubious about your own work, why the first part of "Pattern Language" was split into two parts, why Pete Lutz is a marvelous man, how an old UCB trick resulted in the strange mix of Shakespeare and I Love Lucy, designing custom vernacular, the absence of slang in fantasy stories, Total Meats as a metaphor for Whole Foods, scouring through mythology to come up with obscure beast and creature names, the influence of Hitchhiker's, Douglas Adams, the number of alternative Eds buried within The Gray Area, why Leanne Troutman is a magnificent actor, Peter Falk impressions, the importance of being present as a director, the number of takes you should do with an actor, using every spatula in the house for the BBQ sound design, how being a prolific cook inspires fictitious food dishes, convincing eating moments on film, Moonstruck, how his opposition to self-checkout in stores inspired worldbuilding, London store technology, people and robots, creating fictitious geography, why the Johnsons matter in The Gray Area, the fajita demon origin story, the influence of Fritz Leiber, Terry Pratchett and the Rincewind novels, recording electrical sounds for the Gray Area, having doubts as an artist, stylizing the demons as wiseacres, showing the humanity of outliers, why the demons are obsessed with exercise, using music to cloak deficiencies, Terminator 2, and telling a story from the demon's perspective.  (Running time: 19 minutes, 8 seconds.)

Pat Goras and Lucy Didas are a happy couple living in a fantastical suburban realm preparing for a delightful dragon brisket barbeque with their neighbors. But when a strange portal opens in their backyard, their lives and roles become permanently altered within the very Gray Area itself! (Running time: 20 minutes, 54 seconds) Written, produced, and directed by Edward Champion. CAST: Pat Goras/The Fajita Demon: Pete Lutz Lucy Didas/The Cunning Demon: Leanne Troutman The Neurotic Demon: Melissa Medina The Counting Demon: Vlasto Pejic The Angsty Demon: Nick Boesel Miss Gaskell: Chris Smith and Zack Glassman as The Receptionist   Creature Voices by Samantha Cooper and Rachel Baird   Incidental music licensed through Neosounds and MusicFox. Additional music composed by Edward Champion   Sound design, editing, engineering, and mastering by a bald man in Brooklyn who once considered reciting Dr. Seuss's Green Eggs and Ham in Latin.   Thank you for listening!

There's an old and magical book called “A Pattern Language” that describes many surprising ways humans actually behave in certain spaces like towns, streets, buildings, balconies, and bedrooms. And one section related to sleep says, “Bedrooms don't make any sense.”

We talk with Will Krzymowski, intern architect and all around great guy, about how thinking about our spaces can help us make more connections with others.Will's Bus Conversion Project - Pic 1, Pic 2, Pic 3Our friend Hannah's Instagram about how to use the unremarkable moments to make neighbourhoods into places where people are known and belong. Right where you are.Pattern Language - by Christopher Alexander - Summary. You can use this book to design a house for yourself with your family; you can use it to work with your neighbours to improve your town and neighbourhood; you can use it to design an office, or a workshop, or a public building. And you can use it to guide you in the actual process of construction.You Are What You Love by James K.A. Smith -- On the Spiritual Power of HabitSupport the show

Andrea is an architect, college professor and founder of AKA Architecture + Design, an all-female architecture firm in Los Angeles. She specializes in Sacred Geometry, Pattern Language and the meaning of Symbols. She has worked on four continents and speaks six languages.  Four D Design is a holistic system of Conscious Design practices for advanced sustainability. Learn more at fourddesign.com The behind the scenes of reality TV. “Authenticity matters.” The misconceptions that we've been told about style. “Style is just a narrative— just a story.” “We really should see why we're attracted to things and see it for what it is, so we're not throwing money at things that aren't truly aligned.” We've been programmed to like certain things.  Where to start with optimizing your home for it to embody your beliefs and feel aligned. The importance of clearing your space. Why it's good to move objects around in your home. How to modify the pieces in your home so they feel more aligned. “As soon as you start to establish geometry, then you're showing your intention.” How to translate what you like into your space. Having a conversation with the pieces in your home and how to listen to your furniture.  Why Andrea's whole business changed when she arranged her living room.  “Let your home take care of you.” How to live off the grid and the influence of sacred geometry.  What does 4D Design mean? Why home improvement reality shows want you to feel bad about your home.  “We fix things with our dollars.” (which is what reality TV wants you to do) Learn more at fourddesign.com

Andrea is an architect, college professor and founder of AKA Architecture + Design, an all-female architecture firm in Los Angeles. She specializes in Sacred Geometry, Pattern Language and the meaning of Symbols. She has worked on four continents and speaks six languages.  Four D Design is a holistic system of Conscious Design practices for advanced sustainability. Learn more at fourddesign.com The behind the scenes of reality TV. “Authenticity matters.” The misconceptions that we've been told about style. “Style is just a narrative— just a story.” “We really should see why we're attracted to things and see it for what it is, so we're not throwing money at things that aren't truly aligned.” We've been programmed to like certain things.  Where to start with optimizing your home for it to embody your beliefs and feel aligned. The importance of clearing your space. Why it's good to move objects around in your home. How to modify the pieces in your home so they feel more aligned. “As soon as you start to establish geometry, then you're showing your intention.” How to translate what you like into your space. Having a conversation with the pieces in your home and how to listen to your furniture.  Why Andrea's whole business changed when she arranged her living room.  “Let your home take care of you.” How to live off the grid and the influence of sacred geometry.  What does 4D Design mean? Why home improvement reality shows want you to feel bad about your home.  “We fix things with our dollars.” (which is what reality TV wants you to do) Learn more at fourddesign.com

Listen in to this dialogue with Mike Ninomiya vice grandmaster of Enshin Karate on Pattern Language and preparing for 2021 with awareness and discovery of your energy blueprint.  Check out and subscribe to the new Reasons Mag and podcast for Water element health at www.reasonsmag.com Tap into all the FREE creative food as medicine, embodiment processes, podcast learning and kitchen pharmacy practice for seasonal living.  Host Elzabieta  Guest Mike Ninomiya  Music by Stay Tuned  Intro Outro Ichiban  

RotoWire's Chris Liss and Yahoo Sports' Dalton Del Don talk learning, not teaching, Pattern Language, vacation, outsourcing attention, politics of school, making beef jerky, The Courage To Be Disliked, Raheem Mostert, Beat Chris Liss MLB, Jacob deGrom, Gerrit Cole, political fallout for sports, Ghislane Maxwell, Satoshi, BTC, markets, Liss' epic SQ stock fail, Joe Biden and Kanye West. Learn more about your ad choices. Visit podcastchoices.com/adchoices

Donate to The Permaculture Podcast Online: via PayPal Venmo: @permaculturepodcast In this episode from 2014, one of my favorite people from the permaculture community, Karryn Olson-Ramanujan, joins us to share a pattern language she's identified for women in permaculture, which we can use to create a constructive permaculture movement so that together we can design a world with ever greater beauty, abundance, and inclusivity. The starting point for this conversation is Karryn's article, which forms the title for this episode, “A Pattern Language for Women in Permaculture.” In this powerful piece Karryn outlines the patterns and provides solutions to create an environment for women's full participation and leadership in the permaculture community, and be recognized as the permaculture superstars they are. The eight patterns, some of which we discuss together, are: Shift our “Mental Models” Understand and Advocate for the “30% Solution” as a Vital Step Toward Parity Value Diversity Intersecting Identities Mentoring is Key to Building Women's Leadership Value Archetypically Feminine Ways of Leading Nurture Women's Leadership Through Women's Gatherings Be an Ally In addition to this pattern language, during her research Karryn found many women struggle to earn a living with their good work. To support these entrepreneurs, she offers three different courses: Pathfinders, Sweet Spots, and Abundance Models to help women design their regenerative right livelihood. Enrollment for the next Pathfinders course starts in late February 2020. If you are interested in this, or any of her other courses, you'll find those hosted within the Regenepreneurs Network, which you can also join as a general member. Learn more at Regenepreneurs.com. You will also find more of Karryn's writing on Medium, where she writes as @Regenepreneurs. References and resources from this episode: Regenepreneurs Earth Activist Trainings Gender Schema Tutorials Jeanine Carlson-Nelson Karen Stupski Microaffirmations Timebanking Margaret Wheatley Pandora Thomas Privilege and Allyship (Links to a PDF) Starhawk WPLI – Women's Permaculture Leadership Initiative Women Lead the Way by Linda Tarr-Whelan Profiles of Women in Permaculture Women Working with Permaculture in South Africa Alex Kruger and Berg-en-Dal Ecovillage Jeunesee Park Park at Food and Trees for Africa Several other awesome women were also profiled in Karryn's article.

As The Crowe Flies | Vance Crowe describes the value of creating a pattern language with friends, co-workers and your community by describing how Val Bayes invented "##"To connect with Val Bayes @VBayesTo connect with Rosella Mosby @RosellaMosbyVance Crowe Podcast Facebook PageTwitter: @VanceCroweAbout The Vance Crowe Podcast:The Vance Crowe Podcast interviews experts in unexpected fields and gets them to reveal the discoveries that come from having a knowledge of a highly specific discipline.  Vance Crowe is the CEO of Articulate Ventures (www.VanceCrowe.com) a communications strategy company- and he is regularly invited to deliver speeches around the U.S. and Canada teaching audiences how to communicate so that others want to listen, understand and value what you have to say.  

We open as The Waco Kid tells Bart all the killings got pretty gritty. Then, one day, as he was walking down the street, a voice said, "Reach for it, Mister!" The Waco Kid recalls turning around and standing face-to-face with a 6 year old kid. He threw his guns down and walked away. Then he added, "Little bastard shot me in the ass." He finishes his story, telling Bart that he crawled to the nearest saloon, crawled inside a whiskey bottle, and has been there ever since. After a moment, Sheriff Bart hands Jim a his bottle, telling him to have a drink. Today's guest is Chris Frain who is the producer and co-host of “Open the Podcast Doors, HAL” – a movie-by-minute examination and celebration of 2001: A Space Odyssey. He also records and performs electronic music under the name Pattern Language, and composes music for films on occasion. Thank you so much for tuning into today's episode. Come back tomorrow for another exciting episode of the movie, Blazing Saddles. In the meantime, don't forget to give us a rating and leave us a comment on your pod-catcher of choice. You can also follow us on Facebook, where we have a private listener's group, and we are on Twitter and Instagram. To learn more about us, our guests or to look through a list of all of our previous episodes, feel free to swing by our website. So bookmark, follow or like us everywhere and feel free to reach out to us anytime on this Wilder ride!  

We begin with Jim standing across from Bart with the chess table between them. Jim asks if Bart is ready? Bart says he is. Jim blows air across the tips of his fingers on his right hand and readies himself. He suddenly yells, Go! Sheriff Bart slaps his hands instantly around the King. But, when when opens them to reveal it, it isn't in his hands. Bart is incredulous. Jim then asks, "Are you looking for this?" as he pulls the king out of his holster. Bart exclaims, "Well raise my rent, you are the Kid!" However, Jim corrects him, telling him he "was" the Kid. After asking for details, Jim reveals how it got to the point that every pissant prairie punk wanted to try out The Waco Kid. We close with him saying he must have killed more men than Cecil B. DeMille. Today's guest is Chris Frain who is the producer and co-host of “Open the Podcast Doors, HAL” – a movie-by-minute examination and celebration of 2001: A Space Odyssey. He also records and performs electronic music under the name Pattern Language, and composes music for films on occasion. We hope you enjoyed today's episode. If you have not done so already, take a moment to leave us a rating on your pod-catcher of choice. Also, be sure to leave us a short comment. The comment actually does give more weight to your rating and it will then help others to find our show. To learn more about us, our guests or to look through a list of all of our previous episodes, swing by our website. We are also on Facebook, where we also have a private listener's group, Twitter and Instagram. So like or follow us everywhere and feel free to reach out to us anytime on this Wilder ride!

Donate to The Permaculture Podcast Online: via PayPal Venmo: @permaculturepodcast Avery Ellis, of Colorado Greywater, joins me to talk, in a conversation recorded live at a local coffee shop, about aquaponics, water harvesting, and his entry into the world of community politics when he joined the stakeholder process that changed the laws around how people can collect and use water in Colorado. From these experiences, he created the foundations for a pattern language, which he shares with us, that we can use to remove the restrictions placed upon permaculture designers, homeowners, and businesses that practice sustainability and build resilience. Find out more about Avery and his work at ColoradoGreywater.com -- I mentioned near the end of the conversation about some allies in our work to change the laws that restrict sustainable practices. The two you'll find linked to in the show notes are Community Environmental Legal Defense Fund and National Community Rights Network. The National Community Rights Network also has state chapters in Colorado, New Hampshire, Ohio, Oregon, and Pennsylvania. If you're involved in any kind of community engagement around the use of natural resources, definitely check out those two organizations. I really appreciate people like Avery, or Adam Brock or Karryn Olson-Ramanujan, who continue to develop various pattern languages, drawing on the earlier work of Christopher Alexander and team in the book A Pattern Language. I find that pattern languages extend the core principle of permaculture design and apply this language and thought process to specific problems. Karryn works on issues for women in permaculture. Adam on how to create change, here and now. For Avery, it is to be involved in the stakeholder process and politically engaged on the things we care about and lend our expertise, which lead him to his patterns. The ones he explicitly identified that we walked through in our conversation today were: allies on the inside, stakeholder cohesion, speaking legalese, CYA, people power, immutable force, and grit. Have you been involved in the process of political change? Are there patterns you would add to this list? Let me know. Leave a comment in the show notes or get in touch. Email: The Permaculture Podcast Write The Permaculture Podcast The Permaculture Podcast You can also use those ways to reach out if I can ever help you with your project or permaculture path. I keep my door open to lend a hand in whatever way I can. From here, the next episode is my conversation with Karen Lanier about her book, The Woman Hobby Farmer. Until then, spend each day creating the world you want to live in, but getting involved, changing the laws, and taking care of Earth, yourself, and your community.   Support The Podcast Become an on-going Patreon subscriber Make a one-time donation via PayPal Resources Avery Ecological Design Colorado Greywater Colorado Aquaponics Boulder Permaculture Sandy Cruz High Altitude Permaculture Living Routes (Now defunct. Reorganized as CAPE - Custom Academic Programs in Ecovillages) Auroville Ecovillage - India Master of Ecological Design - San Francisco Institute of Architecture Greywater Action Harvesting Rainwater and Brad Lancaster Allies in our work for change Community Environmental Legal Defense Fund National Community Rights Network Other Interviews on Pattern Languages 1723 – Change Here Now with Adam Brock 1433 - A Pattern Language for Women in Permaculture with Karryn Olson-Ramanujan

Madeleine Clare Elish presents “An AI Pattern Language,” coauthored with Tim Hwang. The publication is the culmination of two years of research and conversations with a range of industry practitioners working in intelligent systems and artificial intelligence. The work was supported by the John D. and Catherine T. MacArthur Foundation. You can purchase your own copy or download the PDF at autonomy.datasociety.net.

"This mix is, among other things, a mark of the season, an ongoing fight for honesty, a need, a desire, a campfire, a peripheral vision, balance that isn't a compromise, a thin blanket of snow, a tribute to Christopher Alexander, a dream seeking words, a roll across the shoulders, an acceptance of the unknown process, and a brush against the edges." - benchun THE SPACE COWBOYS RIPEcast is also available in iTunes. Subscribe for free at the Apple iTunes store with this link: http://bit.ly/RIPEcast-iTunes You can also find the The RIPEcast on Podomatic at http://spacecowboys.podomatic.com For more information on benchun visit www.benchun.net. For more information on The Space Cowboys visit www.spacecowboys.org.