<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://bridgetownrb.com/" version="2.2.0">Bridgetown</generator><link href="https://www.beflagrant.com/feed.xml" rel="self" type="application/atom+xml" /><link href="https://www.beflagrant.com/" rel="alternate" type="text/html" /><updated>2026-11-15T05:07:37-06:00</updated><id>https://www.beflagrant.com/feed.xml</id><title type="html">Flagrant</title><entry><title type="html">Let me introduce you (after I ask)</title><link href="https://www.beflagrant.com/blog/let-me-introduce-you-after-i-ask-2026-11-10" rel="alternate" type="text/html" title="Let me introduce you (after I ask)" /><published>2026-11-10T04:41:00-06:00</published><updated>2026-11-10T04:41:00-06:00</updated><id>repo://posts.collection/_posts/let-me-introduce-you-after-i-ask-2026-11-10.md</id><content type="html" xml:base="https://www.beflagrant.com/blog/let-me-introduce-you-after-i-ask-2026-11-10">&lt;p&gt;On a Friday call, two founders told me about the app they’re considering building. Along the way they mentioned they needed a lawyer, specifically someone with experience drafting contracts for content creators.&lt;/p&gt;

&lt;p&gt;I told them I thought I knew someone and that I’d check whether it was a fit. That was their opt-in. They’d asked me, and now I was going to ask the other side.&lt;/p&gt;

&lt;p&gt;The someone was Gabe Levine. I’ve worked with Gabe since 2011. In our first contract negotiation he caught a clause that never should have been there, and he’s been my lawyer ever since. Before I put him in front of anyone, though, I wrote to him with the shape of the request:&lt;/p&gt;

&lt;blockquote&gt;
  &lt;p&gt;“I have a request from a potential client. They are looking for someone with experience drafting contracts for content creators. They are very early in the process … If it’s a fit, great! If it’s not a fit. No sweat. If you know of other folks who would be a better fit, let me know.”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Gabe didn’t say yes right away. He asked a question first: “To be clear, this is for a lawyer to work with the product/app company to draft contracts between them and content creators?” I wrote back, “That’s correct!” and once that was settled, I made the introduction.&lt;/p&gt;

&lt;p&gt;I love that question. Gabe got to find out exactly what he’d be signing up for while it was still just the two of us talking. If the answer had changed his mind, he could have told me so, and the founders would never have been left waiting on a reply that wasn’t coming.&lt;/p&gt;

&lt;p&gt;The introduction itself opened like this: “As I mentioned on our call on Friday I always try to do double opt-in introductions to avoid burdening either side with contact that can’t work.” Then I told them who Gabe is to me: “Meet, Gabe Levine of Matchstick Legal. He’s based in Northern California and there is nobody I trust more in the realm of contracts than him.” And then I got out of the way: “I mentioned in &lt;em&gt;my words&lt;/em&gt; what you’re looking to build and what I understand your needs to be but it would probably be best for you all to discuss on a quick call.”&lt;/p&gt;

&lt;p&gt;Almost every introduction I make works this way. Before I connect two people, each of them knows what’s being asked and gets a real chance to say whether it fits. The founders heard that I thought I knew someone and would check first. Gabe heard “If it’s not a fit. No sweat.” I didn’t promise the founders a lawyer, and I didn’t promise Gabe a client. Neither one’s time matters more than the other’s, so they both get the same ask.&lt;/p&gt;

&lt;p&gt;The same day I sent that introduction, I saw it from the other side. An agency emailed me looking for Rails help with Solidus experience. Someone I know had passed my name along without checking with me first, which is fine; we know each other well. Before I replied, I talked with Jared Norman of Super Good Software about his availability. The next day I wrote back that we could help, and honestly it “would help us to close out the year.” Then I introduced Jared and his team instead: “They are Solidus experts and good at what they do.” Jared wrote back that evening and moved me to BCC.&lt;/p&gt;

&lt;p&gt;There’s a little bit of judgement involved in knowing when a quick intro is welcome, especially when I know both sides well or know more about their circumstances, and some people have told me I can always make a certain kind of intro. From time to time, one side says no, and when that happens I usually leave the request open so I can ask someone else, or I tell the person who asked that it isn’t a fit this time, without passing along the why.&lt;/p&gt;

&lt;p&gt;In my experience, the person asking for an intro is often assumed to be a yes, and all the care goes to the busier side. I’d rather both sides get the same care, and that matters most for whoever has the least pull. &lt;a href=&quot;https://www.xoruby.com/blog/why-i-am-taking-events-on-the-road-this-fall/&quot;&gt;I last interviewed for a job in 2007&lt;/a&gt;, and “each new opportunity in my career has come through my network.” I know not everyone has a network like that, and when you’re the one asking, &lt;em&gt;let me check first&lt;/em&gt; can sound like a door closing. I hope it reads the other way. Asking first is how I make sure that when the person on the other end says yes, it’s because they want to help, and that nobody ends up stuck in a thread they didn’t ask for.&lt;/p&gt;

&lt;p&gt;Connections like that are a big part of what XO Ruby is for. &lt;a href=&quot;https://www.xoruby.com/blog/why-i-am-taking-events-on-the-road-this-fall/&quot;&gt;As I wrote about San Francisco&lt;/a&gt;, “I’d inevitably end up introducing two locals who lived in the same city but had never crossed paths until a visiting friend gave them both a reason to show up somewhere.” Double opt-in is how I try to do that one email at a time.&lt;/p&gt;

&lt;p&gt;So if there’s someone you’d like to meet, tell me what you’re looking for. I’ll ask them the same way I asked Gabe. And if you’re ever the one getting that email from me, you can tell me it’s not a fit, no sweat.&lt;/p&gt;</content><author><name>Jim Remsik</name></author><category term="[&quot;consulting&quot;]" /><category term="Double Opt In" /><category term="Networking" /><category term="Making Introductions" /><category term="Relationship Building" /><category term="Trust" /><category term="Community Building" /><category term="Referrals" /><category term="XO Ruby" /><category term="Thoughtful Networking" /><category term="Consent Based Networking" /></entry><entry><title type="html">Delightfully Friday Junior: Font or Cheese?</title><link href="https://www.beflagrant.com/blog/font-or-cheese" rel="alternate" type="text/html" title="Delightfully Friday Junior: Font or Cheese?" /><published>2026-11-02T05:50:00-06:00</published><updated>2026-11-02T05:50:00-06:00</updated><id>repo://posts.collection/_posts/delightfully-friday-junior-font-or-cheese-2026-11-02.md</id><content type="html" xml:base="https://www.beflagrant.com/blog/font-or-cheese">&lt;p&gt;By now you’re familiar with &lt;a href=&quot;https://www.beflagrant.com/blog/introducing-delightfully-friday-junior-at-flagrant-2025-10-10&quot;&gt;Delightfully Friday Junior&lt;/a&gt;—our weekly team activity to build camaraderie and have a bit of fun.&lt;/p&gt;

&lt;p&gt;I was feeling inspired, having recently attended a local screening of &lt;a href=&quot;https://www.youtube.com/watch?v=2k9gZuxN1Js&quot;&gt;The Big Cheese&lt;/a&gt;, a documentary about American cheese mongers competing against France in “the Olympics of Cheese.”&lt;/p&gt;

&lt;p&gt;With some fancy cheese in my fridge and a voracious appetite for more, I thought…what better activity to facilitate than a few rounds of that classic game, Font or Cheese?&lt;/p&gt;

&lt;p&gt;You can play along at home! For each of the names below, do you think it’s the name of a font or a cheese? Record your answers, then scroll down for the key and determine your score.&lt;/p&gt;

&lt;h2 id=&quot;font-or-cheese&quot;&gt;Font or cheese?&lt;/h2&gt;

&lt;ol&gt;
  &lt;li&gt;Clarendon&lt;/li&gt;
  &lt;li&gt;Castelmagno&lt;/li&gt;
  &lt;li&gt;Barmeno&lt;/li&gt;
  &lt;li&gt;Picodon&lt;/li&gt;
  &lt;li&gt;Cathelain&lt;/li&gt;
  &lt;li&gt;Raumsonde&lt;/li&gt;
  &lt;li&gt;Cretino&lt;/li&gt;
  &lt;li&gt;Patzcuaro&lt;/li&gt;
  &lt;li&gt;Gjetost&lt;/li&gt;
  &lt;li&gt;Svecia&lt;/li&gt;
  &lt;li&gt;Gonzaga&lt;/li&gt;
  &lt;li&gt;Olimpico&lt;/li&gt;
  &lt;li&gt;Piora&lt;/li&gt;
  &lt;li&gt;Rudelsberg&lt;/li&gt;
  &lt;li&gt;Crescenza&lt;/li&gt;
  &lt;li&gt;Kacst&lt;/li&gt;
  &lt;li&gt;Bembo&lt;/li&gt;
  &lt;li&gt;Kaiser&lt;/li&gt;
  &lt;li&gt;Canora&lt;/li&gt;
  &lt;li&gt;Coulommiers&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Some of these I found in &lt;a href=&quot;https://www.figma.com/design/7CJCwIgOIm033lxNuedAL6/%F0%9F%A7%80%F0%9F%88%AF%EF%B8%8F-Cheese-or-Font---Community-?m=auto&amp;amp;t=4si3ahfVHjUmrXX2-6&quot;&gt;a list someone had already assembled (thanks!)&lt;/a&gt;, but some I added on my own. Something about the “-berg” ending (probably because of Jarlsberg cheese) sounds like cheese to me! But no, Rudelsberg is the name of a cheese!&lt;br /&gt;
&lt;br /&gt;
Picodon makes me think of fonts because “pica” is a unit of typographic measurement. And Olimpico IS a font! But Picodon is one I added in to throw of my design-minded coworkers—it’s actually a delicious regional cheese from France that is soft and a little stinky.&lt;/p&gt;

&lt;p&gt;“Gonzaga” reads a little like “Gorgonzola,” another delicious cheese. But it’s a fake-out! Gonzaga is a font.&lt;/p&gt;

&lt;p&gt;Other “hmm, sounds like…” traps await in the list I created. Proceed to check your answers below.&lt;/p&gt;

&lt;h3 id=&quot;answer-key&quot;&gt;Answer Key&lt;/h3&gt;

&lt;ol&gt;
  &lt;li&gt;Clarendon - Font&lt;/li&gt;
  &lt;li&gt;Castelmagno - Cheese&lt;/li&gt;
  &lt;li&gt;Barmeno - Cheese&lt;/li&gt;
  &lt;li&gt;Picodon - Cheese&lt;/li&gt;
  &lt;li&gt;Cathelain - Cheese&lt;/li&gt;
  &lt;li&gt;Raumsonde - Font&lt;/li&gt;
  &lt;li&gt;Cretino - Font&lt;/li&gt;
  &lt;li&gt;Patzcuaro - Font&lt;/li&gt;
  &lt;li&gt;Gjetost - Cheese&lt;/li&gt;
  &lt;li&gt;Svecia - Cheese&lt;/li&gt;
  &lt;li&gt;Gonzaga - Font&lt;/li&gt;
  &lt;li&gt;Olimpico - Font&lt;/li&gt;
  &lt;li&gt;Piora - Cheese&lt;/li&gt;
  &lt;li&gt;Rudelsberg - Font&lt;/li&gt;
  &lt;li&gt;Crescenza - Cheese&lt;/li&gt;
  &lt;li&gt;Kacst - Font&lt;/li&gt;
  &lt;li&gt;Bembo - Font&lt;/li&gt;
  &lt;li&gt;Kaiser - Font&lt;/li&gt;
  &lt;li&gt;Canora - Font&lt;/li&gt;
  &lt;li&gt;Coulommiers - Cheese&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;How’d you do?&lt;/p&gt;</content><author><name>Glynnis Ritchie</name></author><category term="[&quot;consulting&quot;, &quot;design&quot;]" /><category term="Delightfully Friday Junior" /><category term="Fonts" /><category term="" /></entry><entry><title type="html">Telling Stories With Telestrastions</title><link href="https://www.beflagrant.com/blog/telling-stories-with-telestrastions-2026-10-23" rel="alternate" type="text/html" title="Telling Stories With Telestrastions" /><published>2026-10-23T09:38:00-05:00</published><updated>2026-10-23T09:38:00-05:00</updated><id>repo://posts.collection/_posts/telling-stories-with-telestrastions-2026-10-23.md</id><content type="html" xml:base="https://www.beflagrant.com/blog/telling-stories-with-telestrastions-2026-10-23">&lt;p&gt;Everyone loves stories. Stories bring us together. They help us find our common ground and give us windows into each other’s world. Stories define who we are, where we come from and where we are headed. They show us how much we have in common while highlighting our personal gifts and quirks.&lt;/p&gt;

&lt;p&gt;In this new age of endless screens and boundless AI slop it is even more important that we create and share stories together as humans. Here at Flagrant we make sure to carve out regular time to do something creative and fun together. Since we are a remote team the goal is to find simple but effective ways to reach through the technological interface to reclaim our human connection.&lt;/p&gt;

&lt;p&gt;A couple of weeks ago I came up with an online version of one of our favorite party games that we once played in person at a retreat called &lt;a href=&quot;https://www.amazon.com/dp/B001SN8GF4?lv=shuf&amp;amp;channelId=500&amp;amp;plpRedirect=mhFallback&quot;&gt;Telestrations&lt;/a&gt;. The game is a cross between Pictionary and Broken Telephone. Everyone starts by writing down a phrase which gets passed around and everyone alternates between drawing the caption and writing down what you think the previous drawing represents.&lt;/p&gt;

&lt;p&gt;While this is certainly most fun in person, I found a &lt;a href=&quot;https://www.figma.com/board/EwSkRxOSGbE2yEWbwjAAMS/Telephone-Pictionary--Community-?node-id=0-1&amp;amp;t=E5dfsa0LhjynnMKI-0&quot;&gt;Figjam template&lt;/a&gt; that worked pretty well over a video call. By duplicating the column to match the number of participants and pairing the length to match we had just what we needed to do a full round. Note that it is critical to remind everyone to hide the content using the closed eye icon when moving to the next column.&lt;/p&gt;

&lt;p&gt;The round ends when the stacks make it around back to where they started and that is when the real fun begins. Now each person gets to tell the story of how their original prompt changed as it got passed around the room. Sometimes the storyline is preserved:&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/images/uploads/screenshot-2026-10-23-at-9.47.56 am.png&quot; alt=&quot;Telestrations with storyline preserved&quot; title=&quot;Telestrations Storyline Preserved&quot; /&gt;&lt;/p&gt;

&lt;p&gt;And sometimes it gets transformed into something imaginatively unimaginable:&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/images/uploads/screenshot-2026-10-23-at-8.55.34 am.png&quot; alt=&quot;Telestration with imaginative evolution&quot; title=&quot;Imaginative Telestration&quot; /&gt;&lt;/p&gt;

&lt;p&gt;And, best of all, sometimes you open up associative stories that uncover hidden details about the people you work with:&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/images/uploads/screenshot-2026-10-23-at-8.55.54 am.png&quot; alt=&quot;Telestrations with a hidden story&quot; title=&quot;Hidden Story Telestration&quot; /&gt;&lt;/p&gt;

&lt;p&gt;It turns out that Jim’s mother and many of his family members worked at Oscar Mayer in Madison, WI. One time they opened the plant for a Family Day so people could bring their loved ones to work and see how the sausage was made.&lt;/p&gt;

&lt;p&gt;As a part of that experience they brought ~3-4 Weinermobiles and you could get inside and have a ride around the parking lot in them. If you give the logistics of the vehicle a little thought you’ll quickly come to the realization that there is not much space inside them. There are two side-by-side seats up from and the rest is like a narrow carpeted cargo van.&lt;/p&gt;

&lt;p&gt;He was probably about 12 years old at the time and stuck his head out the door and a couple of people remarked he looked like little Oscar:&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/images/uploads/5b2d7a712dd8b.image.webp&quot; alt=&quot;Little Oscar&quot; title=&quot;Little Oscar&quot; /&gt;&lt;/p&gt;

&lt;p&gt;Try out telestrations at your next work or social event and let us know how it goes. Please also share your favorite parlor games and especially ones that you have adapted for remote work. We are always looking for fun ways to connect and learn more about each other and ourselves.&lt;/p&gt;</content><author><name>Jonathan Greenberg</name></author><category term="[&quot;consulting&quot;]" /><category term="DelightfullyFridayJunior" /><category term="ConsultingLife" /><category term="TeamBuilding" /><category term="FlagrantLife" /><category term="RemoteWork" /><category term="Stories" /><category term="Play" /></entry><entry><title type="html">Delightfully Friday Junior: Magnet Poems</title><link href="https://www.beflagrant.com/blog/delightfully-friday-junior-magnet-poems-2026-09-22" rel="alternate" type="text/html" title="Delightfully Friday Junior: Magnet Poems" /><published>2026-09-22T04:45:00-05:00</published><updated>2026-09-22T04:45:00-05:00</updated><id>repo://posts.collection/_posts/delightfully-friday-junior-magnet-poems-2026-09-22.md</id><content type="html" xml:base="https://www.beflagrant.com/blog/delightfully-friday-junior-magnet-poems-2026-09-22">&lt;p&gt;Remember when fridges used to be decorated with so many individual word magnets? You would go to someones house and find these words on their fridge as you were walking by. Creativity would strike and you would find yourself stringing together these words into funny sentences about toilets or philosophical word jumbles. It was fun and you felt like a sneaky poet dropping lines on unsuspecting hosts.&lt;/p&gt;

&lt;p&gt;Well, for this Delightfully Friday Junior, we brought the past back and channeled our inner writer by creating magnet poems.&lt;/p&gt;

&lt;p&gt;Figma has a really cool plugin that gives you some pre-written magnets of individual words. You can edit the words however you want or turn them into emojis as well. So we used that plug in and had a fun time. Here is one someone wrote about their daughter who is a toddler:&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/images/uploads/screenshot-2026-09-22-at-11.30.13 am.png&quot; alt=&quot;Magnet poem about daughter&quot; title=&quot;Magnet poem about daughter&quot; /&gt;&lt;/p&gt;

&lt;p&gt;Here is one that was written and gets you thinking:&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/images/uploads/screenshot-2026-09-22-at-9.25.40 am.png&quot; alt=&quot;Magnet poem created about a dream&quot; title=&quot;I&apos;ll have a dream&quot; /&gt;&lt;/p&gt;

&lt;p&gt;And we seemed to have a strong milk theme in a few of them. That could be caused by having a few members of the team living in Wisconsin. For those of you that don’t know, Wisconsin is the dairy state so cheese, ice cream and milk are abundant.&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/images/uploads/screenshot-2026-09-22-at-9.27.57 am.png&quot; alt=&quot;Magnet poem about milk&quot; title=&quot;Magnet poem about milk&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/images/uploads/screenshot-2026-09-22-at-9.28.32 am.png&quot; alt=&quot;Magnet poem about milk tasting funny&quot; title=&quot;Magnet poem about milk tasting funny&quot; /&gt;&lt;/p&gt;

&lt;p&gt;Group activities like this help reduce burnout, build deeper relationships between team members, allows us to practice sharing with a larger group and get comfortable with using Figma. Plus it’s fun and you don’t realize in the moment you are “working.”&lt;/p&gt;</content><author><name>Amanda Klusmeyer</name></author><category term="[&quot;consulting&quot;]" /><category term="ConsultingLife" /><category term="ProblemSolving" /><category term="Work" /><category term="Culture" /><category term="Leadership" /></entry><entry><title type="html">Delightfully Friday Junior: Pick Three</title><link href="https://www.beflagrant.com/blog/delightfully-friday-junior-pick-three-2026-08-27" rel="alternate" type="text/html" title="Delightfully Friday Junior: Pick Three" /><published>2026-08-27T06:41:00-05:00</published><updated>2026-08-27T06:41:00-05:00</updated><id>repo://posts.collection/_posts/delightfully-friday-junior-pick-three-2026-08-27.md</id><content type="html" xml:base="https://www.beflagrant.com/blog/delightfully-friday-junior-pick-three-2026-08-27">&lt;h2 id=&quot;survival-shows-arent-really-about-surviving-the-environment-is-backdrop&quot;&gt;Survival shows aren’t really about surviving. The environment is backdrop.&lt;/h2&gt;

&lt;p&gt;What keeps you watching are the people — how they think under pressure, what they reach for first, who holds together and who doesn’t.&lt;/p&gt;

&lt;p&gt;I tested that theory on our team. Split them into two groups, handed each a picture bank of survival gear — an axe, rope, a pot, fishing net, tarps, a lighter, seeds, a bow and arrow — and gave them a single prompt: You’re stranded on a deserted island. You can take three items. You have ten minutes, and the group has to agree.&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/images/uploads/figma_08-27-2026-11.36am.jpeg&quot; alt=&quot;The exercise prompt slide showing fifteen survival items arranged in three rows on a white background. The prompt reads: &amp;quot;You are all stranded on a desert island, and may choose only three of the following objects to survive.&amp;quot; Items shown include two bottles of lamp oil, a first aid kit, a seed sack, a multi-tool, a lighter, a coil of rope, a blue tarp, an axe, a shovel, a fishing net, a bowl of salt, a compass, a bucket, a compound bow and arrows, a large stock pot, and sunblock.&quot; title=&quot;The survival objects&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;

&lt;h3 id=&quot;both-teams-came-back-with-the-pot-that-one-was-unanimous--boiling-water-cooking-carrying-things-hard-to-argue-with&quot;&gt;Both teams came back with the pot. That one was unanimous — boiling water, cooking, carrying things. Hard to argue with.&lt;/h3&gt;

&lt;p&gt;&lt;br /&gt;&lt;/p&gt;

&lt;p&gt;Where they split was more interesting. Team one took the fishing net and the lighter. Team two took the tarp and the bow and arrow. On the surface, different calls. But what came out in the explanation was that each team had pushed their items past their obvious use. Team one’s net wasn’t just for fishing — it was for hauling whatever the shoreline gave them, assuming the island would do some of the work. The lighter was a second anchor: fire for water, fire for food, confidence that fish are abundant near an island. Team two dismantled the tarp entirely in their thinking — shelter, yes, but also material for a net, rope, a carrier. The bow wasn’t just for game. The arrowheads were tools.
&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/images/uploads/figma_08-27-2026-11.58am.jpeg&quot; alt=&quot;Two island examples with three objects selected. Team one had a pot, net and a lighter. Team two has a tarp, pot and bow and arrow.&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;br /&gt;&lt;/p&gt;

&lt;h3 id=&quot;same-prompt-same-ten-minutes-different-mental-models-of-the-environment-and-every-decision-flowed-from-there&quot;&gt;Same prompt. Same ten minutes. Different mental models of the environment, and every decision flowed from there.&lt;/h3&gt;

&lt;p&gt;&lt;br /&gt;&lt;/p&gt;

&lt;p&gt;That’s the part of survival shows I actually find compelling. Not the environment — the psychology. How people think through a problem they’ve never faced. What they prioritize when they can’t have everything. How they negotiate when the stakes feel real. Whether they stay coherent as a team or start pulling in different directions. That’s what makes me come back to the next episode.&lt;/p&gt;

&lt;p&gt;Work isn’t a desert island. But the skills are the same ones: knowing what tools you actually have, understanding how to push them past their obvious use, making a call when there’s no clean answer, staying functional as a team when the pressure is real. Those aren’t things you figure out once. You develop them across projects, across clients, across the moments where the plan stops working and you have to decide what to do next.&lt;/p&gt;

&lt;p&gt;The teams weren’t wrong about their items. They were operating from different assumptions about their environment — and those assumptions shaped every decision that followed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;That’s true of most of the work we do.&lt;/strong&gt;&lt;/p&gt;</content><author><name>Kelly Rauwerdink</name></author><category term="[&quot;consulting&quot;]" /><category term="ConsultingLife" /><category term="ProblemSolving" /><category term="WorkCulture" /><category term="Leadership" /></entry><entry><title type="html">Delightfully Friday Junior: Sentiment Sliders?</title><link href="https://www.beflagrant.com/blog/delightfully-friday-junior-sentiment-sliders" rel="alternate" type="text/html" title="Delightfully Friday Junior: Sentiment Sliders?" /><published>2026-08-24T09:17:00-05:00</published><updated>2026-08-24T09:17:00-05:00</updated><id>repo://posts.collection/_posts/delightfully-friday-junior-sentiment-sliders-2026-08-18.md</id><content type="html" xml:base="https://www.beflagrant.com/blog/delightfully-friday-junior-sentiment-sliders">&lt;p&gt;Delightfully Friday Junior came back for me, and this time &lt;a href=&quot;https://www.beflagrant.com/blog/delightfully-friday-junior-tier-list-edition&quot;&gt;it wasn’t my first rodeo&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;(Psst. Are you new here? Do you not know about Delightfully Friday Junior? &lt;a href=&quot;https://www.beflagrant.com/blog/introducing-delightfully-friday-junior-at-flagrant-2025-10-10&quot;&gt;Let’s fix that.&lt;/a&gt;)&lt;/p&gt;

&lt;p&gt;I did some digging around to search for an activity, and nothing really called to me. Then I considered that &lt;a href=&quot;https://www.beflagrant.com/blog/delightfully-friday-junior-this-or-that-2025-10-22&quot;&gt;we’ve done “This or That”&lt;/a&gt; and I didn’t want to repeat it. But what about a twist on it? What about “This to That”? Is that a thing? Maybe it is now!&lt;/p&gt;

&lt;p&gt;So I put together some things that would work for “this to that”, and honestly some things that don’t really — because what is more fun and interesting than poking at the edges and seeing where something breaks down, and talking about it?&lt;/p&gt;

&lt;p&gt;For instance, where do you fall on the Tent ↔ Hotel spectrum?&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/images/uploads/test-hotel.png&quot; alt=&quot;&quot; /&gt;&lt;/p&gt;

&lt;p&gt;What about Barefoot ↔ Boots?&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/images/uploads/barefoot-boots.png&quot; alt=&quot;&quot; /&gt;&lt;/p&gt;

&lt;p&gt;Or Duck ↔ Swan?&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/images/uploads/duck-swan.png&quot; alt=&quot;&quot; /&gt;&lt;/p&gt;

&lt;p&gt;Yes, a goose is half-way between duck and swan. And also off to the side. And exploding. I don’t make the rules.&lt;/p&gt;

&lt;p&gt;We didn’t talk about it during DFJr. itself, but this is somewhat reminiscent of &lt;a href=&quot;https://longwave.web.app/&quot;&gt;Longwave&lt;/a&gt;, the on-line &lt;a href=&quot;https://boardgamegeek.com/boardgame/262543/wavelength&quot;&gt;Wavelength&lt;/a&gt; adaptation we sometimes play during our monthly &lt;a href=&quot;https://www.beflagrant.com/culture/&quot;&gt;Recharge&lt;/a&gt;.&lt;/p&gt;</content><author><name>Yossef Mendelssohn</name></author><category term="[&quot;consulting&quot;]" /><category term="DelightfullyFridayJunior" /><category term="ThisToThat" /><category term="Choices" /><category term="Sentiment" /><category term="TeamBuilding" /><category term="FlagrantLife" /></entry><entry><title type="html">Developer Round Table - Testing API Calls</title><link href="https://www.beflagrant.com/blog/developer-round-table-testing-api-calls-2026-08-20" rel="alternate" type="text/html" title="Developer Round Table - Testing API Calls" /><published>2026-08-20T01:17:00-05:00</published><updated>2026-08-20T01:17:00-05:00</updated><id>repo://posts.collection/_posts/developer-round-table-testing-api-calls-2026-08-20.md</id><content type="html" xml:base="https://www.beflagrant.com/blog/developer-round-table-testing-api-calls-2026-08-20">&lt;p&gt;This week during our Developer Round Table, Yossef shared some information with the group about API development he’d been doing recently for a client, along with some of the different tools a developer has available for testing an API and showcasing that testing to a client. He walked through &lt;a href=&quot;https://curl.se/&quot;&gt;curl&lt;/a&gt;, &lt;a href=&quot;https://httpie.io/cli&quot;&gt;httpie&lt;/a&gt;, and &lt;a href=&quot;https://github.com/paxtonhare/demo-magic&quot;&gt;Demo Magic&lt;/a&gt; (including his own wrapper around Demo Magic), based on real examples from the work he did.&lt;/p&gt;

&lt;p&gt;When working with APIs, it’s important to be able to test the response to make sure the calls you’re making, and the data you’re retrieving, are what you want and need.&lt;/p&gt;

&lt;p&gt;For example, if you have an application that displays the current weather in a specific location, you need to know that the call to that API is performing as expected and returning the data that you would like. Things like, temperature, location, time, humidity and rain probability percentage. To test this, you have a few different options available.&lt;/p&gt;

&lt;h2 id=&quot;curl&quot;&gt;Curl&lt;/h2&gt;

&lt;p&gt;Curl is a command-line tool used to transfer data to or from a server. It works from any terminal and requires no install of a GUI app to test APIs. Within your command line, you can enter a command like the one below.&lt;/p&gt;

&lt;div class=&quot;highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;curl &quot;https://api.open-meteo.com/v1/forecast?latitude=43.0731&amp;amp;longitude=-89.4012&amp;amp;current=temperature_2m,relative_humidity_2m,precipitation&amp;amp;hourly=precipitation_probability&amp;amp;temperature_unit=fahrenheit&amp;amp;timezone=America/Chicago&quot;
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;You can actually try this now if you want, open-meteo is a free, open weather API. You can make calls to it without needing to pass in extra information like an API key. This will return a JSON response, which is raw text that is unformatted. It looks like the code below.&lt;/p&gt;

&lt;div class=&quot;highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;{&quot;latitude&quot;:43.060394,&quot;longitude&quot;:-89.39947,&quot;generationtime_ms&quot;:0.06282329559326172,&quot;utc_offset_seconds&quot;:-18000,&quot;timezone&quot;:&quot;America/Chicago&quot;,&quot;timezone_abbreviation&quot;:&quot;GMT-5&quot;,&quot;elevation&quot;:272.0,&quot;current_units&quot;:{&quot;time&quot;:&quot;iso8601&quot;,&quot;interval&quot;:&quot;seconds&quot;,&quot;temperature_2m&quot;:&quot;°F&quot;,&quot;relative_humidity_2m&quot;:&quot;%&quot;,&quot;precipitation&quot;:&quot;mm&quot;},&quot;current&quot;:{&quot;time&quot;:&quot;2026-08-12T12:15&quot;,&quot;interval&quot;:900,&quot;temperature_2m&quot;:78.0,&quot;relative_humidity_2m&quot;:84,&quot;precipitation&quot;:0.00},&quot;hourly_units&quot;:{&quot;time&quot;:&quot;iso8601&quot;,&quot;precipitation_probability&quot;:&quot;%&quot;} [hourly data that I ommitted for length reasons]

&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;From this response, we can see the timezone, the temperature, humidity and precipitation. This is a very simple example of using curl. Often as software developers, we have more intensive constraints to deal with, like passing in authorization params and/or API keys. It might look a lot like this:&lt;/p&gt;

&lt;div class=&quot;highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;curl -X POST &quot;https://api.example.com/v1/orders&quot; \
  -H &quot;Authorization: Bearer YOUR_TOKEN&quot; \
  -H &quot;Content-Type: application/json&quot; \
  -d &apos;{&quot;item&quot;: &quot;widget&quot;, &quot;quantity&quot;: 3}&apos;
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Breaking that down:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;code class=&quot;highlighter-rouge&quot;&gt;-X POST&lt;/code&gt;  this is a write, not a read, so GET isn’t right anymore. We want POST&lt;/li&gt;
  &lt;li&gt;&lt;code class=&quot;highlighter-rouge&quot;&gt;-H &quot;Authorization: Bearer ...&quot;&lt;/code&gt; This proves who you are&lt;/li&gt;
  &lt;li&gt;&lt;code class=&quot;highlighter-rouge&quot;&gt;-H &quot;Content-Type: application/json&quot;&lt;/code&gt; This tells the server “the body I’m sending is JSON,” so it parses it correctly&lt;/li&gt;
  &lt;li&gt;&lt;code class=&quot;highlighter-rouge&quot;&gt;-d &apos;{...}&apos;&lt;/code&gt; this is the actual JSON body being sent&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Depending on the needs of the application you are working on, using curl is going to look a lot like the above examples. Although curl is convenient to use, the response can be difficult to parse through and read. Additionally, if you have an error it can be difficult to understand where the error occurred and for what reason, unless you add even more arguments to the command line. Curl doesn’t fail on HTTP error codes by default, so scripts can silently treat failures as successes unless you add &lt;code class=&quot;highlighter-rouge&quot;&gt;-f&lt;/code&gt;/&lt;code class=&quot;highlighter-rouge&quot;&gt;--fail&lt;/code&gt; explicitly.&lt;/p&gt;

&lt;h2 id=&quot;httpie&quot;&gt;Httpie&lt;/h2&gt;

&lt;p&gt;Httpie is a command-line tool that does the same job as curl, sending requests to a server, but it’s built to be more human-friendly, both in how you type the command and how it shows you the response. Where curl mirrors the raw pieces of an HTTP request (flags, headers, a body string), httpie’s syntax reads more like the request itself.&lt;/p&gt;

&lt;p&gt;Within your command line, you can enter something like&lt;/p&gt;

&lt;div class=&quot;highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;http https://api.open-meteo.com/v1/forecast latitude==43.0731 longitude==-89.4012 current==temperature_2m,relative_humidity_2m,precipitation temperature_unit==fahrenheit
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Notice the query parameters aren’t crammed into one long URL string like they were with curl. Each one is just key==value, space-separated. Httpie builds the actual URL for you behind the scenes.&lt;/p&gt;

&lt;p&gt;The response comes back the same JSON as before, but httpie pretty-prints and color codes it automatically (indented, keys sorted, syntax highlighted) without you having to do something like pipe it through &lt;a href=&quot;https://jqlang.org/&quot;&gt;&lt;code class=&quot;highlighter-rouge&quot;&gt;jq&lt;/code&gt;&lt;/a&gt; yourself or suffering trying to decode with your eyes. It looks something like&lt;/p&gt;

&lt;div class=&quot;language-json highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
    &lt;/span&gt;&lt;span class=&quot;nl&quot;&gt;&quot;current&quot;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;:&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;{&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
        &lt;/span&gt;&lt;span class=&quot;nl&quot;&gt;&quot;precipitation&quot;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;:&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;mf&quot;&gt;0.0&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
        &lt;/span&gt;&lt;span class=&quot;nl&quot;&gt;&quot;relative_humidity_2m&quot;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;:&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;mi&quot;&gt;84&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
        &lt;/span&gt;&lt;span class=&quot;nl&quot;&gt;&quot;temperature_2m&quot;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;:&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;mf&quot;&gt;78.0&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
        &lt;/span&gt;&lt;span class=&quot;nl&quot;&gt;&quot;time&quot;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;:&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;s2&quot;&gt;&quot;2026-08-12T12:15&quot;&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
    &lt;/span&gt;&lt;span class=&quot;p&quot;&gt;},&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
    &lt;/span&gt;&lt;span class=&quot;nl&quot;&gt;&quot;latitude&quot;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;:&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;mf&quot;&gt;43.060394&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
    &lt;/span&gt;&lt;span class=&quot;nl&quot;&gt;&quot;longitude&quot;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;:&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;mf&quot;&gt;-89.39947&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;w&quot;&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Way nicer to read and look at. Following the same examples as curl above, lets look at a more complex call to an API using httpie.&lt;/p&gt;

&lt;div class=&quot;highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;http https://api.example.com/v1/orders \
  &quot;Authorization:Bearer YOUR_TOKEN&quot; \
  item=widget \
  quantity:=3
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Breaking that down:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;em&gt;no POST&lt;/em&gt; because of the extra parameters, httpie infers you’re doing a write, so it will automatically send a &lt;code class=&quot;highlighter-rouge&quot;&gt;POST&lt;/code&gt; instead of a &lt;code class=&quot;highlighter-rouge&quot;&gt;GET&lt;/code&gt;. You can provide the method on the command if you want to be explicit, but you don’t have to.&lt;/li&gt;
  &lt;li&gt;&lt;code class=&quot;highlighter-rouge&quot;&gt;“Authorization:Bearer YOUR_TOKEN&quot;&lt;/code&gt; - the colon (:) is httpie’s notation for a header, this proves who you are&lt;/li&gt;
  &lt;li&gt;&lt;code class=&quot;highlighter-rouge&quot;&gt;item=widget&lt;/code&gt; - the equals sign (=) means a plain string field, httpie serializes it into a JSON body for you and sets &lt;code class=&quot;highlighter-rouge&quot;&gt;Content-Type: application/json&lt;/code&gt; automatically&lt;/li&gt;
  &lt;li&gt;&lt;code class=&quot;highlighter-rouge&quot;&gt;quantity:=3&lt;/code&gt; - the colon-equals (:=) means “treat this as raw JSON,” so 3 stays a number instead of becoming the string &lt;code class=&quot;highlighter-rouge&quot;&gt;&quot;3&quot;&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The wonderful thing about using httpie vs curl is that it does a lot more for you in terms of readability. It’s building the JSON body, setting content-type headers, and formatting the response, which makes it easier to read and faster to type. It also defaults to showing the response headers, which carry very useful information. The one potential drawback is you will have to install httpie yourself unlike curl.&lt;/p&gt;

&lt;h2 id=&quot;demo-magic&quot;&gt;Demo Magic&lt;/h2&gt;

&lt;p&gt;Demo Magic is a bash script that lets you pre-script a live terminal demo so it looks like you’re typing in real time, without the risk of actually typing it live. Instead of you fat-fingering a command in front of an audience, you write the commands into a script ahead of time, and Demo Magic “types” them out on screen for you, character by character, before running them.&lt;/p&gt;

&lt;p&gt;This can be super helpful when you are presenting at a conference or if you are demonstrating functionality to a client.&lt;/p&gt;

&lt;p&gt;A demo script usually looks something like&lt;/p&gt;

&lt;div class=&quot;language-shell highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;&lt;span class=&quot;c&quot;&gt;#!/bin/bash&lt;/span&gt;

&lt;span class=&quot;nb&quot;&gt;.&lt;/span&gt; demo-magic.sh

clear
pe &lt;span class=&quot;s2&quot;&gt;&quot;curl https://api.open-meteo.com/v1/forecast?latitude=43.0731&amp;amp;longitude=-89.4012&amp;amp;current=temperature_2m&quot;&lt;/span&gt;
pe &lt;span class=&quot;s2&quot;&gt;&quot;http GET https://api.open-meteo.com/v1/forecast latitude==43.0731 longitude==-89.4012&quot;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;All you need to do is run  &lt;code class=&quot;highlighter-rouge&quot;&gt;./demo.sh&lt;/code&gt;, and from there Demo Magic takes over, simulating the typing and waiting for a keypress before actually executing anything.&lt;/p&gt;

&lt;p&gt;Lets dig into these commands a little more:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;code class=&quot;highlighter-rouge&quot;&gt;. demo-magic.sh&lt;/code&gt; - this sources the Demo Magic functions into your script so &lt;code class=&quot;highlighter-rouge&quot;&gt;pe&lt;/code&gt;, &lt;code class=&quot;highlighter-rouge&quot;&gt;p&lt;/code&gt;, and others become available&lt;/li&gt;
  &lt;li&gt;&lt;code class=&quot;highlighter-rouge&quot;&gt;pe &quot;command&quot;&lt;/code&gt; - stands for “print and execute,” it simulates typing the command, pauses for a bit (or waits for you to hit enter, depending on what options you choose), and then actually runs it&lt;/li&gt;
  &lt;li&gt;&lt;code class=&quot;highlighter-rouge&quot;&gt;p &quot;command&quot;&lt;/code&gt; - “print only,” same fake-typing effect but it never actually executes, useful for commands you want to show without running (like something destructive, or something that needs a real network you don’t have on stage)&lt;/li&gt;
  &lt;li&gt;there’s also &lt;code class=&quot;highlighter-rouge&quot;&gt;pei&lt;/code&gt;, “print and execute immediately,” which skips the wait and just runs right through, handy for setup steps the audience doesn’t need to wait on&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This, as you can tell, solves a pretty specific problem: typing a demo command live, in front of an audience, without the risk of a typo under pressure. The tradeoff is that it’s only useful for that presentation context. It’s not something you’d reach for in day-to-day development the way you would curl or httpie. But if you are meeting with a client and need to show off the work you have been doing, Demo Magic is a great tool to have.&lt;/p&gt;

&lt;h2 id=&quot;yossefs-demo-wrapper&quot;&gt;Yossef’s Demo Wrapper&lt;/h2&gt;

&lt;p&gt;Yossef built his own wrapper around Demo Magic, &lt;a href=&quot;https://github.com/ymendel/dotfiles/tree/main/demo&quot;&gt;in his dotfiles&lt;/a&gt;, which fixes a handful of rough edges and adds a few conveniences on top.&lt;/p&gt;

&lt;p&gt;Using it looks like this:&lt;/p&gt;

&lt;div class=&quot;language-shell highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;&lt;span class=&quot;c&quot;&gt;#!/usr/bin/env bash&lt;/span&gt;
&lt;span class=&quot;nb&quot;&gt;source&lt;/span&gt; &lt;span class=&quot;s2&quot;&gt;&quot;&lt;/span&gt;&lt;span class=&quot;si&quot;&gt;$(&lt;/span&gt;demo-lib&lt;span class=&quot;si&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;s2&quot;&gt;&quot;&lt;/span&gt;

say &lt;span class=&quot;s2&quot;&gt;&quot;First, the orders that already exist&quot;&lt;/span&gt;
hold
pe &lt;span class=&quot;s1&quot;&gt;&apos;http GET :3000/orders&apos;&lt;/span&gt;

say &lt;span class=&quot;s2&quot;&gt;&quot;Creating one takes a customer and a total&quot;&lt;/span&gt; &lt;span class=&quot;s2&quot;&gt;&quot;Watch the location header&quot;&lt;/span&gt;
hold
pe &lt;span class=&quot;s1&quot;&gt;&apos;http POST :3000/orders customer=alice total=42&apos;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;To explain each line:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;code class=&quot;highlighter-rouge&quot;&gt;say &quot;...&quot;&lt;/code&gt; - prints a dimmed narration line above the command, so you can talk through what you’re about to show before you show it&lt;/li&gt;
  &lt;li&gt;&lt;code class=&quot;highlighter-rouge&quot;&gt;hold&lt;/code&gt; - a manual pause between steps that waits for you, separate from the pause &lt;code class=&quot;highlighter-rouge&quot;&gt;pe&lt;/code&gt; already gives you before it runs the command&lt;/li&gt;
  &lt;li&gt;&lt;code class=&quot;highlighter-rouge&quot;&gt;pe &apos;http GET :3000/orders&apos;&lt;/code&gt; - the same pe from vanilla Demo Magic, still simulating the typing and running the real command&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;All the original Demo Magic flags still work on top of this (&lt;code class=&quot;highlighter-rouge&quot;&gt;-d&lt;/code&gt; for no typing, &lt;code class=&quot;highlighter-rouge&quot;&gt;-n&lt;/code&gt; for no waiting, &lt;code class=&quot;highlighter-rouge&quot;&gt;-w N&lt;/code&gt; to auto-advance), plus one Yossef added himself: &lt;code class=&quot;highlighter-rouge&quot;&gt;--unattended&lt;/code&gt;, which runs the whole demo start to finish with no typing and no pauses. That one’s less about presenting and more about confidence, letting you easily test your demo script before running it in front of an audience.&lt;/p&gt;

&lt;p&gt;The rest of what’s in the repo is mostly Yossef fixing things vanilla Demo Magic gets wrong in small but annoying ways, like your typing speed or prompt settings getting silently reset the moment you source the script. None of it changes what the audience sees in a major way, but hopefully it means the person running the demo can trust it a little more.&lt;/p&gt;

&lt;p&gt;Thanks to Yossef for sharing this with the group. Testing tools like these are the kind of thing that’s easy to overlook until you need them, and having options ready for both quick debugging and client-facing demos is a good habit to build. Looking forward to seeing what the next Developer Round Table brings!&lt;/p&gt;</content><author><name>Amanda Klusmeyer</name></author><category term="[&quot;development&quot;]" /><category term="api" /><category term="api testing" /><category term="client demo" /><category term="curl" /><category term="httpie" /><category term="demo magic" /></entry><entry><title type="html">Developer Round Table - Why Do We Still Dismiss CSS?</title><link href="https://www.beflagrant.com/blog/developer-round-table-why-do-we-still-dismiss-css-2026-07-20" rel="alternate" type="text/html" title="Developer Round Table - Why Do We Still Dismiss CSS?" /><published>2026-07-20T09:08:00-05:00</published><updated>2026-07-20T09:08:00-05:00</updated><id>repo://posts.collection/_posts/developer-round-table-why-do-we-still-dismiss-css-2026-07-20.md</id><content type="html" xml:base="https://www.beflagrant.com/blog/developer-round-table-why-do-we-still-dismiss-css-2026-07-20">&lt;p&gt;You know what’s weird? CSS is everywhere, pretty much on every website and yet, there’s this attitude about CSS that persists that it doesn’t need to be taken seriously; it’s just icing on a cake. Casey brought this up at a &lt;a href=&quot;https://youtu.be/20P4GfRI6Mg&quot;&gt;Developer Round Table discussion,&lt;/a&gt; and it hit home. There’s this vibe that CSS is just… weird, or “not real code.” And I get it, a lot of us lived through the ‘try it in every browser and pray it works’ era. It was rough.&lt;/p&gt;

&lt;p&gt;But honestly, those days are mostly gone. With Flexbox, grid, and modern tooling, styling is smoother than ever. But still, the reputation lingers.&lt;/p&gt;

&lt;p&gt;So what’s our responsibility as web folks? Just hand-wave and blame the language? Or dig in and treat CSS with the respect it deserves?&lt;/p&gt;

&lt;p&gt;On a certain level, it feels like a self-fulfilling prophecy. This was a thought brought up by Max, a developer at Flagrant.  If you believe from the start that CSS is a lost cause, you’re never going to bother learning it well. You limp through, hate every second, and when it breaks, you get to say “Told you it was bad.” Which isn’t fair to the language to label it as difficult or broken just because you didn’t bother to truly understand how it works.&lt;/p&gt;

&lt;p&gt;Part of the problem might be that CSS hasn’t had the same level of tooling and support other languages enjoy. In Ruby, Java, or JavaScript, your editor catches errors, helps autocomplete methods, points out typos, it’s a conversation. But with CSS, it’s often silent. No nudges, no suggestions, just… hope for the best.&lt;/p&gt;

&lt;p&gt;But maybe that’s also on us.&lt;/p&gt;

&lt;p&gt;As Casey pointed out, there’s a chicken-and-egg situation happening. We don’t take CSS seriously, so the tooling hasn’t caught up, and because the tooling hasn’t caught up, we don’t take it seriously.&lt;/p&gt;

&lt;p&gt;That’s slowly starting to change. Visual regression testing, design linting tools, better devtools, the ecosystem is maturing. But it’ll only keep improving if we demand more of it and invest time into it.&lt;/p&gt;

&lt;p&gt;This brings me to the heart of it: why do we dismiss CSS in the first place?&lt;/p&gt;

&lt;p&gt;CSS isn’t just about making things “pretty.” It’s about creating a usable, intuitive experience. If you’ve ever visited a site that felt frustrating or clunky, buttons too small, text hard to read, weird layout, you know exactly how much design and styling matter. A beautifully engineered backend doesn’t mean much if the frontend makes users want to leave.&lt;/p&gt;

&lt;p&gt;Styling is functionality. And yet, we treat it like decoration.&lt;/p&gt;

&lt;p&gt;We also discussed how design has historically been a more female-dominated discipline. And we know, historically, that female-dominated fields tend to get dismissed or undervalued. That bias, even if it’s unconscious or unintentional, might be part of why CSS and design work often aren’t given the same technical respect.&lt;/p&gt;

&lt;p&gt;I’m not saying developers are intentionally dismissive or malicious. But it’s worth examining how our own biases, whether personal or systemic, shape the way we value different kinds of work. If we want to grow as developers, and as a community, we have to be willing to question these patterns.&lt;/p&gt;

&lt;p&gt;What would happen if we approached CSS as an equal partner in the stack?&lt;/p&gt;

&lt;p&gt;We’d probably write better code. We’d build better tools. We’d create better experiences for users, and maybe we’d start to close some of the gaps in respect and recognition within our teams and communities.&lt;/p&gt;

&lt;p&gt;Because in the end, CSS isn’t just how things look, it’s how things feel. And that deserves just as much care and craft as any other part of the web.&lt;/p&gt;

&lt;p&gt;Let’s stop treating CSS like an afterthought. Let’s build with it like it matters, because it does.&lt;/p&gt;</content><author><name>Amanda Klusmeyer</name></author><category term="[&quot;development&quot;]" /><category term="CSS" /><category term="Frontend" /><category term="WebDevelopment" /><category term="UX" /><category term="Design" /><category term="WebDesign" /></entry><entry><title type="html">Delightfully Friday Junior: Pet Art Gallery</title><link href="https://www.beflagrant.com/blog/delightfully-friday-junior-pet-art-gallery-2026-06-25" rel="alternate" type="text/html" title="Delightfully Friday Junior: Pet Art Gallery" /><published>2026-06-25T07:16:00-05:00</published><updated>2026-06-25T07:16:00-05:00</updated><id>repo://posts.collection/_posts/delightfully-friday-junior-pet-art-gallery-2026-06-25.md</id><content type="html" xml:base="https://www.beflagrant.com/blog/delightfully-friday-junior-pet-art-gallery-2026-06-25">&lt;p&gt;Here at Flagrant, we’re big fans of our fur babies and critters alike (we even have a dedicated Slack channel to share photos with each other). This week’s Delightfully Friday Junior is brought  to you by our unconditional love for the non-human brethren in our lives and a healthy dose of artistic flair and critique.&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/images/uploads/screenshot-2026-06-24-at-3.56.01 pm.png&quot; alt=&quot;Medium: Photographs 2000s - present Description: Seen in this collage of photos are snap shots of things in and around Kelly’s life that made her laugh or cry. Awkwardness forever and ever and ever and ever and ever and ever&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/images/uploads/screenshot-2026-06-24-at-3.56.10 pm.png&quot; alt=&quot;Title: A Star Description: Gone Supernova&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/images/uploads/screenshot-2026-06-24-at-3.56.18 pm.png&quot; alt=&quot;Title: Woggy The Dragster Description: Once a year Polli (short for Polliwog) likes to dress up for Halloween. This past year she was a Dragster chimera (part dragon, part lobster). As you can see, she wore herself out partying and eating too many treats.&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/images/uploads/screenshot-2026-06-24-at-3.56.41 pm.png&quot; alt=&quot;&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/images/uploads/screenshot-2026-06-24-at-3.56.31 pm.png&quot; alt=&quot;Title: A House Menagerie Description: The dogs never end. And the baby loves them.  And unfortunately, the cat does end.&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/images/uploads/screenshot-2026-06-24-at-3.55.50 pm.png&quot; alt=&quot;Title: To the Walls Description: To the windows, to the walls, to the face against the paws&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/images/uploads/screenshot-2026-06-24-at-3.55.40 pm.png&quot; alt=&quot;Title: Feline Denies Perception Description: Feline rest disturbed by hooman nosiness.&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/images/uploads/screenshot-2026-06-24-at-3.55.26 pm.png&quot; alt=&quot;Title: The Hardest Lives to Have Ever Been Lived Description: Here lie the four-legged creatures of yore that have worked tirelessly begging for food, pets, and attention. Their energies know limited bounds and long live the days of fending for themselves.&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/images/uploads/screenshot-2026-06-24-at-3.54.57 pm.png&quot; alt=&quot;Description: Beware! The sweet face hides a big attitude and lots of table surfing. But we still love her.&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/images/uploads/screenshot-2026-06-24-at-3.54.49 pm.png&quot; alt=&quot;Title: Miss Minnie Description: An An angel who can do no wrong, barking voice sounds like a song. Her legs are short, her hair is long, in my arms she does belong.&quot; /&gt;&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;/images/uploads/screenshot-2026-06-24-at-3.54.39 pm.png&quot; alt=&quot;Title: Mittens Description: 🐈‍⬛&quot; /&gt;&lt;/p&gt;</content><author><name>Lena Yen</name></author><category term="[&quot;consulting&quot;]" /><category term="WorkDoesntHaveToSuck" /><category term="FlagrantLife" /><category term="RemoteWorkVibes" /><category term="RemoteWork" /><category term="PhotoDump" /><category term="TeamBuilding" /></entry><entry><title type="html">I’m Still Clauding</title><link href="https://www.beflagrant.com/blog/still-clauding" rel="alternate" type="text/html" title="I&apos;m Still Clauding" /><published>2026-06-23T10:38:00-05:00</published><updated>2026-06-23T10:38:00-05:00</updated><id>repo://posts.collection/_posts/im-still-clauding-2026-06-23.md</id><content type="html" xml:base="https://www.beflagrant.com/blog/still-clauding">&lt;p&gt;A couple of months ago, I wrote about &lt;a href=&quot;https://www.beflagrant.com/blog/welcome-to-claudeville&quot;&gt;starting to use Claude Code&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I’m still there, still living in Claudeville. I’m still feeling plenty of things, including being conflicted in many ways. And it all comes down to energy use — that is, what energy I have to dedicate to this work.&lt;/p&gt;

&lt;p&gt;The biggest thing that I’m feeling now relates to my position as a consultant, not “just a developer”. Being a consultant at a small company means wearing a lot of hats. Even if you’re primarily a developer, you don’t have the luxury of dedicated PMs, or client management / liaisons, or ops, or all these things that would let you concentrate on just the software. And while I can do these other things, it’s difficult for me to do them all &lt;em&gt;and&lt;/em&gt; do the development, the building. It’s not just that I enjoy the building part (&lt;a href=&quot;https://www.beflagrant.com/blog/the-six-layers-of-art-a-personal-journey-2023-02-16&quot;&gt;the “craft”&lt;/a&gt;) the most, it’s also what I’m best at. And what that means for me in practice is it’s also the part I’m best at pulling back from and giving direction and review on. It’s the part I’m best at giving over to automation, to assistance, to an agent. It lets me concentrate on all the other things I have to do, and truly do myself.&lt;/p&gt;

&lt;p&gt;I’m also feeling plenty about the &lt;strong&gt;amount&lt;/strong&gt; of stuff to do, and the &lt;strong&gt;velocity&lt;/strong&gt; with which it gets done. There’s just &lt;em&gt;so much&lt;/em&gt; to deal with — mountains of LLM output, context-switching with bouncing between separate problems (and even separate projects) — and it’s hard to keep up. Yes, LLMs are truly a “force multiplier”, but consider what forces are being multiplied. I’m not fond of the military origins of the saying “slow is smooth, smooth is fast”, but I do strongly agree with it. I’m feeling so much demand for so much, and giving in to moving at speed means a future where you get caught in a tangle or run fill-tilt into a brick wall. This can only be countered by slowing down, looking around, and doing things well —  or as well as possible. It takes all that time and effort to produce &lt;em&gt;less&lt;/em&gt; — &lt;a href=&quot;https://quoteinvestigator.com/2012/04/28/shorter-letter/&quot;&gt;the right kind of less&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;With so many people using these tools to create literally inhuman amounts of — let’s face it, &lt;em&gt;cruft&lt;/em&gt; — that will need to be rescued, I’m remembering my earlier days. I’ve done rescue missions before. It used to be something of a specialty. But now, without some of these same tools in my tool chest, how will I possibly dig out that amount of rubble?&lt;/p&gt;

&lt;p&gt;So yes, I’m continuing to dwell in Claudeville. I figure if I’m going to do this, I should do it “right”. I should use the tools at my disposal. So I’ve done plenty to understand the tools and fit them into my tool chest, to shape them to my hands. I set up &lt;a href=&quot;https://github.com/ymendel/dotclaude/&quot;&gt;my dotclaude repo&lt;/a&gt;, so I could have a dependable(?), consistent(?) assistant/colleague(?) that goes with me from project to project (and I have &lt;em&gt;plenty&lt;/em&gt; of projects to deal with). And as my understanding has grown, so has that repo, accreting with the sediment of lessons learned, and (hopefully) coral of helpful skills and scripts, and (most likely) the barnacles of wild-attempt stabs at stopping or redirecting away from certain unwanted behavior. If you like, you can take a look at the history, and watch these things happen. And in my not-so-humble opinion, that repo and its history show two things that are not always found in other such places.&lt;/p&gt;

&lt;ol&gt;
  &lt;li&gt;Ownership. My biggest issue with what’s going on is the lack of ownership, the common anti-pattern of, &lt;a href=&quot;https://simonwillison.net/guides/agentic-engineering-patterns/anti-patterns/&quot;&gt;as Simon Willison puts it, “inflicting unreviewed code on collaborators”.&lt;/a&gt; So &lt;a href=&quot;https://github.com/ymendel/dotclaude/blob/main/CLAUDE.md&quot;&gt;my &lt;code class=&quot;highlighter-rouge&quot;&gt;CLAUDE.md&lt;/code&gt;&lt;/a&gt; &lt;em&gt;starts&lt;/em&gt; with “You help; I own the result.” This is probably as much a reminder to myself as it is to the agent. It can be seductive to delegate more and more, and try to take yourself out of the equation. This is another aspect of the vigilance I wrote of &lt;a href=&quot;https://www.beflagrant.com/blog/welcome-to-claudeville&quot;&gt;last time&lt;/a&gt;.&lt;/li&gt;
  &lt;li&gt;Cleanup. It’s not all about doing more, building up. It’s not all about &lt;em&gt;addition&lt;/em&gt;. There’s also removal, &lt;em&gt;deletion&lt;/em&gt;. Call it refactoring. Call it consolidation. Call it &lt;em&gt;judgement&lt;/em&gt;. This dotclaude repo is a project like any other — maybe more so, given its foundational nature, and how every bit I add there has the potential for knock-on effects everywhere I use Claude. Which is, of course, everywhere. Or everywhere I’m working professionally. And I do try to put the emphasis on &lt;em&gt;professional&lt;/em&gt; there (refer to the previous point on ownership).&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;So that’s where I am now, moving along with the world as it is, as best as I can. I hope you, too, are doing the best you can.&lt;/p&gt;</content><author><name>Yossef Mendelssohn</name></author><category term="[&quot;development&quot;, &quot;consulting&quot;]" /><category term="claude" /><category term="llms" /><category term="ai" /></entry></feed>