More from Marco.org
I’ve been taking a break from Mastodon as my social home on the web for about six weeks. It has been more difficult than I’d usually admit. I have an amazing local community in my town that I love and am deeply involved in. But nobody here is a programmer, or even a computer nerd, so it doesn’t serve my need for a tech community. I work alone, for myself, in my house. It’s a fortunate lifestyle with many upsides, but it means I don’t get that form of community at work, either. I’ve had this feeling before… as a teenager in the 1990s. It’s profoundly lonely. But when I got internet access, that started to change. I found my people. First in the Total Annihilation community (RIP, Annihilated), then the HardOCP Forum, then the Something Awful Forums, then Tumblr, then Twitter and our community of Apple bloggers, and then Mastodon. Communities form, change, and dissolve over time. None of those are, today, anything like what they were when I most enjoyed them. We change, too. I didn’t move on from most of those solely because they changed — it was usually because we both changed, and it was no longer a good fit. My break from Mastodon has been a relief in some ways, as I’ve felt increasing divergence between what I wanted and what I was getting from it, but I didn’t know where else to go. Instagram, TikTok, and YouTube are all more video-broadcast platforms than communities. All I’ve found on Bluesky is even more anger and politics, the last things I need or want. Threads hasn’t yet stuck for me, and it’s owned by an asshole. Twitter was an amazing product and community that was previously owned by assholes, and now it’s X, which has a strong but different tech community, and is owned by different assholes. So I’ve just been… nowhere, for the first time since the 1990s. It has been, once again, quite lonely. Sure, it’s been relaxing, too, but in the way a vacation is relaxing. It’s great to take breaks, but after a long vacation, I’m ready to turn my brain back on. Without participating in a large, broad tech community, I’m exposed to fewer new ideas, both of my main jobs (app development and podcasting) are much harder, the quality and reach of my work have suffered, my skills aren’t improving as much, my mind is less stimulated, and I feel disconnected from my professions and passions. My world has gotten smaller. I could keep going like this to prove a stubborn victory or purity test, but I’d mostly just be hurting myself. Communities change, conditions change, and we change. We’re all better off if we’re willing to change our minds, and if our communities let us, no matter how strongly our younger selves declared a previous position. So I’m going to wade back in and see how it goes, trying to find a better balance to hopefully have better results, including on Mastodon. My people are spread across multiple services, and I’m going to explore them all, despite most of them being owned by assholes. I’d love to participate in communities without any assholes benefiting from it, but in the modern world, that simply isn’t possible. The only alternative is to isolate myself and not have a community at all (or a job, or a smartphone, or a computer, or internet access, or a car, or most of my food, or my country). That’s neither a price I’m willing to pay nor a condition I’d try to impose on anyone else. I’d love to have your support, forgiveness, and grace as I try to find my people again, and I strive to offer the same to all of you. Everyone deserves to be part of a community. And as I grow, I’m learning to declare fewer absolutes in a complex, imperfect, and constantly changing world.
For the first half of my childhood in suburban Ohio, we lived next to Bob. Bob and his wife were a kind, reserved older couple who decorated their home mostly with crucifixes and talked about Jesus a lot. Bob helped my mom with a lot of common household tasks after my dad died. When she woke up to a small fire on our deck, she didn’t call the fire department — she called Bob.1 I never learned any of Bob’s political views, though I can make some guesses in retrospect. They never mattered. He was just our neighbor. We later moved, and hit the neighbor jackpot with Van. Van was deeply kind, generous, and friendly — the sort of neighbor everyone wishes for. In my lazy teenage years, he’d often mow our lawn or shovel our snow for us before I even woke up. As his mobility later declined, I was honored to return the favor. Van and his delightful wife passed away years ago, before I learned how either of them felt on any political issue. If they were my neighbors today, how likely would that be? * * * If I learn today that my neighbors have political views that my “side” considers unacceptable and unforgivable, should I be able to have dinner at their house, shovel their snow, or even greet them outside? Should I be condemned for supporting or associating with them in non-political contexts? Should I be condemned for not publicly condemning them myself? While privilege and power dynamics play a complex and unavoidable role in this, I don’t want to associate with any community that would insist on either of those.2 And I can’t help but feel that maybe we were better off before we knew everyone’s hot takes on everything. The town coffee shop was just a coffee shop. We weren’t publicly shamed for going there because one of the owners was an ass. It was just a place to hang out with our friends. Our casual work friends were just casual work friends. We didn’t expect them to take positions on the world’s most complicated conflicts. We could just talk about weather and TV shows, and maybe sometimes get a beer after work. And our neighbors were just our neighbors. That was the day I learned the word “SHIT!” ↩︎ Somewhere on Bob’s wall might’ve been a relevant statement from an influential political dissident about casting the first stone. ↩︎
I have ADHD. Probably.1 My entire adolescence was defined by forgetting to do my homework, disappointing everyone around me, and being told by every adult that I was lazy, “just” needed to try harder, and wasn’t living up to my potential. I’ll be working on the resulting shame and anxiety for the rest of my life.2 If someone tells me, “Remember to pick up the dry cleaning tomorrow,” I definitely won’t remember. If someone tells me, “Remember to put the laundry in the dryer in ten minutes,” I probably won’t even remember that. If you’re thinking, “It’s just ten minutes! Nobody can possibly forget that,” I have made an app that’s probably not for you. * * * Computers saved me. Despite constantly being told that I’d never get a good job, computers provided a lucrative career path filled with even worse academic performers who couldn’t care less about my grades. What a stroke of luck! I’d be mediocre to terrible at most jobs, but I turned out to be very good at using computers to turn coffee and Phish into money. But computers also save me in smaller, everyday ways. They help me remember. * * * Sorry, I just had to go put the laundry in the dryer, which I had forgotten. Really. It’s that bad. * * * Calendar alarms changed my life. Events without alarms don’t happen. (If you’re thinking, “Why doesn’t he just check his calendar?” I have made an app that’s probably not for you.) I had less success with reminders until we had ubiquitous voice capture. If I think of something at inconvenient times, like while driving or exercising, I need to capture it immediately or I’ll forget. It cannot wait until I get to my phone or computer. It has to be recorded right then or it’s gone. Siri, for all of its faults, has always been very good at creating tasks in Apple’s Reminders app — and Siri is everywhere. Computer. Phone. Car. Watch. I can almost always ask Siri to add something to Reminders. So Reminders’ integration and ubiquity are invaluable to me. The Reminders app, though, doesn’t fit me at all. I don’t like how it looks, how it works, or how it’s organized. Hell, I don’t even like its icon. There’s nothing about it I like. So I never open it. (Not as if I’d ever remember to check it anyway.)3 Most of my Reminders interaction has always been via Siri and notifications. And that fits me very well, with three major exceptions: If I say “Remind me to buy milk,” but I forget to specify a time (or Siri misses it), Reminders will never notify me, and I’ll never check the app, so it’ll be lost. If I inadvertently dismiss a Reminders notification without snoozing it, Reminders will never notify me about it again, so it’ll be lost. When I do snooze a Reminders notification, which I do a lot, the snooze options suck.4 This spring, I made myself an app to fix all three, and… it escalated. I’ve been using it for months, and it has profoundly improved my life. Today, I’m releasing it, in hopes that maybe it can help other people, too. * * * Introducing Unforgetful. The concept is simple: Reminders for ADHD. This means: It’s impossible to lose a task. Notifications always repeat, even if you miss or dismiss them, until the task is completed or deleted. Designed for procrastination. Snoozing is a core feature, with thoughtful intervals that scale as you snooze a task more. Nothing is hidden away. A hidden task is a forgotten task. No folders, no tags, no organization, no different views or modes. No judgment or shame. Nothing is overdue. You’re not in trouble. Everything is either due now or in the future. Didn’t get to it today? Maybe tomorrow. Every day is a fresh start. And Unforgetful does all of that with your Reminders data. That means: Siri works perfectly, everywhere. Just say “Remind me…” without having to specify an app. It replaces your Reminders notifications. Turn them off, turn these on. No import. This isn’t a new system to learn or migrate into. Your Reminders data is just… there. No export. If you try Unforgetful and it’s not for you, just delete it and turn Reminders notifications back on, and all of your data is right there in Reminders. Mix and match. Don’t like it everywhere? You can still use Reminders on your Vision Pro or whatever, or simultaneously use Unforgetful with Reminders or any other app that uses Reminders data. I’ve optimized lots of features and details for ADHD, too: Fast capture with dictation. Tap the microphone button in Unforgetful — or its full suite of widgets, or its Lock Screen or Control Center controls — and quickly dictate a task.5 Spaced-out notifications, not an overwhelming pile at once. If multiple tasks are set to alert you at the same time, they space themselves out so you’re not barraged with a hopeless stack of obligations. And the order changes every day, so nothing gets lost between things. Recurring-task backlogs don’t pile up. If you miss multiple intervals for a recurring task, completing it doesn’t make you click through all of your past failures to get to the present day… it just schedules the next one from now. Remind me 5 minutes after I get home. Location-based reminders can notify you after a set delay. Because if a “remind me when I get home” task fires as I pull into the driveway, I’ll forget it by the time I’m inside, unloaded, and ready to do anything about it. Unforgetful is a Mac and iOS app that’s $19.99 per year (US). One subscription buys all platforms. There’s a one-month free trial so you can really live with it and see if it’s right for you before paying. There are a million task-management apps. Unforgetful is not for everyone, but it’s really for me, far more than anything else has ever been. Frankly, I have no idea how to reach the other people it’s for. But I know you’re out there. If any of this resonates with you… give it a shot. Despite significant progress on my mental health around this from therapy and media, I haven’t (yet?) sought an official ADHD diagnosis because I haven’t sought medication, and that seemed like the main reason why I’d want a diagnosis. That’s probably worth reconsidering. I’ll make myself a reminder to do it. Someday. ↩︎ I saw a psychologist throughout high school for my homework problem. Rather than recognizing 7 of the 9 symptoms of what we now call “inattentive” ADHD, he was just one more adult condemning me for not caring. (I really did care. Nobody wanted me to be “better” more than me.) In the 1990s, if you didn’t do homework but weren’t hyperactive, you were obviously just choosing to be lazy, and the solution was apparently to apply more shame. Not all doctors are good. ↩︎ I’ve tried other apps that are beautiful and work differently, but they’re all complete task-management systems that introduce a lot of features and complexity that I neither need nor want, at the expense of Reminders’ ubiquitous integration that I highly value. I’ve also tried other apps that use the Reminders database, but I haven’t found any of them to be… good. (Sorry. I probably didn’t try yours.) ↩︎ At least they specify the actual snooze times now instead of vague descriptions like “the afternoon,” which I proudly take full credit for, since it happened to change only after I ranted about it relentlessly on our podcast for months. If I truly made this happen, it might be the greatest impact on the world I’ll ever have. ↩︎ Dictation just records every word you say as the title, which is extremely fast and reliable. It doesn’t yet recognize things like “Remind me to buy milk at 10 AM tomorrow.” I haven’t nailed that natural-language processing yet — coming soon, maybe! For now, Siri does that part better. ↩︎
As Apple celebrates its fiftieth birthday, we celebrate the spirit of its formation, when people who loved computers started making great computers to inspire more people to love computers. That spirit is difficult to find in the tech business today. Immense scale, soulless optimization, and an insatiable thirst for growth dominate its behavior and discourse, leaving little room for the spirit and principles embodied by Steve Jobs and Steve Wozniak. Apple still has this spirit, and I believe you do, too. But it’s not infinite or invincible. It’s under constant pressure, including from Apple itself. It seems likely that you’ll soon be leading Apple, which will place unfathomable responsibility on your shoulders. As you grow into the leader that we know you can be, I urge you, on behalf of everyone who loves computers as much as we do, to protect and cultivate this spirit of Apple’s founders as the company’s top priority: We love computers. We don’t hide that — we celebrate it! We use computers to enhance our minds, lives, and abilities — not to be controlled, restricted, tricked, placated, angered, or surveilled. Our computers work for us, with the utmost respect for our time, attention, money, data, and privacy. We are customers and owners — not resources to be harvested, annoyed, or badgered into ever more services and upsells. Apple leads the industry in these values, but leading doesn’t always mean excelling. Remaining true to these values requires constant diligence, honest evaluation, introspection, and the audacity and courage to effect change. Apple doesn’t settle for fine, functional, or good enough in its hardware (and thanks for your incredible work on that). We love making and using products that aren’t just great, but greater than they need to be, always raising the bar of greatness for its own sake. Software, services, revenue sources, and world impact need to be held to that same standard. Focus on making great computers with great user experiences above all else, and you can trust that every other major goal will follow: profit, market share, expansion, impact, and benefit to the world. Making great computers must remain Apple’s top responsibility, because if you don’t do it, nobody will.
Ten years ago, Apple’s Phil Schiller surprised Apple enthusiasts and developers by walking out on stage at John Gruber’s The Talk Show Live WWDC event and giving an open, human, honest interview to a somewhat jaded community. I wrote this in response: Both Apple and Phil Schiller himself took a huge risk in doing this. That they agreed at all is a noteworthy gift to this community of long-time enthusiasts, many of whom have felt under-appreciated as the company has grown. […] Phil’s appearance on the show was warm, genuine, informative, and entertaining. It was human. And humanizing the company and its decisions, especially to developers — remember, developer relations is all under Phil — might be worth the PR risk. This started a ten-year run of interviews by Apple executives on The Talk Show every year at WWDC that proved to be great, surprisingly safe PR for Apple. No executive ever said something they shouldn’t have (they’re pros), no sensational or negative news stories ever resulted from them, and Apple’s enthusiastic fans and developers felt seen, heard, and appreciated. * * * For unspecified reasons, Apple has declined to participate this year, ending what had become a beloved tradition in our community — and I can’t help but suspect that it won’t come back. (A lot has changed in the meantime.) Maybe Apple has good reasons. Maybe not. We’ll see what their WWDC PR strategy looks like in a couple of weeks. In the absence of any other information, it’s easy to assume that Apple no longer wants its executives to be interviewed in a human, unscripted, unedited context that may contain hard questions, and that Apple no longer feels it necessary to show their appreciation to our community and developers in this way. I hope that’s either not the case, or it doesn’t stay the case for long. This will be the first WWDC I’m not attending since 2009 (excluding the remote 2020 one, of course). Given my realizations about my relationship with Apple and how they view developers, I’ve decided that it’s best for me to take a break this year, gain some perspective, and decide what my future relationship should look like. Maybe Apple’s leaders are doing that, too.
More in programming
Helping Scout focus and remember
tl;dr: the Explorer Pattern is one individual or team building a functional implementation that minimizes cross-team and cross-functional impacts as much as humanly possible, and then reconciling the details with other teams after that prototype is completed, accepting that this approach can require very substantial rework to that initial development. Why write this? Imprint previously called this the “Tech-led” or “Engineering-led” development model, but it’s pretty unclear to folks what that means. This writeup provides a more defined term, the “Explorer Pattern”, and explains in more detail how this works. Why do we need to adjust the way we work? Before 2026: Code is expensive, and we design process to minimize implementation and rework In and after 2026: Writing software is extremely cheap, but it’s a wider phenomenon: generating output is effectively-free across many dimensions. Code is nearly free — if we have appropriate constraints. Designs are nearly free — if they follow patterns. Analysis is nearly free — if we’ve instrumented things properly Reworking software is extremely cheap. Historically industry has optimized around avoiding engineering rework because engineering was the highest cost / narrowest constraint. In many companies this was interpreted as writing code being the constraint, which was never true, but many common practices were designed as if that were true (e.g. bringing engineering into problem-solving late “to protect their time”) Working on the system is much more effective than historically if we get automated integration and feedback loops right, e.g. not improving a one-off design but improving the design system. Any place where improving the higher-leverage process is slower than solving the one-off is a bug in our process Explorer Pattern: primary-and-replicas metaphor The easiest metaphor to think about the Explorer Pattern is database replication. Databases like MySQL and PostgreSQL have a primary database, where writes are performed. Every write is verified at that point, and once it’s verified, you know that the writes will flow downstream to various secondary replicas. Those downstream replicas can be delayed but they can’t be wrong because writes are verified upstream. (I’ve resisted the desire to talk about the CAP theorem.) A different model for database design is that used by Dynamo or Cassandra (or MongoDB to a certain extent), where you have a replica set, and have to get an acknowledgement from the majority of the replica set for a write to be strongly consistent. This is a very reliable setup, because it means you can tolerate losing a node, but it also introduces inconsistencies, and on a fixed amount of hardware they tend to be much, much slower than running a primary-secondary setup (or rely on bad performance metrics that don’t fsync to disk to create the illusion of throughput). The Explorer Pattern is the former primary-secondary model, where the vast majority of the work is done by the working individual or team. This makes all work internally consistent because it’s passed through the same small group. It doesn’t, however, mean that the work is perfect. For example, you can always insert data that meets the table’s requirements but is still inherently wrong (e.g. 200 is a valid integer, but it doesn’t mean that my credit limit was supposed to be 200, that depends on the surrounding application logic). Other teams become aware of the changes downstream, not synchronously upfront, and it’s instead the working group’s responsibility to both rationalize approach and create visibility into their work for other teams to engage in a non-blocking fashion. Example: Support for Financial Aggregators A concrete example of this practice at Imprint was rolling out financial aggregator support, e.g. allowing folks to connect to their Imprint powered accounts via Plaid. This has always been something folks want, but it’s particularly important in the realm of agentic commerce where more folks’ agents are analyzing their financial state for them. For this project, one of our engineering leaders (Ron), built the first pass of the feature at a low-burn while understanding the shape of the problem in a private alpha. He chatted through some of the details periodically to keep other teams aware, but it was a bit of a side project. However, once he found the full shape of the problem and had implemented a full solution, we cut the replica-lag across teams down to near-zero, identified and ran through the small number of remaining issues, and shipped it. Like many of our projects this year, it was never officially on a roadmap, and shipped a quality feature that our members have wanted for some time. How to follow the Explorer pattern The rough rules for following the Explorer pattern: Know your goal and sponsor: every initiative ultimately has to have a specific outcome it’s pursuing and a sponsor who’s bankrolling that pursuit. This doesn’t always need to be explicit, especially for smaller projects, but once a project goes beyond ~3 weeks of effort, if you can’t very explicitly identify who the stakeholder is sponsoring your project and they would not enthusiastically agree, then you are likely closer to “lost” than “exploring” Small working group is small: at most 5 people, and preferably smaller. Everyone in the group has to keep the entire project in their head for as long as possible to detect problems and opportunities Small working group is flexible: folks in small working groups have to “find a way to yes” rather than “find a way to no”. Exploring is about uncovering the fundamental shape of a problem rather than pretending we know the fundamental shape Publish progress in a public channel: explorers have to report home with the progress they are making so others are aware. This is both a Linear Project and a Slack channel. Make the narrowest viable changes to what already exists: when we introduce unnecessary changes, we invalidate others’ mental models about how the world works. When we haven’t made those changes with care, we’re not only invalidating others’ mental model, we are creating the expectation that we’ve done it very intentionally for a good reason, which has a chilling effect on others improving them later, which is very expensive, whereas the Explorer pattern depends on being as inexpensive as possible Exercise good judgment to identify reasonable hypotheses: discard bad ideas immediately, and then filter the rest by trying to implement them as quickly as possible. Once you see the shape of the implementation, you can figure out which of the remainders are interesting Hold assumptions constant to avoid getting stuck: the only way to navigate complex ambiguous problems is to hold things constant, even when you know they are imperfect. For example, to do headcount planning we have to know our revenue, to know our revenue we have to forecast it, to forecast it we have to know the day that partners will go live next year. We don’t truly know any of those things, so just anchoring on a plausible guess to unblock us is much more valuable than trying to get them accurate. A little prework is useful, but a lot is just artificial precision that’s a distraction from progress Hold space for being totally wrong: when we move fast, with low information, we always find the way out, but often it’s not the way out we anticipated when we got started. Being open to throwing it all away, and starting a second, third, fourth time Ship all the way to production behind a feature flag: features and products move fast when we get the pieces working every step from frontend to backend to data pulls. This is the first step of exploration. Just make sure it’s behind a feature flag that’s only enabled for internal folks!
Comparing two different ways of work and working environments.
I own an old, cheap TV. It has no Internet connection, no fancy smart features that make you want to install a Pi-hole, and no ask-me-again-later updates. However, it is connected to my own desktop computer through an HDMI cable, so I can watch movies and TV series from the couch. Setting it up used […] The post Making a dumb TV just smart enough appeared first on Quentin Santos.
Five days and 540km on a bike across Kyushu, without a laptop. Notes on the peace of riding all day, convenience store dinners, and Japan's emptying countryside.