# Jim Nielsen's Blog

Writing about the big beautiful mess that is making things for the world wide web.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Email Dumpster Diving

DevFeed: [Email Dumpster Diving](<https://devfeed.tech/articles/email-dumpster-diving-142365.md>)

Original publisher: [Read original article](<https://blog.jim-nielsen.com/2026/email-dumpster-diving/>)

Author: Jim Nielsen

Published: 2026-11-18T19:00:00Z

Content type: opinion

Language: en

Sources: [Jim Nielsen's Blog](<https://devfeed.tech/sources/jim-nielsen-s-blog.md>)

Topics: [email](<https://devfeed.tech/topics/email.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [Use Cases for Every Cloud Service Model](<https://devfeed.tech/topics/use-cases-for-every-cloud-service-model.md>)

Tags: [cloud-services](<https://devfeed.tech/tags/cloud-services.md>), [email](<https://devfeed.tech/tags/email.md>), [phishing](<https://devfeed.tech/tags/phishing.md>), [ransomware](<https://devfeed.tech/tags/ransomware.md>), [saas](<https://devfeed.tech/tags/saas.md>), [scam](<https://devfeed.tech/tags/scam.md>), [spam](<https://devfeed.tech/tags/spam.md>)

### AI overview

The author uses spam-folder browsing to learn scam tactics and occasionally finds a legitimate message wrongly flagged. The excerpt describes phishing emails that mimic cloud-service billing warnings, a message claiming to be from Gina Rinehart that builds credibility through a Wikipedia link, and a purported Trump Accounts notice. To assess the last email, the author checked its links, sender, and headers; they matched the IRS-listed GovDelivery sender and official destinations, so the message was legitimate despite Gmail's spam classification. The author also notes how scam demands for payment can resemble SaaS billing practices.

### Source excerpt

Sometimes, for fun, I like to go rummage around in my email's Spam folder. Why? Who knows (probably a question for a licensed medical professional). I think there's some part of me that chases the dopamine hit of finding a "needle in the haystack": an email flagged as spam that shouldn't be (which almost never happens, so I guess this behavior falls under the label of addictive/impulsive seeking). I think there's also a part of me that enjoys keeping a finger on the pulse of scam tactics, like "Let's see how people are trying to trick me today..." Almost like a form of inoculation: deliberate exposure to scam tactics in a controlled environment. It helps me develop an immunity, which comes in handy when family members come to me with their emails and ask, "Is this legit?" Here's a little exposure to what I've seen recently. First: I see a lot of emails that exploit the way cloud services bill us. For example: "You've hit your limits! Better log in or you'll lose access!" Or, "Your credit card has expired. Better log in and enter your new credit card so you can keep doing what you're doing." ⁣ (Note the little green banner at the top -- "This message was sent from a trusted sender." A kind of "Why would I deceive you?") These emails are interesting not only as an exercise in analyzing scam tactics, but also as a meta-commentary on legitimate software use cases. For example, isn't it interesting how difficult it can be to distinguish scammer tactics from legitimate software company practices? "Hey, you better give us your credit card or you'll lose access to your thing!" That's what ransomware is; it's also what SaaS is, lol. It's kinda funny, yeah? No, just me? Ok, I digress. Next email. This is an interesting one. Usually phishing emails are pretty overt in their intentions: click this big button and get taken to a page where you do what we want, e.g. enter sensitive info like a password or credit card. (Again, interesting that legitimate marketing teams follow the sam

## Making a Website in 2026

DevFeed: [Making a Website in 2026](<https://devfeed.tech/articles/making-a-website-in-2026-128946.md>)

Original publisher: [Read original article](<https://blog.jim-nielsen.com/2026/making-websites-in-2026/>)

Author: Jim Nielsen

Published: 2026-11-10T19:00:00Z

Content type: opinion

Language: en

Sources: [Jim Nielsen's Blog](<https://devfeed.tech/sources/jim-nielsen-s-blog.md>)

Topics: [Website](<https://devfeed.tech/topics/website.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [decision-making](<https://devfeed.tech/topics/decision-making.md>), [no-code website builders](<https://devfeed.tech/topics/no-code-website-builders.md>), [React](<https://devfeed.tech/topics/react.md>), [hosting](<https://devfeed.tech/topics/hosting.md>), [Single-page application (SPA)](<https://devfeed.tech/topics/spa.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-tools](<https://devfeed.tech/tags/ai-tools.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [auth0](<https://devfeed.tech/tags/auth0.md>), [conference](<https://devfeed.tech/tags/conference.md>), [database](<https://devfeed.tech/tags/database.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [e-commerce](<https://devfeed.tech/tags/e-commerce.md>), [email](<https://devfeed.tech/tags/email.md>), [fullstack](<https://devfeed.tech/tags/fullstack.md>), [html](<https://devfeed.tech/tags/html.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [llm](<https://devfeed.tech/tags/llm.md>), [llms](<https://devfeed.tech/tags/llms.md>), [lovable](<https://devfeed.tech/tags/lovable.md>), [make](<https://devfeed.tech/tags/make.md>), [payment-processing](<https://devfeed.tech/tags/payment-processing.md>), [post](<https://devfeed.tech/tags/post.md>), [react](<https://devfeed.tech/tags/react.md>), [website](<https://devfeed.tech/tags/website.md>)

### AI overview

AI website builders can turn a simple prompt into a full-stack site with third-party services, leaving users to depend on choices they may not understand. In the cited examples, Lovable produced a full-stack React app with a Supabase comments database that required no user setup; Vercel's v0 prompted the user to install Neon and created an account for them. The article questions how such providers are selected and whether referral payments could shape those integrations. It also criticizes opaque credit meters, arguing that tools should show costs in dollars. The author sees AI generation as making end-user programming more accessible, while warning that sites made with little human thought can be worse than no site and difficult for users to understand.

### Source excerpt

Pete Millspaugh has a great post over on the Val Town blog where he documents his attempt at making generating the same website across a variety of AI tools. I love the post. Here are a couple of thoughts that come to mind. The Space Is Ripe for Referral Fees Pete decided to make a website for his conference talk, and he added a comments section to make it a less static / more dynamic demo. This is interesting because LLMs are really good at generating one-off HTML pages you open at file://, but as soon as you start to introduce technological dependencies -- like a database, or an analytics tool, or a service for sending email, or payment processing, etc. -- the question becomes: How does the LLM choose which service to rely on? It's one thing to have the LLM choose React over Angular or Vue over Svelte. But how (and why) does it choose something like an auth provider? Does it build you a site with Auth0 or WorkOS or Clerk? How would a non-technical user even know how to weigh the trade-offs of making such a decision? Pete said he was deliberately vague about these details, which is why I find his experience so intriguing. For example, here's what he found after generating a site in Lovable: My Lovable app is fullstack React, I learn, clicking around to find the code. It seems a bit heavy for a single-page site what with dozens of files [...] The comments database seems to be using Supabase, which required no intervention on my part to set up. There's a whole lot more--analytics, e-commerce and AI integrations, etc. I'd be really curious to know what that "a whole lot more" was. Which tools/services did it choose to depend on? How many people creating these sites understand that, even for a website that's mostly static content, they're being given an output that ships a JavaScript application framework, router, hydration runtime, analytics, component bundles, etc.? You asked for a sailboat, but you got an aircraft carrier. Do you know? Or more importantly, do you care? B

## Addition By Subtraction

DevFeed: [Addition By Subtraction](<https://devfeed.tech/articles/addition-by-subtraction-122996.md>)

Original publisher: [Read original article](<https://blog.jim-nielsen.com/2026/addition-by-subtraction/>)

Author: Jim Nielsen

Published: 2026-11-08T19:00:00Z

Content type: opinion

Language: en

Sources: [Jim Nielsen's Blog](<https://devfeed.tech/sources/jim-nielsen-s-blog.md>)

Topics: [Website](<https://devfeed.tech/topics/website.md>), [Icons](<https://devfeed.tech/topics/icons.md>)

Tags: [addition](<https://devfeed.tech/tags/addition.md>), [better](<https://devfeed.tech/tags/better.md>), [choice](<https://devfeed.tech/tags/choice.md>), [control](<https://devfeed.tech/tags/control.md>), [dimensions](<https://devfeed.tech/tags/dimensions.md>), [functionality](<https://devfeed.tech/tags/functionality.md>), [gallery](<https://devfeed.tech/tags/gallery.md>), [great](<https://devfeed.tech/tags/great.md>), [less](<https://devfeed.tech/tags/less.md>), [list](<https://devfeed.tech/tags/list.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [more](<https://devfeed.tech/tags/more.md>), [need](<https://devfeed.tech/tags/need.md>), [number](<https://devfeed.tech/tags/number.md>), [options](<https://devfeed.tech/tags/options.md>), [pixel](<https://devfeed.tech/tags/pixel.md>), [plus](<https://devfeed.tech/tags/plus.md>), [simple](<https://devfeed.tech/tags/simple.md>), [site](<https://devfeed.tech/tags/site.md>), [sites](<https://devfeed.tech/tags/sites.md>)

### AI overview

The author simplified icon gallery list views by removing the 512x512 option, leaving 56x56, 128x128 (the default), and 256x256. The smaller size suits mobile, while the larger list size shows more detail; for a 512-pixel view, users can open an icon's detail page. The author says the three-step choice--default, smaller, or bigger--reduces decision-making. A dynamic slider is a possible future addition, but has not been implemented.

### Source excerpt

I still think saying no is important. In that vein, here's something I shipped by removing functionality (and I think my site is better for it). For the longest time on my icon gallery sites, you could view a list of icons in four pixel dimensions: 56x56 128x128 256x256 512x512 Each of these sizes could be accessed via a control on the website. This has been true for years on my site, whether it's the current site: Or an older version of the site: By default, I loaded the 128-pixel version of the icons. But if you wanted to see other sizes, you could. However, the more I used the site myself the more I thought, "Four options is too many". When it comes to choice, what I really wanted was: Default Smaller Bigger (Plus three is always a good number, unless you have a reason otherwise). So I removed the big 512 option. If I want to study an icon at that size and detail, I click through to the icon's detail page. Now there are three options for list views: 56, 128, and 256. Small (great on mobile), 128 (great by default), and big (let me see more detail). It's simple to think about: You get a size by default. Not big enough? Go up a size. Too big? Go down a size. You don't need to think about it anymore than that. I mean you can, but I've found I don't need to. So I've taken that off your plate. Less cognitive overhead. Maybe one day I'll add a slider and make it all dynamic. But for now, I like this small addition by subtraction. Reply via: Email - Mastodon - Bluesky

## "It Gives Great Demo"

DevFeed: ["It Gives Great Demo"](<https://devfeed.tech/articles/it-gives-great-demo-119130.md>)

Original publisher: [Read original article](<https://blog.jim-nielsen.com/2026/it-gives-great-demo/>)

Author: Jim Nielsen

Published: 2026-11-04T19:00:00Z

Content type: opinion

Language: en

Sources: [Jim Nielsen's Blog](<https://devfeed.tech/sources/jim-nielsen-s-blog.md>)

Topics: [User Experience](<https://devfeed.tech/topics/user-experience.md>), [touchscreen](<https://devfeed.tech/topics/touchscreen.md>), [inclusive design](<https://devfeed.tech/topics/inclusive-design.md>)

Tags: [115-billion-stock-swap](<https://devfeed.tech/tags/115-billion-stock-swap.md>), [amazing](<https://devfeed.tech/tags/amazing.md>), [attention](<https://devfeed.tech/tags/attention.md>), [career](<https://devfeed.tech/tags/career.md>), [demo](<https://devfeed.tech/tags/demo.md>), [doesn-t](<https://devfeed.tech/tags/doesn-t.md>), [jobs](<https://devfeed.tech/tags/jobs.md>), [macbook](<https://devfeed.tech/tags/macbook.md>), [multitouch](<https://devfeed.tech/tags/multitouch.md>), [people](<https://devfeed.tech/tags/people.md>), [practical](<https://devfeed.tech/tags/practical.md>), [product](<https://devfeed.tech/tags/product.md>), [technology](<https://devfeed.tech/tags/technology.md>), [testing](<https://devfeed.tech/tags/testing.md>), [touchscreen](<https://devfeed.tech/tags/touchscreen.md>), [user-testing](<https://devfeed.tech/tags/user-testing.md>), [vertical](<https://devfeed.tech/tags/vertical.md>), [video](<https://devfeed.tech/tags/video.md>)

### AI overview

Using Steve Jobs's explanation of why touchscreen MacBooks were not made, the excerpt contrasts an impressive demo with everyday usability: vertical touchscreens may look compelling, but extended use can cause arm fatigue, while touch surfaces are better suited to horizontal use. It generalizes this as a tension in technology: demos capture attention and help sell products, while products that work well can fade into the background. The same distinction, it argues, applies to people who excel at presentations.

### Source excerpt

There's that famous video of Steve Jobs explaining why they don't didn't make touchscreen MacBooks: We thought about [a touch screen MacBook] years ago. We've done tons of user testing on this and it turns out it doesn't work! Touch surfaces don't want to be vertical. It gives great demo. But after a short period of time, you start to fatigue. And after an extended period of time, your arm wants to fall off. It doesn't work. It's ergonomically terrible. Touch surfaces want to be horizontal [...] that's why we've perfected our multitouch trackpads over the years. I'm not going to weigh in on the new MacBooks. But what I find specifically intriguing in this video -- and broadly relevant -- is that phrase: "It gives great demo." Damn, that is a great line for so much of technology. "It gives great demo." Something that looks amazing when it's presented to you, but in practical day-to-day use you discover, "Actually this is kinda terrible." Demo is everything nowadays. Whatever can garner attention. Who cares if it works in practice, does it give great demo? Because demo time is sale time. The purpose of a demo is to get your attention. To make you think about the product and that it exists. But a great product often makes you forget it exists at all. It seems like a paradox: we're attracted to what stands out, but we become enamored with what disappears. Of course, this doesn't just apply to products. People can give great demo, too. You can make a whole career out of just giving great demo. Reply via: Email - Mastodon - Bluesky

## No Need for Retirement When Utopia Is Around the Corner

DevFeed: [No Need for Retirement When Utopia Is Around the Corner](<https://devfeed.tech/articles/no-need-for-retirement-when-utopia-is-around-the-corner-92986.md>)

Original publisher: [Read original article](<https://blog.jim-nielsen.com/2026/skip-retirement-for-utopia/>)

Author: Jim Nielsen

Published: 2026-10-21T16:51:17.567850Z

Content type: opinion

Language: en

Sources: [Jim Nielsen's Blog](<https://devfeed.tech/sources/jim-nielsen-s-blog.md>)

Topics: [national security](<https://devfeed.tech/topics/national-security.md>), [intelligence](<https://devfeed.tech/topics/intelligence.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [cancer](<https://devfeed.tech/tags/cancer.md>), [corporate](<https://devfeed.tech/tags/corporate.md>), [cost](<https://devfeed.tech/tags/cost.md>), [employees](<https://devfeed.tech/tags/employees.md>), [lab](<https://devfeed.tech/tags/lab.md>), [mission](<https://devfeed.tech/tags/mission.md>), [nuclear](<https://devfeed.tech/tags/nuclear.md>), [nuclear-weapons](<https://devfeed.tech/tags/nuclear-weapons.md>), [rand-corporation](<https://devfeed.tech/tags/rand-corporation.md>), [retirement](<https://devfeed.tech/tags/retirement.md>), [world](<https://devfeed.tech/tags/world.md>)

### AI overview

The author compares Daniel Ellsberg's account of RAND during the missile gap years with rhetoric associated with AI labs such as Anthropic. Ellsberg described a close-knit, almost religious sense of mission: RAND researchers saw themselves as insiders with special knowledge, working to save the world from nuclear danger. He and Alain Enthoven skipped RAND's generous retirement plan because, in their late twenties, they doubted they would live to collect it. The author connects this to reports of AI researchers smoking in the belief that AI may cure cancer before smoking harms them, then speculates that ending employer retirement benefits could serve as a signal of faith in near-term universal high income, while also saving companies money. The article excerpt presents this as a provocative analogy and speculation, not a reported policy change.

### Source excerpt

I've mentioned before my interest in the history and development of nuclear weapons. Currently, I'm reading The Doomsday Machine: Confessions of a Nuclear War Planner by Daniel Ellsberg (of Pentagon Papers renown). In the first chapter, Ellsberg talks about his time working at the RAND Corporation during the missile gap years when the U.S. thought it was falling behind the Soviet Union in nuclear capabilities. Many of his descriptions sound strikingly similar to the rhetoric coming out of places like Anthropic. For example, note the religious overtones of working at a corporation: I loved RAND, where I ended up spending ten years [...] Much, I imagined, like members of a religious order would, I shared with my colleagues a sense of brotherhood, living and working with others for a transcendent cause. They were insiders: burdened with the responsibility of knowledge others did not possess. precisely in my early missile-gap years at RAND and as a consultant in Washington, there was our sense of mission, the burden of believing we knew more about the dangers ahead, and what might be done about them, than did the generals in the Pentagon or SAC, or Congress or the public, or even the president. It was an enlivening burden. And what was their "enlivening burden"? Saving the world: [My colleagues] shared a feeling--soon transmitted to me--that we were in the most literal sense working to save the world. What really stood out was this part, where Ellsberg describes how he and his colleagues truly believed the end was nigh: From the Air Force intelligence estimates I was newly privy to, and the dark view of the Soviets, which my colleagues shared with the whole national security community, I couldn't believe that the world would long escape nuclear holocaust. Alain Enthoven and I were the youngest members of the department. Neither of us joined the extremely generous retirement plan RAND offered. Neither of us believed, in our late twenties, we had a chance of collecting on i

## No More Icons In Every Menu By Default

DevFeed: [No More Icons In Every Menu By Default](<https://devfeed.tech/articles/no-more-icons-in-every-menu-by-default-90460.md>)

Original publisher: [Read original article](<https://blog.jim-nielsen.com/2026/icons-in-every-menu/>)

Author: Jim Nielsen

Published: 2026-10-19T19:00:00Z

Content type: opinion

Language: en

Sources: [Jim Nielsen's Blog](<https://devfeed.tech/sources/jim-nielsen-s-blog.md>)

Topics: [User interface design](<https://devfeed.tech/topics/ui-design.md>), [Dark Mode](<https://devfeed.tech/topics/dark-mode.md>), [Icons](<https://devfeed.tech/topics/icons.md>), [macOS](<https://devfeed.tech/topics/macos.md>), [User Experience](<https://devfeed.tech/topics/user-experience.md>)

Tags: [apple](<https://devfeed.tech/tags/apple.md>), [icons](<https://devfeed.tech/tags/icons.md>), [macos](<https://devfeed.tech/tags/macos.md>), [news](<https://devfeed.tech/tags/news.md>)

### AI overview

The author argues that Apple's reversal of its default use of icons in macOS menus offers a stronger case against the design choice than Apple's previous nonuse. Apple's revised Human Interface Guidelines cite Tahoe's menus as an example of what not to do, and the author frames the change as a lesson in learning through experience.

### Source excerpt

Have you heard the good news? I bemoaned the approach of putting an icon in every menu item by default which shipped with macOS Tahoe -- but now it's gone in Golden Gate! John Gruber wrote about this reversion back in June, including the fact that Apple's new Human Interface Guidelines specifically call out Tahoe's approach to menus as an example of what not to do on macOS. As the old saying goes, it takes a big man corporation to admit when they're wrong. As I mentioned in my original post, one of the arguments I had in my quiver against this practice was "Apple doesn't do it". But once Apple started putting icons in all their menus in Tahoe, I lost a persuasive point in my argument. But now, I think I have an argument that's even stronger than before! It's no longer: "Apple doesn't put icons in their menus." It's: "Apple tried putting icons in all their menus, and even they went back on it!" They designed it, shipped it, lived with it for a year, then publicly changed their guidance on it. To me, that's a lot more persuasive than simply saying, "Apple doesn't do this." Choosing not to do something you've never done is one thing. Choosing not to do something you've done is experience. That's the essence of life: learning by doing. Reply via: Email - Mastodon - Bluesky

## We Need All the Disciplines

DevFeed: [We Need All the Disciplines](<https://devfeed.tech/articles/we-need-all-the-disciplines-88266.md>)

Original publisher: [Read original article](<https://blog.jim-nielsen.com/2026/we-need-all-disciplines/>)

Author: Jim Nielsen

Published: 2026-10-15T19:00:00Z

Content type: opinion

Language: en

Sources: [Jim Nielsen's Blog](<https://devfeed.tech/sources/jim-nielsen-s-blog.md>)

Topics: [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Product Management](<https://devfeed.tech/topics/product-management.md>), [AI Engineering](<https://devfeed.tech/topics/ai-engineering.md>), [trust](<https://devfeed.tech/topics/trust.md>), [Self-organizing Team](<https://devfeed.tech/topics/self-organizing-team.md>)

Tags: [collaboration](<https://devfeed.tech/tags/collaboration.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [llm](<https://devfeed.tech/tags/llm.md>), [product](<https://devfeed.tech/tags/product.md>), [software](<https://devfeed.tech/tags/software.md>), [trust](<https://devfeed.tech/tags/trust.md>)

### AI overview

The article argues that making and shipping dependable software requires collaboration across product, design, engineering, and DevOps. It values the varied judgment, expertise, trust, and shared understanding people bring, even when collaboration takes longer than delegating work to machines or an LLM.

### Source excerpt

From where I sit, figuring out what to build, building it, and shipping it are all part of the art of making software. Many disciplines have emerged through the years to facilitate this work: product, design, engineering, devops, etc. We need all these disciplines to make great, dependable software (granted, in different doses). Each brings different values and judgments; each sees things the others don't. And including all might mean going a bit slower. Human collaboration may seem less "efficient" than handing the work over entirely to the machines. But inefficiency may be the cost of collaborating with humans, rather than extracting an output from a machine. We gain not only from their judgment and expertise in a particular discipline, but from the relationship, trust, and shared understanding that blossoms from making something together. As the old proverb says: "If you want to go fast, go alone. If you want to go far, go together." Reformulated for today: If you want to go fast, go with the LLM. If you want to go far, go with your fellow humans. Reply via: Email - Mastodon - Bluesky

## The Fascinating World of Domains

DevFeed: [The Fascinating World of Domains](<https://devfeed.tech/articles/the-fascinating-world-of-domains-85055.md>)

Original publisher: [Read original article](<https://blog.jim-nielsen.com/2026/domains-article-on-wired/>)

Author: Jim Nielsen

Published: 2026-10-11T19:00:00Z

Content type: opinion

Language: en

Sources: [Jim Nielsen's Blog](<https://devfeed.tech/sources/jim-nielsen-s-blog.md>)

Topics: [Web](<https://devfeed.tech/topics/web.md>)

Tags: [domain](<https://devfeed.tech/tags/domain.md>), [icann](<https://devfeed.tech/tags/icann.md>), [internet](<https://devfeed.tech/tags/internet.md>)

### AI overview

The author reflects on a WIRED article about domain names, covering Verisign's .com registry, ICANN's 2026 application window, application costs and naming restrictions. The commentary also explores domains as portable online identities, citing Bluesky's use of domains as usernames.

### Source excerpt

Pete Millspaugh has a lovely article over on WIRED that peers into the world of domains. (If you're as interested in the esoteric details of domains as I am, follow Pete's writing at Dot Com Press.) You should just read the article, but here are a few things that stood out to me. The .com Registry Did you know who the registry for .com is? I didn't. The registry that owns .com, Verisign, makes a billion and a half dollars every year just by keeping the lights on. To Verisign's credit, the lights never go out: It reports 100 percent uptime over the past 28 years. It's a pretty slick business model, watching over a database of words and collecting annual renewal fees. Warren Buffett thought so too, investing in Verisign in 2012, when its stock price was about one-eighth what it is today. Why is it simultaneously surprising and not surprising that the company running .com makes billions and has 100% uptime over almost three decades? Maybe GitHub should reach out for some advice, lol. Buying Domains Is a Spy Thriller Apparently the last time you could buy generic top-level domains (gTLDs) was in 2012. So now that ICANN is providing another window of purchases in 2026 -- and nobody knows when another window will open -- there's a lot of interest in capitalizing on these moments for new gTLDs. most organizations [are] extremely secretive about their plans. One applicant from the last round tells me companies were flying around the world, meeting in person to avoid any risk of digital leaks, avoiding Gmail for fear of Google spying. Instead of email or video calls, she flew to London, then to Madrid. "We did it all in person. People got a little weird and scary, super paranoid." There's a certain irony to this -- people flying around the world to conduct business on owning a piece of the internet because they don't trust the internet. It appears the future of the internet is to be negotiated offline lol. More Domains = More Online Handles We haven't had new gTLDs since 2012.

## Getting off the Modernization Treadmill: Build accessible, resilient websites with web standards

DevFeed: [Getting off the Modernization Treadmill: Build accessible, resilient websites with web standards](<https://devfeed.tech/articles/getting-off-the-modernization-treadmill-77117.md>)

Original publisher: [Read original article](<https://blog.jim-nielsen.com/2026/talk-notes-modernization-treadmill/>)

Author: Jim Nielsen

Published: 2026-10-08T17:45:46.520742Z

Content type: opinion

Language: en

Sources: [Jim Nielsen's Blog](<https://devfeed.tech/sources/jim-nielsen-s-blog.md>)

Topics: [Web Development](<https://devfeed.tech/topics/web-development.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [performance-optimization](<https://devfeed.tech/topics/performance-optimization.md>), [Website](<https://devfeed.tech/topics/website.md>), [Legacy Modernization](<https://devfeed.tech/topics/legacy-modernization.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [css](<https://devfeed.tech/tags/css.md>), [develop](<https://devfeed.tech/tags/develop.md>), [html-css](<https://devfeed.tech/tags/html-css.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [modernization](<https://devfeed.tech/tags/modernization.md>), [performance](<https://devfeed.tech/tags/performance.md>), [software](<https://devfeed.tech/tags/software.md>), [talk](<https://devfeed.tech/tags/talk.md>), [technologies](<https://devfeed.tech/tags/technologies.md>), [the-web](<https://devfeed.tech/tags/the-web.md>)

### AI overview

Notes from Alexander Petros's Big Sky DevCon 2026 talk argue that public service websites should use HTML, CSS and JavaScript according to the web platform's strengths. Semantic HTML and core functionality that works without JavaScript can improve performance, accessibility and usability, especially for people using slower connections or devices. The talk also connects technology choices to values, contrasting user-focused public services with ad-driven engagement priorities.

### Source excerpt

My notes from this talk by Alexander Petros at Big Sky DevCon 2026. Alex starts by noting how "modernize" used to mean something along the lines of "update this thing that was made before I was born". But now "modernize" means something more like "update this thing from 5-10 years ago" (hence the framing of the talk, the "modernization treadmill"). Using a real-world example of an incredibly slow website that was required to access state-sponsored programs for welfare, Alex points out the disparity in conditions between those of us who make software and those who have to use them: The people who develop these websites are usually doing so on high-powered internet connections and high-powered devices, but they're not using them in the conditions that the people who most need those benefits are going to be. Then he shows a Reddit thread where somebody essentially posted, "I'm having problems with this website. I've been waiting for months for my application to go through. Any suggestions?" And one Reddit user responded, "The best thing you can do is go into the physical office, get a case worker, and your problems will be solved within the hour." The irony. I guess we've come full circle now. It used to be: "Don't talk to anybody. It's faster and more convenient to use the website!" But now it's: "Don't use the website. It's faster and more convenient to talk to somebody!" Have we failed at making websites? And is our failure, at least in part, rooted in the fact that we don't leverage the basic tools for making websites: HTML, CSS, and (in a distant third) JavaScript? Alex goes on to argue that the technologies of the web have an ideological bent and, if used as designed, can solve so many of the performance, accessibility, and usability issues that plague so many websites. The grain of the web's technologies are rooted in these values: User-friendly Backwards- and forwards-compatibility Long-term viability Universal accessibility Which means if you use them as inten

## Apple's App Icon HOA

DevFeed: [Apple's App Icon HOA](<https://devfeed.tech/articles/apple-s-app-icon-hoa-65447.md>)

Original publisher: [Read original article](<https://blog.jim-nielsen.com/2026/app-icon-hoa/>)

Author: Jim Nielsen

Published: 2026-10-06T17:43:43.009950Z

Content type: opinion

Language: en

Sources: [Jim Nielsen's Blog](<https://devfeed.tech/sources/jim-nielsen-s-blog.md>)

Topics: [User interface design](<https://devfeed.tech/topics/ui-design.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [macOS](<https://devfeed.tech/topics/macos.md>)

Tags: [app](<https://devfeed.tech/tags/app.md>), [apple](<https://devfeed.tech/tags/apple.md>), [icons](<https://devfeed.tech/tags/icons.md>), [ios](<https://devfeed.tech/tags/ios.md>), [macos](<https://devfeed.tech/tags/macos.md>)

### AI overview

The author compares Apple's move toward squircle app icons on iOS and macOS with homeowners' associations. The standardized style helps weaker icons fit the platform but can make distinctive icons look worse, raising the baseline while lowering the ceiling.

### Source excerpt

Louie Mantia has a great post about how app icons are converging towards the squircle on iOS and macOS. His post reads like a history. If you're wondering, "How did we get to a place where all app icons are becoming squircles?" Mantia's post answers that question by starting at the beginning. It's hard to walk away from Mantia's article without a sense of empathy for Apple's position, like "Oh ok, I get why they're doing what they're doing. It makes sense." Apple's direction is kind of a tacit acknowledgement to how most people are shipping app icons. Apple is "paving the cowpaths" as it were, because most app icons are just brand logos. Nowadays, it's these bland, big-business logo icons that make up a good chunk of iOS Home Screens and macOS Docks, instead of the beautiful, illustrative app icons that used to dominate our devices. So many app icons are just logos in a squircle, so Apple made tools like the Icon Composer and glass effects to help make that approach look good by default. Apple is helping most people most of the time make app icons that don't suck. [Apple is making] it easier for all apps to fit in on the platform, especially apps built by designers and developers who aren't familiar with how to make an icon that looks great next to first-party icons. The net effect is: some of the platform's best icons look worse, while some of the platform's worst icons look better. In other words, this new approach raises the floor but it also lowers the ceiling. The thought that came to mind as I read Mantia's post was, "This reminds me of HOAs." I grew up in a neighborhood where anyone could do anything with their homes and yards, so you had this eclectic mix throughout the neighborhood -- everything from "Wow, that house is so unique!" to "That thing is a dump." Somewhere along the way HOAs became more prevalent (in my neck of the woods), where all the houses in a neighborhood have to meet a certain standard -- and so they all start to look the same. It keeps the

## "I'm Embarrassed on Behalf of the Tech Industry"

DevFeed: ["I'm Embarrassed on Behalf of the Tech Industry"](<https://devfeed.tech/articles/i-m-embarrassed-on-behalf-of-the-tech-industry-64663.md>)

Original publisher: [Read original article](<https://blog.jim-nielsen.com/2026/embarrassed-by-tech/>)

Author: Jim Nielsen

Published: 2026-10-04T19:00:00Z

Content type: opinion

Language: en

Sources: [Jim Nielsen's Blog](<https://devfeed.tech/sources/jim-nielsen-s-blog.md>)

Topics: [Business, Industry, Usability, User Experience, User Research, Web Strategy](<https://devfeed.tech/topics/business-industry-usability-user-experience-user-research-web-strategy.md>), [Community, Industry, State of the Web, Web Strategy](<https://devfeed.tech/topics/community-industry-state-of-the-web-web-strategy.md>)

Tags: [industry](<https://devfeed.tech/tags/industry.md>), [tech](<https://devfeed.tech/tags/tech.md>)

### AI overview

The author reflects on how difficult and confusing digital technology can be for people outside the tech industry, and expresses embarrassment over the industry's collective failure to make things work well for them.

### Source excerpt

That's something Ben Thompson said a recent episode of Dithering. He was referring to how he felt while trying to help his mom get control of her digital life. Everything was just too hard and convoluted and he felt embarrassed as someone who works in tech. That very same evening, I randomly got this text from a family member. I hear this a lot from family and friends who sit outside tech. "Nothing works." "Everything is hard to use." "I can't make sense of this." And to them I am a representative, a connection, to this pain in their lives. And I, too, am embarrassed on behalf of the tech industry -- by our collective failure. Reply via: Email - Mastodon - Bluesky

## Dear Software Makers

DevFeed: [Dear Software Makers](<https://devfeed.tech/articles/dear-software-makers-62924.md>)

Original publisher: [Read original article](<https://blog.jim-nielsen.com/2026/dear-software-makers/>)

Author: Jim Nielsen

Published: 2026-09-30T19:00:00Z

Content type: opinion

Language: en

Sources: [Jim Nielsen's Blog](<https://devfeed.tech/sources/jim-nielsen-s-blog.md>)

Topics: [A/B Testing](<https://devfeed.tech/topics/a-b-testing.md>)

### AI overview

Drawing on Marques Brownlee's concerns about YouTube video variants, the author argues that software makers should favor creative work and repeated releases over optimizing every decision for metrics such as engagement and efficiency.

### Source excerpt

Marques Brownlee just released a video essay titled "Dear YouTube". I loved it. He talks about how YouTube is going to start shipping this new feature where makers can essentially publish different "variants" of their videos and see which performs best (an A/B test). Which immediately begs a lot of questions. Brownlee voices his: If I'm watching a video, do I know if it's part of one of these A/B tests? If I'm reading the comments of a video, how do I know I saw the same thing as another commenter? How do linked timestamps work? It's pretty wild when you think about it. I mean, imagine sending someone a link, "Check out this cool video!" And at that point you're basically crossing your fingers, "I hope they see the same thing I did..." Marques says he spoke to some YouTube engineers about these questions and they didn't really have answers. They were kind of just like, "We don't know -- yolo! This'll ship soon." So his video is a kind of plea to YouTube creators everywhere: Don't use this feature! There's this sort of unspoken rule of community on YouTube, that like we're all having this same experience together -- we're all watching the same video. That is what makes it a cultural phenomenon is that we all saw the same thing [...] so letting people put up two or three different videos of the same thing at the same time kind of fundamentally breaks that, which doesn't feel right. I agree, 100%. Brownlee goes on to make a lot of great points in the video that, I think, can be applicable to making software as well. A few that stood out: The skill of being a "creator" is not about maximizing views, retention, etc. It's about finding creative ways to share stories, teach concepts, explore ideas, etc. Views, retention, etc. are all downstream of that. Making (and finishing) something over and over and over is a better use of your time than making one thing and then trying all kinds of variants and obsessing over their varied performance. When you focus on optimizing, you end u

## Using CLIP embeddings to add visual search and related-icon discovery to icon galleries

DevFeed: [Using CLIP embeddings to add visual search and related-icon discovery to icon galleries](<https://devfeed.tech/articles/vlm-enhanced-metadata-for-my-icon-galleries-62177.md>)

Original publisher: [Read original article](<https://blog.jim-nielsen.com/2026/icon-galleries-vlm/>)

Author: Jim Nielsen

Published: 2026-09-29T19:00:00Z

Content type: article

Language: en

Sources: [Jim Nielsen's Blog](<https://devfeed.tech/sources/jim-nielsen-s-blog.md>)

Topics: [Image](<https://devfeed.tech/topics/image.md>), [Fine-tuning](<https://devfeed.tech/topics/fine-tuning.md>)

Tags: [embedding](<https://devfeed.tech/tags/embedding.md>), [embeddings](<https://devfeed.tech/tags/embeddings.md>), [llm](<https://devfeed.tech/tags/llm.md>), [proof-of-concept](<https://devfeed.tech/tags/proof-of-concept.md>), [vlm](<https://devfeed.tech/tags/vlm.md>)

### AI overview

The author explores using CLIP image embeddings to support artwork-level search and find related icons in icon galleries. The post describes comparing embeddings and building a proof of concept with a script and local HTML pages.

### Source excerpt

Confession: I got nerd-sniped by Sam Henri Gold's request for my icon galleries: I'd like to humbly request artwork-level searching in macosicongallery.com What follows is a train-of-thought blog post as I play with what an implementation might look like. I've actually long-wanted something like this, e.g. let me search for "coffee" and show me all icons that have some depiction of coffee in them. Similarly, I've wanted some kind of "related" representation for icons. I have this today via existing metadata, e.g. "Show me other icons in the category 'Productivity'" or "Show me other icons tagged as 'orange'". But I've wanted a more robust representation of this, so if you were looking at an icon that had a microphone in it, the site would say "Here are other icons that also have microphones in them." And the relationship would be rich/smart enough to know that "microphone" was meant broadly, i.e. dynamic mics, condenser mics, ribbon mics, etc. So how would you do this? I could go through every icon one-by-one and classify/tag any attribute of its design that comes to mind, but that would take ages! Seems like a good use case for a vision model. Trying CLIP First, I'll look at Sam's suggestion: run every image through CLIP. I'm not familiar with CLIP so I start with a little research: What is it? How would I use it? And most importantly: is it free/open (because I ain't spending a ton of money to send my thousands of icon PNGs to an AI provider via their API)? Ok, so CLIP will take an image and spit back an embedding (basically a bunch of numbers representing features of the image). When you do it with multiple images, you can then compare those embeddings to see what the model considers similar (and, if you like, set a threshold for what constitutes a "match"). After getting a sense of the task in front of me, I work with the LLM to come up with a proof of concept. I don't need to fit this into my existing site. I just want to make one-off HTML pages where I can fee

## Humane Interfaces

DevFeed: [Humane Interfaces](<https://devfeed.tech/articles/humane-interfaces-60670.md>)

Original publisher: [Read original article](<https://blog.jim-nielsen.com/2026/humane-interfaces/>)

Author: Jim Nielsen

Published: 2026-09-27T19:00:00Z

Content type: opinion

Language: en

Sources: [Jim Nielsen's Blog](<https://devfeed.tech/sources/jim-nielsen-s-blog.md>)

Topics: [User Experience](<https://devfeed.tech/topics/user-experience.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [Design system](<https://devfeed.tech/topics/design-system.md>), [enterprise certificate authority certificates](<https://devfeed.tech/topics/enterprise-certificate-authority-certificates.md>), [free software](<https://devfeed.tech/topics/free-software.md>)

Tags: [growth](<https://devfeed.tech/tags/growth.md>), [humane](<https://devfeed.tech/tags/humane.md>), [interfaces](<https://devfeed.tech/tags/interfaces.md>), [technology](<https://devfeed.tech/tags/technology.md>), [user](<https://devfeed.tech/tags/user.md>)

### AI overview

The author argues that humane interfaces and technology respect users' needs and frailties rather than exploiting them through growth tactics. Such technology should rely on users' free choice, not impulse, addiction, or imposition.

### Source excerpt

So there I am reading Unsung when I come across this quote from Jef Raskin: An interface is humane if it is responsive to human needs and considerate of human frailties. This articulation perfectly captures why I recoil at modern "growth tactics" in user interfaces and experiences: they are designed to exploit human frailties, not be considerate of them. Stated again: a humane interface -- or a humane system, even a humane technology -- is considerate of human frailties. It acknowledges they exist and works with them, rather than taking advantage of them. Humane technology does not rely on impulse, addiction, or imposition to survive. It survives purely on the free choice of its user. You choose to use it because you have the freedom not to. Reply via: Email - Mastodon - Bluesky

## Using an LLM to Automate the Process of Archiving New macOS App Icons

DevFeed: [Using an LLM to Automate the Process of Archiving New macOS App Icons](<https://devfeed.tech/articles/using-an-llm-to-automate-the-process-of-archiving-new-macos-app-icons-59838.md>)

Original publisher: [Read original article](<https://blog.jim-nielsen.com/2026/faster-app-icon-retrieval/>)

Author: Jim Nielsen

Published: 2026-09-25T17:06:42.164790Z

Content type: article

Language: en

Sources: [Jim Nielsen's Blog](<https://devfeed.tech/sources/jim-nielsen-s-blog.md>)

Topics: [Automation](<https://devfeed.tech/topics/automation.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [macOS](<https://devfeed.tech/topics/macos.md>)

Tags: [automation](<https://devfeed.tech/tags/automation.md>), [image](<https://devfeed.tech/tags/image.md>), [llm](<https://devfeed.tech/tags/llm.md>), [macos](<https://devfeed.tech/tags/macos.md>)

### AI overview

The author describes using an LLM to automate extracting and archiving 76 macOS application icons. The workflow locates the largest available icon image, avoids upscaling smaller versions, and saves the results as PNG files, reducing a tedious manual process.

### Source excerpt

Whenever a new version of macOS drops, I find myself archiving the new app icons for my macOS icon gallery. In the past, the work to do this was a bit tedious. First, I'd find the app in the "Applications" folder (or elsewhere on the Mac), right click and choose "Get Info": Right-click the app icon in the Get Info pane and choose "Copy": Open the Preview app and go "File -> New from Clipboard": This gets me the app icon file with a variety of sizes (the 1024-pixel version is the one I want). From here, I go "File -> Export...", choose "PNG", and name the file as the app name, lowercased, hyphenated -- e.g. "app-store.png" (I do this for automation purposes not relevant here). Doing that for every Apple-supplied app in the OS can get tiring. It's often upwards of 75+ icons. "This seems like the perfect task for an LLM," I thought. So I hastily wrote a prompt to see if it could do it. And it did -- sort of, after a little coaching. On the first try it found an app's .icns file, grabbed the 256x256 version, upscaled it to 1024x1024, and saved it. So I scolded it, "No, no. NEVER upscale an image. Always find the biggest one. I can get the 1024 version myself from the 'Get info' pane, so surely you can find that size somewhere." It came back dutifully, having found the right image, and said it would never upscale again. Satisfied it could do what I wanted, I worked on creating a list of all the apps whose artwork I wanted to archive. Then I gave that list to the LLM and said, "Do your thing." And it worked! It was kind of wonderful. Saved me a ton of time. 76 app icons found, extracted, and saved in much less time than it would've taken me to do this "by hand". Reply via: Email - Mastodon - Bluesky

## A Google AI Hallucination Invents a Simpsons Quote

DevFeed: [A Google AI Hallucination Invents a Simpsons Quote](<https://devfeed.tech/articles/a-great-story-capturing-the-essence-of-being-online-in-2026-57871.md>)

Original publisher: [Read original article](<https://blog.jim-nielsen.com/2026/online-in-2026/>)

Author: Jim Nielsen

Published: 2026-09-21T19:00:00Z

Content type: opinion

Language: en

Sources: [Jim Nielsen's Blog](<https://devfeed.tech/sources/jim-nielsen-s-blog.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [Google](<https://devfeed.tech/topics/google.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-hallucination](<https://devfeed.tech/tags/ai-hallucination.md>), [article](<https://devfeed.tech/tags/article.md>), [google](<https://devfeed.tech/tags/google.md>), [language](<https://devfeed.tech/tags/language.md>), [llm](<https://devfeed.tech/tags/llm.md>)

### AI overview

The article recounts how Google's AI falsely attributed an original Bryan Cantrill phrase to The Simpsons, then reversed its answer when challenged. It uses the incident to illustrate an AI hallucination and the uncertainty it can create about the origin of ideas.

### Source excerpt

I made a note of it, but Bryan Cantrill wrote a post about the ex-Anthropic employee who pegged the probability of AI killing humanity in the next decade at >10%. The article is a good one and you should read it, but what I want to capture here is a side story from Cantrill on the Oxide and Friends podcast where he talks about how proud he was of this phrase from his post: "These ghoulish claims strike brazenly at the hearth...". He notes that someone online commented on that phrase, saying it sounded like a mix of classic literature and a line from The Simpsons. Amused, Cantrill says he came up with the line all by himself, so he knew it wasn't a classic literature reference nor a line from The Simpsons. But just to be sure, he Google'd it: "These ghoulish claims strike brazenly at the hearth" with "The Simpsons" tagged on to the end. To his surprise, Google's AI told him that the line was, in fact, a line from The Simpsons. Here's Google's response (as reported by Cantrill): During the Springfield mayoral debate on Channel 6, Sideshow Bob dramatically delivers the line "these ghoulish claims strike brazenly at the hearth of Springfield" while turning the debate against Mayor Joe Quimby. Instead of denying his criminal history, Bob exploits Quimby's record and boldly tells the audience they secretly long for a cold-hearted Republican to rule them like a king. (Here's my homemade graphic for illustration purposes.) Cantrill was astonished. Not knowing the episode enough by heart to discern whether this claim was true, he had a little bit of a panic attack: If I am having what I feel to be original thoughts that are, in fact, just Simpsons lines regurgitating from 30 years ago, that's troubling [...] How am I not an LLM? So he set out to find the truth. He finds the episode and watches it, but doesn't hear the line. But what if the episode he watched was an edited version and the full-length one is out there somewhere? He's gotta get to the bottom of this. So he goes bac

## Do You Prefer Artificial?

DevFeed: [Do You Prefer Artificial?](<https://devfeed.tech/articles/do-you-prefer-artificial-55208.md>)

Original publisher: [Read original article](<https://blog.jim-nielsen.com/2026/who-wants-artificial/>)

Author: Jim Nielsen

Published: 2026-09-18T19:00:00Z

Content type: opinion

Language: en

Sources: [Jim Nielsen's Blog](<https://devfeed.tech/sources/jim-nielsen-s-blog.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Claude](<https://devfeed.tech/topics/claude.md>)

Tags: [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [availability](<https://devfeed.tech/tags/availability.md>), [claude](<https://devfeed.tech/tags/claude.md>), [convenience](<https://devfeed.tech/tags/convenience.md>), [cost](<https://devfeed.tech/tags/cost.md>)

### AI overview

The essay argues that artificial intelligence should be understood as a useful alternative with trade-offs in cost, convenience, and availability, rather than a substitute for human intelligence.

### Source excerpt

"Artificial" things can get a bad rap next to their counterparts, but they have their place. For example, artificial light (i.e. not from the sun)? Super useful, especially at night. And when it comes to skiing, I'll take artificial snow if I have to. Beats no snow. Artificial isn't necessarily inferior in all cases, everywhere, all the time. But it is optimized for different values. For example: Artificial grass (i.e. turf) is great for certain contexts, but I don't want a golf course of artificial grass. Artificial flowers are great for certain scenarios, but I don't want them at my wedding. Artificial flavoring is yummy (love me some peach rings), but I'd prefer a real peach pie over one with artificially flavored filling. Artificial is an alternative. It's understood as a trade-off, not a substitute. You trade the real for the artificial when you're concerned about attributes like cost, convenience, and availability. Which brings me to "artificial" intelligence: surely a trade-off, not a substitute. Ain't nothing like the real thing. These labs should consider ripping off (cause they're good at that) Mastercard's old tagline: "There's some intelligence money can't buy; for everything else, there's Claude." Reply via: Email - Mastodon - Bluesky

## Preserving Netlify Analytics Data Beyond 30 Days

DevFeed: [Preserving Netlify Analytics Data Beyond 30 Days](<https://devfeed.tech/articles/preserving-netlify-analytics-data-beyond-30-days-49238.md>)

Original publisher: [Read original article](<https://blog.jim-nielsen.com/2026/preserving-netlify-analytics-data/>)

Author: Jim Nielsen

Published: 2026-09-13T19:00:00Z

Content type: article

Language: en

Sources: [Jim Nielsen's Blog](<https://devfeed.tech/sources/jim-nielsen-s-blog.md>)

Topics: [Val Town](<https://devfeed.tech/topics/val-town.md>), [Netlify](<https://devfeed.tech/topics/netlify.md>), [Automation](<https://devfeed.tech/topics/automation.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>), [data](<https://devfeed.tech/topics/data.md>), [Code](<https://devfeed.tech/topics/code.md>), [Database](<https://devfeed.tech/topics/database.md>), [Website](<https://devfeed.tech/topics/website.md>)

Tags: [automation](<https://devfeed.tech/tags/automation.md>), [code](<https://devfeed.tech/tags/code.md>), [database](<https://devfeed.tech/tags/database.md>), [netlify](<https://devfeed.tech/tags/netlify.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>), [storage](<https://devfeed.tech/tags/storage.md>), [traffic](<https://devfeed.tech/tags/traffic.md>), [val-town](<https://devfeed.tech/tags/val-town.md>), [websites](<https://devfeed.tech/tags/websites.md>)

### AI overview

The author explains how Val Town is used to preserve Netlify Analytics data beyond its 30-day retention period. A scheduled Val fetches recent analytics, stores them in SQLite, and uses scoped code, secrets, storage, and automation primitives to keep the task isolated from unrelated work.

### Source excerpt

I've got Netlify Analytics turned on for a few of my websites. I use it send myself a little daily digest that alerts me when folks link to my writing, be it an individual sending me a few referrals, a newsletter sending me a few hundred, or Hacker News sending me thousands. But sometimes I want to know more than, "What happened with traffic in the last 24 hours?" Sometimes I want to know, "What happened with traffic in the last month?" I can log in to Netlify to answer that question. Sometimes I want to know, "What happened with traffic in the last six months?" Netlify doesn't have an answer for that because they only store the last thirty days of traffic data. I've known about this limitation for years and always thought, "I really should just start saving that data for myself." But, you know, laziness. How bad do I really want it? The answer, it seems, was "I only want it if it's _easy_". Enter Val Town. Val Town makes this kind of task easy. Each "Val" is it's own little bucket of scoped computing primitives for just such a task: Code (run a script that fetches data) Secrets (securely store my Netlify access token) Storage (my own little SQLite database for persisting data over time) Automation (run this task every 30 days) All of this might seem like overkill for a single-script task like mine. But I like it. The scoped nature of each of these primitives makes composition easy without the kind of entanglement I'd have to fight to keep isolated if I were co-locating this task with other small tasks. I don't want to think about a shared schema for this task and whatever other tasks I might think of in six months. I don't want to have to reason about evolving an architecture and maintaining a codebase of miscellaneous, unrelated tasks. Vals are perfect for this. So the way I have this setup is: run the .ts file every 30 days which fetches the last 30 days worth of analytics data from Netlify and stores it in SQLite. (You can see my Val here.) At that point, I have

## Links as Technical and Cultural Foundations of the Web

DevFeed: [Links as Technical and Cultural Foundations of the Web](<https://devfeed.tech/articles/an-ode-to-links-49237.md>)

Original publisher: [Read original article](<https://blog.jim-nielsen.com/2026/ode-to-links/>)

Author: Jim Nielsen

Published: 2026-09-10T19:00:00Z

Content type: article

Language: en

Sources: [Jim Nielsen's Blog](<https://devfeed.tech/sources/jim-nielsen-s-blog.md>)

Topics: [Web](<https://devfeed.tech/topics/web.md>), [Website](<https://devfeed.tech/topics/website.md>)

Tags: [links](<https://devfeed.tech/tags/links.md>), [the-web](<https://devfeed.tech/tags/the-web.md>)

### AI overview

The article distinguishes URLs as technical structures from links as cultural connections, examining how people save, share, follow, and use links. It concludes that links form the web and shape how people relate to it.

### Source excerpt

A URL is a technical thing: a hostname, a path, a port, an origin, some query parameters, etc. But a link is a cultural thing: an invitation, a citation, a gift, a shortcut, a connection. All from a simple idea: here's a thing that points to another thing, off you go! We've built an entire culture around links. Just look at the language we use for them: "Drop me a link." "Send me the link." "Got a link?" "Link in bio." "Link in the description." "Here's the link." "Don't click that link." "Sorry, wrong link." Or even just, "Link?" Our language spans the spectrum of meaning, from one end to the other: We save links. We lose links. We share links. We hide links. We send links. We receive links. We collect links. We discard links. We open links. We close links. We add links. We remove links. We make links. We break links. We shorten links. We expand links. We follow links. We ignore links. We click links. We don't click links. We link in. We link out. We make links. Links make the web. The web makes Us. Reply via: Email - Mastodon - Bluesky

## The Bulldozing of an Interface

DevFeed: [The Bulldozing of an Interface](<https://devfeed.tech/articles/the-bulldozing-of-an-interface-49233.md>)

Original publisher: [Read original article](<https://blog.jim-nielsen.com/2026/bulldoze-ui/>)

Author: Jim Nielsen

Published: 2026-09-08T19:00:00Z

Content type: opinion

Language: en

Sources: [Jim Nielsen's Blog](<https://devfeed.tech/sources/jim-nielsen-s-blog.md>)

Topics: [interface](<https://devfeed.tech/topics/interface.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [interface](<https://devfeed.tech/tags/interface.md>), [interface-design](<https://devfeed.tech/tags/interface-design.md>), [refactor](<https://devfeed.tech/tags/refactor.md>)

### AI overview

An interface cannot be fully evaluated by comparing static images before and after a redesign. Interactive details, accumulated design decisions, and real-world use cases can be lost during large refactors, including AI-enabled refactors, without being noticed.

### Source excerpt

Marcin Wichary has a lovely article titled "Photoshop's challenges with focus, pt. 2". If you're into the minutiae of interface design, this is a good 'un. It perfectly illustrates how impossible it is to try and compare two interfaces side by side as static images. What matters in an interface is how it works, i.e. how you interface with it. And when you bulldoze an interface to build a new one, comparing the old vs. new side-by-side to make sure you "captured everything" is a lie. It's never obvious what has been lost because the interactive pieces are missing from the static images -- and those are what matter most because it's how the feature works! I've found this to be true a lot as of late. Lots of tiny details that were meticulously crafted over years with specific rationales tied to real-world use cases, all completely bulldozed in a giant refactor. (All made possible by the great omniscient power of AI.) Few notice what's gone because few can see what's being lost in the first place. Reply via: Email - Mastodon - Bluesky

## Uptime Percentages Are a Poor Public Interface for Communicating Service Reliability

DevFeed: [Uptime Percentages Are a Poor Public Interface for Communicating Service Reliability](<https://devfeed.tech/articles/can-we-stop-with-the-uptime-percentages-49240.md>)

Original publisher: [Read original article](<https://blog.jim-nielsen.com/2026/stop-with-the-uptime-percentage/>)

Author: Jim Nielsen

Published: 2026-09-03T19:00:00Z

Content type: opinion

Language: en

Sources: [Jim Nielsen's Blog](<https://devfeed.tech/sources/jim-nielsen-s-blog.md>)

Topics: [reliability-engineering](<https://devfeed.tech/topics/reliability-engineering.md>), [interface](<https://devfeed.tech/topics/interface.md>), [service](<https://devfeed.tech/topics/service.md>)

Tags: [downtime](<https://devfeed.tech/tags/downtime.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [interface](<https://devfeed.tech/tags/interface.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [uptime](<https://devfeed.tech/tags/uptime.md>)

### AI overview

The article argues that uptime percentages such as 99.9% and 99.99% are difficult for general audiences to interpret. It proposes showing the amount of time a service was affected alongside the percentage so people can understand downtime more directly.

### Source excerpt

I was reading Jason Gorman's article "The Wall Confronting Reliable Coding Agent Autonomy" and he says: the journey from 90% to 99% reliability is just as hard as it was to get to 90%. And from 99% to 99.9% is just as hard again. This stood out, as I've been experiencing more and more "downtime" in my day-to-day work. GitHub's down. CI's down. AI's down. Slack's down. Downtime's going mainstream! More and more I find myself visiting service status pages, where I'm confronted with a wall of colors and numbers like this: 100%? 99.72%? 99.09%? 98.98%? Those don't all seem so different or bad? I mean, those are all an A in grade school. Then I have to remind myself of Jason's point and re-interpret the numbers, which is more like reading earthquake measurements. The difference between a 6.2 and a 7.8 might not seem that big, but it represents a massive difference in magnitude. Uptime percentages have a similar problem: 99.9% and 99.99% look pretty much the same, but the latter is 10x less! Infrastructure people understand this. They even have a shorthand for it: two nines, three nines, four nines. They intuitively grasp the difference because they swim in these numbers every day. But the audience for status pages isn't just infra people anymore. It's increasingly everybody. I understand the math is straightforward. Percent uptime is a good metric for those in the industry. But it's a lousy interface for people who don't care about the best way to measure infrastructure reliability in a standardized, reliable, compliant way. And status pages are the public interface for understanding the reliability of a service. I just want to know, "Dude, how much have you been down lately? Seems like a lot..." So how about, and I'll just throw this out there, instead of: GitHub Actions: 98.31% uptime. We say something like: GitHub Actions: 12 hours affected in the last 30 days (98.31% uptime). One requires you to understand the nonlinear significance of numbers near 100%. The other requ

## Why People Rely on Systems They Know Are Flawed

DevFeed: [Why People Rely on Systems They Know Are Flawed](<https://devfeed.tech/articles/nobody-believes-it-everybody-does-it-49235.md>)

Original publisher: [Read original article](<https://blog.jim-nielsen.com/2026/nobody-believes-it-everybody-does-it/>)

Author: Jim Nielsen

Published: 2026-09-01T19:00:00Z

Content type: opinion

Language: en

Sources: [Jim Nielsen's Blog](<https://devfeed.tech/sources/jim-nielsen-s-blog.md>)

Topics: [data](<https://devfeed.tech/topics/data.md>), [trust](<https://devfeed.tech/topics/trust.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>), [Users](<https://devfeed.tech/topics/users.md>), [Website](<https://devfeed.tech/topics/website.md>)

### AI overview

This essay examines how people and organizations continue relying on systems they recognize as flawed. It discusses Flash-based marketing, data-driven discount schemes, KPIs, performance reviews, standardized tests, terms of service, privacy notices, cookie banners, and surveys.

### Source excerpt

Speaking of things we know individually, but let slide collectively, here's Jeremy Keith talking about how we all used Flash: Remember when almost every website had a Flash intro? Everyone knew they were annoying and uneccessary, but everyone else was doing it. And here's John Gruber writing about his experience with those marketing schemes that trade your personal information for a discount: The marketing shitbirds who press for these schemes [...] do so by pointing to data that shows that they do convert some number of users. "It works" they claim, pointing to data. What doesn't show up in their data are interactions like mine. They don't have analytics that measure that I now consider their website an antagonist to avoid at all costs. There's a funny thing about us humans: we place trust in systems that our own individual experience tells us are flawed. For example: KPIs: we know metrics get optimized at the expense of reality, but leadership treats dashboards as a reflection of truth. Performance reviews: we know they're political and subjective, yet companies leverage them for promotions, compensation, even firings. Standardized testing: we know tests don't measure real ability, but institutions rely on them for admissions, funding, and rankings. Terms of Service: nobody reads them, but the legal system acts like informed consent is given. Privacy notices / cookie banners: everybody clicks through them mindlessly while companies claim transparency and compliance. This behavior is best summed up by Scott Berkun in Confessions of a Public Speaker: I know I avoid most surveys I'm asked to fill out, as do many of you, which begs the question why we place so much faith in survey-based research. What's convenient at scale becomes a substitute for the reality we experience as individuals (because scale excludes the parts of reality it cannot conveniently capture). Reply via: Email - Mastodon - Bluesky

## My Experience Has Nuance, Yours Is a Data Point

DevFeed: [My Experience Has Nuance, Yours Is a Data Point](<https://devfeed.tech/articles/my-experience-has-nuance-yours-is-a-data-point-49236.md>)

Original publisher: [Read original article](<https://blog.jim-nielsen.com/2026/nuance-for-me-none-for-you/>)

Author: Jim Nielsen

Published: 2026-08-31T19:00:00Z

Content type: opinion

Language: en

Sources: [Jim Nielsen's Blog](<https://devfeed.tech/sources/jim-nielsen-s-blog.md>)

Topics: [data](<https://devfeed.tech/topics/data.md>), [Users](<https://devfeed.tech/topics/users.md>), [interface](<https://devfeed.tech/topics/interface.md>), [recommendation systems](<https://devfeed.tech/topics/recommendation-systems.md>)

Tags: [data](<https://devfeed.tech/tags/data.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [interface](<https://devfeed.tech/tags/interface.md>), [netflix](<https://devfeed.tech/tags/netflix.md>), [recommendations](<https://devfeed.tech/tags/recommendations.md>), [users](<https://devfeed.tech/tags/users.md>)

### AI overview

An opinion piece argues that simple interface feedback signals, such as thumbs-up ratings, can misrepresent users' nuanced experiences. It cautions product teams against treating aggregate engagement data as objective evidence without considering values, context, and long-term direction.

### Source excerpt

Eric Bailey has a fun little post about how we need more than a few icons to express the nuance of our shared human experience. For example, he suggests Netflix provide some feedback buttons to indicate the kinds of experiences we all share consuming and rating media: "Just because I expressed interest in this show does not mean I want to be inundated with recommendations for its genre" "Disregard that I pressed 'thumbs up' my cat walked over the keyboard" "I am making bad choices and hatewatching this" What's great about the examples in Eric's post is how familiar they are. We can read them and laugh because we've had the same thought -- "I'm pressing 'thumbs up' here, but what I really mean is..." We know when we click that button that it's a reductive expression of our experience that'll be erroneously interpreted, but we do it anyway. As Bryan Cantrill shared from his experience: There's no way to indicate, "I'm engaging with this, but I hate myself for doing it." I need another mouse button that is like, "I'm clicking on this, but I'm rage clicking on it and for my own mental health could you not drag more of this in front of me please?" We know these feedback mechanisms are often a misrepresentation of our actual experience. Yet we turn around in our professional contexts and see numbers like "142,432 users gave this a 'thumbs up'" and we forget everything we knew about our own individual experience with these systems. We make it mean what we want it to mean, what's convenient for measurement and reporting e.g. "Wow, what a great insight about our offerings! Let's restructure our entire catalog around this new, objective, (pseudo)scientific fact that so many people obviously like this thing!" We reduce the experiences of others to mere data, but grant ourselves exemption from such oversimplifications. Where's the conversation around: Values, e.g. "Should we provide more of this? We can say no to the data..." Nuance, e.g. "What do people really mean when they click

## A Calendar View For My Blog

DevFeed: [A Calendar View For My Blog](<https://devfeed.tech/articles/a-calendar-view-for-my-blog-49231.md>)

Original publisher: [Read original article](<https://blog.jim-nielsen.com/2026/blog-calendar-view/>)

Author: Jim Nielsen

Published: 2026-08-27T19:00:00Z

Content type: article

Language: en

Sources: [Jim Nielsen's Blog](<https://devfeed.tech/sources/jim-nielsen-s-blog.md>)

Topics: [User interface design](<https://devfeed.tech/topics/ui-design.md>)

### AI overview

The author describes building and shipping a calendar view for a personal blog. The view visualizes posting patterns over time, with clickable days that reveal posts and indicators for posts that reached Hacker News.

### Source excerpt

807 blog posts across 14 years. That's how much I've published on my blog at the time of this writing. And here's the question I've been turning over in my mind: "How do I convey that kind of volume across time in a more interesting way than a mere reverse-chronological list?" I'm not hating on reverse-chronological lists. I love my list view. I use it all the time to find stuff I've written. But it's only one way of navigating and digesting all my posts. "What would be another way?" Surely there are many answers to that question. And I'll probably be exploring them more and more over time. But I had an idea for a new view that I built out and shipped: my calendar view. It's also just a reverse-chronological view, but it's meant to convey a sense of posting patterns through time more than it is meant to be a good browsing experience of content. The view is simple: a calendar view of days in each year, and if I posted on a day, it gets a circle (bonus: if a post hit hacker news, it gets an orange square instead). You can click on the dots to see the names of the posts from that day (and follow the link to them, but really this view is basically to scratch an itch of mine. Because you can just make stuff for yourself, and that's what I've done here. And now I'm writing about it because that means I get another little circle for today! Good job, Jimbo. Check it out Reply via: Email - Mastodon - Bluesky

[Next page](<https://devfeed.tech/sources/jim-nielsen-s-blog.md?cursor=WyIyMDI2LTA4LTI3VDE5OjAwOjAwKzAwOjAwIiwgIjZhYzYyZmNjLTY4MmYtNGZiYS1hN2FmLTFmYjFiZTE1MmU5ZSJd>)