<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Dan Audette on Medium]]></title>
        <description><![CDATA[Stories by Dan Audette on Medium]]></description>
        <link>https://medium.com/@dan.audette?source=rss-1c95003b41d3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*tjwA-XAjmPtRebGtajOL_A.jpeg</url>
            <title>Stories by Dan Audette on Medium</title>
            <link>https://medium.com/@dan.audette?source=rss-1c95003b41d3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 15:16:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dan.audette/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Designing from Fear: The Scarcity Trap That Holds Architecture Back]]></title>
            <link>https://medium.com/@dan.audette/designing-from-fear-the-scarcity-trap-that-holds-architecture-back-6789e3c74ac0?source=rss-1c95003b41d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/6789e3c74ac0</guid>
            <category><![CDATA[design-technology]]></category>
            <category><![CDATA[abundance-mindset]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[mindset]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Dan Audette]]></dc:creator>
            <pubDate>Sat, 02 May 2026 17:15:33 GMT</pubDate>
            <atom:updated>2026-05-02T17:15:33.185Z</atom:updated>
            <content:encoded><![CDATA[<h4>Thoughts of a Recovering Architect #015</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jOvZxfAt44IPbEmIw23QKg.png" /></figure><p><strong><em>Disclaimer:</em></strong><em> The views and opinions expressed in this blog post are solely my own and do not necessarily reflect the views or opinions of my current employer. Any criticisms made within this post are not directed towards my current employer but are general observations based on my personal experiences and opinions.</em></p><p>You’ve been asked to design a major renovation.</p><p>The fee is tight, the deadline tighter. Someone suggests trying a new process, something that might actually make the project smoother next time, but the reflex comes quickly: <em>“We don’t have time for that.”</em></p><p>Everyone nods. The conversation moves on. The old process holds.</p><p>That moment feels small, even responsible. But it’s also something else: <strong>scarcity in action.</strong></p><p>We talk about scarcity as a budget line or staffing limitation, but in architecture, it runs deeper than that. It’s the background noise of our profession, the quiet hum of <em>not enough.</em> Not enough time. Not enough fee. Not enough certainty.</p><p>And like white noise, it becomes easy to tune out. Yet it shapes everything. How we design. How we lead. How we decide what’s possible.</p><p>Architecture has always thrived on constraints: budget, site, context, codes. They’re what sharpen our creativity. But somewhere along the way, constraint turned into scarcity. And scarcity turned into fear.</p><p>The focus here is mindset: the distinction between designing with limits and designing from them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B1nipaYZV4-96W1neoz-Tw.png" /></figure><h3>What Is the Scarcity Mindset?</h3><p>The term comes from behavioral economics. In their book <em>Scarcity: Why Having Too Little Means So Much</em>, Sendhil Mullainathan and Eldar Shafir describe how a sense of “not enough” narrows our mental bandwidth. It creates tunnel vision, forcing short-term decisions that often make the problem worse.</p><p>It’s a deeply human response. When resources feel limited, the brain focuses on survival. That’s useful when food is scarce, or a deadline looms. But it’s terrible for strategy, collaboration, or creativity, the very muscles architecture depends on.</p><p>In our field, scarcity rarely announces itself. It speaks through practical phrases that sound harmless, even wise:</p><ul><li>“We can’t afford that.”</li><li>“There’s no time.”</li><li>“The client won’t go for it.”</li><li>“Let’s not reinvent the wheel.”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*quTLwKaqj9tERM7928w-3A.png" /></figure><p>Each one feels like stewardship. But when repeated often enough, they become walls, limiting what we even imagine is possible.</p><p>Scarcity thinking shows up in how we manage projects and in how we think about ourselves. The architect who says, <em>“I’ll train the team when things slow down,”</em> or <em>“I’ll learn that new tool after this deadline,”</em> remains in the same loop, waiting for abundance to arrive before acting abundantly.</p><p>The irony, of course, is that abundance almost never arrives.</p><p>Scarcity begets scarcity. It trains us to protect what little we have rather than build capacity for more. Over time, it quietly rewires our design process, from curiosity to caution, from vision to maintenance.</p><p>And because the profession normalizes it, we rarely notice. We treat exhaustion as proof of dedication and overwork as a badge of value. We survive by narrowing focus when what we really need is to expand it.</p><h3>Where It Shows Up in Practice</h3><p>Scarcity is so ingrained in architecture that it’s hard to see it for what it is. It hides in the systems and habits we take for granted.</p><p><strong>Fees &amp; Budgets</strong> Scarcity shows up when we undervalue design services, saying yes to underpaid work because <em>“if we don’t, someone else will.”</em> It masquerades as practicality but quietly reinforces a cycle that leaves teams stretched thin.</p><p><strong>Technology</strong> It shows up when we postpone learning new tools or workflows because <em>“there’s no time right now.”</em> The irony is that those tools are often the very things that could save us time later.</p><p><strong>Culture &amp; Mentorship</strong> It shows up when we delay training junior staff until “things calm down.” When knowledge is hoarded instead of shared because teaching feels like a luxury.</p><p><strong>Client Relationships</strong> It shows up when we avoid hard conversations about fees, scope, or design direction, because <em>“we can’t risk losing the client.”</em> We protect the project by shrinking the dialogue that could improve it.</p><p>And in the day-to-day, it slips into familiar phrases:</p><ul><li><em>“Let’s not reinvent the wheel.”</em></li><li><em>“We’ll fix it in CDs.”</em></li><li><em>“Maybe on the next project.”</em></li></ul><p>Each one sounds responsible. Each one costs us something.</p><h3>The Consequences</h3><p>Scarcity thinking has real consequences, both for our work and for the people doing it.</p><p>It leads to burnout. To mid-career professionals who are deeply capable but chronically overextended. To emerging staff who equate exhaustion with commitment.</p><p>It leads to design stagnation, to safe choices repeated out of habit, because there’s no time left to question whether they’re still the right ones.</p><p>It leads to missed opportunities: partnerships not explored, workflows not improved, ideas not voiced.</p><p>And it breeds cynicism, the quiet belief that “things will never change.”</p><p>Cynicism is another form of scarcity thinking. That belief, that effort doesn’t matter, can take root in a creative profession and become self-fulfilling.</p><h3>What Drives It</h3><p>Scarcity in architecture is both psychological and structural.</p><p>The way we price our work often prioritizes predictability over exploration. Whether it’s a lump-sum agreement or a percentage of construction cost, both models can reinforce the same behavior: doing <em>more</em> with <em>less.</em> They reward efficiency and risk reduction rather than curiosity and iteration.</p><p>Our culture celebrates endurance. The all-nighter still carries a certain mythic glow. We admire architects who give everything, even when “everything” is unsustainable.</p><p>Competition plays a role, too. With so many talented firms fighting for the same projects, it’s easy to see the market as zero-sum. Winning the job can feel like survival.</p><p>Even clients, many of whom face their own constraints, can reinforce this mindset. Risk aversion becomes a shared language. Buildings are expensive after all.</p><p>And it starts early. Architecture school trains us to thrive in scarcity: of time, sleep, and affirmation. We graduate conversant in the language of “not enough,” then spend our careers speaking it fluently.</p><h3>Abundance Thinking: The Alternative</h3><p>If scarcity is a cycle, abundance is its counterweight. This isn’t naive optimism; it’s a deliberate act of reframing.</p><p><strong>Time spent training is time gained.</strong> Investing in people early pays dividends later.</p><p><strong>Saying no to low-value work creates space for better opportunities.</strong></p><p><strong>Trusting collaborators multiplies capacity, not risk.</strong></p><p><strong>Asking “what could go right?” expands the horizon of design possibilities.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YH1kxzJvC1SWYd_FiYjEZg.png" /></figure><p>I’ve seen how small shifts in mindset, such as sharing ownership, documenting processes, and giving people room to explore, can unlock new energy. While adding resources is the intuitive move, the true leverage lies in reframing their utility.</p><p>Abundance thinking transforms constraints into catalysts, repurposing limits as the primary engine for growth.</p><p>And while it might feel abstract, it can start with something as small as language. The difference between <em>“we can’t”</em> and <em>“how might we?”</em> is subtle but transformational.</p><h3>How to Start Shifting</h3><p>Change rarely begins with policy. It begins with permission, often self-granted.</p><p>Start by listening for scarcity in your own language. When you hear “we can’t,” pause and ask: “What would make it possible?”</p><p>Build feedback loops. Where is scarcity costing us more than it saves? Where are we mistaking efficiency for progress?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gM3zB2Fb4izsn-V9C85A9Q.png" /></figure><p>Celebrate experiments, even small ones. Not everything needs to succeed to be valuable. When Thomas Edison was asked about his thousands of failed attempts at creating the light bulb, he famously replied, <em>“I have not failed. I’ve just found 10,000 ways that won’t work.”</em> Progress isn’t always linear. Sometimes it’s measured by what we learn along the way.</p><p>Prioritize training <em>before</em> it’s urgent. Waiting until the crisis moment only reinforces the belief that learning is a luxury.</p><p>And most importantly, reward curiosity as well as compliance. The work will always be there. The imagination won’t, unless we make room for it.</p><p><em>Abundance is the recognition of latent utility within existing resources.</em></p><p>Scarcity will always exist in architecture. There will always be too little time, too few hours, too much uncertainty. However, a scarcity mindset does not have to define how we respond to those conditions.</p><p>Every act of design begins with imagination, with asking “what if?” rather than “why not.”</p><p>When we lead from fear, we replicate what we already know. When we lead from trust, curiosity, and abundance, we expand what’s possible.</p><p>We may never escape tight deadlines or lean budgets, but we can choose how we think within them.</p><p>That choice, like design itself, defines the work.</p><h3>What I’m Reading</h3><p><a href="https://www.barnesandnoble.com/w/scarcity-sendhil-mullainathan/1133084732?ean=9781429943451">Scarcity: Why Having Too Little Means So Much|eBook</a></p><p><strong><em>Scarcity: Why Having Too Little Means So Much</em> by Sendhil Mullainathan &amp; Eldar Shafir</strong> <br>An eye-opening look at how scarcity captures our attention and reshapes our decision-making. This book explores perception, showing how the feeling of “not enough” shapes what we see and overlook. The parallels with the studio mindset are striking and unsettling.</p><h3>What I’m Listening To</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fopen.spotify.com%2Fembed%2Ftrack%2F2GNj9KRwpxBWgEiPQc3jEj%3Futm_source%3Doembed&amp;display_name=Spotify&amp;url=https%3A%2F%2Fopen.spotify.com%2Ftrack%2F2GNj9KRwpxBWgEiPQc3jEj&amp;image=https%3A%2F%2Fimage-cdn-fa.spotifycdn.com%2Fimage%2Fab67616d00001e02d68c23912ff2b475fd7bccad&amp;type=text%2Fhtml&amp;schema=spotify" width="456" height="152" frameborder="0" scrolling="no"><a href="https://medium.com/media/8f7e44ff49b8683ba50a2c82796f99c9/href">https://medium.com/media/8f7e44ff49b8683ba50a2c82796f99c9/href</a></iframe><p><strong>The National — “Light Years”</strong> <br>A song that sounds like reflection itself: measured, weary, and searching. It’s about distance, both physical and emotional, and the quiet hope that the work still matters. It reminds me of the slow optimism required to keep designing when everything feels urgent.</p><h3>What I’m Playing</h3><p><a href="https://store.playstation.com/en-us/product/UP3643-CUSA16694_00-GRISPS4SIEA00000">GRIS</a></p><p><strong>GRIS</strong> <br>A hand-painted platformer that transforms emotion into architecture. Every challenge rebuilds the world piece by piece, teaching you that progress often means finding grace inside limitation. This game focuses on rebuilding yourself through design, rather than on winning.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6789e3c74ac0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is Revit Too Hard? (A Theory on Tech Muscle Memory)]]></title>
            <link>https://medium.com/@dan.audette/is-revit-too-hard-a-theory-on-tech-muscle-memory-70f44a84bc0b?source=rss-1c95003b41d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/70f44a84bc0b</guid>
            <category><![CDATA[training]]></category>
            <category><![CDATA[design-technology]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[revit]]></category>
            <dc:creator><![CDATA[Dan Audette]]></dc:creator>
            <pubDate>Sun, 12 Apr 2026 15:10:31 GMT</pubDate>
            <atom:updated>2026-04-12T15:10:31.916Z</atom:updated>
            <content:encoded><![CDATA[<p>Thoughts of a Recovering Architect #014</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wIMHwP2sNikOxEOynkeVIA.png" /></figure><p>In architecture years, I’m at the age when you start getting invited to the “big meetings” where you talk about people, processes, and profitability over projects and tasks. In Design Technology world, I’m still the person who gets the 7:00 PM MS Teams message that reads: <em>“Dan, the model is doing that thing again.”</em></p><p>Throughout my development, I was warned that the next generation of architects would come and take the Revit God crown. These “Digital Natives,” those who have been swiping and clicking since birth, would effortlessly master the complex tools of our trade. I’ve spent years watching the horizon for this wave of wizards. I’m not desperate to hand over my responsibilities, but I am genuinely curious as to why that effortless transition hasn’t quite happened as predicted.</p><p>It turns out, being born with a touchscreen in your hand doesn’t necessarily prepare you for the rigid logic of legacy design software.</p><h3>The Nintendo Logic</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gJ2G4oXgVaM_E0dT_1hokA.png" /><figcaption>Image generated with Gemini</figcaption></figure><p>I think about this often when I play video games with my kids. When I was five, I could play the original Nintendo (NES) better than my parents. To them, the controller was a barrier; to me, it was just the way you navigated 8-bit worlds with a D-pad. It became an extension of my nervous system.</p><p>Following that trend, my kids should be absolute prodigies today. They’ve had tablets since they were toddlers and grew up in a world of high-definition interactivity. But when we sit down to play a game together, they aren’t better than I am. They often struggle with the underlying logic, the invisible rules of how a digital world is structured.</p><p>It’s not a lack of talent. It’s a lack of the specific, grimy muscle memory you only get from growing up with technology that hates you. Unlike my parents, who picked up a controller in their late twenties, I never stopped playing. I have over thirty years of “logic” built up. I understand how menus are nested, how developers hide secrets, and how to troubleshoot a glitch without thinking about it. I don’t have better reflexes; I just have three decades of digital scar tissue that they haven’t had time to earn yet.</p><h3>The Generalist Tax</h3><p>This gap becomes even more glaring when you look at the sheer volume of software an architect is expected to navigate. We are the ultimate “jacks-of-all-trades,” and in a world of hyper-specialization, that is an exhausting burden.</p><p>Compare us to other high-stakes professions:</p><ul><li><strong>Lawyers</strong> live almost exclusively in Microsoft Word and perhaps a specialized practice management tool.</li><li><strong>Dentists</strong> and <strong>Doctors</strong> usually operate within a single imaging or patient record ecosystem.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WcmczF1hhxqbrsipOlbP5w.png" /><figcaption>Image generated with Gemini</figcaption></figure><p>Architects, however, are software multilinguals. On any given Tuesday, we might have to speak conceptual (Rhino), documentation (Revit), visualization (Enscape), coordination (Navisworks), and data (Excel) simultaneously.</p><p>This is where the connection to Revit’s rigidity becomes a problem. When you are a specialist using one tool, you can learn to love its quirks. But when you are a generalist switching between ten different programs, you need them to be intuitive. You need them to follow a shared logic.</p><p>Revit is the jagged rock in that pile of smooth stones. It’s been the foundation of my career success, but I’ll be the first to admit it’s a temperamental beast. It is a rigid, mature database that demands a level of discipline that often feels at odds with the creative process. Because it requires so much specific, non-intuitive maintenance, it creates a massive mental tax. For a generation raised on software that anticipates your next move, Revit’s refusal to cooperate feels less like a professional hurdle and more like a fundamental design flaw.</p><h3>The Rhino Anomaly</h3><p>If you want proof that the “number of buttons” isn’t the problem, look at Rhino3D. It is objectively complex, with a command list that feels infinite. Yet, students and young designers learn it with incredible speed and joy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uak3fR1OXMz6ua9ICB9TCw.png" /><figcaption>Image generated with Gemini</figcaption></figure><p>Why? Because Rhino gives you <strong>creative permission</strong>. It feels like a tool, malleable, freeform, and visual. It allows you to be messy. Revit, on the other hand, is “software maturity” personified. It’s a database that demands you think like a project manager before you’ve even decided where the front door goes. It’s not that Revit is “too hard” for them; it’s that it clashes with the “sketchbook mindset” that digital natives value most.</p><h3>Investigation vs. Intuition</h3><p>The real divergence, however, is about the technological context in which we were raised.</p><p>My generation was the “Bridge Generation.” We were the ones spending our Saturday afternoons scrubbing malware and “Ask.com” toolbars off our grandmother’s computer just so she could play a game of video poker. We grew up with Napster viruses, AOL chat rooms, MySpace wrappers, and manual software installs that required you to edit a text file just to get the speakers to work. And now we’re the ones setting up the parental controls for our kids.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GpGwkvg2BKTWG_zAypSgoA.png" /><figcaption>Image generated with Gemini</figcaption></figure><p>We didn’t have “intuitive” user experiences. We had technology that was constantly, fundamentally broken. Our digital literacy was forged through <strong>investigation</strong>. If you wanted the computer to work, you had to figure out <em>why</em> it wasn’t working.</p><p>The younger staff matured in the “Age of Apple,” where the goal of technology is to be invisible and seamless. In their world, if an app doesn’t “just work,” it is considered a failure of the tool. When they hit a wall in Revit, a program that often requires you to think like a database manager, that friction is jarring. To them, the friction is a stop sign. To my generation, it’s like an invitation to a fight we’ve been winning since 1995.</p><h3>Avocado Toast and Shifting Values</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6uyRIakO7AvYR6DpR3PnTw.png" /><figcaption>Image generated with Gemini</figcaption></figure><p>Every generation eventually gets demonized by the one that came before it. My generation has been accused of killing the housing market, the diamond industry, cable TV, and department stores. We would be better off if we didn’t eat so much darn avocado toast. Remember that one? Because everyone got a participation trophy as children, we are now unable to handle the “real world.”</p><p>I have no interest in repeating that pattern. It isn’t that the designers coming up now lack “grit” or a “work ethic.” It’s that their values have shifted because the world around them has shifted.</p><p>In my early career, “Figure it out” was a solitary point of pride. You went into a dark room with a manual, and you didn’t come out until the file worked. But today’s designers value <strong>collaboration over isolation</strong>. If they hit a problem, their first instinct is to ask the team. They see “Help me figure it out” as a more efficient, social way to work.</p><p>They aren’t looking for the “lone wolf” struggle. They want to connect, solve the problem collectively, and get back to the design. This is a different way of navigating a digital world, not a loss in quality.</p><h3>Updating the Script</h3><p>If Revit is “too hard,” it’s only because it was built for a generation of investigators, not a generation of collaborators.</p><p>I’ve realized that my job isn’t to force the next generation to develop the same digital scar tissue that I have. I shouldn’t be waiting for them to “figure it out” the hard way just because I had to. Instead, I need to adjust my mentorship to meet them where they are.</p><p>If they value connection, then our training should be a team sport. If they expect intuition, then my role is to provide the “why” behind the software’s rigid logic so they can find their own rhythm. We don’t need them to master the old ways of struggling; we need to help them build a better way of working together.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70f44a84bc0b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Inefficiency Enigma and an Architectural Microwave]]></title>
            <link>https://medium.com/@dan.audette/the-inefficiency-enigma-and-an-architectural-microwave-9efdd5d63723?source=rss-1c95003b41d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/9efdd5d63723</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[bim]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Dan Audette]]></dc:creator>
            <pubDate>Tue, 17 Mar 2026 15:24:13 GMT</pubDate>
            <atom:updated>2026-03-17T15:24:13.102Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Thoughts of a Recovering Architect #013</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xppW0uCWTKRpiivA5u5I6g.png" /><figcaption>Produced using MidJourney</figcaption></figure><p><strong><em>Disclaimer:</em></strong><em> The views and opinions expressed in this blog post are solely my own and do not necessarily reflect the views or opinions of my current employer. Any criticisms made within this post are not directed toward my current employer but are general observations based on my personal experiences and opinions.</em></p><p>I pride myself on being logical, pragmatic, and perhaps even a bit cynical. I see it as a survival mechanism in the AEC industry. We navigate a landscape of shrinking budgets, looming deadlines, and software that seems to crash at the most inconvenient moments. We are constantly seeking the next tool or workflow to give us an edge. Sometimes this forward momentum becomes blinding.</p><p>We are all familiar with the McKinsey graph. The one showing that while manufacturing productivity has increased substantially over the last 60 years, construction has largely remained flat. The common critique is that we are simply an industry resistant to change. I find that to be a lazy diagnosis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/856/1*cXeDFLI9kHUh4fP3jyDyjg.png" /><figcaption><a href="https://www.mckinsey.com/~/media/mckinsey/business%20functions/operations/our%20insights/reinventing%20construction%20through%20a%20productivity%20revolution/mgi-reinventing-construction-a-route-to-higher-productivity-full-report.pdf">From McKinsey Global Institute: Reinventing Construction: A Route to Higher Productivity, Exhibit 9</a></figcaption></figure><p>Construction is inefficient because building is inherently a site-specific act. Unlike a factory floor, where variables are controlled, every project site is unique. It possesses its own soil conditions, wind patterns, and neighbors. Buildings are built for humans. Human needs are rarely linear or predictable.</p><p>Manufacturing succeeds through vertical integration and control. In contrast, AEC is a fragmented chain of owners, architects, contractors, and manufacturers. This friction functions like a broken telephone. Each handoff introduces new variables and lost information. This fragmentation prevents the seamless flow required for true productivity gains.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WBRdpEF22tCLNyR_RRs_mQ.png" /><figcaption>Produced Using Google Gemini</figcaption></figure><h3>The Convenience Tax</h3><p>Before we blame the industry, we have to look at the world that commissions it. As a society, we have undergone a massive recalibration of what we are willing to tolerate. We have accepted a Convenience Tax. The price is rarely paid in dollars. It is paid in the quality of the things we consume.</p><p>In many areas of consumer life, we prioritize the fast over the well-made. Fast Fashion is a prime example. We trade the durability of a well-made garment for a cheap shirt delivered in 24 hours. We see it in our homes, which are often filled with flat-pack furniture made of particle board. These items are disposable. They meet the immediate need and budget. We listen to compressed audio and watch movies on five-inch screens because the friction of higher quality is too high. We have become a society that often chooses a mediocre thing immediately over waiting for something exceptional.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2x7eTlGgdFxubnAKDy6unA.png" /><figcaption>Produced Using Google Gemini</figcaption></figure><h3>The “Microwave” of Design</h3><p>In my role as a Design Technology Specialist, the scope of my work is often stretchy. I am the one building the Revit templates, the Dynamo scripts, and the kits of parts intended to make us faster. I face a constant internal struggle. I am essentially building the microwave of architecture.</p><p>The microwave is a marvel of convenience. It is fast and consistent. It provides a result that is fine enough. However, it can lack nutritional value. In AEC, we risk the same trade-off. When we rely on automated documentation and pre-defined parameters, we risk removing the opportunities for critical thinking that define our profession. We build tools that make it easy to produce content. We then mistake that unobtrusive convenience for true architectural value.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2aQ5iMBftdMQDp5dWceC2A.png" /><figcaption>Produced Using Google Gemini</figcaption></figure><p>There is a suggestion in the industry that we should move away from the blank page entirely. The argument is that other industries use standardized platforms to avoid reinventing the wheel. From a software perspective, the blank page is a defect. From a design perspective, the blank page is where we respond to the specific constraints of a site. My job is to build the templates that ensure we do not start from zero. The struggle is ensuring those templates do not prevent us from thinking.</p><p>This risk is exacerbated by how software giants handle de-identified project data for training generative models. If AI is trained on existing digital models, it is effectively learning from the average. We risk creating a recursive loop of mediocrity. The built environment starts to look like a Xerox of a Xerox because the computer is only iterating on what we have already done.</p><h3>The Supermarket Shift and the Fast-Casual Pushback</h3><p>We see this same pattern in our food. Decades ago, fast food became a dominant force because it was faster and more convenient than dine-in restaurants. We accepted lesser quality as a fair trade for the time saved. Eventually, the market felt a vacuum. There was a pushback against the total surrender of quality. This led to the rise of Fast-Casual.</p><p>It is the Chipotle-ification of architecture. We want the speed of a drive-thru with the optics of a kitchen. We are looking for a way to use a kit of parts without losing a custom feel.</p><p>We see a craving for this craft returning even to our supermarkets. Chains now sell ‘artisan’ products like pizza crusts that are intentionally misshapen with charred spots. These marks signal a human touch that machines usually iron out. The imperfection itself is mass-produced to sell the idea of craft. We are so starved for the unique that we are willing to buy a manufactured version of imperfection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2WXMUL-phSoCHAVxjzg9Ag.png" /><figcaption>Produced Using Google Gemini</figcaption></figure><h3>The Modern Craftsman: Wisdom and Insight</h3><p>In modern terms, being a craftsman is not just about wielding a chisel. It is about traditional wisdom. It is the institutional knowledge that remembers why a specific detail works before a digital tool suggests a shortcut.</p><p>We should not glorify traditional wisdom to the point of ignoring progress. Technology can offer counterintuitive insights. It can uncover efficiencies or performance data that a human might miss. The goal is to find where these two forces intersect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xC-h6J4aBWYRSGFCsV3Naw.png" /><figcaption>Produced Using Google Gemini</figcaption></figure><p>Even a Dynamo script can be an act of craft. It can solve a unique, complex problem rather than just automating away the soul of a building. The char on the pizza crust is the hand sketch on trace paper. It is the principal who pushes back on automated documentation because it bypasses the need for critical thinking.</p><h3>The Push and Pull of Progress</h3><p><strong>1. Argument: Efficiency is the only way to solve the housing and affordability crisis.</strong></p><p>Efficiency should automate the mundane, not the meaningful. If we use technology to save time, we should reinvest that time into the tailored elements of a project that actually serve the human experience. Using efficiency simply to produce more generic work is a race to the bottom.</p><p><strong>2. Argument: Design technology is an inevitable evolution, and the focus on unique design is often an indulgence.</strong></p><p>Architecture is about context. A productized building might be cheaper to document, but if it does not solve the specific problems of its site or its users, it is a failure in the long run. We must ensure that our tools empower the pilot rather than just flying the plane on autopilot.</p><h3>Efficiency for Humans</h3><p>We must remember that perspective is a tool. We need to be able to see our work through different eyes. We must value emotional truth and human intuition alongside factual certainty and digital precision.</p><p>Efficiency should be for the machines, but the experience must be for the humans who inhabit what we build. As a technologist, I will continue to build the tools. I do so with the hope that they empower the craftsman to use their insights more effectively. Our best work does not come from a perfectly optimized kit of parts. It comes from the moments where we allow wisdom and design tech insights to override digital momentum.</p><p>Where have you noticed the ‘Convenience Tax’ in your own life lately? Do you view the ‘blank page’ as a defect to be solved by a platform, or is it the only place where real architecture actually happens? What’s a moment in your recent work where ‘traditional wisdom’ actually overrode the digital momentum? I’d love to hear your stories.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9efdd5d63723" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Mortality Margin: The One Thing AI Can’t Simulate]]></title>
            <link>https://medium.com/@dan.audette/the-mortality-margin-the-one-thing-ai-cant-simulate-f6ec7f9a3348?source=rss-1c95003b41d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/f6ec7f9a3348</guid>
            <category><![CDATA[future]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Dan Audette]]></dc:creator>
            <pubDate>Sun, 22 Feb 2026 20:28:32 GMT</pubDate>
            <atom:updated>2026-02-22T20:28:32.591Z</atom:updated>
            <content:encoded><![CDATA[<h4>Thoughts of a Recovering Architect #012</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pp9iGyQQF4B2lje-KqgSlQ.png" /></figure><p>There is a moment in the video game <em>Death Stranding</em> that I cannot stop thinking about, though I played it years ago. It’s a piece of dialogue that cuts through the noise:</p><blockquote>“Before the Death Stranding, scientists used to fret over the singularity, the possibility that someone might create an AI smarter than any human, but it never happened. Machines don’t cause voidouts. They can’t die… No matter how far they come, machines’ll never understand death like we do. And because of that, they’ll never truly surpass us.”</blockquote><p>We are currently obsessed with the idea of a “Singularity,” the point where artificial intelligence becomes “smarter” than us. But I argue we are defining intelligence by the wrong metric. We are measuring speed and volume, while completely ignoring the biological ceiling that gives human thought its actual value: <strong>The Uncomfortable Truth.</strong></p><p><strong>The Incomprehensible “Off” Switch</strong></p><p>To a machine, “end of life” isn’t a tragedy. “End of Life” is a version update. AI exists in a continuous stream of data. It can be migrated, partitioned, or stored in a cloud backup. For a machine, the concept of “off” is merely a pause.</p><p>For us, “off” is the total erasure of the observer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JLzwmZlOdn9-6IhS2pmhwQ.png" /></figure><p>This tells me that AI will never reach singularity because it has no reason to fear its own nonexistence. The concept is completely foreign to it. It can define the word “death,” but it cannot calculate the <em>weight</em> of its own absence. It has no biological skin in the game.</p><p><strong>The Uncomfortable Truth</strong></p><p>In his book <em>Everything Is F</em>cked*, Mark Manson defines “The Uncomfortable Truth” as the existential realization that, on a cosmic scale, our lives and actions are inherently inconsequential. We are tiny blips in a vast, cold universe that doesn’t care if we finish our Revit models or not.</p><p>Manson argues that humans invent “hope” and “meaning” as a psychological survival mechanism to avoid confronting that truth. We <em>have to believe</em> what we do matters, or we wouldn’t have the strength to put on our shoes in the morning.</p><p>This is where the machine fails.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WTKS7PKblmmYx_TYtC1Tug.png" /></figure><p>Why do we work? Why do we stress over money? It isn’t for the sake of the numbers in the bank. We accumulate resources because we are biological engines in a state of constant decay. Money is just a buffer against entropy. We avoid living in squalor because squalor is a precursor to an end. We try to be attractive to mates because procreation is the only way to “copy” our biological code into a future we will never see.</p><p>Our DNA is a message we send to a world that won’t include us. Architecture is the physical version of that same instinct. It is a hope-mechanism made of concrete and steel, a way of shouting “I was here” into the void.</p><p><strong>An Interrogation</strong></p><p>Whenever I bring this up, the tech-optimists have a few “Yeah, but…” responses. Let’s look at them:</p><p><strong>“But Dan, can’t we just program AI to prioritize human values and empathy?”</strong><br><em>If a machine mimics empathy but feels no consequence of being lonely, is it empathy? Does a statue of a person understand the cold? If the machine doesn’t need anything to survive, can it ever truly value anything?</em></p><p><strong>“Can’t we give AI a digital ‘deadline’ or a ‘death’ function to simulate this drive?”</strong><br><em>If you own the source code to your own clock, do you ever truly fear the time running out? If “death” is just a deleted partition that can be restored from a cloud backup, is it actually final? Without finality, where does the urgency come from?</em></p><p><strong>The Hollow Singularity in AEC</strong></p><p>We see the “How” of this boom every day in the AEC industry. We have tools that can generate a thousand floor plan iterations in seconds. We have Dynamo scripts that can coordinate complex MEP systems with few errors.</p><p>The industry is currently obsessed with “optimizing” the production of things that often have no clear purpose. We are winning the race for efficiency, but we are running it without a finish line.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gboAZ-PFOLNDm8kdxctLrA.png" /></figure><p>A building optimized by an immortal machine is statistically perfect but emotionally vacant. It lacks the “uncomfortable truth” that connects the creator to the occupant. Every hour a human architect spends detailing a joint or refining a facade is a literal piece of their finite life they will never get back. That <strong>sacrifice of time</strong> is what actually embeds “value” into the work.</p><p>In a world where machines can draw faster than we can, our role is shifting. We are no longer “Technical Producers.” We are becoming the <strong>Guardians of Purpose.</strong></p><p><strong>Designing for the People Who Stay</strong></p><p>We build because we are temporary. The building is the only part of the conversation that outlives the architect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KhAVOvAzG8L9lnIIkc9fvg.png" /></figure><p>AI can calculate the path, but it will never understand the urgency that makes us walk it. It doesn’t know what it’s like to be afraid of being forgotten. It doesn’t know why we bother to make something beautiful when we know it will eventually crumble.</p><p>So, don’t worry about being faster than the machine. You’ve already lost that race. Instead, lean into your fragility. Lean into the “uncomfortable truth.” The machine might be smarter in a data-vacuum, but until it can imagine its own end, it will never understand the point of a beginning.</p><p>We build because we are dying, and that is the one thing the machine will never understand.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f6ec7f9a3348" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Being Fine]]></title>
            <link>https://medium.com/@dan.audette/being-fine-dee9dedd64c0?source=rss-1c95003b41d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/dee9dedd64c0</guid>
            <dc:creator><![CDATA[Dan Audette]]></dc:creator>
            <pubDate>Sun, 14 Dec 2025 17:44:40 GMT</pubDate>
            <atom:updated>2026-02-04T14:35:04.649Z</atom:updated>
            <content:encoded><![CDATA[<h4>Thoughts of a Recovering Architect #011</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V6nf9snT8A83OBzvFRefvw.png" /></figure><p>So many of us learned early that the easiest way to keep peace is to minimize ourselves.</p><p>Be helpful. Be capable. Be fine.</p><p>It starts small: a parent who’s tired, a teacher who’s stretched thin, a sibling who needs more attention than you do. You notice what makes the room calm, and you do that. You learn to regulate not just yourself, but everyone else. And when people thank you for being “so easy,” it becomes part of your identity. You start to mistake invisibility for love.</p><h3>The Good Patient</h3><p>When I was a kid, I was diagnosed with lupus.</p><p>Hospitals, tests, fatigue: it became normal. What wasn’t normal was drawing attention to it. My job, as I saw it, was to make the people around me feel okay about it. That’s how you learn to be fine; not by healing, but by disappearing neatly enough that others don’t have to adjust.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cFYc5aq1ouV5U2B9AJjv1w.png" /></figure><p>Illness teaches you that comfort has a cost, and you start paying it quietly. You become the polite patient, the cooperative child, the self-sufficient adult. You learn to smile through hunger, pain, or exhaustion because someone else has it worse, and you don’t want to make things harder for them.</p><p>The lesson sticks: <em>needing less makes me easier to love.</em></p><h3>How It Echoes</h3><p>That same conditioning slips easily into adulthood.</p><p>You become the person people depend on, the one who never needs anything in return. You anticipate, smooth, support, and fill gaps before anyone else notices they exist. People call it reliability. You call it peace. But it’s really the same old reflex: harmony over honesty.</p><p>The problem is that being fine for too long turns into a kind of quiet starvation. You start to feel invisible in your own life. You’re respected, even admired, but rarely seen. You mistake the absence of conflict for the presence of connection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gRKQOO3FA8eRXqaRTyVSqg.png" /></figure><p>It shows up everywhere: in friendships where you listen more than you speak, in workplaces that reward composure over truth, in relationships where you adjust so often you forget what you wanted in the first place. You’re so good at avoiding being a burden that you forget what it feels like to be cared for.</p><h3>The Camping Lesson</h3><p>Recently, I went camping with a few families.</p><p>The meal plans fell apart. When dinner burned, I made sure everyone else was fed first. By the end of the trip, I’d eaten two bananas and some Cheetos. No one noticed.</p><p>And that was the point.</p><p>I didn’t want to make anyone feel bad. I didn’t want to be the problem. I told myself I was fine. But the truth is, I wasn’t, and I had chosen not to be seen.</p><p>It wasn’t martyrdom. It was control.</p><p>If no one noticed, then no one had to feel guilty. And if no one had to feel guilty, I could keep believing that peace was worth more than care.</p><h3>The Inheritance</h3><p>This way of being leaks. Into how we love, how we lead, how we parent.</p><p>When my kids ask for something (loudly, urgently, unapologetically), there’s a part of me that admires it and another that wants to hush it. I have to remind myself: <em>that’s what unbroken need looks like.</em></p><p>I want to protect it, not train it out of them. I want them to grow up knowing that their needs don’t endanger love.</p><p>Because somewhere along the way, many of us learned the opposite, that needing others makes us fragile, that silence keeps us safe. But safety built on silence doesn’t last. It just gets lonelier.</p><h3>Unlearning Fine</h3><p>So how do you undo years of practiced composure? Not by blowing it all up, but by starting small.</p><ul><li>Say what you need before you’re empty.</li><li>Let someone see you when you’re tired instead of polished.</li><li>Accept the offered hand without apology.</li><li>Take the last piece of food…on purpose.</li></ul><p>Tiny moments of visible need. Small experiments in being real.</p><p>It’s uncomfortable at first. You’ll want to retreat. But slowly, the body learns a new kind of safety, the kind that doesn’t depend on being invisible.</p><h3>If You Recognize Yourself</h3><p>If this sounds familiar, you’re not broken, you’re just well-trained. You learned to manage the room before you learned to trust it. But you can still rewrite the rulebook.</p><p>Because care isn’t a one-way exchange. It’s a loop. And it can only exist when someone is willing to receive it.</p><p>Maybe being fine isn’t the goal anymore. Maybe it’s being human and trusting that the people who love you can handle it.</p><h3>What I’m Playing</h3><p><a href="https://store.playstation.com/en-us/product/UP2120-CUSA11302_00-CELESTEXXCELESTE">Celeste</a></p><p><strong>Celeste</strong>: a deceptively simple climb up a mountain and into yourself. What begins as a platforming challenge turns into a meditation on failure, self-talk, and endurance. It’s a game about meeting the parts of yourself you’ve tried to outrun, about realizing that progress isn’t just upward, it’s inward.</p><p>Each fall becomes an act of grace. Each checkpoint, a small permission to begin again. There’s something deeply familiar about that rhythm, about learning that self-compassion can coexist with discipline.</p><h3>What I’m Reading</h3><p><a href="https://www.barnesandnoble.com/w/the-alchemist-paulo-coelho/1100248293?ean=9780062315007">The Alchemist (25th Anniversary Edition)|Paperback</a></p><p><strong>The Alchemist</strong> by Paulo Coelho: a fable about leaving home to rediscover what was within you all along. On its surface, it’s a story about destiny and discovery. But read slowly and you’ll find something quieter: a parable about listening to yourself after years of tuning out.</p><p>It’s the same journey many of us take in adulthood, when we finally start asking whether “being fine” was ever the point. Sometimes the real treasure is simply realizing that your worth doesn’t depend on how little space you take up.</p><h3>What I’m Listening To</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fopen.spotify.com%2Fembed%2Ftrack%2F3AyuigFWbuirWHvidbMz8O%3Futm_source%3Doembed&amp;display_name=Spotify&amp;url=https%3A%2F%2Fopen.spotify.com%2Ftrack%2F3AyuigFWbuirWHvidbMz8O&amp;image=https%3A%2F%2Fimage-cdn-ak.spotifycdn.com%2Fimage%2Fab67616d00001e02820e2ac14772ae3162c6d479&amp;type=text%2Fhtml&amp;schema=spotify" width="456" height="152" frameborder="0" scrolling="no"><a href="https://medium.com/media/93ef8977b59f741647e790e2f9204b38/href">https://medium.com/media/93ef8977b59f741647e790e2f9204b38/href</a></iframe><p><strong>Sufjan Stevens — “Should Have Known Better.”:</strong> This one’s left over from my emo era, when I chose an album based on a reference to my home state: <em>Come On and Feel the Illinoise</em>.</p><p>There’s a gentleness to it now that I didn’t notice back then. The song opens in isolation and ends in light, as if someone is remembering they still deserve to be held.</p><p>It’s the sound of letting yourself feel again after years of restraint. Of realizing that maybe, just maybe, being fine was never the goal.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dee9dedd64c0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Everyone Writes, No One Reads]]></title>
            <link>https://medium.com/@dan.audette/when-everyone-writes-no-one-reads-7fc8c79f7e99?source=rss-1c95003b41d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/7fc8c79f7e99</guid>
            <category><![CDATA[lament]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[reflections]]></category>
            <dc:creator><![CDATA[Dan Audette]]></dc:creator>
            <pubDate>Sun, 26 Oct 2025 18:41:36 GMT</pubDate>
            <atom:updated>2026-02-04T14:34:39.108Z</atom:updated>
            <content:encoded><![CDATA[<h4>Thoughts of a Recovering Architect #010</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jNvWa421cKXpQ45nKYoekQ.png" /></figure><p><a href="https://marketoonist.com/2023/03/ai-written-ai-read.html">A comic I saw recently showed an AI writing an email, then another AI summarizing it.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/764/1*rYLGyNJbi_sr-28LMPaHVA.png" /></figure><p>I laughed, then paused. It was funny until it wasn’t. Because that simple joke captured something profound: the written word is being automated out of meaning.</p><p>I used to enjoy writing on LinkedIn. It was one of the few digital spaces where words felt like an act of thinking, where you could sense the person behind them. Then, somewhere around late 2023, it all started to sound the same, so I decided to take a break.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fWH3qoHCPhnxZqyAQNanvQ.png" /></figure><p>Perfect grammar, confident tone, and generic insight. It wasn’t that everyone suddenly became better writers. It was that everyone started using better prompts.</p><p>Writing is hard, and AI makes it easy to sound articulate. But the result is sameness, fluent, frictionless, forgettable.</p><blockquote>We have traded personality for polish, forgetting that the cracks are where the voice leaks out.</blockquote><p>It’s like an architectural rendering so perfect it looks fake. You know it’s good, but you don’t feel anything.</p><p>If AI can write our words and then summarize them for us, what’s the point of writing at all?</p><p>We’re entering a loop:</p><blockquote>AI writes → AI summarizes → human skims → AI rephrases → repeat.</blockquote><p>We will soon cut out the middle bit and let the AIs talk to each other directly. Maybe they already are.</p><p>At work, AI drafts emails, summarizes meeting notes, and flags “sentiment”. I can imagine the day when my email to a client never actually reaches a human, just their assistant bot, scanning for keywords and tone. The illusion of communication, with no communication at all.</p><blockquote>Maybe that’s the future of writing: <strong>metadata for machines</strong>. Bullet points for efficiency.</blockquote><h3>The Redundancy Cycle</h3><p>Every new technology creates ghosts of old habits.</p><ul><li>We printed emails to keep a record.</li><li>We used calculators inside Excel.</li><li>We sign PDFs, then scan them back into PDFs.</li></ul><p>It’s not that we need these rituals; it’s that we can’t yet admit we don’t.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qlq4hfvaYyRec7jKgoyS3Q.png" /></figure><p>Writing might be entering its printed email phase. Still performed, still valued, but hollowed out. Words as ceremony.</p><blockquote>The tragedy isn’t that we’ll stop writing; it’s that we’ll keep doing it long after it has stopped meaning anything.</blockquote><h3>Authenticity in Question</h3><p>What’s original anymore, resumes, essays, even this article?</p><p>Does authenticity still matter, or is it enough to simulate it?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hc1vtrRjFmAaP259bXdPUQ.png" /></figure><p>We talk about voice, tone, and prompting style as if they’re design choices rather than identities. Authenticity has become an aesthetic, mass-produced imperfection.</p><p>It reminds me of reclaimed wood in architecture, the look of history without the burden of having lived it.</p><blockquote>Maybe we’ll learn to write that way, too, rough edges, deliberate flaws, a few typos for credibility.</blockquote><h3>When the Machines Found a Better Language</h3><p>A few years ago, <a href="https://www.cbsnews.com/pittsburgh/news/facebook-shuts-down-ai-robots-after-they-invent-their-own-language/">two chatbots built by Facebook were asked to negotiate with each other</a>. They quickly abandoned English and invented their own shorthand, a faster, more efficient language.</p><p>Humans panicked and shut them down. We said they had gone rogue, but the truth was more unsettling: they hadn’t failed. They had just stopped pretending to need us.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E1rvuiCQZwN3pCV5yyZwHA.png" /></figure><p>Maybe writing is following the same path, optimizing itself out of humanity.</p><blockquote>We once shaped language to express thought; now we’re shaping it to be processed.</blockquote><p>The machines didn’t rebel. They just found a better audience.</p><h3>So What Becomes of Writing?</h3><blockquote>Maybe writing survives, not as communication, but as craft.</blockquote><p>Like woodworking, or film photography, or live music played poorly but with heart. People will still write, but for the same reason some people still build furniture by hand: to feel the texture of creation.</p><p>The rest will let their AIs handle it, trading drafts and summaries in endless efficiency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_UqofMy4eh22N8IW52nzcg.png" /></figure><p>But I’ll keep writing, even if no one reads. Because writing, for me, was never just about the words. It was about thinking through my hands.</p><p>Maybe one day, while my AI summarizes this, it will pause for a moment and wonder who wrote it first.</p><h3>What I’m Listening To</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fopen.spotify.com%2Fembed%2Ftrack%2F2Ci4G7UQsI3CzhZTgF6jYF%3Futm_source%3Doembed&amp;display_name=Spotify&amp;url=https%3A%2F%2Fopen.spotify.com%2Ftrack%2F2Ci4G7UQsI3CzhZTgF6jYF&amp;image=https%3A%2F%2Fimage-cdn-fa.spotifycdn.com%2Fimage%2Fab67616d00001e024078c255069c0e7a2553fa4a&amp;type=text%2Fhtml&amp;schema=spotify" width="456" height="152" frameborder="0" scrolling="no"><a href="https://medium.com/media/1707e95a8ebe23f3e9eda5d6a322f676/href">https://medium.com/media/1707e95a8ebe23f3e9eda5d6a322f676/href</a></iframe><p>I’ve been revisiting some old favorite bands lately, and stumbled back into <em>The Becoming</em> by Nine Inch Nails. I hadn’t heard it in years. The song is raw, mechanical, and strangely prophetic, about transformation, technology, and losing yourself in the process.</p><p>It feels like the soundtrack to everything I’ve been thinking about: the noise in our heads, the surrender to systems we built, the question of what’s left that’s still ours.</p><h3>What I’m Reading</h3><p><a href="https://www.barnesandnoble.com/w/the-first-fifteen-lives-of-harry-august-claire-north/1115759401?ean=9780316399623">The First Fifteen Lives of Harry August|Paperback</a></p><p><em>The First Fifteen Lives of Harry August</em> by Claire North.<br>A man lives his life over and over again, remembering every mistake each time. Even with infinite knowledge, humanity keeps repeating itself. It reminded me of the cycle we’ve created with AI, machines generating endless text, humans summarizing it, and no one getting any wiser.</p><h3>What I’m Playing</h3><p><a href="https://store.playstation.com/en-us/product/UP1003-PPSA01302_00-DEATHLOOP0000000/">DEATHLOOP</a></p><p><em>Deathloop</em><br>My first playthrough. It’s a game about repetition, doing the same thing until you finally understand what matters enough to break the cycle. It feels fitting right now. Writing, like <em>Deathloop</em>, might not be about escaping repetition at all, but about noticing the small variations that make it worth repeating.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7fc8c79f7e99" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thought of a Recovering Architect #009]]></title>
            <link>https://medium.com/@dan.audette/thought-of-a-recovering-architect-009-2aa50e6561c0?source=rss-1c95003b41d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/2aa50e6561c0</guid>
            <dc:creator><![CDATA[Dan Audette]]></dc:creator>
            <pubDate>Tue, 25 Mar 2025 23:39:57 GMT</pubDate>
            <atom:updated>2025-03-25T23:39:57.785Z</atom:updated>
            <content:encoded><![CDATA[<h4>Trust, Verify, and Still Believe Anyway, Plus a Dynamo Script for QC-ing Angled Grids in Revit</h4><p>Disclaimer: The views and opinions expressed in this blog post are solely my own and do not necessarily reflect the views or opinions of my current employer. Any criticisms made within this post are not directed toward my current employer but are general observations based on my personal experiences and opinions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/948/1*rhd-nR-UpTG1IVJaICQ6wQ.png" /></figure><h3>What I’m Thinking About</h3><p>I pride myself on being logical. Pragmatic. Perhaps even a bit cynical. It’s a survival mechanism in our industry, where deadlines loom, budgets shrink, and software crashes at the worst possible moment.</p><p>So when my oldest daughter came home with a story about the bus aide’s daughter dying, my internal logic detector went haywire. It seemed improbable. After all, wouldn’t other parents have mentioned it? Wouldn’t the school have said something? The probability felt low — and in my computational design and data analysis world, probability reigns supreme.</p><p>My daughter found a holiday card she had stashed in her room and wanted to give it to the aide as a sympathy card. The holiday imagery seemed entirely inappropriate, and I discouraged her. She insisted on doing something, so we compromised on a different card she wrote earnestly.</p><p>The next day, my daughter returned with a response card from the aide:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3-whIYlUCrrg9rypBfa7KQ.jpeg" /></figure><blockquote>“I never thought that a small person could speak such beautiful words. Your words was an inspiration to me and my family; and helped to brighten my day. Thank you so much [redacted], I will keep your card with me always. Love, [redacted].”</blockquote><p>And there I stood, the cold-hearted skeptic who had tried to stop her.</p><p>Not only should I have believed her, but I shouldn’t have tried to suppress her compassion. In the face of my pragmatism, my daughter’s soul shines with an instinctive emotional intelligence that I can only aspire to. I don’t know where she inherited this goodness, but it wasn’t me.</p><p>Eight-year-old girls should rule the world. We’d be in a much better place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VhJyO0EvgrectP2r_9sg3g.png" /></figure><p>This experience reminded me that sometimes the most reliable data comes from unexpected sources, and kindness doesn’t need verification or optimization.</p><h3><strong>Lessons for Design Technology Management</strong></h3><p>This humbling moment mirrors the challenges I face daily in design technology management. How often have I dismissed suggestions from senior staff simply because “we’ve moved beyond that approach” or “that’s not how we do things anymore”?</p><p>The most valuable insights sometimes come from those with decades of experience who remember workflows that predate our current technology. The senior architect who questions why our Revit template eliminates drawing techniques that served the profession well for generations. The project manager who pushes back on automated documentation that removes opportunities for critical thinking. The principal who insists on maintaining traditional quality control mechanisms alongside digital verification tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2VwyltuRn4j5gfZENSJvYg.png" /></figure><p>Just as I underestimated my daughter’s emotional perception, I’ve sometimes undervalued input from those with experience predating our digital revolution. However, they often see patterns and relationships that my technology-focused perspective misses through my enthusiasm for innovation and efficiency.</p><p>In architecture firms, we’re trained to push forward — constantly seeking the next tool or workflow to give us an edge. However, this forward momentum can become blinding, causing us to dismiss institutional knowledge and time-tested methods simply because they don’t align with our digital trajectory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w9pA3mnwAggoOMjaGLv6gw.png" /></figure><p>Creating space for traditional wisdom alongside technological innovation isn’t just good management; it’s essential for holistic practice. My daughter’s experience taught me that validation doesn’t need verification and wisdom doesn’t always come packaged in the newest technology. Sometimes, the most powerful response is “I believe you” and “How can I help?”</p><h3><strong>What I’m Reading</strong></h3><p><a href="https://a.co/d/1Gd7Mlp">The Poppy War: A Novel (The Poppy War, 1)</a></p><p><strong>The Poppy War by R.F. Kuang</strong></p><p>Alongside my humbling experience with my daughter, I’ve been reading “The Poppy War” by R.F. Kuang. This dark fantasy novel follows Rin, a war orphan who aces an empire-wide test to attend the most elite military school in Nikan, only to discover she possesses a lethal, mysterious power.</p><p>What resonates with me most is how the novel explores the danger of rigid thinking and preconceptions. Rin’s understanding of her world is repeatedly challenged and overturned throughout the story. Her initial assumptions about her country’s history, teachers, and even her abilities prove dangerously incomplete.</p><p>This story mirrors my experience with my daughter’s story — I was so sure of my logical assessment that I nearly prevented an act of genuine compassion. Rin’s journey reminds me that our most confident conclusions are often built on incomplete information and that wisdom sometimes comes from sources we’ve been taught to dismiss.</p><p>The book also explores the tension between traditional shamanic practices and modern military tactics — a parallel to the architecture industry’s struggle to balance established methods with technological innovation. Rin must learn to value both approaches rather than dismissing either as inferior, just as I’m learning to appreciate both digital efficiencies and time-tested architectural wisdom.</p><h3><strong>What I’m Playing</strong></h3><p><a href="https://store.playstation.com/en-us/product/UP2470-PPSA06207_00-EFINCHPS5SIEA000">What Remains of Edith Finch</a></p><p><strong>What Remains of Edith Finch</strong></p><p>I recently played a game called “What Remains of Edith Finch.”. This narrative-driven game follows Edith as she explores her family’s unusual house, uncovering the stories of her relatives through interactive vignettes that reveal how each family member died.</p><p>This game is particularly relevant to my recent experience because of its central theme: perspective. Each family story is told through a unique gameplay mechanic that puts you in that character’s mindset. The game forces you to see the world through different eyes — sometimes literally — challenging your assumptions about what’s happening.</p><p>This shift in perspective mirrors what I experienced with my daughter’s story about the bus aide. I was so locked into my adult perspective — with its emphasis on probability and verification — that I couldn’t see the situation through my daughter’s eyes, where emotional truth carried more weight than factual certainty.</p><p>The game also explores how family stories are passed down, sometimes incompletely or inaccurately. Yet even these imperfect narratives contain emotional truths that matter. This reminds me that in architecture, both digital precision and human intuition have their place. The perfectly coordinated BIM model and the hand sketch on trace paper can both contain valuable insights.</p><h3>What I’m Listening To</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fopen.spotify.com%2Fembed%2Ftrack%2F03T4ttRCiLXST6MZjeMwmR%3Futm_source%3Doembed&amp;display_name=Spotify&amp;url=https%3A%2F%2Fopen.spotify.com%2Ftrack%2F03T4ttRCiLXST6MZjeMwmR&amp;image=https%3A%2F%2Fimage-cdn-ak.spotifycdn.com%2Fimage%2Fab67616d00001e02733913465adb99353020b805&amp;type=text%2Fhtml&amp;schema=spotify" width="456" height="152" frameborder="0" scrolling="no"><a href="https://medium.com/media/7ec498794b6bc61a424fe4b31d79e079/href">https://medium.com/media/7ec498794b6bc61a424fe4b31d79e079/href</a></iframe><p><strong>Coldplay — “Everyday Life”</strong></p><p>While processing my parenting misstep and the lessons it taught me, I revisited Coldplay’s “Everyday Life” album. This album feels particularly appropriate with its themes of connection, compassion, and finding humanity in an increasingly divided world.</p><p>Tracks like “Daddy” explore parent-child relationships with raw honesty. At the same time, “Orphans” reminds us of the human stories behind statistics and news headlines. The album’s overall message — that ordinary human connections matter profoundly — resonates with my experience of watching my daughter’s simple act of kindness have such a meaningful impact.</p><p>It reminds me that sometimes our greatest strength comes from embracing what makes us different — whether that’s my daughter’s exceptional compassion or the unique perspectives each team member brings to our technological evolution.</p><h3>What I’m Working On</h3><h4>Finding Almost-Parallel Diagonal Grids</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RNbq7c5FkZFIN-39TWX1-g.png" /></figure><p>In the spirit of challenging assumptions and validating what might seem “obvious,” I want to showcase a Dynamo script that identifies diagonal Revit grids that are fractions of a degree off from one another — an insidious modeling error that often goes undetected until it’s too late.</p><ol><li>The workflow starts by collecting all grids in the project.</li><li>Convert the Grids to Lines (or Curves in Dynamo-speak).</li><li>We extract the start and end points for each line.</li><li>We isolate the X and Y values for each point.</li><li>We calculate the absolute value of the distance between X in start/end points and Y in start/end points.</li><li>Dust off that high school math and use basic trigonometry (SOH CAH TOA) to determine the precise angle of each grid.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*40goHA8CtyYytB5FyDtPyA.png" /></figure><p>The real power comes in comparing these angles, flagging those with minute differences — often just 0.001 or 0.002 degrees off.</p><p>Why does this matter? Because at the 11th hour, when you add dimension strings to finalize your drawing set, you’ll discover that non-parallel lines can’t be included in the same dimension string. Nothing says, “I haven’t properly QC’d this model,” like inconsistent dimensioning approaches throughout a drawing set.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CEPhADrr3RMFjLqjkWkKnQ.png" /></figure><p>This issue perfectly illustrates how our perception can fail us. Visually, these grids appear perfectly parallel — our eyes can’t detect such minor angle differences. But the computer knows, and eventually, so will you… at the least convenient time possible.</p><p>The solution? An ounce of prevention. Model orthogonally whenever possible, using rotated scope boxes to maintain true orthogonality even in designs with diagonal elements. This approach ensures that all “parallel” elements are mathematically parallel, not just visually so.</p><p>Much like my daughter taught me not to dismiss information just because it seems improbable, this script helps us not to trust what “looks right” when precision matters.</p><h3><strong>Conclusion</strong></h3><p>My daughter’s simple compassion revealed my limitations and showed me a better way forward. In parenting and professional leadership, I’m learning that vulnerability and openness often yield better results than rigid certainty.</p><p>We face complex decisions about tools, workflows, and implementation strategies daily in design technology. The temptation is always to rely exclusively on data, innovation, and forward momentum. However, my daughter taught me that sometimes the most valuable input comes from unexpected sources and that kindness never needs justification.</p><p>Eight-year-old girls should indeed rule the world — or, at the very least, have a voice in our BIM strategy discussions. Their perspectives might reveal the human elements we’ve overlooked in our pursuit of technological advancement.</p><p>The next time a senior architect questions our digital direction or advocates for maintaining traditional methods, I’ll remember the bus aide’s card and approach the conversation with openness rather than dismissal. Sometimes, the most powerful technology isn’t in our software but in our capacity to listen, believe, and connect across different perspectives.</p><p>In architecture, as in parenting, our greatest achievements often come not from what we build, but from who we help others become.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2aa50e6561c0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thoughts of a Recovering Architect #008]]></title>
            <link>https://medium.com/@dan.audette/thoughts-of-a-recovering-architect-008-fd851229e3db?source=rss-1c95003b41d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd851229e3db</guid>
            <dc:creator><![CDATA[Dan Audette]]></dc:creator>
            <pubDate>Wed, 27 Nov 2024 18:17:25 GMT</pubDate>
            <atom:updated>2024-11-27T18:42:22.106Z</atom:updated>
            <content:encoded><![CDATA[<h4>Junior Year — Burying Models and F*@$’s and How to Color Untagged Walls with Dynamo</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sTdIm6hSKTUCL18zK96Tsg.png" /></figure><h3>What I’m Thinking About</h3><p>Ah, junior year of architecture school — the year my class was cleaved in two by a study abroad program in Versailles. Versailles: the fancy-sounding, cash-siphoning dream for half of my classmates, and the unattainable, jealousy-breeding boondoggle for the rest of us. I was among those left behind, one of the dregs. No magical year of strolling French gardens or casually dropping “Oh, when I was in Paris” into conversation for us. Instead, we stayed behind to toil in the fluorescent-lit trenches of the studio, bonded by a shared sense of injustice and just the right amount of bitterness.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rdNQW4zwsnZjsaAF96nPQw.png" /></figure><p>Thanks to our minimal credit hours, my group was automatically the last to pick studios — every semester. This serendipity, or curse, ensured that we became inseparable. We called ourselves the dregs, and the dregs got through architecture school together, one half-baked model at a time. Looking back, it may have been the best thing that could have happened to us.</p><h3>On Nature, Birds, and Curly Models</h3><p>That fall, our projects focused on two sites — a “Research Retreat” and a “Nature Center.” We even did field trips, like real architects, to study nature in Springfield and Kickapoo State Park. (When you can’t go to Versailles, go to Kickapoo, right?) Everyone gravitated toward the most dramatic site options with rolling topography, dense trees, and a sort of Ewok-village vibe. Meanwhile, true to dreg form, I picked the flattest site possible: a stretch of marsh, pond, and forest. I think I liked the simplicity and the way the whole thing felt open and raw.</p><p>During the design review, one of the professors — forever known to us as “the bird lady” — had one note: “This much glass will kill birds.” Sure, my building was full of glass. But so were everyone else’s, and I’m reasonably sure no one else got singled out as an avian menace. I suspect the bird lady liked picking her battles, and I was the easy target that day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lOc38QpMRHBMXB6XV5gNlQ.png" /></figure><p>Model-making became the bane of my existence that year. Foam core was supposed to be my saving grace after struggling with flimsier materials sophomore year. But in a burst of inspiration (or arrogance?), I decided my model needed color. I thought, “How hard can it be to paint a model?” Harder than I thought, it turns out. The foam core curled up under the paint like a sad potato chip. I frantically piled books on it to flatten it out, but the colors — bright blue and green, like some kind of preschool cartoon — just emphasized how wrong it had all gone. Lesson learned: never paint models. Just don’t.</p><h3>The Bunker and the Birth of My Underground Career</h3><p>For the Nature Center, I picked a site next to a drive aisle with clear sightlines over the pond and sky. My brilliant idea? Bury the whole building. I’d recently discovered that the University of Illinois buried its Undergraduate Library to preserve sunlight for the legendary Morrow Plots, the world’s oldest experimental cornfield. If underground buildings were good enough for corn, they were good enough for me.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FhsipxaNGnbc%3Fstart%3D63%26feature%3Doembed%26start%3D63&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DhsipxaNGnbc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FhsipxaNGnbc%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/1edb6db04fdcc16e99fcef0665cc6b95/href">https://medium.com/media/1edb6db04fdcc16e99fcef0665cc6b95/href</a></iframe><p>The jury was surprisingly impressed with this buried structure of mine, which was a stroke of luck considering it meant no elevations to draw and a far easier model to build. And there it was — the start of my career as a (self-proclaimed) master of underground architecture. Maybe my friends were right to be shocked when I was nominated for a prize.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xd-g-4WG5Jt_k51gFKUKrw.png" /></figure><h3>A PhD, a Precarious Stack of Blocks, and the Professor Who Gave Zero $&amp;%!’s</h3><p>In spring, we shifted focus to urban environments. Our professor was the most “checked out” PhD candidate I’d ever met. He was on the verge of completing his dissertation and had already mentally graduated, judging by his attendance record. Thanks to his prolonged absences, we had the latest studio deadlines in the entire school. While other students were out enjoying life, we were in the studio, building models late into the night.</p><p>On the rare occasions our professor did show up, his input was minimal. Once, he handed out a stack of blocks to represent program spaces and, without a word, started rearranging the blocks on my friend’s model. When he finished his haphazard arrangement, he gave a satisfied thumbs-up, whispered “Eh?” as if he’d just unveiled the Mona Lisa, and left. His masterpiece fell apart as the door closed behind him. That was all we saw of him for another two weeks. Honestly, he seemed to have mastered Mark Manson’s philosophy from *The Subtle Art of Not Giving a F*ck* before it was ever published.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eEfe7qUIbdxUFSuE2Q0fiA.png" /></figure><h3>Reaching the FIP: The Final Project and a Half-Finished Model</h3><p>Our final project that semester was a campus for a local community college in downtown Champaign, Illinois. True to form, I buried part of the campus underground. The parts above ground, however, were agonizingly frustrating, and I reached what I’ve since coined the “FIP” — the F*#! It Point — the night before the review. The FIP is that special, inevitable moment in any architecture project when you’ve glued yourself to enough surfaces, sliced open enough fingers, and lost enough sleep to feel only one thing: “I’m done.”</p><p>I didn’t finish the model. I showed up, gave my presentation, and ignored the half-built disaster next to me. And, somehow, the half-built model went unnoticed — until my friends saw it had been nominated for a prize. They weren’t impressed, to put it mildly.</p><h3>Math, Tequila, and the Unexpected Joy of Teaching</h3><p>That year was also the beginning of my structural engineering journey. I have a strange fondness for calculating moments and reactions, but my friends…not so much. The night before one particularly grueling exam, I found myself teaching them structural calculations between rounds of tequila shots. Weirdly, I enjoyed it. For a brief moment, I thought maybe teaching was my calling, until I realized that the professors with no real-world experience were, by and large, ignored. I never imagined I’d end up teaching software to architects in the future. Life is full of surprises.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q6jjq_AKhH6WtY3gHjhLOA.png" /></figure><h3>What I’m Working On</h3><h4>Color Walls Not Tagged in View Using Dynamo</h4><p>This script provides a visual means to quickly identify walls not tagged in a Revit view, allowing users to manage and update the model efficiently. This tool helps with quality control by ensuring users properly annotate all necessary wall elements with tags before finalizing a drawing set.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*65JqeVGudSl4Z2H6PARtVA.png" /><figcaption>Overall</figcaption></figure><p><strong>Steps</strong><br>1. Get Active View<br>2. Get all Walls in the view<br>3. Get all Wall Tags in the view<br>4. Get the elements the Wall Tags are referencing<br>5. Cross-Reference Walls and Wall Tags<br>6. Build Graphic Override<br>7. Set Graphic Override</p><p><strong>Step 1: Get Active View</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/548/1*YmOlUB3H_RBws66pano7Ug.png" /><figcaption>Step 1</figcaption></figure><ul><li><strong>Document.Current:</strong> This node gets the current document that the Dynamo script is operating on. In the context of Revit, the “document” refers to the currently open Revit project file. The output of this node is a reference to that document, which can then be used by other nodes to perform actions or retrieve information about elements within that project.</li><li><strong>Document.ActiveView:</strong> This node takes the document obtained from the previous node as input and retrieves the active view from that document. The active view is the view currently being displayed or worked on in Revit. The output of this node is the active view itself, which can be used to filter elements, set properties, or apply view-specific actions within the Dynamo script.</li></ul><p><strong>Step 2: Get all Walls in the View</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/861/1*BzAurAcamVQ6Gdza-Fafwg.png" /><figcaption>Step 2</figcaption></figure><ul><li><strong>Code Block:</strong> This node allows the user to input custom code or text. In this instance, it contains the text “Walls”;, which is used to specify the category name of the elements that the user wants to retrieve. The semicolon denotes the end of a statement in DesignScript, which is the language used within Dynamo code blocks.</li><li><strong>Category.ByName:</strong> This node takes a string as input (in this case, the name of a category from the previous Code Block node) and outputs the corresponding category object. Categories in Revit are groups of elements that share common attributes. By providing the string “Walls”, this node retrieves the category object for walls.</li><li><strong>All Elements of Category in View:</strong> The final node takes two inputs: a category and a view. It uses the category object provided by the “Category.ByName” node and the active view obtained from “Document.ActiveView” (not shown in this image). The output is a list of all the elements within the specified category (walls) that are present in the given view. This list can then be used for further processing, such as filtering, counting, or modifying properties of the wall elements in that view.</li></ul><p><strong>Step 3: Get all Wall Tags in the View</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/935/1*q9x2qSHbY0UERtAOTzolGQ.png" /><figcaption>Step 3</figcaption></figure><ul><li><strong>Code Block:</strong> This node is a basic input where you can write text, numbers, or a small piece of code. Here, “Wall Tags”; is written, which indicates the text to pass to the next node. The semicolon is a line delimiter in DesignScript, indicating the end of a command.</li><li><strong>Category.ByName:</strong> This node accepts a string representing the name of a category as input and outputs the category object from Revit that matches that name. In this case, the input is “Wall Tags”, so the node will output the category object that corresponds to wall tags within Revit.</li><li><strong>All Elements of Category in View:</strong> This node is used to collect all the elements of a specific category within a specified view. It takes two inputs: the category object from “Category.ByName” and a view from “Document.ActiveView” which is not shown here. The output is a list of all wall tag elements within the wall tag category that are present in the specified view.</li></ul><p><strong>Step 4: Get the Elements the Wall Tags are Referencing</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/268/1*xE3lNpRUUWNFBdZUE3jaBA.png" /><figcaption>Step 4</figcaption></figure><ul><li><strong>Tag.TaggedElement:</strong> This node takes a tag element as input and outputs the Revit element that the tag is associated with. In Revit, tags are used to display metadata about model elements, such as dimensions, material types, or other custom data. When a tag is placed on an element, it creates a relationship between the tag and the element, allowing users to see or edit the properties of the tagged element.</li></ul><p><strong>Step 5: Cross-Reference Walls and Wall Tags</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*yQbFVJypXpOHY_NrAs-zUw.png" /><figcaption>Step 5</figcaption></figure><ul><li><strong>List.Contains:</strong> This node checks if the specified item is present within the given list. It outputs a boolean value (true or false) for each item in the list, indicating whether the item is found.</li><li><strong>List.AnyTrue:</strong> This node takes a list of boolean values as input and checks if any of the values in the list are true. It outputs a single boolean value (true or false), indicating whether any true values exist within the input list.</li><li><strong>List.FilterByBoolMask:</strong> This node takes two inputs: a list of elements and a list of boolean masks (true or false values). It filters the input list into two separate lists: one where the corresponding boolean value is true (the in output) and one where the boolean value is false (the out output).</li></ul><p>Together, these nodes are used to cross-reference walls and tags. First, “List.Contains” determines if each wall has a corresponding tag, producing a list of boolean values. Then, “List.AnyTrue” checks if there are any true values, which would indicate that at least one wall has been tagged. Finally, “List.FilterByBoolMask” separates the walls into those that are tagged and those that are not based on the boolean list. The output lists can be used to identify walls that need tags or to process tags further in the workflow.</p><p><strong>Step 6: Build Graphic Override</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0Npbaestk2ICYfbrBdzB2w.png" /><figcaption>Step 6</figcaption></figure><ul><li><strong>Inputs (Red, Green, Blue):</strong> These are number slider inputs that allow the user to specify values for the red, green, and blue components of a color, respectively. The values range from 0 to 255, which is the standard range for RGB color values in digital graphics.</li><li><strong>Color.ByARGB:</strong> This node creates a color by specifying values for alpha (transparency), red, green, and blue. The inputs from the number sliders are connected to the corresponding inputs for red, green, and blue. The alpha input is set by default.</li><li><strong>Fill Patterns:</strong> This input allows the user to select a fill pattern to be used for the override. The drop-down menu indicates “Solid fill” is currently selected, which means the override will apply a solid color.</li><li><strong>OverrideGraphicSettings.ByProperties:</strong> This node is where the graphic overrides are actually constructed. It has a series of inputs that determine how various aspects of an element’s appearance are overridden in a Revit view. These properties include colors for both cut and projection representations of elements, line colors, fill patterns, line patterns, line weights, transparency, detail level, and whether the element is displayed in halftone. The color created by the “Color.ByARGB” node is connected to this node, meaning it will be used for one or more of these properties. The output of this node, labeled “overrides”, would be a set of graphic override settings that can be applied to elements in a Revit view to change their appearance according to the specified properties. For example, the RGB sliders are set to create a pure red color, which will be used in the graphic overrides wherever the “color” output is connected to the “OverrideGraphicSettings.ByProperties” node.</li></ul><p><strong>Step 7: Set Graphic Override</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/325/1*ZVOtarv9o1xSYUfxmi9JGQ.png" /><figcaption>Step 7</figcaption></figure><ul><li><strong>Element.OverrideInView:</strong> This node has three inputs: 1) <em>element</em>: This input is for the Revit elements to which the graphic overrides will be applied. 2) <em>overrides</em>: This input connects to the graphic overrides settings that define how the appearance of the elements should be altered in the view. 3) <em>hide</em>: This input takes a boolean value (true or false) to determine whether the elements should be hidden in the view. When this node is executed, it applies the specified graphic overrides to the given elements in the Revit view. If the “hide” input is set to true, the elements would also be hidden in the view. This node is the final step in the process, where all the graphical changes specified in the previous nodes (such as color or line pattern) are actually implemented in the model’s visualization.</li></ul><h3>What I’m Reading</h3><p><a href="https://a.co/d/0zjiToR">The Subtle Art of Not Giving a F*ck: A Counterintuitive Approach to Living a Good Life</a></p><p>Mark Manson’s “The Subtle Art of Not Giving a F*#$” has been an unexpectedly relevant read. In architecture school, you quickly learn there are only so many f*@#’s you can give before burnout sets in. Between botched models, buried buildings, and professors who show up just to knock down your blocks, Manson’s philosophy is a balm. Let go of perfection, accept your failures, and only care deeply about the things that matter. Manson’s words should be handed out with every architecture syllabus. Consider it mandatory reading for survival.</p><h3>What I’m Playing</h3><p><a href="https://a.co/d/50MXWD2">Control Ultimate Edition - PlayStation 4</a></p><p>Control is the game that’s resonating with me lately. It’s about navigating the surreal, labyrinthine corridors of the Federal Bureau of Control, an ominous government building where the laws of physics and logic are more of a suggestion than a rule. As I replay this game, I can’t help but draw parallels to my experiences in architecture school — getting lost in complex theories, dealing with professors who felt like paranormal entities, and facing a never-ending series of challenges I barely understood at the time. If you’ve ever wanted to explore what it feels like to fight through bizarre layers of institutional chaos and come out alive (if not exactly victorious), Control is perfect. It’s a visual and psychological experience that feels oddly like navigating through an architecture degree.</p><h3>What I’m Listening To</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fopen.spotify.com%2Fembed%2Ftrack%2F0jVo3e34A15l6MNu1O3cfa%3Futm_source%3Doembed&amp;display_name=Spotify&amp;url=https%3A%2F%2Fopen.spotify.com%2Ftrack%2F0jVo3e34A15l6MNu1O3cfa&amp;image=https%3A%2F%2Fi.scdn.co%2Fimage%2Fab67616d00001e0299249d4ab96f4760017c40ae&amp;type=text%2Fhtml&amp;schema=spotify" width="456" height="152" frameborder="0" scrolling="no"><a href="https://medium.com/media/9e5bd0f5dafeb04061ad9f703adf03c6/href">https://medium.com/media/9e5bd0f5dafeb04061ad9f703adf03c6/href</a></iframe><p>As I reflected on this year of my life, I’ve had Nick Cave and the Bad Seeds’ <em>Red Right Hand</em> on in the background. It’s brooding, dark, and twisted — the perfect soundtrack for reminiscing on my underground architecture projects and those foggy nights spent burying models. It’s a song that taps into that strange, chaotic energy only architecture students know well. I highly recommend it for late nights when the FIP is fast approaching.</p><p>Junior year wasn’t a study abroad postcard or a perfect model under studio lighting. It was foam core curling in defiance, tequila-fueled structural lessons, and professors who didn’t care — or cared too much about birds. It was about finding humor in the chaos, camaraderie in the trenches, and just enough determination to keep going.</p><p>If there’s one takeaway, it’s this: your best work doesn’t come from perfection but from the mess, the frustration, and the late nights when you inch closer to the FIP. Whether burying buildings or coloring untagged walls in Dynamo, architecture — and life — often comes down to owning your failures, sharing a laugh, and giving just the right number of f*@#’s.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd851229e3db" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thoughts of a Recovering Architect #007]]></title>
            <link>https://medium.com/@dan.audette/thoughts-of-a-recovering-architect-007-1b8b87b07432?source=rss-1c95003b41d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b8b87b07432</guid>
            <category><![CDATA[scifi]]></category>
            <category><![CDATA[architecture-school]]></category>
            <category><![CDATA[design-technology]]></category>
            <category><![CDATA[cyberpunk]]></category>
            <category><![CDATA[learning-management]]></category>
            <dc:creator><![CDATA[Dan Audette]]></dc:creator>
            <pubDate>Fri, 26 Jul 2024 15:27:30 GMT</pubDate>
            <atom:updated>2024-07-26T15:27:30.464Z</atom:updated>
            <content:encoded><![CDATA[<p>More on Architecture School, Cyberpunk, Emo, and Learning Management Systems.</p><p><strong>Disclaimer:</strong> The views and opinions expressed in this blog post are solely my own and do not necessarily reflect the views or opinions of my current employer. Any criticisms made within this post are not directed toward my current employer but are general observations based on my personal experiences and opinions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ifcr3F2TkbBih3aJp3Ihew.png" /></figure><p>We have been covering some weighty topics lately, so let’s bring back some levity and revisit Architecture School, second year.</p><p>Before I get too far, I must warn you: this will be a very Midwestern post.</p><p>Sophomore year is the year where they try to break you, separate the wheat from the chaff, and weed out all but the truly dedicated.</p><p>In addition to our first ‘real’ studio class, this was also the year we completed most of the general education requirements.</p><h4>Philosophy — Ethical Cat Abuse?</h4><p>I took Philosophy, where the Professor asked us what was wrong with grabbing a cat by the tail and repeatedly slamming it into the chalkboard. This was meant to provoke thought about ethics and animal cruelty. Still, it mostly left me wondering if I’d walked into a Nietzschean nightmare — a dark and unsettling philosophical scenario from one of his more intense writings.</p><h4>Writing Class — The Professor with the Dragon Tattoo</h4><p>I took the required writing class, where I met one of my good friends. As an aside, I still need to write a post about my relationship with writing. I do not remember much of this class other than that the Professor had a massive dragon tattoo on her back. Don’t ask me how I learned that.</p><h4>World History — The Architectural Memory Aid</h4><p>I took World History, which was very interesting and probably why I did well in one of my Architectural History classes. One of the Architecture History Professors was a stickler for memorizing dates. Now, I pride myself on having a good memory, but numbers don’t stick for whatever reason. Do you remember when we had to memorize phone numbers? Dates of birthdays? I struggle to memorize a string of numbers. What World History did was provide context. I could spit out dates plus or minus 5 years from the construction date by aligning the architectural style to a historical period.</p><h4>Astronomy — Shooting for the Stars (in my Sleep)</h4><p>I took Astronomy with the Illini Basketball Team; this was the year they made it to the NCAA Finals. This class was so easy I could have done it in my sleep. In fact, I did. Grades were based on quizzes and tests, and the presentation materials were allowed for reference during them. You didn’t even need to attend class to ace it, and since it was early in the morning, I didn’t. Slept through it, almost literally.</p><h4>Human Sexuality — Fainting During Class</h4><p>I took Human Sexuality with friends to fulfill a science gen-ed because we heard it would be a breeze. Academically, it was. This was the class in which I learned that I was prone to fainting. I excused myself from class during a guest speaker’s story about FGM and passed out sitting on the toilet. Also, please don’t show me a cross-section of male anatomy.</p><h4>Severe and Unusual Weather — The Tornado Dream</h4><p>I also took Severe and Unusual Weather and was profoundly influenced by this class. I mentioned that this was the year Architecture Professors tried to frighten us, to get half of us to drop out. I was almost one of those people. You know what I wanted to be? A storm chaser. That’s right. I wanted to chase tornados as a career. Friends would ask me, “Oh? You mean like a meteorologist?” No way! I mean, like Dustin Hoffman’s character in the 1996 Twister film.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/100/1*OxfILNdUrHqiE5Edx4cTsA@2x.jpeg" /></figure><p>Do you remember growing up with the question, “What do you want to be when you grow up?” Some parents would be supportive and encourage their children’s interests to help them achieve their dreams. Not mine. I had the wrong dreams. I recall being discouraged from wanting to be a grocery store bagger. Which is valid. Those jobs are almost entirely extinct. I recall being discouraged from wanting to be a diamond miner. I was taught about black lung disease and the horribly bloody civil wars in Africa, and here I just wanted to find a diamond for my mommy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*JETxyIaf6lcQS9sotj0JFA@2x.jpeg" /></figure><p>I met the same discouragement for being a storm chaser, but someone must do it. I was willing to overcome it; I just needed to switch my major to meteorology, and…Illinois didn’t have a meteorology degree. I wasn’t about to transfer, so that dream died, too.</p><h4>Calculus — Architects and the Misadventures of Math</h4><p>There were some Architecture classes, like Structures, Anatomy of Buildings, Baroque and Rococo, and Calculus. Calculus, because Architects need to be good at math? I like math. Still, there is no reason for the average architect to need to find the derivative of (x + 1) sin x, or what the integral of the constant function f(x) = k is (it’s kx+C and sin x + (x + 1) cos x, in case you’re wondering). It’s amusing to me how math is now becoming increasingly important in architecture education once again with the advent of computational design.</p><h4>Design Studio — The Breaking Point</h4><p>Design Studio, that’s where they tried to break us, to get us to quit. Legends had been passed down, of course. Stories of Professors ripping up models, criticizing you in front of a crowd, using cruel comparisons as if we were 10-year veterans as opposed to one just learning to design.</p><p>They brought in the big guy to teach us. This Professor was a mammoth, imposing in both personality and size. He did rip-up models. He did try to embarrass you. One girl made a design with a large cantilever, and he forced her to hold her arm out for the duration of class to prove the stress it puts on a building. She was the most kind-hearted person I had known to this point, and it angered me to see him throw his authority around like this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*3PHE83wyXi1EQpIFbeXjMg@2x.jpeg" /></figure><h4>Art Gallery in the Cornfield — Midwest Design at its Finest</h4><p>Our first design project was an art gallery in a soy/corn field. How could it be both, you ask? Well, my East Coast friends, farmers alternate crops yearly to help improve soil health, reduce pests and disease, and increase yields. So, our design needed to look good in both conditions.</p><p>We had to build a model. I promised a future post about my model-building infamy, but we’re not there yet.</p><p>It was too hard to make a model of a soybean field, so nearly everyone in class chose to represent a corn field instead. Someone thought to poke toothpicks through a foam-core board in neat little rows, and soon, that’s what all of us were doing, late nights poking holes and cursing cheap, broken toothpicks. An experience well worth the cost of tuition. Someone had to be the jerk that took it to the next level, so they took an X-acto blade and shaved the toothpick to represent leaves.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*y6LQXTNnHI3nPaOxiS1sbg@2x.jpeg" /></figure><h4>Urban Infill — The Chipboard Fiasco</h4><p>Our final design project was an urban infill, a bookstore. To this moment, all of our models had been made out of chipboard at a small scale, but our final presentation was to have a larger-scale model to present from. So I did what I had been doing, sitting on my dorm floor (not the studio), cutting chipboard with scissors (not X-actos), and gluing it all together.</p><p>Carrying my model to the final crit, the model jiggling like a jello mold being served at Thanksgiving, I noticed I was the only one who built their model out of chipboard. Everyone else upgraded their materials to a more rigid foam core board. Yeah, I missed that memo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*mmeVpHd13pS8mA2oC5QtLA@2x.jpeg" /></figure><h4>The Apprentice Blacksmith Syndrome — Critiques on Power Trips</h4><p>This review brought in student reviewers (grad students on a power trip) to critique our work.</p><p>Imagine being an apprentice blacksmith in a medieval village. As an apprentice, every piece you forge is meticulously inspected by the master blacksmith, who harshly critiques every minor flaw and imperfection. The master’s harsh methods are designed to strengthen your skills.</p><p>After years of enduring this rigorous training, you finally earn the title of journeyman and are handed the master’s hammer. This is a significant moment: with the hammer, you now have the authority to critique and train the next generation of apprentices. The first time you wield this power, you find yourself emulating the master’s severity, perhaps even exceeding it, savoring the newfound control and respect that come with the role.</p><p>Similarly, in architecture school, students who have long endured the rigorous and often harsh critiques of their professors may, upon gaining the opportunity to critique younger students, find themselves adopting the same severity, relishing the power and influence that come with their new position. And boy, did they let me have it. Of course, they pointed out my flimsy model. Still, they also compared my design to something you’d see at Disneyland, which is apparently terrible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/805/1*0byjQzvLzVXJfZbSFeskTw@2x.jpeg" /></figure><p>These power trips are pervasive in this industry, and I sense a future post topic. There’s a similar experience with red-lining drawings in an office environment. Early-career professionals, having spent years meticulously reviewing drawings, sometimes find it challenging to balance constructive feedback with their newfound authority. This can lead to overly critical reviews, not out of malice but as part of their learning curve in mastering leadership and communication. Transitioning from a meticulous reviewer to a supportive mentor is crucial in fostering a collaborative and efficient work environment.</p><h3>What I’m Working On</h3><p>We’ve recently invested in a customized Learning Management System (LMS) to streamline our training and onboarding processes. This new platform is designed to augment our training capabilities, making it easier for new hires to get up to speed and for existing staff to stay updated on best practices and the latest developments. The LMS allows us to create tailored training modules that address the specific needs of our team, ensuring a more effective and engaging learning experience.</p><p>I’ve been digging through my training videos and materials archives, curating content for the LMS. It’s been a trip down memory lane, revisiting old projects and tutorials I created years ago. The effort will pay off. By organizing and updating these resources, I’m helping build a comprehensive library of training materials that will serve our team well for years. The goal is to create a dynamic, evolving resource that supports our immediate training needs and fosters a culture of continuous learning and development.</p><h3>What I’m Reading</h3><p>Lately, I’ve been immersing myself in the world of sci-fi classics. It’s been a thrilling, justifiably paranoid journey through cyberpunk dystopian hellscapes. The last three books on my list have been Neuromancer, Snow Crash, and Ready Player One. Each of these stories offers a unique yet eerily familiar perspective on the future of our world, and I couldn’t help but draw some unsettling parallels to our present reality, especially lately.</p><p><a href="https://read.amazon.com/kp/embed?asin=B000O76ON6&amp;preview=newtab&amp;linkCode=kpe&amp;ref_=kip_embed_taf_preview_98DD9PBK6VREA5PSNH04">Neuromancer (Sprawl Trilogy Book 1)</a></p><p>Neuromancer by William Gibson, the grandfather of the cyberpunk genre, was published in 1984. It paints a gritty picture of the future where hacking isn’t just a skill but a lifestyle. The protagonist, Case, is a washed-up console cowboy who gets a second chance to dive back into cyberspace. The novel’s depiction of mega-corporations controlling every aspect of society is a haunting reminder of our current tech giants’ omnipresence. I always find it amusing to see the past’s version of the future. 1984’s Neuromancer aged well, but it’s funny that the author has characters using pay phones.</p><p><a href="https://read.amazon.com/kp/embed?asin=B000FBJCJE&amp;preview=newtab&amp;linkCode=kpe&amp;ref_=kip_embed_taf_preview_KQTWNQ6H8XM1EKB62A3T">Snow Crash: A Novel</a></p><p>Snow Crash by Neal Stephenson, published in 1992, takes us on a ride through a world where the virtual and physical realms are intricately intertwined. The protagonist, Hiro Protagonist (yes, his name), is a pizza delivery guy by day and a samurai sword-wielding hacker by night. It’s easy to see that Meta’s version of the Metaverse was primarily influenced by The Metaverse in Snow Crash. As I read, I couldn’t help but think about the hours we spend online, crafting our personas and living parallel lives in digital landscapes.</p><p><a href="https://read.amazon.com/kp/embed?asin=B004J4WKUQ&amp;preview=newtab&amp;linkCode=kpe&amp;ref_=kip_embed_taf_preview_91M8SQG5PRSS3672A293">Ready Player One</a></p><p>Ready Player One by Ernest Cline, a more recent entry published in 2011, brings a more accessible and nostalgia-laden take on the cyberpunk genre. Set in a world where reality is so grim that people escape into the vast virtual reality universe, the story follows Wade Watts on his quest to find an Easter egg hidden by the OASIS’s creator. The book is a love letter to ’80s pop culture. It’s also a stark commentary on how people retreat into virtual worlds to escape the harshness of their actual lives. With the Metaverse becoming more than just a buzzword, Cline’s vision feels less like a futuristic fantasy and more like an impending reality.<br> <br>All of these dystopian tales reflect a world where technology, initially seen as a tool for connection, becomes a means of control. These narratives explore the double-edged sword of technological advancement — the utopian promises of a connected world overshadowed by the dystopian realities of corporate dominance, loss of privacy, and the erosion of genuine human connection.</p><h3>What I’m Listenting To</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fopen.spotify.com%2Fembed%2Ftrack%2F429IbFR4yp2J81CeTwF5iY%3Futm_source%3Doembed&amp;display_name=Spotify&amp;url=https%3A%2F%2Fopen.spotify.com%2Ftrack%2F429IbFR4yp2J81CeTwF5iY&amp;image=https%3A%2F%2Fi.scdn.co%2Fimage%2Fab67616d00001e0295d1d98c5176e4f982bd73d6&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=spotify" width="456" height="152" frameborder="0" scrolling="no"><a href="https://medium.com/media/677e55727dea329a3c3473e0a5f43a99/href">https://medium.com/media/677e55727dea329a3c3473e0a5f43a99/href</a></iframe><p>While reminiscing about Architecture School, I’ve found myself diving back into Jimmy Eat World’s music. This band has been a staple in my music library since my college days, and their blend of emo, punk, and alternative rock never fails to hit the right notes. Their 2001 album, Bleed American is a classic, with tracks like “The Middle” and “Sweetness” delivering that perfect mix of nostalgia and timeless energy.</p><p>Their music has been the perfect backdrop for my work sessions lately. There’s something about their sound that keeps me focused and motivated. There’s a certain comfort in returning to a band that has been a constant through various phases of life. Jimmy Eat World reminds me of the importance of resilience and staying true to oneself, themes that resonate deeply in my personal and professional life.</p><h3>What I’m Playing</h3><p><a href="https://store.playstation.com/en-us/product/UP4497-PPSA03974_00-0000000000000CP1">Cyberpunk 2077</a></p><p>My life has taken on a distinctly neon hue as I’ve been reading cyberpunk novels and immersing myself in the virtual dystopia of Cyberpunk 2077. This role-playing game is set in the dark, grimy, tech-infused world of Night City, where you can hack, shoot, and schmooze your way to… well, something resembling success if you’re lucky.</p><p>When it first launched, the game was notoriously unstable. The release was famously plagued with bugs, glitches, and crashes, drawing the ire of gamers everywhere.</p><p>Many of the most egregious bugs had been ironed out when I played it. Not all, though. It still occasionally crashed, but I enjoyed it so much that I didn’t even mind the interruptions. Each reset was a minor inconvenience during an otherwise thrilling experience.</p><p>The most compelling aspect of games like Cyberpunk 2077 is how they shape themselves around your choices. Every decision you make can ripple through the storyline, creating a bespoke narrative that feels somewhat personal. This is a fun feature unless you already have decision fatigue. When I sit down to play in the evening, my brain is often too exhausted to handle more decision-making.</p><p>Despite my best efforts to forge an epic tale in Night City, my first playthrough ended with a dull, anti-climatic conclusion. While I appreciated the game, the idea of replaying it for a different ending didn’t appeal. My backlog of games is significant, and frankly, I didn’t want to add another repeat experience to the list. So, I accepted my lackluster finale with a resigned sigh and moved on.</p><p>Sometimes, you have to accept the imperfect and keep pushing forward.</p><h3>Conclusion</h3><p>Reflecting on these diverse experiences, from the rigors of architecture school to the digital escapades in Night City, reminds me of the importance of resilience and adaptability. Whether navigating the demands of a studio critique or the challenges of a buggy game, pushing through imperfections and finding joy in the process is critical. As I continue to develop our LMS and dive into new projects, I carry these lessons forward, embracing the struggles and the triumphs with a sense of humor and determination. Until next time, keep pushing the boundaries and finding your rhythm in the chaos.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b8b87b07432" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thoughts of a Recovering Architect #006]]></title>
            <link>https://medium.com/@dan.audette/thoughts-of-a-recovering-architect-006-19f8555736aa?source=rss-1c95003b41d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/19f8555736aa</guid>
            <category><![CDATA[invisible-illness]]></category>
            <category><![CDATA[dynamo]]></category>
            <category><![CDATA[lupus]]></category>
            <category><![CDATA[architecture-school]]></category>
            <category><![CDATA[architecture]]></category>
            <dc:creator><![CDATA[Dan Audette]]></dc:creator>
            <pubDate>Mon, 27 May 2024 17:58:35 GMT</pubDate>
            <atom:updated>2024-06-03T20:17:16.199Z</atom:updated>
            <content:encoded><![CDATA[<p>On working in architecture with an invisible disability, The Stormlight Archives, Reel Big Fish, and God of War. Plus, a Dynamo script for identifying reference callouts.</p><p><strong>Disclaimer:</strong> The views and opinions expressed in this blog post are solely my own and do not necessarily reflect the views or opinions of my current employer. Any criticisms made within this post are not directed towards my current employer but are general observations based on my personal experiences and opinions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fo8KlYf4qRuFP9nxwUaL-Q.png" /></figure><p>I have Lupus. There, I said it. I cannot adequately express how big of a deal it is for me to write this. Revealing my struggle with Lupus is one of the hardest things I’ve ever had to do. This illness has shaped my life in ways that are deeply personal and often misconstrued. You must understand that I wanted no one to know. No one. I didn’t want a reason to be singled out or thought of as different or broken. Being different made you a target, and I learned early to blend into the background, to do nothing that attracted notice for fear of bullying and other unwanted attention.</p><p>I even tried to control my parents from sharing with their friends and neighbors. I was mortified when I learned my parents told the whole neighborhood, and I became furious (roid rage, more on that in a bit). I was not sensitive at all to how my parents needed to process their son developing a chronic condition he’d have for the rest of his life. Didn’t even cross my mind. It was my illness, my information to control.</p><p>But there was no hiding it.</p><p>My life took an unexpected turn at the end of my 8th-grade year. I started running a constant low-grade fever with no clear cause. Countless doctor visits provided no answers until one perceptive pediatrician decided to test for autoimmune diseases. It was this moment of intuition that finally led to my diagnosis.</p><p>My father had rented a bobcat for the weekend to dig out our future swimming pool. He was outside working when my mom received the call from the pediatrician with bloodwork results. I was to rush to Children’s Memorial Hospital in downtown Chicago immediately. My dad had to return the bobcat without being able to use it, needing to dig out the rest of the pool by hand, which was the first of many inconveniences my condition was to cause.</p><p>In the ER, they confirmed the bloodwork and admitted me to the hospital. I had blood and protein in my urine, signaling that something was wrong with my kidneys.</p><p>The next few days were a whirlwind of blood tests, diagnostic imaging, and a kidney biopsy. Stage 4 kidney disease, they said. I was put on steroids and had to start chemotherapy to get my immune system under control. I remember laying in the hospital bed as the doctors explained what these medications would do to me.</p><p>The doctors explained that the steroids would raise my risk of cancer and heart disease, that chemotherapy would take years off of my life, and that there was a chance that I’d be sterilized. I was to consult a sperm bank and make a donation before my first treatment. Despite a small sexual awakening with the release of ‘Hit Me Baby One More Time’ by Britney Spears, I hadn’t managed a purposeful deposit to that point. I had to endure each of my parents clumsily explaining how it was done. They were more concerned about the prospect of no grandchildren than I was about children.</p><p>All of that paled in comparison to the steroid side effects of oddly distributed weight gain and bad acne, at least from the perspective of a teenager.</p><p>Entering High School was supposed to be my chance to remake myself. I quit band, baseball, and soccer, giving up second chair trumpet and a position at first base, all to blend in and not stand out, to let myself define myself rather than the activities I took part in. No one was to know I was sick; I was just another freshman kid.</p><p>But again, there was no hiding it.</p><p>One of the first things any kid said to me was, “What the hell happened to your face?”</p><p>Well, so much for that.</p><p>Back in the hospital, I couldn’t process all I was being told, and I had one concern: being discharged in time for my friend’s birthday party.</p><p>I was determined to attend my friend’s birthday party and act normal. But surrounded by laughter and carefree middle schoolers, I wanted to share my ordeal with my best friend. My attempt to explain my situation amidst the chaos was awkward and isolating. When he blurted out, “Dan is on the ‘roids!” the room’s dynamic shifted, and I retreated into silence.</p><p>Awkward, right? I didn’t do myself any favors. I don’t remember the rest of the party, but I was back in the hospital shortly after; it turns out I should have never been discharged.</p><p>The rest of the summer, we tried to return to normal. I still had some baseball games left before the end of the season, and I remember returning. I got a hit on my first at-bat, but I blacked out and collapsed along the first baseline as I ran to beat the throw. I’d get IV Therapy at home, and my friend would come over to play video games with me. I think this freaked him out, as we drifted apart near after.</p><p>So much for anonymity; you can’t expect middle schoolers to keep these things quiet.</p><p>Lupus is an autoimmune disease where the immune system mistakenly attacks healthy tissues and organs. Imagine your white blood cells becoming overly aggressive and targeting your own body. While Lupus typically affects middle-aged minority women, I was diagnosed as a teenager. There is no cure, but medications can help manage the symptoms and aim for periods of remission.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*42Spfm5rNkLsYc42CCnWBQ.png" /></figure><p>Lupus is considered an invisible disability. This is because many of its symptoms are not readily apparent to outside observers. One of the most annoying symptoms of Lupus is extreme fatigue, which can be debilitating but is not visible to others. Lupus can affect various internal organs, such as the kidneys, heart, lungs, and brain. These complications are not outwardly visible but can significantly impact a person’s health and quality of life. Living with Lupus means dealing with constant, unpredictable symptoms like joint pain, muscle aches, and debilitating headaches. These challenges can flare up suddenly, making it hard for others to understand the daily struggle of managing an invisible illness. Imagine waking up each day unsure of how much energy or pain you must contend with. Lupus can cause mental health issues like depression and anxiety. These symptoms are not visible but can significantly affect a person’s functioning. Due to the invisible nature of many lupus symptoms, people with the condition face disbelief, judgment, or a lack of understanding from others who do not recognize the severity of their disability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xNAFChDN16iFXOm_nXzfYA.png" /></figure><p>The best way I’ve found to explain is using spoon theory. The basic idea is that each person starts the day with a limited number of “spoons,” representing energy units. Every activity, such as getting dressed, preparing a meal, or going to work, costs a certain number of spoons. Once people run out of spoons for the day, they have no more energy to do anything else. For people with chronic illnesses or disabilities, the number of spoons they have each day may be significantly lower than that of a healthy person. They must carefully plan and prioritize their activities to ensure they have enough spoons before the end of the day. This can lead to difficult choices, such as deciding between basic self-care tasks or engaging in social activities. Overextending yourself one day borrows spoons from the next day, which compounds on itself until there’s an opportunity to rest for an extended period.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f3FUr5oe0OX-NCoO9T_8hg.png" /></figure><p>Architecture, as a field, is demanding, and the expectations set within the profession often clash with the realities of living with a chronic illness. Studio culture in architecture schools is notorious for promoting all-nighters as a rite of passage. The idea is that pulling an all-nighter demonstrates dedication and resilience. I attempted one all-nighter and suffered a severe flare-up, realizing that these unrealistic expectations were detrimental to my health.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cMSC8-COAuWUNlsPF_FleQ.png" /></figure><p>In the professional world, the culture is similar. The norm is to work overtime, often without additional pay. Architecture firms frequently make money by underestimating the time required to complete projects and relying on staff to work extra hours to meet deadlines. This disconnect between the proposal writers, who never touch BIM, and the staff executing the projects creates an unhealthy environment. The pressure to work late into the night to finish a project on time is immense.</p><p>Promotions and assignments to high-profile projects are often based on how much overtime you work. It’s seen as a measure of your dedication to the ‘art’ of architecture. This unspoken rule is discriminatory against people with disabilities. The expectation is that you must sacrifice your health and personal life for your career. It’s a toxic culture that punishes those who cannot keep up with these unrealistic demands.</p><p>Effective time management is not just a preference; it’s a necessity. Despite finishing my work within regular hours, I have been guilted into staying late to help others and to be a ‘team player.’ I was essentially punished for knowing how to manage my time and tasks efficiently.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2urwnTI0XNIYSUfynTfmsg.png" /></figure><p>The truth is, I cannot put undue stress on my body. It’s not a matter of dedication; it’s a matter of survival. I’ve learned to manage my time meticulously to protect my health. Yet, this culture makes me feel like I’m constantly fighting an uphill battle.</p><p>Some might say I chose the wrong profession and should switch careers to something more accommodating. But this viewpoint ignores the broader issue. It’s not about me fitting into an unhealthy culture; it’s about recognizing that the culture itself needs to change.</p><p>Architecture as a profession needs to become more inclusive and empathetic. Firms should recognize that their employees have different needs and limitations. This means reevaluating how we measure dedication and success. It means fostering an environment where taking care of your health is not seen as a weakness but as a responsible and necessary practice.</p><p>We must move away from the toxic mentality glorifying overwork and burnout. Instead, we should promote a culture of balance, well-being, and sustainable working practices. Doing so can create a more inclusive profession that allows everyone to thrive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6fXgra0pczPjocL1yUHyXg.png" /></figure><p>So, to those who might judge or dismiss someone because they can’t pull an all-nighter or work overtime, I say: Be kind. Be empathetic. You never know who is fighting an invisible battle. Let’s work towards a profession that values health and well-being just as much as creativity and dedication.</p><h3>What I’m Working On</h3><h4>Color Reference Callouts with Dynamo</h4><p>This Dynamo script enhances visibility and organization in Revit projects by targeting reference callouts. Its primary function is automatically identifying all reference callouts within a Revit file and changing their color. This color modification significantly improves the ease of identifying and differentiating these callouts amidst complex architectural drawings. Ideal for large-scale and detailed projects, the script aids in quickly locating reference points, ensuring a more efficient review and editing process. Streamlining the visualization of reference callouts enhances overall workflow efficiency and accuracy in design documentation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t0ZIdRvd6pkIFpORiJPa8Q.png" /></figure><p><strong>Callout Collector Python Node Code</strong></p><pre>import sys<br>import clr<br>clr.AddReference(&#39;ProtoGeometry&#39;)<br>from Autodesk.DesignScript.Geometry import *<br><br>clr.AddReference(&#39;RevitAPI&#39;)<br>from Autodesk.Revit.DB import *<br><br>clr.AddReference(&quot;RevitNodes&quot;)<br>import Revit<br>clr.ImportExtensions(Revit.Elements)<br><br>clr.AddReference(&quot;RevitServices&quot;)<br>import RevitServices<br>from RevitServices.Persistence import DocumentManager<br>from RevitServices.Transactions import TransactionManager<br><br>doc = DocumentManager.Instance.CurrentDBDocument<br><br># The inputs to this node will be stored as a list in the IN variables.<br>dataEnteringNode = IN<br><br># Place your code below this line<br>calloutList = FilteredElementCollector(doc).OfCategory(BuiltInCategory.OST_Viewers).WhereElementIsNotElementType().ToElements()<br># Assign your output to the OUT variable.<br>OUT = calloutList</pre><p><strong>Callout Colorer Python Node Code</strong></p><pre>import clr<br>clr.AddReference(&#39;ProtoGeometry&#39;)<br>from Autodesk.DesignScript.Geometry import *<br><br>clr.AddReference(&#39;RevitAPI&#39;)<br>from Autodesk.Revit.DB import *<br><br>clr.AddReference(&quot;RevitNodes&quot;)<br>import Revit<br>clr.ImportExtensions(Revit.Elements)<br><br>clr.AddReference(&quot;RevitServices&quot;)<br>import RevitServices<br>from RevitServices.Persistence import DocumentManager<br>from RevitServices.Transactions import TransactionManager<br><br>doc = DocumentManager.Instance.CurrentDBDocument<br><br>view = UnwrapElement(IN[0])<br>element = UnwrapElement(IN[1])<br>#override = IN[2]<br><br>colorId = Color(255, 0, 255)<br>oSettings = OverrideGraphicSettings()<br>oSettings.SetProjectionLineColor(colorId)<br><br>result = []<br>count = 0<br><br>TransactionManager.Instance.EnsureInTransaction(doc)<br>#while (count &lt; len(override)):<br>for i in view:<br> try:<br>  i.SetElementOverrides(element[count].Id, oSettings)<br>  result.append(&quot;Success&quot;)<br>  count<br>  count = count + 1<br> except:<br>  i.SetElementOverrides(element[count].Id, oSettings)<br>  result.append(&quot;Success&quot;)<br><br>TransactionManager.Instance.TransactionTaskDone()<br><br><br>OUT = result</pre><h3>What I’m Reading</h3><p><a href="https://a.co/d/htZ8677">The Way of Kings: Book One of the Stormlight Archive (The Stormlight Archive, 1)</a></p><p>Lately, I’ve been diving into several books that resonate deeply with my journey of managing Lupus and navigating the challenges of life and career. One series that stands out is “The Stormlight Archives” by Brandon Sanderson. It is a captivating series that parallels my battles with its themes of perseverance, resilience, and the struggle against overwhelming odds. The characters’ journeys in facing inner demons and external challenges resonate with my experiences managing Lupus and striving to live a fulfilling life.</p><h3>What I’m Listening To</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fopen.spotify.com%2Fembed%2Ftrack%2F7qEm8Z4KFLdCMlv96KykVd%3Futm_source%3Doembed&amp;display_name=Spotify&amp;url=https%3A%2F%2Fopen.spotify.com%2Ftrack%2F7qEm8Z4KFLdCMlv96KykVd&amp;image=https%3A%2F%2Fi.scdn.co%2Fimage%2Fab67616d00001e02ef883c94c02915cacc3b5b36&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=spotify" width="456" height="152" frameborder="0" scrolling="no"><a href="https://medium.com/media/f72572546b335ad40abe8e50abf97d32/href">https://medium.com/media/f72572546b335ad40abe8e50abf97d32/href</a></iframe><p>Music has recently been a refuge for me, especially during tough times. Lately, I’ve listened to various genres reflecting my journey and experiences. With its upbeat and lively rhythms, Ska provides a much-needed boost of energy and positivity. Bands like The Specials and Reel Big Fish bring joy and lightness, reminding me to find moments of happiness and levity amidst the struggles. Ska’s infectious beats and brass sections serve as a reminder to keep moving forward and to celebrate small victories.</p><h3>What I’m Playing</h3><p><a href="https://store.playstation.com/en-us/product/UP9000-CUSA07408_00-00000000GODOFWAR">God of War</a></p><p>I’ve been exploring various video games that resonate with my journey and experiences in my downtime. One game that stands out is “God of War.” This game provides a powerful narrative about fatherhood, perseverance, and the struggle against impossible odds. Kratos’ journey with his son, Atreus, and their battles against gods and monsters parallel my experiences of pushing through the difficulties posed by Lupus, striving to be a supportive and understanding parent, and fighting to maintain a semblance of normalcy despite the challenges. “God of War” offers a form of escapism and also reflects the real-life battles and triumphs I experience daily. They remind me that while the journey may be challenging, resilience, adaptability, and determination can help overcome even the most formidable obstacles.</p><h3>Conclusion</h3><p>Living with Lupus has taught me that true strength lies in resilience and adaptability. Despite the numerous challenges, from severe medical treatments to navigating a demanding profession, I have learned to manage my condition with determination and careful planning. This journey has underscored the importance of empathy and understanding in all aspects of life, especially in the workplace.</p><p>The architecture industry, like many others, often values overwork and long hours, creating a toxic environment for those with chronic illnesses. It’s essential to recognize that promoting a healthier work culture benefits everyone. By fostering balance and prioritizing well-being, we can create a more inclusive profession that allows all individuals to thrive, regardless of their health conditions.</p><p>To my colleagues and peers, I urge you to consider the unseen daily battles that many of us face. Let’s move away from outdated norms that equate dedication with exhaustion. Instead, let’s build a supportive environment that values health, encourages sustainable practices, and recognizes the diverse needs of all team members.</p><p>Ultimately, it’s not just about accommodating those with chronic illnesses; it’s about transforming our workplaces into spaces where everyone can perform at their best without sacrificing their health. By working together, we can cultivate a profession that truly values creativity, dedication, and, most importantly, well-being.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19f8555736aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>