A shift is happening in Design… New tools. New workflows. New capabilities. Because… → As production gets automated → Thinking becomes more valuable → Creativity becomes the new premium That’s why I’m speaking to Shamus Scott Grubb on The Design of Everyday People Livestream. We’re diving deep into: 1. How AI separates design from production 2. What skills actually matter in this new reality 3. How to position yourself on the right side

Every technology with real staying power goes through waves of adoption. The first wave attracts the early experimenters – the ones who can sense the future before it’s evenly distributed. The second picks up the enterprises that’ve felt enough pain to seek out something better. The third comes when the rest of the world catches up, usually because the ground itself has shifted and the old tools can no longer do the job. GraphQL is now entering that third wave. Most people still describe GraphQL as an alternative to REST. That was true in 2015. What’s happening today is different. In the era of LLMs and autonomous agents, GraphQL isn’t

AI has changed the texture of design. We’re not designing for people alone anymore, we’re designing with/for intelligence. That changes everything. I’m obviously not the only person thinking about how Design frameworks evolve. Recent research has started reframing what this looks like. Adam Fard calls it “AI-First Design Thinking.” Weisz, He, and Muller (2024) propose six design principles for generative AI that move beyond the empathy-prototype-test loop: Source: Design Thinking for AI: The 5-Stage Framework Every Builder Needs

I recently attended the Enterprise UX conference in Amersfoort. The presentations made it very clear that successful AI integration requires big changes in how companies work and how we build systems. The main message was: AI is not just a new tool; it forces us to change our basic rules for design and data. Source: New Rules for Enterprise UX and AI — jasha.eu

Generative UI and the Ephemeral Interface This week, Google debuted their Gemini 3 AI model to great fanfare and reviews. Specs-wise, it tops the benchmarks. This horserace has seen Google, Anthropic, and OpenAI trade leads each time a new model is released, so I’m not really surprised there. The interesting bit for us designers isn’t the model itself, but the upgraded Gemini app that can create user interfaces on the fly. Say hello to generative UI. I will admit that I’ve been skeptical of the notion of generative user interfaces. I was imagining an app for work, like a design app, that would rearrange itself depending on the task at

In one of the most popular episodes yet, Vitaly Friedman talked about what’s next for AI design patterns (https://www.dive.club/deep-dives/vita…) . In that episode he frequently referenced Shape of AI (https://www.shapeof.ai/) which is an incredible database of AI design patterns.So I wanted to get to the source and go deep with the creator [Emily Campbell]( / emmiecampbell ) to learn how to design great AI experiences. Because she’s studied AI products more than just about anyone I’ve ever seen 👀

I find it’s always important to examine why you made a mistake. The worst mistake I ever made was reading “Bitcoin: A Peer-to-Peer Electronic Cash System” in January of 2009, thinking “cool math toy, maybe someone will turn it into something useful someday” and moving on. My most recent mistake, however, was not realizing that software development would be the first field to be transformed by agentic AI. I always assumed it would be the last. Let’s examine why that was. Source: Why Software Development Fell to AI First

A Month of Chat-Oriented ProgrammingOr when did you last change your mind about something?Nick Radcliffe. 12th November 2025. TL;DR: I spent a solid month “pair programming” with Claude Code, trying to suspend disbelief and adopt a this-will-be-productive mindset. More specifically, I got Claude to write well over 99% of the code produced during the month. I found the experience infuriating, unpleasant, and stressful before even worrying about its energy impact. Ideally, I would prefer not to do it again for at least a year out two. The only problem with that is that it “worked”. It’s hard to know exactly how well, but I (“we”) definitely produced far more than

Source: Don’t Fight the Weights

Five months ago, my lifelong profession of software development changed completely. My profession was born in the 1940s, created to help fight demons. Our first encounter with the strange new angels of agentic AI is changing every aspect of it.Hardly anyone has noticed yet. Source: Software Development in the Time of Strange New Angels

Source: How I use AI (Oct 2025) – Ben Stolovitz

Some concepts are easy to grasp in the abstract. Boiling water: apply heat and wait. Others you really need to try. You only think you understand how a bicycle works, until you learn to ride one. There are big ideas in computing that are easy to get your head around. The AWS S3 API. It’s the most important storage technology of the last 20 years, and it’s like boiling water. Other technologies, you need to get your feet on the pedals first. LLM agents are like that. People have wildly varying opinions about LLMs and agents. But whether or not they’re snake oil, they’re a big idea. You don’t have to like

2025 is a strange time to start a newsletter about web technology. The past four editions of WTN have focused on the intersection of the web and AI, because frankly that’s where most of the excitement is on today’s internet. But as a few people I link to this week point out, the web platform has improved to a point that it now does much of what frontend frameworks do. So why isn’t there as much exciting activity to report on regarding the web platform? The problem, I think, is that web platform improvements are being undermined by AI development trends. I see two main issues: I’ve heard both Vercel and Netlify

We saw this cycle with jQuery in the past, and we’re seeing it again now with React. We’ll see it with whatever comes next. Success breeds standardization, standardization breeds inertia, and inertia convinces us that progress can wait. It’s the pattern itself that’s the problem, not any single framework.But right now, React sits at the center of this dynamic, and the stakes are far higher than they ever were with jQuery. Entire product lines, architectural decisions, and career paths now depend on React-shaped assumptions. We’ve even started defining developers by their framework: many job listings ask for “React developers” instead of frontend engineers. Even AI coding agents default to React

A programming language is the single most expensive choice a company makes, yet we treat it like a technical debate. After watching this mistake bankrupt dozens of companies and hurt hundreds more, I’ve learned the uncomfortable truth: these decisions are rarely about technology. They’re about identity, emotion, and ego, and they’re destroying your velocity and budget in ways you can’t see until it’s too late. Source: Why engineers can’t be rational about programming languages | spf13

Having stuck to Claude Code for the last few months, this post is my set of reflections on Claude Code’s entire ecosystem. We’ll cover nearly every feature I use (and, just as importantly, the ones I don’t), from the foundational CLAUDE.md file and custom slash commands to the powerful world of Subagents, Hooks, and GitHub Actions. This post ended up a bit long and I’d recommend it as more of a reference than something to read in entirety. Source: How I Use Every Claude Code Feature – by Shrivu Shankar