<?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 Garrett Brusewitz on Medium]]></title>
        <description><![CDATA[Stories by Garrett Brusewitz on Medium]]></description>
        <link>https://medium.com/@garrett.brusewitz?source=rss-95e658d9daa0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ViEezvkTvh0BLp1nCrqtrA.png</url>
            <title>Stories by Garrett Brusewitz on Medium</title>
            <link>https://medium.com/@garrett.brusewitz?source=rss-95e658d9daa0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 12:58:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@garrett.brusewitz/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[I Don’t Want to Make It About Me]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@garrett.brusewitz/i-dont-want-to-make-it-about-me-ddb1c3b404ca?source=rss-95e658d9daa0------2"><img src="https://cdn-images-1.medium.com/max/2600/1*lPLuNm7Udg6l0bHfQW9SVA.png" width="3360"></a></p><p class="medium-feed-snippet">A link in my comments got me thinking about how I want to show up in yours.</p><p class="medium-feed-link"><a href="https://medium.com/@garrett.brusewitz/i-dont-want-to-make-it-about-me-ddb1c3b404ca?source=rss-95e658d9daa0------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@garrett.brusewitz/i-dont-want-to-make-it-about-me-ddb1c3b404ca?source=rss-95e658d9daa0------2</link>
            <guid isPermaLink="false">https://medium.com/p/ddb1c3b404ca</guid>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[community-engagement]]></category>
            <dc:creator><![CDATA[Garrett Brusewitz]]></dc:creator>
            <pubDate>Fri, 20 Nov 2026 14:31:01 GMT</pubDate>
            <atom:updated>2026-11-20T14:31:01.951Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[You Might Know the Workaround. You Should Not Have To.]]></title>
            <link>https://medium.com/@garrett.brusewitz/you-might-know-the-workaround-you-should-not-have-to-429cc6f3e9b7?source=rss-95e658d9daa0------2</link>
            <guid isPermaLink="false">https://medium.com/p/429cc6f3e9b7</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[ios-apps]]></category>
            <category><![CDATA[ios-development]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Garrett Brusewitz]]></dc:creator>
            <pubDate>Fri, 13 Nov 2026 21:15:40 GMT</pubDate>
            <atom:updated>2026-11-13T21:15:40.839Z</atom:updated>
            <content:encoded><![CDATA[<p>Every so often I stop writing code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XCFGYzyiWH_DEbqmIAgxvw.png" /></figure><p>No new features, no refactors, nothing off the list. The only thing I do is use the app. Run a full backup, start to finish, the way an actual person would. Then do it again. And again. And again. Then do it with Voice Control turned on and my eyes closed. I intentionally use the app in ways I normally would not.</p><p>This is not a dramatic thing. It is a rhythm I come back to. I use the app over and over, I write down everything that bothers me, and sometimes I end up with fixes I would never have found by staring at code.</p><p>For SquirrelCache, one of those use tests turned up the date picker.</p><p>It was a different kind of problem from the crash I wrote about in an earlier piece. That one came to me. A report showed up and I went and fixed it. Nobody reported the date picker. Nobody was ever going to, because the people most affected by it had not installed my app yet.</p><p>I switched on Voice Control, which lets you run your device entirely by speech, and tried to use my own app that way. It did not go well, and that was my fault.</p><h3>Why a backup app has a date picker</h3><p>SquirrelCache lets you back up a range of dates instead of everything at once. September 1st through September 30th, for example. Backing up in batches is good practice, and with a large library it is far more manageable than one enormous run.</p><p>So the date picker is not tucked away in a corner. It sits in the middle of the main thing people come to the app to do.</p><h3>VoiceOver is not the whole job</h3><p>I have written before about accessibility being the forethought and not the afterthought, so I will keep this short. Full VoiceOver support, WCAG AA contrast, and Dynamic Type are the baseline for everything I ship. I had done that work. I had tested it. I thought I was covered.</p><p>Here is what I got wrong. Most accessibility work in the iOS world stops at VoiceOver. It is the one everyone knows and the one with the most documentation. But VoiceOver is one assistive technology among several, and supporting it does not mean you have supported the others. They have different needs.</p><p>The good way to use Voice Control is by name. You say the name of the thing you want and you land on it. The fallback is a grid of numbers laid over everything on screen. The grid works, but it is slower, and it feels like being handed a worse version of your own device.</p><p>Working by name only holds up if every control a person needs has a name they can say.</p><h3>Where I got stuck</h3><p>Getting to the date picker by voice was fine. I said its name and I landed on it.</p><p>Then I had no idea what to do.</p><p>I did not know how to spin it. I did not know how to say the month I wanted. Nothing on screen gave me any guidance. The picker looks like one tidy control, and as far as I could tell it behaved like one. There was no “month” I could say and land on.</p><p>I was sitting in my own app, on a screen I built, and I could not set a date.</p><h3>Am I holding it wrong?</h3><p>I should be honest about my uncertainty here, because I think it is more useful than a verdict.</p><p>I am not an experienced Voice Control user. My first assumption was that I was doing it wrong.</p><p>So I did a quick search. It took me to Reddit, to Apple’s forums, and to a handful of other places. There were plenty of complaints about the stock date picker and Voice Control. That gave me some confidence that it was not only me.</p><p>I hold that loosely, for two reasons. The internet collects complaints. You hear from the small slice of people who hit a wall and bothered to post, and you never hear from everyone else. And people who depend on Voice Control every day almost certainly know ways around this that I do not. They learn the corners of a tool in a way a developer poking at it for an afternoon never will.</p><p>Here is why none of that changes my conclusion.</p><h3>A workaround is a tax</h3><p>If a person needs tips and tricks to operate a control in my app, then my app is charging them something.</p><p>Every workaround is a small tax on attention. It is not free just because it is possible. Somebody who uses Voice Control every day might know exactly how to get the stock picker to do what they want. It will work. And every single time, they will have spent a little thought on how to use the thing instead of on what they came to do.</p><p>You might know the workaround. You should not have to.</p><p>Daily life already asks more of me than it asks of most people. So I know what that tax feels like. It is not dramatic. It is just constant.</p><p>I do not want my apps to be one more thing in the world that is harder than it needs to be. I want somebody using SquirrelCache to be thinking about which photos they are backing up. Not about how to make the date field work.</p><p>So my claim is not that the stock picker is broken. My claim is that it costs too much. Something can work and still be worth replacing.</p><h3>This is not a complaint about Apple</h3><p>Apple builds for the largest number of people. That is good business and I do not blame them for it. The calendar view looks clean. I think it looks nice. For most people, by touch, it does the job well.</p><p>A company that size has to design the default for the many. I am one person. I get to build for the person the default does not fit. That is one of the few real advantages an indie developer has, and I would be wasting it if I did not use it.</p><h3>What I built</h3><p>I added a setting. You can keep the default picker, or you can switch to individual pickers.</p><p>With individual pickers, the month is its own control. The day is its own control. The year is its own control. Each one has its own name. By voice, you say the one you want and set it. Then you do the same for the day. Then the year. Done.</p><p>Mine is plainer than Apple’s. It keeps things simple, and that is the point.</p><p>Two things about how I did it matter more than the implementation.</p><p>It is an option, not a replacement. For some people who tap, three pickers are more of a pain than one. For others, three clear fields are easier to deal with. I ended up in that second group myself. I use the individual pickers by touch now, because I like them more than the calendar grid. People are different. A setting lets them choose instead of me choosing for them. Accessibility for one group should never come at the expense of another.</p><p>It is easy to find. It is one tap into settings and you see Date Picker Style right away. A fix nobody can find is not a fix.</p><h3>Passing is not the same as good</h3><p>This is the part I keep coming back to.</p><p>“Is this accessible?” is a checkbox question. It has a yes or a no, and once you reach yes, it is easy to stop. That is how software ends up technically passing an audit while still being miserable to use.</p><p>“How can I make this better?” does not have a stopping point.</p><p>The stock date picker would have passed. It is a standard Apple control. Nobody would have flagged it in a review. It was accessible in the sense that matters to a checklist, and it was still the hardest part of my app to use by voice.</p><p>I only asked the better question because I had stopped building long enough to ask it. When you are shipping features, every hour is measured against the list. “Go use your own app slowly, with an assistive technology you do not depend on, and pay attention to how it feels” is never on the list. It does not close anything. It does not look like progress.</p><p>It is also the only way I was ever going to find this.</p><h3>What I still do not know</h3><p>I tested VoiceOver and Voice Control myself. I have not had meaningful testing from people who use VoiceOver every day, or Switch Control, or who navigate by voice out of necessity and not a developer’s curiosity.</p><p>Testing an assistive technology as somebody who does not depend on it tells you whether it functions. It does not tell you whether it is any good. Those are different questions, and I have only really answered the first one.</p><p>So if that is you, and something in SquirrelCache costs you more than it should, I want to hear about it. The comments are open. I read all of them.</p><p>Not because I want to be told I did well. The checklist already told me that. The checklist was right, and it was not enough.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=429cc6f3e9b7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Training My Brain Back]]></title>
            <link>https://medium.com/@garrett.brusewitz/training-my-brain-back-9d0064e52b23?source=rss-95e658d9daa0------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d0064e52b23</guid>
            <category><![CDATA[health]]></category>
            <category><![CDATA[mindfulness]]></category>
            <category><![CDATA[brain-health]]></category>
            <category><![CDATA[brain]]></category>
            <category><![CDATA[mental-health]]></category>
            <dc:creator><![CDATA[Garrett Brusewitz]]></dc:creator>
            <pubDate>Fri, 13 Nov 2026 00:01:02 GMT</pubDate>
            <atom:updated>2026-11-13T00:01:02.009Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Coming out of chemo fog taught me that curiosity might be the best brain exercise there is.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o1Vm7oRixAFq1zv9XcfQJw.png" /></figure><p>I spent most of my 20s trying to get my body back to where it was before chemo. What I didn’t expect was how much work my brain would need too.</p><p>If you’ve been through chemo, you might know the fog. <a href="https://www.cancer.gov/about-cancer/treatment/side-effects/memory">The National Cancer Institute</a> describes it as a mental fog that can follow chemo and radiation to the brain. For me it was real, and it was heavy. There were okay hours and there were bad hours, and early on there were a lot more bad ones than okay ones. The fogginess would roll in and thinking just got harder. Slower.</p><p>For a long time my whole focus was tipping that balance. More okay hours. Fewer bad ones. I wasn’t thinking about training my brain. I was just trying to get through the day with a clear head for a little longer.</p><p>It took me years to understand that getting my mind back was its own kind of training. Sometimes after a traumatic brain injury, your brain doesn’t get back to what it was. I had a brain surgery with some issues after the fact, then radiation, then chemo. That’s kind of a hurricane of hurt for a still developing brain.</p><p>Once I faced that fact, it wasn’t so much woe is me as what can I do from here?</p><p>Something my neuro oncologist mentioned at a routine followup really stuck with me. He said there was good research suggesting that rebuilding neural pathways is possible, even long after a brain injury. At that point I had been out of treatment for close to 10 years. There was still hope for me. Not hope that I would get back to where I was as a teenager before my treatments. Hope that I could improve my daily life as it is now.</p><p>He was right about the research. <a href="https://journals.sagepub.com/doi/full/10.1177/1545968317723748">A 2017 review</a> looked at 11 studies of cognitive rehabilitation after traumatic brain injury. It found measurable changes in how the brain works, even in people who were years past their injury.</p><p>And the thing that helped most was not what I expected.</p><h3>The bridge</h3><p>Years before, one of the doctors at the Next Steps clinic at the children’s hospital where I was treated suggested I try Adderall to get me over the chemo fog hump. The clinic is there to ease the transition to an adult hospital. She had been seeing promising results in some of her patients. So I did.</p><p>There is research behind that idea. <a href="https://doi.org/10.3390/children11020187">Studies of childhood brain tumor survivors</a> have found that methylphenidate, a similar stimulant medication, can help with attention and processing speed after treatment.</p><p>And it worked, for a while. It was nice to have a clearer head. But it was also a lot of hassle, like having to see my doctor every month for a new prescription. I knew from the start that I didn’t want to be on it long term. I took it for a couple of years.</p><p>Then everything kind of came to a head with my body, and I decided I needed to figure this out naturally.</p><p>Here is the part that stuck with me. When I got off the Adderall, I did notice a difference between me then and the worst of the chemo fog. But I don’t think the Adderall is what made 100 percent of that difference. It might have gotten me over the hump when I needed it, and I’m grateful for that. But it’s essentially a stimulant. It didn’t necessarily heal anything.</p><p>What actually helped was time. Time, and my brain slowly rebuilding its own pathways. The Adderall was a bridge. It was never the destination.</p><h3>The small things that actually helped</h3><p>Even after I understood that time and healing were doing the real work, it took me a while to find the little things that help on a daily basis. None of them are dramatic. That’s kind of the point.</p><p>When I need to calm down, breathing and focusing on one single thing really helps. Just one thing, instead of the million racing thoughts. <a href="https://www.sciencedirect.com/science/article/abs/pii/S1053810010000681">One study</a> found that just four days of short mindfulness sessions improved attention and working memory in college students.</p><p>Taking a walk in nature helps too, but only when I actually focus on it. If I walk and let my thoughts run wild, it does nothing. If I walk and really listen to the sounds around me, the racing quiets down. Researchers at the University of Michigan <a href="https://deepblue.lib.umich.edu/handle/2027.42/150702">found something similar</a>. A walk in nature improved memory and attention by about 20 percent. A walk down city streets did not.</p><p>And doing things that make my brain work helps. Recognizing patterns. Learning something new. Giving my mind a problem to chew on instead of leaving it to spin.</p><p>None of that is a cure. But little by little, it adds up.</p><h3>Curiosity is the engine</h3><p>If I had to name the one thing that trains my brain the most, it would be curiosity. Just staying curious and being willing to learn hard things.</p><p>This is a big part of why I got into app development. It’s also why I got into 3D printing, and into photography. I had no real basis for any of them. I taught myself those three. And the point was never to become an expert. The point was the learning itself.</p><p>That turned out to be the key. Sometimes it’s better to just try to learn something, even when it’s hard, than to not bother because you’ll never be great at it. The struggle is the workout. Your brain doesn’t grow from the stuff you already know.</p><p>There is research that backs this up, and it happens to involve photography. In <a href="https://agingmind.utdallas.edu/the-synapse-project/">the Synapse Project</a>, about 200 older adults spent 15 hours a week for three months learning something new, like digital photography or quilting. They showed memory gains that people doing easier activities did not. The photography group improved the most, likely because it was the hardest. That study was on older adults, not people with brain injuries like me. But the idea fits. The challenge is the point.</p><p>So I stay curious on purpose. I try to be intentional about seeking out new experiences and opportunities. It keeps my mind active, and it feels a lot better than sitting in the fog waiting for it to lift.</p><h3>The load you can’t see</h3><p>There’s another side to this that most people never think about. Honestly, I’m glad they never have to think about this.</p><p>I’m single sided deaf, and my balance takes real work when I walk. Those two things cost me mental bandwidth all day long. Locating a sound when you only hear from one side takes focus. Staying balanced takes focus. For most people those things are automatic. For me they are tasks.</p><p>I’m not imagining that cost. <a href="https://www.cambridge.org/core/journals/journal-of-laryngology-and-otology/article/concentration-motivation-activity-and-subjective-fatigue-in-patients-with-singlesided-deafness/2D38C323ACAF234EF03BC8CF87F52223">A 2024 study</a> compared 41 adults with single sided deafness to 41 adults with typical hearing. The single sided deaf group reported more fatigue and more trouble concentrating. The researchers tied it to the extra effort that listening takes.</p><p>For a long time that extra load just made everything harder, especially on a foggy day. But I found that the same trick helps here too. When I slow down and really focus on the sounds, instead of fighting them, it gets easier. Not easy. Easier.</p><p>So in a strange way, my disabilities pushed me toward the exact habits that help my brain. I think they are mostly unseen to the majority of people, unless you’re personally close to me like family or friends. Slowing down. Paying attention to one thing. Being deliberate instead of scattered. I didn’t choose those habits because a wellness article told me to. I found them because I needed them.</p><h3>The one I’m still working on</h3><p>I’ll be honest about one I haven’t nailed yet.</p><p>Language learning is something I really want to do, specifically for the neuroplasticity. Picking up a new language is supposed to be great exercise for the brain, and that appeals to me a lot. <a href="https://pubmed.ncbi.nlm.nih.gov/22571459/">One study</a> even found changes in the brain’s white matter as adults learned a second language.</p><p>I have apps downloaded on my phone. I have the intention. What I don’t have yet is the consistency. Between building my apps and focusing on my health, it’s in my mind but not at the front of my mind. I need to push it closer to the front of my mind.</p><p>I’m not going to pretend I have a perfect daily streak going, because I don’t. But I know what the fix is. I just need to squeeze it into my day. Even five minutes would be worth something.</p><h3>My dad, the proof</h3><p>When I think about where curiosity leads over a lifetime, I think about my dad.</p><p>He’s an engineer who worked in heating and cooling systems. But his knowledge goes way beyond that. I can ask him almost anything about my car, about electricity, about how something works, and he just knows. I’ll bring up something out of the blue that I’m into, like my 3D printer, and he instantly understands how it works. It’s genuinely impressive to watch someone hold that much understanding and reach for it on the spot.</p><p>For a while I thought of him as a self-taught expert. That’s not quite right, though. His own dad was a mechanic and a true handyman, the kind of man who knew how everything worked. So my dad got a foundation from his father. But he also put in decades of real effort to keep up with his knowledge and keep building on it.</p><p>That’s the part I try to remember. His range didn’t come from nowhere. It came from a foundation plus a lifetime of staying curious.</p><h3>Five minutes is enough</h3><p>If you’re coming out of your own fog, whether it’s from chemo, another treatment, or something else entirely, here’s what I’d encourage you to take from this.</p><p>You don’t need to overhaul your life. You just need to squeeze a little in. Five minutes a day of giving your brain something real to do is worth it. It adds up in a way that waiting around never does.</p><p>And you don’t have to be an expert. That’s the part I had to let go of. I’m not fluent in anything. I’m not an expert in photography, I just know what most of the settings do and I take pictures I like. Who cares? I’m not an expert in 3D printing either, but I’m good enough to design and make what I need. Learning and being curious was never about mastery. Just knowing how things work, even in a general way, is useful. It keeps your mind alive.</p><p>My dad is proof of where that leads over a lifetime. But you don’t have to get there to benefit. You just have to stay curious, and keep showing up. Five minutes at a time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d0064e52b23" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[About Me — Garrett Brusewitz]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/about-me-stories/about-me-garrett-brusewitz-323cdd7efab5?source=rss-95e658d9daa0------2"><img src="https://cdn-images-1.medium.com/max/2600/0*eZXi7-fl1qcXlzN9" width="7008"></a></p><p class="medium-feed-snippet">Still a kid in the candy store.</p><p class="medium-feed-link"><a href="https://medium.com/about-me-stories/about-me-garrett-brusewitz-323cdd7efab5?source=rss-95e658d9daa0------2">Continue reading on About Me Stories »</a></p></div>]]></description>
            <link>https://medium.com/about-me-stories/about-me-garrett-brusewitz-323cdd7efab5?source=rss-95e658d9daa0------2</link>
            <guid isPermaLink="false">https://medium.com/p/323cdd7efab5</guid>
            <category><![CDATA[about-me]]></category>
            <category><![CDATA[about-me-stories]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[personal-growth]]></category>
            <dc:creator><![CDATA[Garrett Brusewitz]]></dc:creator>
            <pubDate>Tue, 03 Nov 2026 07:46:01 GMT</pubDate>
            <atom:updated>2026-11-03T07:46:01.790Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The Game Didn’t Get Better. Sharing It Did.]]></title>
            <link>https://medium.com/@garrett.brusewitz/the-game-didnt-get-better-sharing-it-did-805d3fc2551d?source=rss-95e658d9daa0------2</link>
            <guid isPermaLink="false">https://medium.com/p/805d3fc2551d</guid>
            <category><![CDATA[baseball]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[community]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[sports]]></category>
            <dc:creator><![CDATA[Garrett Brusewitz]]></dc:creator>
            <pubDate>Tue, 27 Oct 2026 21:08:35 GMT</pubDate>
            <atom:updated>2026-11-12T23:19:20.649Z</atom:updated>
            <content:encoded><![CDATA[<p><em>30,000 People and One Giant TV</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4PtMidWDAMSUL9EAbm-ZoQ.png" /></figure><p>At home, a great play gets a “that’s a great play.” Maybe I clap. Maybe I text my brother. Last night, the same kind of play gave me goosebumps. The picture on that screen was the same picture everyone at home was watching. The game didn’t get better. The only thing that changed was who I was watching it with.</p><p>The moments I’ll remember came with two outs in the fifth inning. The Brewers got a hit. Then another. Then another. Every pitch could have ended it, and it just kept not ending. The whole building was thinking the same thing at the same time. When will this end? Every single person was going crazy, and I was on my feet with my brother and my nephews. I’ve been a Brewers fan my whole life, and I had never seen anything like that from my team. Playoffs or not.</p><p>That’s my experience, and it’s anecdotal. One guy in one seat. So I went looking for whether the research backs it up.</p><h3>What the Research Says</h3><p>It does. In 2014, psychologists Erica Boothby, Margaret Clark, and John Bargh published a study called “Shared Experiences Are Amplified.” People tasted chocolate either at the same time as a stranger, or while that stranger did something else. They never talked to each other.</p><p>When they tasted it together, good chocolate seemed better. Bitter chocolate seemed worse. Sharing didn’t just make it more fun. It turned the volume up on whatever the experience already was.</p><p>The part I love is that nobody spoke. That’s a ballpark. I didn’t talk to 99 percent of the people around me last night, and I still felt it with them.</p><p>A 2016 follow-up from the same group found the boost only showed up when people felt close. That could mean they’d gotten to know each other, or simply that they were in the same room instead of separate ones. That one I didn’t need a study for. It meant a lot going with my brother and his family.</p><p>There’s an older name for the crowd version, too. More than a century ago, the sociologist Émile Durkheim called it collective effervescence. It’s that electric feeling a group gets when everyone is focused on the same thing at the same time.</p><h3>Shared Across Generations</h3><p>The Brewers hadn’t been to the World Series since 1982. That was before I was born. My parents went to the parade that year, even though the Brewers lost to the Cardinals in seven games.</p><p>In 2008, my brother and I went to the Brewers’ first playoff game since 1982. We watched them lose and get eliminated, and I remember “Wonderwall” playing. My nephews weren’t born yet. Last night, before the first pitch, the ballpark played an electronic version of “Wonderwall.” Nobody there meant it as a callback. It was one anyway, at least for me. Now my nephews are just entering their teens, and they got to feel it too.</p><p>So shared experience doesn’t only run across a crowd. It runs across a family, a city, a state, and a whole fan base. Different people, different decades, the same team.</p><p>This city has felt it before. The Packers won the Super Bowl after the 2010 season. The Bucks won the title in 2021. But the Brewers have always felt like the small guy, a franchise used to losing, especially before 2008 and before Christian Yelich showed up. Those years matter to me. They’re what give a night like last night its context.</p><p>You can see how much this means in the numbers, too. MLB officials told owner Mark Attanasio that the Brewers have sold more merchandise this postseason than any team in history.</p><h3>Last Night</h3><p>This season was the best in team history. The most wins they’ve ever had, the best record in baseball, and the National League pennant. The question all October has been whether they could stay dominant when it mattered most.</p><p>The night started with something I love about sports. Freddy Peralta was pitching for the Rays. Until this season, he was a Brewer. When he showed up on the screen, 30,000 people gave him a loud ovation. He was in Florida. He was never going to hear it. We did it anyway. He got recognition until the first pitch. Then he was the opposition.</p><p>Then came the rally. Then, in the ninth, Brandon Woodruff walked out to pitch. He hadn’t pitched in the majors since early July, and he’s been a pillar of this team for most of the decade. I was so happy for him. He earned that moment.</p><p>The Brewers won 10 to 1. When it ended, the place was loud. Loud, loud, loud.</p><p>That puts them up 3 games to 0. They have never been this close. In 1982 they led the World Series 3 games to 2, and they had two chances to win one game. Now they have four.</p><p>The chocolate study says good things get better when they’re shared. Last night was the best chocolate I’ve ever had.</p><p>You may not have felt that way about those moments. During the rally in the fifth, the close-ups of Rays fans showed them absolutely miserable. Even in my extreme happiness, that was hard to see. A year ago, in the NLCS against the Dodgers, that was us. Shared experiences work both ways. Last night, Rays fans were eating the bitter chocolate Brewers fans ate last year. Some experiences transcend time. A year apart, on opposite ends of the country, two fan bases shared the same feeling of watching the other team pull ahead 3 games to 0.</p><p>No team has ever come back from down 3 games to 0 in the World Series. If the Rays do it, Tampa Bay will get the most legendary comeback in World Series history, and they’ll talk about it forever. I don’t want that experience to happen. But I understand why Rays fans would want it.</p><h3>Not Just Sports</h3><p>This isn’t only a baseball thing. I’ve seen Blink-182 in concert a couple times. They played a little worse than their CDs and messed up a few times, and somehow it was ten times better. I’ve heard those songs a million times. I’d never heard them with thousands of other people singing along.</p><p>Remember people camping out for a new iPhone or a midnight video game release? Nobody stood in that line because it was cheaper. You went for the anticipation. Am I going to get one, or am I too far back? Is the game going to be an instant classic? Everyone in that line was nervous together, and getting it first made it special.</p><h3>Any Size</h3><p>Shared experiences don’t need 30,000 people. The chocolate study only used two. It can be a ballpark, a concert, a line outside a store, or a family watching the first person in it go off to college.</p><p>There’s no real definition of a shared experience, other than that it isn’t an individual one. And that is amazing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=805d3fc2551d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I Learned From My First TestFlight Crash]]></title>
            <link>https://medium.com/@garrett.brusewitz/what-i-am-learning-from-my-first-testflight-crash-d54676a86999?source=rss-95e658d9daa0------2</link>
            <guid isPermaLink="false">https://medium.com/p/d54676a86999</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[testflight]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Garrett Brusewitz]]></dc:creator>
            <pubDate>Fri, 23 Oct 2026 01:46:20 GMT</pubDate>
            <atom:updated>2026-11-12T23:16:10.592Z</atom:updated>
            <content:encoded><![CDATA[<p>The place the bug lives will not always be the hardest part of the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QU8MJDguUzdqgvU7sotMTw.png" /></figure><p>Somebody in the Netherlands opened my app for the first time, granted access to a photo library with more than a hundred thousand photos in it, and watched it crash.</p><p>I know this because of a TestFlight feedback report that arrived on a Saturday afternoon. “Opened app for the first time and allowed access to the photo library, which contains 100.000+ photos. Then the app crashed.” Two sentences, submitted anonymously. No email address. No way to follow up. Just the report, and underneath it, the device details Apple attaches automatically:</p><ul><li>iPhone 11</li><li>iOS 26.6</li><li>Battery: 30%</li><li>Location: Netherlands</li><li>Disk free: 4.08 GB of 238.35 GB</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0dpLnRdMuw4swEh52jIGOg.png" /></figure><p>I had been running this build on my own phone for weeks. I had run it through Instruments. I had specifically stress tested the part of the app I was worried about, the backups. That is the app’s function. And here was a stranger, on the other side of an ocean, hitting a crash on first launch.</p><p>I started to think about what could be causing it. Then my mind sidetracked me:</p><blockquote>This is my first crash report ever! How cool is that? I’m kind of real now.</blockquote><p>Then I was back to thinking about the cause.</p><blockquote><em>My first thought was the iPhone 11 is a six year old device with only 4 gig available. Their Photos library is huge too.</em></blockquote><blockquote>Ok, let’s take a step back and think about this Garrett.</blockquote><blockquote>How did I test? On my iPhone 16 Plus. My phone storage usually hovers between five and 10 gig free. My photo library is about 30,000…</blockquote><blockquote>hmmm… my Photos are only 30% of his… does that mean anything?..</blockquote><blockquote>RAM maybe?… my phone has 8gb ram… what is the 11… half that at 4gb… ok so now I can say he has half the RAM to load a Photos Library more than three times the size… that means something. But what does that mean…</blockquote><blockquote>WAIT. How did I not think of that? The Photos Library loads at first launch!</blockquote><p>I was not worried about launch, because launch was not an issue on my phone. Nor my friend’s phone. Or my parents’. But we had all updated within the last couple of years to devices with at least 8gb RAM. I pulled out my previous phone, an iPhone XR that I had forgotten about. That has 3gb RAM and would catch the issue if the app was using too much memory loading on first launch. I charged it, loaded the TestFlight beta, and…</p><p>… it crashed!</p><p>Yay. Confirmation of the actual issue.</p><p>This was my first troubleshooting experience with a user issue where I could not talk to the person. It made me feel less like an impostor and more like someone who actually knows things.</p><h3>Lesson 1: My own device is the least representative device I own</h3><p>I use an iPhone 16 Plus. Eight gigabytes of RAM. The tester was on an iPhone 11. Four gigabytes.</p><p>That gap is not a minor one. It is the entire difference between a memory spike the system absorbs quietly and a memory spike that gets your process killed. On my phone, first launch with a large photo library was a little slow and then it was fine. On theirs, the system looked at what my app was asking for and shut it down.</p><p>I want to be precise here, because “test on older devices” is advice everyone has heard and it is not practical in every situation. Not everyone has a backup device sitting in a drawer. The real problem is more specific than that.</p><p>The device I use every day is the device I will never catch a bug on. That is not because it is new. It is because it is <em>mine</em>. It has my photo library, my settings, my storage situation, my locale, my usage patterns. Every hour I spend testing on it is an hour spent confirming that the app works for exactly one person whose data I already understand. As the developer, I also know the workarounds and the happy paths. I use my app the way it was designed to be used, because I designed it.</p><p>The 4 GB versus 8 GB thing is the headline. But look at the rest of that report.</p><p><strong>Disk free: 4.08 GB of 238.35 GB.</strong> Their phone was almost full. Low disk space changes how the system behaves under memory pressure. It changes what can be cached, and what the OS is willing to let a foreground process get away with.</p><p><strong>Locale: Dutch (Netherlands).</strong> Note the number formatting in their own description: “100.000+ photos.” A period as the thousands separator. Not a typo. A different locale convention, and a small reminder that my app was being used in a language and a formatting context I do not personally read.</p><p><strong>Time since boot: 0 minutes.</strong> They had just restarted the phone. So this was not a device bogged down after two weeks of uptime. This was a clean boot, and it still fell over.</p><p>Each of those is a variable I would not have thought to set deliberately. Together they describe a real person in a real state that I would never have constructed as a test case, because test cases come out of your imagination, and your imagination is furnished entirely with your own life.</p><h3>Lesson 2: I optimized the operation I was afraid of and got hit by the one I wasn’t</h3><p>The app backs up photos. Backup is the main event. Backup is where you are reading large files, moving bytes around, holding things in memory, doing work over a network connection that might drop.</p><p>So that is where all my attention went. I watched the memory graph during backup. I tuned batch sizes. I made sure the app released what it was holding. I tested it with the biggest library I could reasonably assemble. Backup was solid.</p><p>First launch was not backup. First launch was: ask for photo library permission, get it, and enumerate what is there so the app can show the user their own photos and let them choose what to do. In my naive head this was bookkeeping. Counting. It did not feel like a major operation. It felt like the thing that happens before operations start.</p><p>That framing was the bug. Not any particular line of code.</p><p>There is a general shape to this that I suspect is not specific to me. I formed a mental model of where the risk lived in SquirrelCache. Then I spent my effort there, and the effort worked, and the risky part became the safe part. Meanwhile the part I had classified as trivial never got a second look, because it was never on my list. The list was made once, early, by a version of me who understood the app, and iOS development in general, less well than I do now. Nobody ever went back and rewrote the list.</p><p>The place the bug lives will not always be the hardest part of the app. Sometimes it is the part I stopped thinking about.</p><h3>Lesson 3: No analytics made this harder, and I would do it again</h3><p>I should be honest about the cost of my own principles.</p><p>I do not put analytics in my apps. No telemetry, no session tracking, no crash reporting SDK, nothing that phones home. That is deliberate and it is not negotiable for me. It also meant that when this crash happened, I had exactly one source of information: what a stranger chose to type into a text box.</p><p>A developer with a crash reporting SDK would have had a stack trace, a memory footprint at the moment of death, a breadcrumb trail of what the app was doing, and a count telling them how many other people were hitting it. I had two sentences and a spec sheet.</p><p>So yes. It was harder. Anyone telling you that going analytics free costs nothing is selling you something.</p><p>But the report was enough. Not comfortable, not fast, but enough. The thing I actually needed to know, that first launch died on a large library on a low memory device, was in the tester’s own words. A stack trace would have told me <em>where</em> it died. The tester told me <em>why</em>, and why was the harder half.</p><p>Not having a dashboard also forced me to reason. With aggregate data I think I would have gone looking for the pattern in the numbers. Without it I had to build a model of what was happening from first principles, and I understand that code path far better now than I would if a tool had pointed at a line for me.</p><p>And the people who will use SquirrelCache will choose it partly for this. An app whose entire pitch is that your photos stay yours cannot ship a library that reports back what you do with them. There is no version of that where I am not undermining the only thing I am actually offering.</p><p>There is one more thing about this that I did not expect. Without analytics, my beta was not producing data and my testers were not a sample. My beta produced <em>reports</em>, and my testers were people I was in a conversation with, even when that conversation was one sentence long and one directional. That is a difference in kind, not degree. It made the number of testers matter less and the quality of their attention matter more. It also made me write better feedback prompts, because the text box was not a supplement to my data. It <em>was</em> my data.</p><p>I am not arguing that everyone should drop analytics. I am arguing that the tradeoff is more even than it is usually presented, and that “you cannot fly blind” is overstated. I flew blind. It took longer. I landed.</p><h3>What the beta could not tell me</h3><p>I want to end here rather than on a confident summary, because a confident summary would be dishonest.</p><p>I had a small number of testers. Not thousands. Not a statistically meaningful sample of anything. That puts hard limits on the shape of what I know, and I would rather name them than let this read as though I have it figured out.</p><p><strong>I do not know how common the crash was.</strong> One person reported it. I have no idea whether ten others hit it and deleted the app without a word, or whether that tester’s setup was genuinely rare. Silence is not data, and without analytics I cannot tell the difference between “did not happen” and “happened and nobody said anything.” That is the real cost of my choice. Not the diagnosis difficulty. This.</p><p><strong>I do not know what my testers were not doing.</strong> They told me about what they tried. Features nobody touches produce no feedback at all, and I cannot tell the difference between “this works fine” and “nobody found this.”</p><p><strong>I do not know what happens at scale.</strong> A beta with a small group and a launch to strangers are different events. Support load, edge cases, the sheer variety of real devices in real conditions. None of that is visible from here.</p><p><strong>I do not know which of these lessons will survive.</strong> Some of this will look obvious in a year and some of it will look wrong.</p><p>What I do have is one anonymous report from the Netherlands that made the app meaningfully better, and a much clearer sense of the gap between an app that works and an app that works for someone whose life is not mine.</p><p>If you are running a beta of your own, go find the least representative device you can get your hands on. Fill up the storage. Put it in another language. Load it with more data than you think is reasonable. Then try to use your app on it.</p><p>That is where your report is waiting.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d54676a86999" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>