More from Bryan Braun - Blog
I’ve had “AI usage statements” in the back of my mind ever since I read Ethan Marcott’s blog post sharing a round-up of his favorite ones. I didn’t consider writing one for this site, since it had the smell of status-signaling. Like a quasi-political declaration of allegiance to some sort of in-group (be it pro-AI, anti-AI, etc). I couldn’t be less interested in that.1 But then something happened that caught me completely off-guard. I was reading a post on my friend’s personal blog. This was a guy that I knew personally and looked up to. I’ve been reading everything he had been writing for years. About two-thirds of the way through a long (and fairly insightful) blog post, I had a sudden realization that the post had been written by AI. I’m not the best at detecting this kind of thing, but once I saw it, I couldn’t unsee it. It was unmistakable. And the thing is, I didn’t feel indifferent or even disappointed, as I might have predicted. I felt betrayed. For somebody who considers themselves open-minded—even optimistic—towards the development of AI, I didn’t know where this feeling was coming from. I have theories… maybe it has something to do with the social contract between the writer and the reader. Whatever it is, I didn’t want anyone who was reading my blog (hi mom 👋) to feel the same thing. So for the sake of transparency, here is my AI usage statement: The content of this website is written by me. I do not use AI to generate the text you are reading because writing from scratch helps me process my thoughts (which is one of the main reasons I blog in the first place). I don’t currently use AI-powered writing tools (grammar-check, spell-check, dictation tools, etc), but I may experiment with them as long as they don’t undermine the thinking process. The code for this website was originally hand-written, but I have since used AI to make several useful updates. I expect to continue using AI to write code for this website and other personal coding projects. When I create a public project exclusively with AI, I mention that fact in the project README.2 I am experimenting and my AI usage may change. When it does, I’ll update the policy here on my /about page, which is where it will live long-term. To explain why, see Paul Graham's Keep your Identity Small. ↩ For an example, see s-tier ↩ Thanks for reading this post via RSS! Let me know your thoughts by leaving a comment on the original post or sending me an email.
In October, a new movie will be released based on one of my favorite books, Klara and the Sun. This has happened a lot for me recently (see The Three Body Problem, The Martian, Project Hail Mary, and Tomorrow and Tomorrow and Tomorrow). I know it’s cliché to say that the book is better, but that has generally been my experience. The Martian was groundbreaking but when you force it into a 2-hour format for general consumption it becomes a forgettable action movie. The Klara trailer doesn’t give me much hope. The cheery, jokey vibe, feels nothing like the experience I had reading the book, so I wanted to take this opportunity to share what made it special to me. Note: I wrote a succinct, spoiler-free review back in 2024, so if you want the basics, I invite you to read that. For everybody else, let’s continue. Klara is an advanced humanoid robot—an Artificial Friend (“AF”)—who was designed to be a companion for children. We follow along as Klara is purchased from her store, meets Josie, her child, and assists Josie’s family as they navigate the challenges of their world. The story is told from Klara’s perspective, allowing the reader to see what she sees and feels. As a new robot, Klara is somewhat like a child, trying to piece together an understanding of the world, and the reader is brought along on that journey. We know from the beginning that Josie’s life is complicated and that there’s something unhealthy about her or her family, but neither we nor Klara understand what or why. The process of discovering what’s actually happening made the book very interesting. As an AI, Klara sees things differently than humans see things. She often focuses on things that a human would dismiss and breezes over things a human would care about. She also sees the world with fresh eyes, which allows her to make observations I wouldn’t have considered. For example, she notices that humans go to great lengths to avoid loneliness. This fear of loneliness, she observes, is at the root of nearly all human decisions (a surprising insight that I would never have considered). At the same time, Klara is naive. At times, I found myself wondering if I could trust her observations and conclusions. One of the themes that emerges throughout the story is the question of whether humans are replaceable. The robots in the story are different from humans, but they’re clearly intelligent and capable of doing human work. Klara often expresses simple emotions like joy and fear, which help her care for Josie. The humans caring for Josie, have greater emotional range, but it’s almost a liability. The mother’s grief over her other daughter’s death has left emotional scars, and her neighbor’s guilt has left her incapacitated in many ways. The humans are trying to hold it together, but they’re clearly volatile while Klara is endlessly patient, optimistic, and kind. I was originally turned off by Klara’s obsession with the sun. She gets this idea in her mind that somehow the sun could help heal Josie from her sickness, and it was obvious to me that Klara was confused. I knew that the sun was a distant ball of gas, but to Klara, a solar-powered robot, it was a magical source of life and rejuvenation. I became certain that her programming as a robot (and her early formative experiences in the store), were throwing off her judgement. Clearly, she was blinded by what she was, and thus wasn’t able to see that her side-quests would have no effect and waste precious time. But I was wrong. The sun healed Josie, not because it was an anthropomorphic life-giver that took pity on Josie, or respected Klara’s sacrifice. It healed Josie because it gave everyone hope. It gave them hope at their lowest moments, when they were willing to throw away logic, and try anything if it might help her get better. To Klara, the sun was God. It was her distant life giver and the provider of miracles. That’s why Klara didn’t want to tell the humans all the details of her plan. She knew there needed to be space for all of them to have faith. This storyline about the sun impacted me because it was basically a speedrun of the religious-skepticism journey we often experience in the real world. We care so much about our worldview being evidence-based that we fail to realize that there are some things that evidence cannot give us. Things like hope, meaning, purpose, and a reason to act selflessly. The sun also brings back the fundamental question. If a robot can heal a child by exercising faith in God and risking her life to save the ones she loves, then how can there be anything left that’s special about humans? Are the humans not doomed to obsolesce? Online reviews for Klara and the Sun call it a “dystopian novel,” but I found the story quite hopeful. Human gene-editing, advanced artificial intelligence, and the obsolescence of humans are difficult topics to grapple with, but that world is coming fast. Some parts are already here. This story paints a picture of people finding a way to navigate it. Some people embrace the future (often paying heavy costs), some run from it, some fight it, and others accept it. But they all find a way. You and I get to decide how we respond to our own changing world, but if I can take one lesson from Klara it would be to keep an open mind. We become so certain of what we know that we forget to leave space for what we don’t. Curiosity is a gift. If we allow it to fade as we mature, we lose the opportunity to see things that could change our lives for the better. Thanks for reading this post via RSS! Let me know your thoughts by leaving a comment on the original post or sending me an email.
“You are not your grand plans. You are your daily patterns.” I love this quote from James Clear because it hurts me in all the right ways. At my worst, I feel like my daily patterns are at war with my grand plans. When I’m fighting a daily battle and willpower is slipping, I need every reminder that this moment, right now, is critical. Because it is! Your body is the result of your daily food and exercise choices, not your healthy ambitions. Your mind is the result of your regular media choices, education environment, and adjacent relationships, not an independent observer, hovering uninfluenced above your day-to-day interactions. Your character is the result of your actual sacrifices—for others, for your integrity, and for the common good—not your generous aspirations. When I’m struggling with daily patterns, it’s helpful for me to look at the times I was rocking it. I’ve had periods of my life when my workouts were really consistant, or I journaled every day, or I always woke up early. What contributed to those things? Often, it was social pressure, an accountability buddy, or a change of environment that pushed me into a productive place (underrated benefit of having a blog: it’s a historical record of your successes and failures). Of all the things I might learn looking back at these experiences, perhaps the most important is that it’s never been easy. I’ve got 15+ years of posts documenting the battle. Sometimes I’m winning and sometimes I’m losing, but I’m always fighting, and that’s a daily pattern too. Thanks for reading this post via RSS! Let me know your thoughts by leaving a comment on the original post or sending me an email.
Over the last four months I’ve increased my use of AI for web dev work pretty dramatically. I use it every day at work, as do most of my coworkers. I don’t think it’s disputed anymore that AI-assisted development can save a lot of time and effort. The question is, what do we do with all that surplus? The standard narrative in the industry is to use it to go faster. Ship three features a day instead of one. Get a half-dozen agents working in parallel. 10x your productivity. If you don’t move fast, your competitors will! I get it. Speed is good and it has benefits beyond just finishing more stuff per unit time. Speed matters! But we live in an era of extreme consumer choice, especially in the world of software. Even pre-AI, there were dozens of good email clients, to-do lists, fitness apps, and analytics tools, all chock-full of useful features at reasonable prices. What is “going faster” going to give us? Even more options, with even more features? Apparently yes. In the past quarter, iOS app store submissions have risen by 84 percent, and Hackernews, “ShowHN” submissions have nearly tripled. We live in an era of software abundance. But as software grows increasingly abundant, attention grows increasingly scarce. Attention was scarce even before AI but it’s going to get worse. Consumers have more choices than ever, and increasingly those choices are becoming undifferentiated as the industry uses AI to produce them. What if we did the opposite? Instead of using your AI surplus to go faster, what if you used it to go deeper? What if, instead of building ten good features, you built two amazing ones? What if, instead of blasting out a dozen landing pages, you poured your attention and care into a home page that knocked someones socks off—one that could not have been built by an AI, because nothing like it could have been found in the training data? What if you doubled-down on performance? On accessibility? On user-experience? On creating a strong personal touch? It would stand out! That matters, arguably, even more than speed. Striking a balance The more I thought about this, the more I recognized it as the same ol’ quality vs quantity debate, where it pays to strike a balance: If we pour all our surplus time into quality, we end up hurting quality by failing to iterate. If we pour all our surplus time into quantity, we end up hurting speed as tech debt accumulates1. But what’s the ideal balance? Is it 90% quality, 10% speed? 50% - 50%? How would you spend your AI surplus? Remember: Slow is smooth, and smooth is fast. ↩ Thanks for reading this post via RSS! Let me know your thoughts by leaving a comment on the original post or sending me an email.
More in life
When you get a cold, the virus hijacks your cells and uses them to make copies of itself, destroying the cells in the process. The virus does not care about you. And yet, if you get a cold, your body doesn’t dissolve into a pile of virus-enriched goo as a result of all your cells disregarding survival to focus on virus manufacturing. Why? Well, you have an immune system. But also, if that did happen, other people would say, “Oh no, Alice has dissolved into a pile of virus-enriched goo; we should stay away lest we also become goo piles.” Better to just hijack some of your cells, so you can walk around and spread the virus to other people. Thus, the theory of optimal virulence says that a more laid-back cold virus will be more successful in the long run, which is why the cold viruses that thrive today are the non-goo-pile-converting kind. Anyway. Most people reading this have paid Apple $400-$1600 for a phone on which you can’t do anything without Apple’s permission and monitoring. That was a strange decision, but on Android phones you can run whatever you want. For example, I noticed a couple of months ago that all RSS apps were terrible, so I spent 15 long minutes having AI make me a non-terrible one. I copied the file to my phone, installed it, and entered RSS nirvana, no registration, no app store, no nothing. It seems ludicrous that I wouldn’t be able to do that. And yet, Google plans to change things. Soon, you won’t be able to run any app on an Android phone unless the person who made it bends the knee by paying a fee, giving Google their government ID, listing all apps they’ve ever made, etc. There will be an “escape hatch” for users to install other apps, but it involves secret menus and scary warnings and a 24-hour waiting period. Google says they’re doing this for security reasons, to prevent people from installing malware that does things like steal financial information. Three things that any credible analysis of this situation must acknowledge The security issue is real, and this change will help. Lots of people are in fact getting tricked into installing malware on their phones, and common sense says that this will accelerate with AI. Common sense also says that during that 24-hour waiting period, some of those people might wonder if it’s really normal for OfficialMicrosoftSupportProfessional021 to contact them on WhatsApp to send totally-safe-virus-scanner.apk. It would be convenient for lockdown opponents if the security issue was fake, but it isn’t. For 95% of people reading this, these restrictions would not be a big deal. You click a few buttons, wait 24 hours once, and then you have the same freedom you have now. That’s still far better than Apple phones where there is no process at all. Oddly, it’s also better than Apple computers, where installing programs from non-verified developers has all sorts of friction that can never be removed. Most people I know use Apple computers anyway and just tolerate the indignity. If Google cared about freedom or privacy, they could have achieved their security goals without as much harm to freedom or privacy. For example, instead instead of making themselves the sole arbiter, they could have allowed for multiple certifying entities, and could have allowed users to add others (perhaps after a 24-hour waiting period). Arguably, that would be more secure: That way, grandma could install my RSS app without leaving herself open to random malware. Or, Google could have used private on-device malware scanning, or lots of other things. Google didn’t do that because they don’t care about freedom and privacy and because they like money.1 I think that’s a fair summary. This change addresses a real issue, but it does so in a self-serving way that needlessly destroys freedom. Even so, it only destroys a bit of freedom. This change, by itself, isn’t really a huge deal. Reading between the lines, I think the real concern is what this might portend. Having made this change, maybe Google will gradually add further restrictions, slowly boiling the frog and moving ever-closer to an Apple-style dictatorship. But will they? Maybe! Still, this whole situation seems under-theorized. There are good reasons to think that a full lockdown would not be in Google’s interest. And if you care about digital freedom, you could argue that a full lockdown would be a good thing. Some other analogies Switching insurance sucks, so some insurers offer a low initial rate and then gradually raise it over time. But they don’t want to raise it too much. Maybe they can charge you $50 more per year than a competitor, because it’s not worth your time to switch to save $50. But if they tried to charge you $5000 more per year, you’d be gone. Or try this: Say it’s 1750 AD and you’re the King of France. You care nothing about your subjects and only want to extract the maximum possible loot for yourself, no offense Louis XV. How high should you set taxes? High, because you want loot. But not too high, because you don’t want your subjects to revolt and kill you. But still pretty high, because revolting is hard, and your subject know that even if they succeed, they might just end up with another ruler that’s just as rapacious as you. Or: Say you put a frog in a pot of water and slowly heat it up. What do you think actually happens? Back to phones Why are there no Linux phones? OK, technically there are Linux phones. There are various Linux phone operating systems (PureOS, postmarketOS, Mobian, Manjaro Mobile, Fedora Mobility, openSUSE Mobile) as well as sorta-Linux-sorta-Android operating systems (Ubtuntu touch, Droidian, FuriOS, Sailfish OS) and manufacturers who support them (Purism, Pine, Fairphone, Shift, FuriLabs, {J,V}olla). While I love and support these (♡), the general consensus is that they don’t currently offer an experience that’s remotely comparable to stock Android or iOS, especially for the price. (Even more technically, Android is itself a kind of Linux, but you know what I mean.) Obviously, the laws of physics do not forbid Linux phones from being just as good and cheap as an Android phone. They currently aren’t because: Making cheap phones requires huge economies of scale. Making a good operating system requires a huge amount of work. For a phone to be useful it needs good apps, which requires a huge amount of work. Linux phones don’t have those economies of scale because few people buy them. So, there isn’t enough money to pay people to perfect the operating systems, and most companies don’t bother making apps, and so few people buy those phones. Meanwhile, there are also various Android-except-de-Googled phone operating systems (LineageOS, GrapheneOS, /e/OS, CalyxOS), and the consensus is that these do come reasonably close to the experience of stock Android or iOS. Personally, I used Android for a long time while trying to disable as much of Google’s apps and telemetry as I could. A while ago, I got fed up with this and switched to Graphene, one of the most popular Android-except-de-Googled variants. I don’t enjoy tech support bullshit, so I expected some pain, but I was willing to tolerate it for freedom/privacy/whatever. In practice, I found that everything was easy and worked flawlessly and there was no pain at all. Using Graphene made me realize that I had forgotten what it feels like to be “respected” by technology. So, on a personal level, I recommend that you use Graphene. But this whole situation is full of weird tensions. For one thing, the Graphene project depends on Google for the base of their operating system, and only really survives because of Google’s tolerance. And, at the moment, the only way to use Graphene is to… buy a phone made by Google. And while I recommend you use Graphene, what I’d prefer you do is switch to a true Linux phone. That would mean that you pay a lot of money for a poor phone experience. But it would help grow the Linux phone ecosystem. If enough people did that, then Linux phones might become become good enough that selfish people like me would switch, further growing the Linux phone ecosystem, et cetera. That seems unlikely, because digital freedom weirdos face a collective action problem: Linux phones are bad and people are selfish, so we keep buying Android phones and Linux phones stay bad. There are two ways to solve that collective action problem. Either some entity could invest a ton of money to make Linux phones good, or some entity could do something to make Android worse. The status quo is good for Google You may already see the argument I’m making here. Currently Android is just open enough that weirdos like me can run a variant that gives us most of what we want. But doing that is annoying enough that 99.9% of people don’t. This gives Google almost all the benefits of full control, while also sucking up all the oxygen and preventing a real alternative from emerging. (Apple, incidentally, is laughing. They get to enjoy a full dictatorship while Google does all the hard work.) Suppose that in six months, Google decides to escalate the lockdown and completely removes the ability to run independent apps. What then? In the short-run, not much. Tech freedom weirdos would howl, normies wouldn’t notice, and the world would keep turning. But let’s look at some numbers. A rough estimate is that 3-5 million people currently use private de-Googled Android variants like Lineage or Graphene. That’s a crisp 0.1% of the global Android market. Meanwhile, it’s thought that 300-500 million people install Android apps outside the Google store. (That’s excluding China and things like the Samsung and Epic Games Stores.) The biggest reasons are (i) piracy, (ii) modified YouTube/Spotify/WhatsApp clients, (iii) region-locked games, (iv) forbidden gambling or crypto apps, (v) local sharing to save on mobile data, and (vi; least common) open-source app repositories like F-Droid. In an escalated lockdown, some of this might still be allowed, e.g. local sharing. And many people would simply accept the new restrictions. But I expect that a substantial number would suddenly become interested in de-Googled Android variants that don’t enforce the lockdown. That would be dangerous for Google: If a significant fraction of those 300-500 million people switched, there’s a risk of a vicious/virtuous cycle, where people tell their friends, manufacturers start to cater to those variants, and so on. If that happened, what would Google do? Might they clamp down on those Android variants, too? Again, maybe! Technically, Android is open-source, but if Google really wanted to kill Lineage or Graphene, there are about 200 different ways they could do that. So say they did. What would the people currently using those variants do? Again, many would simply submit. That’s good for Google. Others would decide that if they must have an overlord, they’d prefer Apple. That’s not good for Google, but probably not a huge problem given the numbers. But others would decide to look elsewhere, likely to true Linux phones. Currently, it’s estimated that less than 100 thousand people daily-drive true Linux phones, 30-50 times less than the number of people who use de-Googled Android variants. I’m too lazy and selfish to use a Linux phone now, but Google will take my RSS app from my cold dead hands, so in this scenario, I’d likely switch. If a fraction of people do that—or even get a second Linux phone—it would still represent a huge infusion of money and energy into the Linux phone ecosystem. If this pushed Linux phones from “bad” to “sort of OK”, that could kick off a growth cycle. Eventually, there would be a risk that Europe—eager to decouple from an unreliable US—might embrace them by mandating that government employees use them, or passing a law that popular apps must provide a web-app version that works on Linux phones, or whatever. Would that actually happen? I don’t know, but neither does Google. My point is that the downside risk of losing their phone duopoly seems vastly larger than the upside, so why risk it? The smart move is to crush alternative app stores and fight malicious apps while making the bare minimum concessions to keep the freedom and privacy people onside. That’s exactly what what Google appears to be doing. Of course, they might go for a full lockdown anyway. Corporations do dumb things all the time. But I really don’t see how it would be in their self-interest, and I’m not sure it would be a bad thing if they did. Dynomight: could google achieve the security aims of the android lockdown without so much harm to freedom or privacy Google Gemini 4: Yes. Security experts, privacy advocates, and open-source developers widely agree that Google’s primary security objectives—protecting users from malware, financial fraud, spyware, and social engineering—can be achieved through architectural containment, transparent auditing, and informed consent rather than centralized gatekeeping and surveillance. […] The reason Google chooses centralized lockdown over user-controlled security is largely economic and strategic, not technical: Ecosystem Lock-in: Tying security APIs (like Play Integrity) to Google Play Services makes it nearly impossible for competitors or open-source forks to build a viable alternative Android ecosystem that supports banking and media apps. Advertising Revenue: Features that dramatically improve both security and privacy—like a native network firewall, revocable internet permissions, or frictionless support for system-wide ad blockers—directly threaten Google’s primary revenue stream. Liability & Support Reduction: Treating all users as untrusted and removing root/power-user capabilities reduces the surface area of user error, even if it removes the user’s ownership of their own hardware. ↩
How my 2.5 year-old is training me to speak more confidently, or else.