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.
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
Once a year at my church, I usually give one sermon. I was asked to tie the theme to a young adult retreat we had taken to the Sunshine Coast. My first experience giving a sermon was many years ago at my old home church in El Monte, California. It was a Vietnamese-American church, but…
As with my last post on AI, let me open with a statement: Just because most people hold AI a certain way, doesn’t mean that we always must, either now or in the future. As I noted in that piece, and my shades of gray post, I am well aware — and agree with — … Continue reading Must we always use LLMs this way? →
The CSS Working Group resolved to use cursor: pointer for buttons and other clickable form controls in the new appearance: base styles. That happened on October 21, but I posted about it yesterday and, uh, people have feelings about cursors. I wrote about buttons and cursors back in 2022, when a post titled "Buttons shouldn't have a hand cursor" was making the rounds. I admitted I didn't have a strong opinion either way, then argued that not using the hand cursor had become the new anti-pattern anyway. The web isn't an operating system, and people expect clickable things to show a hand. The issue is Cursors For Base Appearance in CSS Forms Level 1. The group adopted the rules from this comment, and the part that's triggering half the Web is: select, option, input[type=checkbox], input[type=radio], button, input[type=button], input[type=submit], input[type=reset], input[type=color], input[type=image], ::file-selector-button { cursor: pointer; } It seems like we have a tabs vs. spaces sort of debate. Again. Nicole Sullivan pulled cursor data from a bunch of design systems and, in September, 27 of the 33 systems that set a cursor used pointer. After she added more systems, it was closer to a 50/50 split. Elika Etemad made the usability case in the meeting. Per the minutes, she said the hand "makes it clear, as soon as you're hovering an interactive control, you're supposed to click on it," and called it a "usability benefit even if not historically done on some platforms." "But the hand means it's a link" Haz had an interesting reaction: The debate is over, and evil has won. His point is that he can't tell whether ⌘-clicking something will open it in a new window anymore. He feels more confident clicking a button when he knows it won't change the URL, like when it just opens a popover or a panel. He's not wrong about that.* I replied that I've been on team evil since 2022 (albeit without a strong opinion, just following what users seem to expect). Touch screens don't have a cursor at all, and on desktop, browsers show a link's URL in the corner when you hover it. That's some type of hint, at least. Haz pushed back that he'd have to watch the bottom-left corner with his peripheral vision, which is fair. He also said he never cared which cursor buttons got, he just wanted links to have their own. I can appreciate that. "But desktop apps don't do it!" Jacob Paris liked the standard cursor on buttons because it makes web apps feel more like desktop apps than websites. My opinion hasn't changed, though. People have already learned that a hand cursor means clickable on the Web. It's by no means mandatory, but it's familiar and satisfying, so it stuck. Either way, nothing changes today. The resolution only covers appearance: base, which browsers haven't shipped yet. Buttons and selects still use appearance: auto, and their cursor is still default. If your CSS reset, design system, or web components already set cursor: pointer on buttons, keep it. When appearance: base ships, controls that opt in will get the same cursors by default. But remember, these are only defaults! You can still add whatever cursor you want to whatever element you want. Nobody's gonna stop you. In 2022, I said I'd keep changing the cursor on buttons until there's a good reason to stop. In 2026, I still haven't found one…and neither has the CSS Working Group. *Thinking about this more, if 50% of design systems opted to add cursor: pointer to buttons already, isn't this already a moot argument? **In general, I think the Web should be more personal and expressive so who even cares about a default? This is especially true for personal and fun sites. Just don't go too crazy, especially when it affects accessibility and the overall user experience.
TokyoDev has grown substantially over the past few years. We’ve expanded our community, dramatically increased the scope and frequency of our events, and have curated a library of articles for international developers. Despite all that, the way we run the business hasn’t changed much. I’ve continued to coordinate most of these activities myself, making the final decisions and keeping everything connected. In short, TokyoDev cannot run without my daily input. That approach worked well when TokyoDev was smaller, but it’s increasingly limiting how much we can accomplish. To help the business grow further, I wanted to find someone to take over some of my responsibilities and bring a fresh perspective. This is a significant step for me personally, as while I have worked with many contractors over the years, I have never actually hired a regular employee. Most importantly, I wanted to ensure that this person was someone I could trust to understand what TokyoDev stands for, and to make decisions in line with our philosophy. So I’m happy to announce that Scott Rothrock is joining TokyoDev full time as our Head of Operations. About Scott Scott has lived in Japan for nearly 20 years and has worked as a software engineer in multiple industries and environments, including small Japanese-owned businesses, overseas employers, and international companies based in Japan. Until the end of October 2026, he was the head of the Japan Markets team at Kraken Technologies, where he led an international team of software engineers in delivering complicated, regulated products on strict timelines for Japanese electricity and gas retailers, while also ensuring compliance with evolving organizational and global standards. He’s made a name for himself both inside and outside Japan as a kind, effective mentor who can cultivate great engineers and leaders. Scott’s previous role in TokyoDev Some of you may already know Scott in another capacity, as he has been involved with TokyoDev since 2022. He began as a community volunteer and later became our community manager, which also included responsibilities such as managing our article pipeline from submission to publishing. When I created TokyoDev’s Discord, I had no previous experience running an online community. Scott joined soon after I started and began helping other members, stepping in when people behaved inappropriately, and configuring our roles and permissions and safety features. I was impressed by his initiative and asked him to become an official moderator in January 2023. Outside of his role as a moderator, Scott has always pushed TokyoDev to grow; for example, he arranged internet events such as livestreamed AMAs and interviews. He organized TokyoDev’s first meetup as a volunteer in February 2023, which taught me that there was interest in TokyoDev events outside of the internet. By the end of 2023, I had brought him on as our part-time community manager. What I saw throughout his tenure was that Scott continued to take initiative in expanding TokyoDev. Scott was one of our first external contributors, writing about his experience living with a disability in Japan. He encouraged me to expand and refine both our editing and submission processes so that we could reach out to even more contributors and platform their perspectives. The editorial team now consists of him and Rebecca Callahan, and they’ve had a hand in every article that TokyoDev has published. In other words, since 2022, Scott has shown that he cares about TokyoDev as much as I do. He is invested in what we do and why we do it, and shares my vision for what TokyoDev can become. What changes now Scott’s experiences as an engineer, a mentor, and a leader make me confident that, as our Head of Operations, he will continue to help TokyoDev mature. A big part of what has made TokyoDev successful is that I see the software developers who use our site as my peers and genuinely want to help them. Scott shares that perspective, and will join me in ensuring that TokyoDev remains true to its principles while we grow. So what changes in the short term? Nothing dramatic. I will teach Scott about managing TokyoDev as a business, and he will document our processes and products as a part of that learning. He will also look for areas of improvement while ensuring that we remain compliant with regulations and labor law. Over time, I will hand over some other responsibilities. I will continue to run TokyoDev, but TokyoDev will become less dependent on me for its day-to-day operations. Long term, I’m excited about what this will enable us to do. TokyoDev has always been about helping international software developers build successful careers in Japan, and bringing Scott on full time puts us in a much better position to continue doing that. We look forward to writing the next chapter of TokyoDev together.