Today
Front-end, in one read.
The latest from the sources worth following, newest first.
DEV CommunityThe Giantsread at source
Common SEO Mistakes Developers Make in JavaScript Websites
Most JavaScript websites I audit are not broken because the developer did something wrong on purpose. They are broken because the page Google sees and the page the user sees are two different pages. A founder builds a site with an AI tool like Lovable, Bolt, or v0, and gets a working product in a weekend. What they usually get is a Vite React single-page app, and Google sees almost none of it. The site looks finished in the browser and is nearly empty to a crawler. This post covers the ten mistakes I see most often in JavaScript websites, the fix for each one, one trap nobody warns you about, and a five-minute test that shows you exactly what Google sees. How Google Actually Handles JavaScript Google handles JavaScript in three phases: crawl, render, then index. It indexes the rendered HTML, not the raw source you see when you click view source. That middle phase is where the trouble starts. A page can sit in the render queue for a few seconds, but it can take longer than that, in Google's own words. Vercel and MERJ measured Googlebot on a large site in 2024 and found a median wait of 10 seconds from crawl to finished render, and the slowest 1 percent waited about 18 hours. Google's own JavaScript SEO basics guide says server-side or pre-rendering is still a great idea, because it makes the site faster for users and crawlers, and not all bots can run JavaScript. As Martin Splitt from Google put it, a lot of people are still looking at view source, and that is not what Google uses for indexing. Google uses the rendered HTML. Mistake 1: Content That Only Exists After JavaScript Runs The most common mistake is also the most basic: the server sends an almost empty shell, a div with an id, and everything else only exists after JavaScript runs. All seven guides I read for this post cover it, and it is still the one I find most often. The classic version is an H1 set inside a useEffect after an API fetch. The user sees a headline, the crawler sees an empty div, and the content only appears in Google's delayed second pass, late, partially, or never. Other crawlers and AI bots often cannot render JavaScript at all, so for them the page stays empty. The fix is simple to say and harder to ship: use server-side rendering or static generation for every public page you want to rank, and keep client-side rendering for logged-in areas. In Next.js that means Server Components, getStaticProps, or getServerSideProps. In Nuxt it means SSR, in Angular it means Angular Universal, and for an existing SPA it means prerendering with a tool like Prerender.io. Mistake 2: Empty or Duplicate Meta Tags Every route ships the same title, usually React App, with no meta description and no Open Graph tags. Six of the seven guides I read cover this one, and every shared link ends up showing the same preview. Tags set by React Helmet after the page mounts exist only in the rendered DOM. Google usually picks them up in its delayed second pass, but AI crawlers and link previews on Slack, LinkedIn, and iMessage never run JavaScript, so they see nothing. Give every route a unique title under 60 characters and a description around 150 characters, rendered in the initial HTML. In Next.js use the metadata export or generateMetadata, in React use react-helmet-async, in Vue use @unhead/vue, and in Angular use the Title and Meta services. Mistake 3: Links That Are Not Links A div with an onClick that calls router.push is not a link, and Googlebot will never follow it. This is the mistake that silently deletes a whole site's internal linking. Google can only discover links that are a elements with an href attribute. When navigation lives in click handlers, the internal link graph disappears, and pages that are not linked from anywhere are never discovered at all. Use real anchors everywhere: the Link component in Next.js, Link in React Router, router-link in Vue Router, or a plain a href. If it navigates, it should be an anchor, not a div. Mistake 4: Canonical and Hreflang Injected After Load A canonical tag added by JavaScript after hydration is often missed by Google, and the wrong language page can end up ranking in the wrong market. There is a second version of this trap that only Sitebulb covers: when the canonical in the response HTML and the canonical in the rendered HTML are different, search engines may honour the wrong one. Google's own rule is to never use JavaScript to change the canonical to a different value than the one in the original HTML. Render the canonical and hreflang server-side, in the initial HTML. In Next.js, generateMetadata handles alternates.canonical and alternates.languages, and every page should carry a self-referencing absolute canonical. Mistake 5: Lazy Loading the Content Google Needs First Lazy loading is meant for content below the fold, but I keep seeing it on the hero image and the main copy. That is the content Google needs first, and it is the content that gets delayed. A lazy-loaded hero image delays the Largest Contentful Paint, and images without width and height cause layout shift. Text that loads only when the user scrolls may never be indexed at all, because Googlebot does not click and does not scroll. Lazy-load only below-the-fold images and non-critical resources, and always with explicit dimensions. The hero image should load eagerly with fetchpriority set to high. Content inside tabs and accordions should be in the DOM at load and hidden with CSS if you need it hidden. Mistake 6: No Structured Data No JSON-LD means no rich results, and AI tools like ChatGPT understand the page less well. Four of the guides I read cover this, and it is still missing from most JavaScript sites I audit. Add JSON-LD in the HTML for the types that fit the page: Article, Product, SoftwareApplication, FAQPage, and BreadcrumbList are the common ones. Google confirms that JavaScript-generated JSON-LD is acceptable, as long as you test it, so validate the result with the Google Rich Results Test. Structured data will not fix a page Google cannot render, but once the page renders, it is the cheapest way to win more space in the results. Mistake 7: Soft 404s on Dynamic Routes The single-page app server returns index.html with a 200 status for every path, so a page that does not exist looks like a real page to Google. The app shows a Not found message, and Google indexes the junk URL. Hit a dynamic route with an invalid ID and the page renders an Oops, not found message at HTTP 200. Google logs soft 404s, and if the pattern repeats it can drop the whole URL pattern. Martin Splitt described it plainly: instead of responding with 404, the site just responds with 200, always showing a page based on the JavaScript execution. Return a real 404 from the server or framework: return notFound true in Next.js, or res.status(404) in Express. Google's own workarounds for JavaScript-only sites are a redirect to a server 404 URL, or injecting a noindex meta tag with JavaScript on error pages. Mistake 8: A Missing or Stale Sitemap A JavaScript site with no sitemap leaves discovery to chance, and a stale sitemap wastes crawl budget. Pages that are not linked from the homepage may never be found at all. On a large single-page app the sitemap has to list only canonical, indexable URLs. Error URLs, redirected URLs, and noindex URLs in the sitemap are wasted fetches, and they send Google the wrong signal about what matters on the site. Generate the sitemap at build time from the real routes, include lastmod, refresh it on every deploy, and submit it in Google Search Console and Bing Webmaster Tools. Mistake 9: Infinite Scroll With No Pagination Content that only loads when the user scrolls is content Google never sees. Search engines cannot access it, and Google's guidance says to follow its pagination guidelines and avoid infinite scroll. The fix is pagination with crawlable links: a href links to page 2, page 3, and so on. If you want the scroll experience, add a Load More button that also exposes those paginated URLs, so users get the smooth feed and crawlers get the links. Mistake 10: Blocking JavaScript in robots.txt or Leaving noindex Live Two lines in the wrong file can remove a whole site from Google: a staging Disallow pushed to production, or a noindex tag that survives launch. A Disallow for JavaScript or CSS files stops Googlebot rendering the page at all, because it will not render JavaScript from blocked files. A noindex tag from staging does the same thing in reverse: the page never indexes. Gate staging with an environment variable, so production always gets index, follow, and check robots.txt after every deploy. There is also the inverted version of this trap, which only Sitebulb covers. If noindex is in the response HTML but JavaScript removes it, Google skips rendering entirely, so it never sees that the noindex was removed, and the page is never indexed. Fix noindex in the HTML, never in JavaScript. The Mistake Nobody Warns You About: Hydration Mismatch Turns SSR Back Into CSR Here is the mistake none of the guides I read warns you about: your server-side rendering can silently turn back into client-side rendering, and you will never see it happen. When the HTML the server sends and the HTML the client renders disagree, React throws a hydration error and discards the server HTML, re-rendering everything on the client. The page you thought was server-rendered is, in practice, client-rendered again, with all the same SEO risks: delayed indexing, and missing content if the re-render fails. The usual causes are small and easy to miss: a date rendered differently on the server and the client, a random ID or Math.random in the markup, a browser-only API like window or localStorage read during render, and HTML that changes after an auth check. You can spot it three ways: hydration warnings in the browser console, content that flashes or disappears on load, and rendered HTML in Search Console that is missing content present in the raw HTML. Prevent it by rendering browser-only parts after mount, keeping server and client data identical, and using suppressHydrationWarning only where the difference is expected. One more silent delay works the same way. Google's rendering service may cache your JavaScript and CSS for up to 30 days, ignoring your own caching headers, so a fix you shipped can take weeks to show up in Google's render. The fix is content fingerprinting, a filename like main.2bb85551.js that changes with every build. Ranking on Google and Invisible to AI Search at the Same Time Your site can rank on Google and be invisible to AI search at the same time, and this is the part most developers have not heard yet. Vercel and MERJ tested the major AI crawlers in December 2024 and found that none of them rendered JavaScript. GPTBot, ClaudeBot, and PerplexityBot fetched the raw HTML and moved on. A client-side rendered site gets no citations in ChatGPT, Claude, or Perplexity, because there is nothing in the raw HTML to cite. The fix is the same as mistake one: server-rendered HTML. Bing renders JavaScript with limits, and its index feeds Copilot, so a page that cannot be reliably rendered may not be indexed or selected for grounding there either. Quick Comparison The table below compares the ten mistakes side by side: what breaks, and the fix. Mistake What Breaks The Fix CSR-only content Google indexes late, partially, or never SSR or SSG for public pages Empty or duplicate meta tags No per-page signal, same preview everywhere Unique title and description in initial HTML Links that are not links Pages never discovered, link graph gone Real a href anchors everywhere Canonical and hreflang after load Wrong page or language ranked Render canonical and hreflang server-side Lazy loading critical content Hero and copy missed, LCP and CLS suffer Lazy-load below the fold only, with dimensions No structured data No rich results, weaker AI understanding JSON-LD in HTML, validate with Rich Results Test Soft 404s Junk URLs indexed, trust drops Real 404 from the server Missing or stale sitemap Pages never discovered, crawl budget wasted Build-time sitemap, only indexable URLs Infinite scroll, no pagination Content past the fold never indexed Crawlable paginated links Blocked JS or live noindex Rendering blocked or page never indexed Allow JS and CSS, gate noindex by environment Hydration mismatch SSR silently becomes CSR again Identical server and client render The 5-Minute Test: See What Google Actually Sees You do not need a paid tool to see what Google sees. Five minutes is enough. First, disable JavaScript in Chrome DevTools and reload the page. If the page is blank, that is Googlebot's first view of it. Second, curl the page and grep for your headline: if the headline is not in the response, neither is it in Google's first pass. Third, curl the page with the GPTBot user agent to see what AI crawlers get. curl https://example.com | grep -i "your headline" curl -A "GPTBot/1.0" https://example.com | grep -i "your headline" Fourth, compare the raw HTML with the rendered HTML using Screaming Frog in JavaScript rendering mode or the View Rendered Source extension. Fifth, run the URL through Search Console URL Inspection, click Test Live URL, then View tested page: the HTML tab shows what Google indexed, and the Screenshot tab shows the render. FAQs Three questions developers ask me most often about JavaScript and SEO. Can Google index a JavaScript website? Yes, Google can index JavaScript websites, but only after rendering, and rendering is delayed. Google uses an evergreen Chromium renderer, and content can be indexed late or partially. Other crawlers often cannot render JavaScript at all, so server-rendered HTML is the safe route for any page you want found, ranked, or cited. Is client-side rendering bad for SEO? Client-side rendering is not bad for logged-in pages, but it is a bad default for public pages you want to rank. Behind a login, nobody needs to find the page in search, so render it however you like. For public pages, use server-side rendering or static generation, and use prerendering as the bridge for an existing single-page app. Do I need to rebuild my SPA in Next.js to rank? No, you do not need to rebuild to rank, but you do need server-rendered HTML somehow. Prerendering an existing SPA takes an afternoon, with a service like Prerender.io or Rendertron, and it is the practical first step. Server-side rendering or static generation is the better choice for the next rebuild. Dynamic rendering is a workaround, not a long-term fix, and it is not cloaking as long as the served content matches what users see. About the Author Written by Belayet Hossen Sakib. He is a professional SEO expert . He provides SEO consultancy and search engine optimization services with strategic leadership for SEO client projects, from technical audits and keyword research to content that gets cited on Google and AI platforms like ChatGPT, Gemini, and Perplexity.
DEV CommunityThe Giantsread at source
Five open-source tools for Razer, Logitech and RGB gear on Linux
I run I Did My Own , a site that collects open-source projects where someone looked at an app and built their own version. This week a little cluster of new listings landed on the Just shipped page, all scratching the same itch: setting up mice, keyboards and RGB lighting on Linux, where the vendor apps (Razer Synapse, Logitech Options+, Corsair iCUE) aren't an option. Here are the five, with the language and licence shown on each project page. OpenRazer: the driver layer Open-source Linux drivers for Razer keyboards, mice and other devices. It exposes lighting, DPI and device settings to user-space apps, which is what the next two projects build on. C · GPL-2.0 Polychromatic: a graphical front end for OpenRazer Controls lighting effects, DPI, polling rate and other device settings through OpenRazer, so you don't have to poke at it from scripts. Python · GPL-3.0 RazerGenie: the Qt option Another front end for OpenRazer, this one a native Qt desktop app for Razer lighting and device settings. C++ · GPL-3.0 Piper: buttons, DPI and profiles A GTK app on top of libratbag for configuring gaming-mouse buttons, DPI and profiles on Linux. It's listed as its own take on both Logitech Options+ and Razer Synapse. Python · GPL-2.0 OpenRGB: lighting across brands A cross-platform app to control RGB lighting on hundreds of devices (many Razer ones included) without vendor cloud software. C++ · GPL-2.0 How they fit together OpenRazer talks to Razer hardware; Polychromatic and RazerGenie are two different desktop front ends for it. Piper comes at it from a different library, libratbag, and focuses on mouse buttons, DPI and profiles. OpenRGB is the one to look at if your desk mixes brands and you mostly care about lighting. All five sit side by side on one product page, and each card links through to the maker's GitHub repo: 👉 Open-source Razer Synapse alternatives on idmo The rest of this week's new listings are on Just shipped . Do you run any of these? I'd like to hear what your Linux peripheral setup looks like, especially if you've hit a device none of them handle yet. And if you've built your own version of a vendor app, you can add it to the site.
DEV CommunityThe Giantsread at source
The Executive Communication Secret That's Spreading Through Silicon Valley
You dread Fridays. Not because the week was ending, but because you have to write your weekly executive update. Every Friday afternoon, same routine: dig through Slack messages, try to remember what shipped versus what we thought would ship, and craft diplomatic ways to say, "most tasks are delayed." Four hours later, you would have something that was too long, not specific enough, and somehow may still missed the things executives truly cared about. To help you, I built a system to write these updates. Now you can spend 15 minutes reviewing versus 4 hours creating. The Problem Every PM Knows You drive grooming sessions all week. You track tickets in Jira. You have the information executives need scattered across five different tools. But when Friday comes, you are starting from scratch. Looking through chat logs, trying to piece together what happened, explaining why dates moved. The typical PM workflow: Check JIRA for what is open/pending/closed Scroll through Slack for context on blockers Remember (or forget) the important conversation from Tuesday Write everything up in a way that won't get you fired Send it off hoping no one asks follow-up questions This is exactly the kind of work AI handles better than humans. Pattern recognition across multiple data sources, consistent formatting, clear communication of status updates. What Executives Actually Want Having driven leadership meetings for years, I can tell you executives want the same seven things every week: What shipped this week What's blocked and why Key metrics and trends What they need to decide Risks that could affect bigger goals Next week's priorities How this connects to quarterly objectives That's it. Everything else is noise that just makes our job harder. The Simple System Instead of writing updates, collect data all week and let AI assemble it on Friday. Daily data collection (already happening): Team posts updates in specific Slack channels JIRA tickets get updated as work progresses Ensure you keep notes from important meetings Friday processing (15 minutes): Export the week's data Run it through three AI prompts Review and edit the output Send the update AI handles the tedious part (organizing scattered information) while you handle the strategic part (context and priorities). Setting Up Your Data Flow Since you are already creating this information, you just need to organize it slightly differently. Slack channels: Create #product-shipped and #product-blocked channels. Train your team to post there instead of only in DMs. Takes two weeks to become habit. Jira labels: Add exec-update labels to tickets that matter for leadership. Filter by this label when exporting weekly data. Meeting notes: Use this simple template for any important meeting: Decision: [what was decided] Owner: [who's responsible] Deadline: [when it's due] Risk: [what could go wrong] This setup takes 30 minutes and makes your weekly exports clean and useful. The Three AI Prompts Prompt 1 - Organizing the chaos: “I'm giving you a week of product team updates from Slack, Jira, and meeting notes. Sort everything into these categories: SHIPPED: Things that went live to users BLOCKED: Problems that need attention METRICS: Numbers that show progress DECISIONS: Things leadership needs to approve NEXT: Priorities for next week” For each item, write one sentence explaining why it matters. Prompt 2 - Write the update: “Create a 7-section executive update using the organized information: Week Summary (one sentence + three key numbers) What Shipped (max 3 items) What's Blocked (problems + solutions) Decisions Needed (specific asks with deadlines) Key Metrics (actual numbers) Next Week Priorities (max 3 items) Strategic Impact (connection to quarterly goals)” Keep each section to 3 bullets. Use specific dates and numbers. Prompt 3 - Make it executive-ready: “Rewrite this for senior leadership. Remove uncertainty language. Make problems and solutions clear. Use numbers instead of vague terms like "significant" or "substantial." The 15-Minute Review AI gives you 90% of what you need. Now, you can apply the human judgment: Accuracy check: Are the numbers right? Any missing context? Strategic connections: How does this week connect to bigger objectives? Risk assessment: What should executives be worried about? Now, hit send. Real before and after impact you will notice Before (your old style): "The homepage experience encountered some technical challenges this week. The engineering team is working to resolve integration complexities with our payment provider. We expect more clarity on timeline next week." After (AI + your review): "Homepage flow delayed 3 days due to Stripe API rate limits affecting 2% of transactions. Engineering implementing retry logic. New ship date: March 15. Risk: Could impact Q1 revenue by $50K if unresolved." The second version tells executives exactly what's happening and what they need to know for their own planning. How you can get started on Monday · Today: Create the Slack channels and start using them · Monday: Add the JIRA labels to relevant tickets · Wednesday: Test the prompts with this week's data · Friday: Use the system for your actual update Most PMs see immediate improvement in their first AI-generated update. The consistency alone makes you look more organized. This is critical because better executive communication isn't just about saving time on Friday afternoons. When your updates are consistently clear and comprehensive, executives start including you in strategic conversations. The PM who communicates clearly is the PM who gets promoted. While other PMs spend hours wrestling with updates, you are using AI to handle the routine work and focusing on the strategic thinking that moves your career forward. Next week, I will show you how to build an AI agent that tracks everything your competitors are shipping, and struggling with. While everyone else checks competitor websites manually once a month, you will have real-time intelligence.
DEV CommunityThe Giantsread at source
The AI Shame Epidemic
Your director just complimented your “thoughtful” PRD in yesterday’s leadership meeting. What she doesn’t know: Claude wrote 80% of it in 10 minutes. You feel like a fraud. But you’re not going to tell anyone. You are not alone. Studies show that over 50% of executives are hiding their AI use at work. The interesting observation here is the people using AI the most are the ones most ashamed to admit it. This secret is costing PMs their careers. The Confession No One’s Making A PM at a Series B startup admitted to me: “I used Claude to analyze 47 user interviews in 20 minutes. Found three patterns our team missed in weeks of manual analysis. Presented it as if I did the entire thing myself. Took full credit.” Another PM at a Fortune 500: “I let AI draft all my user stories now. My velocity looks insane. My manager thinks I’m suddenly a rockstar. I’m terrified someone will find out.” The data reinforces this. According to WalkMe’s 2025 survey of over 1,000 workers: 48.8% of employees hide their AI use to avoid judgment 53.4% of C-suite executives hide it even more 62.6% of Gen-Z have used AI for work but pretended it was all their effort The people at the top, with the most power and influence, are the most afraid to admit what they’re doing. Think about it. Why This Is Happening A senior PM told me about an executive meeting where someone asked how their team produced the quarterly roadmap so fast. The PMs looked at each other. Neither said “we used AI to analyze market data and generate scenarios.” Instead, they talked about “improved processes” and “better collaboration.” Here is why they lied: Fear of looking incompetent ; If AI did the work, does that mean I’m not actually good at my job? If anyone can use ChatGPT to write user stories, what’s my value? Unclear company policies ; Most companies have zero guidance on AI use. You are operating in a gray area. Better to stay quiet than risk being the test case. Comparison to others ; Everyone else seems to be grinding it out manually. If you are using AI, are you cheating? Taking shortcuts? Job security fears ; In a market where PMs are getting laid off, the last thing you want is leadership thinking “wait, AI can do this role?” The shame runs deep. And I believe it is (silently) killing careers. The Real Cost of Staying Silent The fact is this - while you are hiding your AI use, here is what is happening: You are ultimately not getting better at it. This is because by default, you can’t improve what you can’t discuss. You can’t share prompts with your team. Can’t learn from others’ techniques. You are stuck at amateur level while pretending to be an expert at manual work. You are missing strategic opportunities. When you frame AI-generated insights as “I spent 40 hours analyzing this,” leadership allocates resources accordingly. They think you need more time and people. The opportunity to restructure how your team operates never comes up. Your competition is pulling ahead. Some PMs have companies with clear AI policies. They are experimenting openly. Building AI workflows. Getting exponentially better each week. You are still pretending it’s 2023. Make no mistake, you are reinforcing the problem. Every time you hide AI use, you signal to junior PMs that it’s shameful. You are creating the next generation of secret AI users instead of skilled practitioners. Teams that talk openly about AI use are moving 3x faster than teams that don’t. The gap widens every sprint. What Top PMs Are Actually Using AI For Since most folks are hiding it, let me just tell you what’s happening behind closed doors. User research synthesis : Remember my article two weeks ago about analyzing interviews? Every senior PM I know is doing this now. The ones who admit it get better at it. The ones hiding it stay mediocre. Competitive intelligence : AI tracks competitor releases, analyzes their job postings, monitors their customer reviews. Some PMs spend 20 hours a month doing this manually. Others spend 2 hours with AI and get better insights. Executive updates : You read about this last week. The PMs crushing it are not spending 4 hours writing updates. They are using AI and spending those 4 hours on actual strategy. PRD first drafts : It is true that no PM worth their weight, is shipping AI-written PRDs without tweaking them. But everyone is using AI to generate structure, catch edge cases, and draft acceptance criteria. Then adding human judgment and context. Roadmap scenario planning : “If we delay feature X by 2 weeks, what’s the downstream impact?” AI can model this in minutes. You can spend days doing it manually, or 15 minutes with AI and the rest of your time deciding which scenario to choose. Data analysis: Pulling insights from analytics, identifying patterns in user behavior, connecting metrics across tools. AI does in seconds what takes hours with spreadsheets. Can you see the pattern I am trying to piece together? AI handles the pattern recognition and initial processing. Humans add judgment, context, and strategic thinking. Now, here is how to break free without career risk Don’t get me wrong, you don’t need to walk into Monday’s standup announcing “I’ve been using ChatGPT for everything.” This will drown your perception fast. Your messaging and approach should be as follows: Start with low-stakes sharing ; Next time someone asks how you analyzed something quickly, say “I used Claude to process the initial data, then I reviewed it for accuracy and added context.” Simple. Honest. No drama. Position it as a skill, not a shortcut; Don’t say “AI did it for me.” Say “I’m developing my ability to work with AI tools to deliver faster insights.” Same outcome, different framing. Share what you verified; When presenting AI-generated insights, emphasize what you checked, what you changed, what you added. This demonstrates your judgment, not just AI’s output. Credit AI like you would credit a junior analyst; If a junior PM helped you analyze data, you would say “Sarah pulled these insights, and here is what they mean.” Do the same with AI. “I used Claude to process these interviews, and here are the patterns I validated.” Lead with outcomes, not methods; Focus on “we identified three critical user pain points” not “I used AI to analyze transcripts.” If someone asks how, be honest. But lead with value. The 48-Hour AI Transparency Test If you want to know if your company culture can handle AI transparency? Try this: Monday morning: In your next team meeting, mention one AI tool you used. Keep it casual. “I tried using Claude to draft these acceptance criteria. Saved about an hour. Happy to share the prompt if anyone is interested.” Watch what happens. Option 1: People lean in. Ask questions. Want to learn. Your company is ready for AI-augmented work. Option 2: Awkward silence. Leadership frowns. Someone makes a comment about “taking shortcuts.” Option 3: Mixed reactions. Some interested, some resistant. Normal organizational change. Based on the reaction, you will know how open you can be. What This Looks Like in Practice A PM at a major tech company shared their experience: They presented a competitive analysis to executives. Usually takes 3 weeks of manual research, analyst reports, website monitoring. This time, they used AI to monitor competitors, analyze their releases, track their hiring patterns, and synthesize customer sentiment. Took 4 hours. In the presentation, they said: “I used AI to process competitor data across multiple sources in real-time. Here’s what I validated and what it means for our strategy.” The VP of Product asked: “Can you share that workflow? Sounds useful for the whole team.” No one cared that they used AI. They cared that they delivered better insights faster. The Window Is Closing Right now, you’re in an interesting moment. Most PMs are (still and should not be)using AI secretly. A small group is using it openly and getting exponentially better. By mid-2026, companies will split into two camps: Organizations with clear AI policies where skilled AI use is a requirement Organizations where everyone’s still hiding it and collectively falling behind The PMs who get comfortable using AI openly now will (most likely and in addition to other competencies) dominate the promotion cycle next year. The ones still hiding it will be competing with people who’ve had 18 months of open practice and improvement. Your choice: keep pretending you’re grinding everything out manually or start building actual AI skills that make you irreplaceable. Listen, you are already using AI. Everyone knows this. Leadership knows. Your peers know. You are not fooling anyone. The shame isn’t protecting you. It’s limiting you. The PMs leading the charge right now aren’t the ones with the best AI prompts. They are the ones comfortable saying “I used AI for X, applied my judgment on Y, and here is why the outcome matters.” Stop hiding. Start improving. The career you save might be your own.
DEV CommunityThe Giantsread at source
My review subagents said "waiting for the notification" and handed back. 11 of 21 did it, and the parent sat idle 12 minutes
Short version: when a subagent puts its wait in the background and ends its turn with "waiting for the notification," the parent sees that as a finished task. On November 21 I dispatched 23 UI cards in a data platform repo, one after another. For 21 of them I can line up the subagent's transcript with the receipt timestamp. In 11 of those, the review subagent handed back before Codex had written its receipt. The parent got a message that said "still waiting," and then it stopped too. The longest stall was 12 minutes, until I typed "how's it going?" The fix was one commit: the wait now runs in the foreground in 170-second slices and returns a special exit code when it isn't done yet, so the caller just runs it again. Some background. Claude Code splits work into cards and reviews it; Codex writes the code. For each card, the parent session starts a background review subagent. The subagent opens a Codex terminal, waits for the receipt, reruns tests and browser checks against a checklist, and writes a verdict. The parent only reads the verdict and decides whether to merge. What happened It was a fast morning: 23 cards dispatched between 10:52 and 14:13 UTC. The trouble was in the "wait for the receipt" step. The review brief at the time said: "Run wait in the background with Bash, wait for the completion notification, don't poll." The subagents did exactly that. They put the wait in the background, printed something like "Dispatch done, waiting for Codex's round 1 receipt, will continue reviewing when the background notification arrives," and ended their turn. From the subagent's side that's fine. When the background task finishes, it gets woken up and carries on. But from the parent's side, a subagent that ends its turn has handed back. The parent gets a "task completed" notification, and what's inside is a half-finished report. Two concrete cases: UX-3a : the subagent handed back at 11:36:53 saying it was waiting for the receipt. A second later the parent replied "round 1 is still running, no result yet" and stopped. The receipt landed at 11:41:35. The parent only moved again because I sent it an unrelated instruction at 11:40. UX-10a : the subagent handed back at 13:59:05, and the notification summary said it was "waiting on its own background task." This time the parent didn't even reply. It just stopped. The receipt was written at 14:08:54, and the parent didn't move. At 14:11:13 I asked "how's it going?" Only then did it check the evidence folder and find the receipt had been there for a while. From the early hand-back to my question: 12 minutes. Early the next morning, in a different session, I wrote: "I keep seeing the parent agent sitting idle. Either it never dispatched a subagent, or the subagent already finished." Why it happened Reading through the transcripts, there were three layers. Layer one: the brief told the subagent to go to the background. When I wrote it I was thinking "no polling, save tokens." I didn't think about what a subagent ending its turn means to the parent. Layer two: the foreground can't wait forever either. Why not have the subagent wait two hours in the foreground? Because Claude Code moves any foreground command that runs past 180 seconds into the background, whatever timeout you set. So a two-hour foreground wait was never an option, and the subagent would end up at "background wait, end turn" anyway. Layer three: notifications can arrive early. A different child exposed this one. On November 21 a child agent that doesn't report its status to my terminal orchestration tool was announced as "turn finished" right after it launched. The parent trusted the note, went to read the result, saw the child was still busy, and stopped, with nothing left to wake it. I had fixed a bug in the same family on November 19 (a child messaging the parent mid-task made the wait return early). This was the same problem coming in through a different door. Stack the three together and the result is always the same: the parent thinks someone will wake it, and nobody does. The fix: one commit The November 22 fix (6 files, +96 / −23) did four things: The wait now runs in the foreground in slices. Each call waits at most 170 seconds, so it returns before the 180-second cutoff. If the round isn't done, it exits with code 4, meaning "Codex is still working, run the same command again." No receipt file is written until the round ends, so a half result can't be mistaken for a full one. Other messages no longer cut the wait short. When the parent's terminal receives a message from another child, the underlying wait returns early. Now it just keeps waiting until the slice is used up. "Turn finished" needs evidence. The dispatch script records the child's turn counter before sending the task. It only notifies the parent once the counter has moved and the status is no longer "working." For a child that never reports status, it tells the parent after 10 minutes, honestly: "can't tell, don't sit waiting for it, go look yourself." One line in the global rules. Before the parent ends its turn "waiting for a result," it has to confirm something will wake it. If a subagent hands back "still waiting" instead of a result, the parent checks the evidence folder right away: if it's done, carry on; if not, send the subagent back to wait in the foreground until the end. Where the rules live The dispatch script's wait subcommand : the default slice is 170 seconds, a named constant with a comment about the 180-second limit. While Codex is still working it exits 4 and writes no receipt. The review brief : step 2 of phase two now says "run wait in the foreground; on exit code 4, run it again unchanged; don't background it, don't replace it with a sleep loop, don't end your turn 'waiting for the notification'," along with the reason: once a subagent hands back, the parent only has half a report. Tests : three new ones. One checks that a message from someone else doesn't end the wait, one checks that a still-working round exits 4 and writes no receipt, and one asserts the default slice is under 180 seconds. All 9 tests in that file pass, and CI on the fix commit is green. Still open The fix is less than a day old. I don't have post-fix dispatch data yet, so I can't say the stalls are gone. After the next batch of cards I'll count early hand-backs the same way. The brief is text, not a hook. Slicing the wait removes the reason to background it, but if a subagent does it anyway, nothing stops it. The parent's "check before you stop" rule is the backstop. What you can take from this Know what "ending a turn" means one level up. A subagent's "background wait, wait for notification" looks to the parent like a finished task. Anything you need to wait for, wait for before handing back, not after. If your tool backgrounds long commands, slice the wait. Here's a generic version: wait for a receipt file, return 4 when the slice runs out, and the caller runs it again on 4. I tried both cases locally: with no file it returned 4 after 6 seconds; with the file showing up at 3 seconds it returned 0 right away. #!/bin/sh # usage: slice_wait.sh [seconds]; 0 when the receipt appears, 4 when the slice runs out (run again) receipt = $1 ; slice = ${2:-170} end = $( ( $( date +%s ) + slice ) ) while [ "$(date +%s)" -lt "$end" ] ; do [ -s "$receipt" ] && { echo "done: $receipt" ; exit 0 ; } sleep 5 done echo "still working: run the same command again" ; exit 4 Count early hand-backs. For each card, compare two times: when the subagent first handed back, and the receipt file's modification time. If the first is earlier, it handed back early. For me it was 11 of 21 that day. At that rate, a human watching won't keep up. Base "done" notifications on state changes, not on time. Record the turn count before sending the task, and only call the turn over once it has moved. If a child can't report status, say so plainly. This is part 10 of the series. Earlier parts were about putting rules where the agent can't route around them. This one is the other side: the wait has to go somewhere it can't be skipped too. A wait that happens after the hand-back is a wait nobody is doing. About the numbers 23 cards, dispatched 10:52–14:13: the 23 UI card folders in that repo's evidence directory for 2026-11-21; times are the first timestamp in each review subagent's transcript (UTC). 21 matched, 11 early: I read each review subagent's transcript from that day, took the card name from its wait command, and compared it against the modification time of the last receipt file in the evidence folder. If the parent got its first hand-back or completion notice from that subagent before the receipt time, it counts as early. 2 more cards are excluded because the card name in the command was quoted and didn't parse. UX-3a's 11:36:53, 11:36:54, 11:41:35, and 11:40, and UX-10a's 13:59:05, 14:08:54, and 14:11:13: timestamps from the parent session transcript and receipt file modification times (UTC). "12 minutes" is 13:59:05 to 14:11:13. The brief line "run wait in the background with Bash, wait for the completion notification, don't poll": the line removed from the brief in the fix commit (arguments omitted). 180 and 170 seconds: the wait slice constant and its comment in the fix commit. The child announced as finished at launch (11-21) and mid-task messages ending the wait early (fixed 11-19): from a code comment in the fix commit and the message of the 11-19 commit, respectively. 6 files, +96 / −23, 3 new tests, 10 minutes: from the diff of the 2026-11-22 fix commit. 9 tests passing and green CI: a local run of that test file on 2026-11-22 and the CI result for that commit. My own words: from my message in the fix session on 2026-11-22.
Darek KayMore Front-end Bloggersread at source
#0201
A curvy road between trees and a lake leading to the Mount Cook mountain
AbduzeedoMulti Author Blogsread at source
Best of the Week: Die Grotesk, B416, and Sonny's Corner
This best of the week edit gathers Pentagram's Poetry Foundation, Klim's Die Grotesk, Order's Sonny's Corner, and eight more sharp releases. Borrowed history and everyday mechanics turned up everywher...
Hacker News Front PageThe Giantsread at source
Show HN: I built a game where you are an LLM's subagent
Hacker News: Show HNLibraries, Frameworks, etc.read at source
Show HN: I built a game where you are an LLM's subagent
Comments
Hacker News: Show HNLibraries, Frameworks, etc.read at source
Show HN: NestDaddy Memory, one memory shared by ChatGPT, Claude and Cursor
Comments
Flavio CopesMore Front-end Bloggersread at source
A deep dive into Clairic
Extract typed values from text, screenshots, and PDFs with Clairic on Cloudflare Workers AI. Build a Worker and learn how to check the model's answers.
Hacker News Front PageThe Giantsread at source
Muru – AI-assisted Rust server for Python apps by mod_WSGI's creator
Hacker News Front PageThe Giantsread at source
87% of the Anthropic power will come from gas and 11% from coal in 2028
Hacker News: Show HNLibraries, Frameworks, etc.read at source
Show HN: I built a newspaper for white-collar crime that paints every portrait
Comments
Flavio CopesMore Front-end Bloggersread at source
A deep dive into Inkling 2 Mini
Run Inkling 2 Mini on an Apple silicon Mac, send it a screenshot through Ollama, measure a local request, and see how a looped transformer reuses its layers.
Hacker News Front PageThe Giantsread at source
Notes on the discrete Fourier transform (DFT)
Hacker News Front PageThe Giantsread at source
Show HN: The Riemann Proof Handbook
Hacker News: Show HNLibraries, Frameworks, etc.read at source
Show HN: The Riemann Proof Handbook
Comments
Hacker News: Show HNLibraries, Frameworks, etc.read at source
Show HN: Npx.tools, a keyboard-friendly index of developer tools
Comments
AbduzeedoMulti Author Blogsread at source
Inside Pentagram’s Brand Identity for Poetry Foundation
Pentagram rebuilds Poetry Foundation’s brand identity around a redrawn Pegasus mark, central-axis type stacks, and two-color covers. Seventy black silhouettes sit in neat rows on off-white paper, trac...
AbduzeedoMulti Author Blogsread at source
Insomnia Cookies Rebrand Is a Masterclass in Branding by &Walsh
Insomnia Cookies rebrand by &Walsh: a photo cookie-moon logo, late-night purple and chunky type for the warm-cookie chain. The logo is a photograph, not a drawing. A real chocolate chunk cookie, b...
AbduzeedoMulti Author Blogsread at source
London Film School: Rebellious Branding by Rabbithole
Rabbithole revamps London Film School’s branding with Kimera’s Waldenburg type, a brighter red, and stark framing bars across print and web. One solid black bar sits directly above three tightly stack...
AbduzeedoMulti Author Blogsread at source
Emiglia Brand Identity by Another Collective
Emiglia brand identity by Another Collective: a hand-cut red wordmark, script lettering and windowed packs for a Porto pasta maker and bar. The rebrand unifies two sides of one business, the Pasta Fre...
AbduzeedoMulti Author Blogsread at source
Polar’s Utilitarian Graphic Design System for P.A.C. Bakery
São Paulo studio Polar builds a reactive graphic design system for P.A.C. bakery, trading formal logos for typed-out letters and receipt menus. Two of São Paulo studio Polar’s four founders are partne...
AbduzeedoMulti Author Blogsread at source
pen.dev: The Fast Agentic Canvas in Our Daily Workflow
pen.dev pairs a 60fps WebGL canvas and live shaders with browser import and two-way MCP integration for real product design. We've been testing pen.dev closely for quite some time, and we're ready to ...
AbduzeedoMulti Author Blogsread at source
Giga Unveils the AD Italia redesign
Giga rebuilds AD Italia for its 45th anniversary: the AD Italia redesign pairs Arizona type, Ghirri colour and a modernist grid. The first thing you see is the masthead. AD sits in black flared serif ...
HTML All The ThingsPodcastsAudioListen
Does Xbox Need Exclusives to Survive?
Xbox is struggling to compete with PlayStation in console sales, despite offering consumer-friendly features like Game Pass, more affordable hardware options, and games across multiple platforms. Could the solution be bringing back exclusive games? In this edition of the Web…
Chris HawkesYouTube ChannelsVideoWatch on YouTube
I Tested Seedance 2.5 in 4K — Can AI Recreate a WWII Battlefield?
AdactioTop Front-end Bloggersread at source
See you later, Amsterdam!
Flavio CopesMore Front-end Bloggersread at source
Resend: the email API I use for my sites, my apps and my AI agents
What Resend does, how I use it to send sign-in links and form emails across my course sites, why I like it, and how to give AI agents email with its MCP server, CLI and skills.
Flavio CopesMore Front-end Bloggersread at source
Turn on automatic security updates on your VPS (and decide about auto-reboot)
Set up unattended-upgrades on Ubuntu and Debian, tested on a real Droplet with the November 2026 NGINX HTTP/2 fix: security-only vs all packages, auto-reboot, needrestart, third-party repos, logs and alerts.
Flavio CopesMore Front-end Bloggersread at source
Finishing is a skill
How I get things done: the three states every project is in, why everything I ship is version one, the seven-day rule, why I ship lots of small experiments, and why deleting or automating something counts as finishing it.
Frontend Masters BlogMore Front-end Bloggers8 min read
Apps I’ve Vibe-Coded Lately That Are Pretty Damn Useful To Me, Actually
Hey, we can all vibe code. But sometimes what you need are ideas that are actually useful.
Google for DevelopersYouTube ChannelsVideoWatch on YouTube
Google Antigravity and Gemini 4: Creating an interactive MIDI mapped 3D world
Heroku BlogCompany/Startup Blogs5 min read
Borealis Isolated Postgres: Serious Database Security for the Common Runtime
The power of Heroku lies in its simplicity. Developers can spin up an entire app stack, complete with its own database and caching layers with just a single command. No need for the specialized, time-consuming work of managing servers and virtual machines. This convenience applies to interacting with your app stack as well. Need to apply some database schema migrations or populate your database with reference data? Just connect directly to the PostgreSQL database server using your app’s username and password and run your scripts. The post Borealis Isolated Postgres: Serious Database Security for the Common Runtime appeared first on Heroku .
Jeffrey Zeldman PresentsMore Front-end Bloggers1 min read
Snow White, 2008–2026
Our family had sixteen unforgettable years with this magical, majestic, queenly feline. The post Snow White, 2008–2026 appeared first on Jeffrey Zeldman Presents .
CSS-TricksThe Giantsread at source
Andy Clarke answers six questions about Standout Designs for the Web
Web designer, author, and Stuff & Nonsense founder Andy Clarke has released Standout Designs for the Web , a new e-book that encourages designers to move beyond familiar templates and conventional layouts to create more personality-driven websites. The book draws … Andy Clarke answers six questions about Standout Designs for the Web originally handwritten and published with love on CSS-Tricks . You should really get the newsletter as well.
Go Make ThingsMulti Author Blogsread at source
Gardening updates for November 2026
I’ve been doing a lot of digital gardening this week! I added content to the guides on Anarchy and Anti-Work (they had previously been placeholders). I wrote guides on the ResizeObserver and MutationObserver APIs. I made some small updates to the Array Methods guide, and removed the standalone guide on Array.prototype.slice(). Enjoy!
The Mozilla BlogBrowsers, engines, etc.2 min read
Why there are still no non-WebKit browsers on iOS
Firefox on iPhone is growing fast across the world. This is especially true in the EU since 2024, when the EU Digital Markets Act (DMA) started requiring Apple to let people choose their default browser; millions have picked Firefox, and daily use on iOS has doubled. People want to choose the browser on their phone. […] The post Why there are still no non-WebKit browsers on iOS appeared first on The Mozilla Blog .
SitePointThe Giantsread at source
How to Add AI Facial Expression Editing to Your Video Pipeline (2026)
null Continue reading How to Add AI Facial Expression Editing to Your Video Pipeline (2026) on SitePoint .
HeyDesignerDeveloper/Designer Newsread at source
On drawing icons
Design by playground, Lighting that feels just right, Execution over everything.
Net NinjaYouTube ChannelsVideoWatch on YouTube
"Anti-Slop" Designs with Impeccable (a Crash Course) #6 - Other useful Commands
Flavio CopesMore Front-end Bloggersread at source
How to thrive in the agentic AI era
Agents made producing things cheap. What's scarce now is judgment, trust and knowing what done looks like. What that means for developers, professionals, prosumers and small business owners.
Flavio CopesMore Front-end Bloggersread at source
Cloudflare Browser Run: headless Chrome for AI agents and web apps
What Cloudflare Browser Run is, the problem it solves, and how to use Quick Actions, Puppeteer sessions, CDP and MCP for AI agents and web apps.
Flavio CopesMore Front-end Bloggersread at source
AI model names explained: Luna, Haiku, Hydrogen and the rest
OpenAI, Anthropic and Google each name their models by size. Here is which name is small, medium, large and largest, what the IDs mean, and how versions move.
SitePointThe Giantsread at source
What to get right before you ship webhooks
Before you ship webhooks: an event log, signed payloads, retries with backoff, deduplication and delivery logs, with working Node.js code and Standard Webhooks. Continue reading What to get right before you ship webhooks on SitePoint .
Ana RodriguesMore Front-end Bloggers1 min read
A new talk in my pocket
Earlier this year, Pawel from NN1 Dev Club sent me a message inviting me to do a talk. According to him, the topic was simple: “whatever excites you at the moment”. This invitation came around the time I was having a big girl cry over an article that was going viral, claiming…
Brad FrostTop Front-end Bloggers3 min read
Putting AI & Design Systems to work
I just got off stage at the phenomenal Detach! Conference in Fortaleza, Brazil. I gave my presentation using my custom eddie-slides framework, which embeds psychedelic visualizations from bf-visualzzz and showcases our course websites , my blog , and Black Friday sale webpage .…
PiccalilliMore Front-end Bloggersread at source
The Index: Issue #207
When everything has changed, what do we do next? This is a message to managers and decision makers who are mandating their staff to use AI all day with a warning: you're burning your staff out and setting yourself up for long term problems unless you get back to investing in their skills and satisfying their curiosities. The CSS caret-* properties and custom caret accessibility As always, Sara has put an unbelievably in-depth resource together for us. A must read. Tech for good (enough) jobs list Hiring in tech has slowed to a crawl but there is hope still. Jess has gathered a great list of open opportunities at companies who are not horrible and evil. They've put together a very useful spreadsheet system too . What can't I press? A very useful app by Eric to show you what keyboard shortcuts are already claimed by screen readers and apps, for if you're adding key bindings to what you're building. Understanding CSS random() There's been a lot of people talking about how exciting CSS random() is and also plenty mentioning how they're struggling to understand it. Luckily Mat is very good at explaining complex stuff and he's brought a nice design pattern as the context with him too. P.S. this is a fun . Sponsor message Our Black Friday deal is launching on November 23 for two weeks only . We’re announcing it now so you can get the approvals you need from your bosses. The deal is simple: save 50% on every course , including the newly re-worked and updated JavaScript for Everyone . Sign up for updates to get alerted when the deal goes live! Check it out
Twilio BlogMulti Author Blogsread at source
How To Import Data From Your CRM Or Another External Source Into Conversation Memory
How To Import Data From Your CRM Or Another External Source Into Twilio Conversation Memory
Twilio BlogMulti Author Blogsread at source
What is an SMTP server? How Simple Mail Transfer Protocol works
An SMTP server sends and relays email. See how SMTP works, which port to use, and the SMTP server addresses for Gmail, Outlook, Yahoo, and more.
Microsoft Edge BlogBrowsers, engines, etc.4 min read
Hybrid intelligence on the Web: Introducing Aion Instruct and Prompt API in Microsoft Edge
Rapidly evolving AI capabilities are redefining what sites can do for users on the web. With on-device AI in Microsoft The post Hybrid intelligence on the Web: Introducing Aion Instruct and Prompt API in Microsoft Edge appeared first on Microsoft Edge Blog .
Bram.usMore Front-end Bloggers12 min read
CodePen Commander — Sync, serve, and build local CodePen 2.0 Pens straight from the CLI
I scratched my own itch (again 😅) and built CodePen Commander — a CLI cdpn command to sync local folders with CodePen 2.0 Pens, deploy them, and manage privacy rules right from the terminal.
DigitalOcean BlogMulti Author Blogs3 min read
Benchmarking v5 Droplets: what the numbers say across real workloads
We ran v5 (5th Gen AMD EPYC “Turin”) compared to our existing Dedicated Premium Droplets across a range of workloads: a realistic microservices application, raw CPU, memory, and database transactions. We measured throughput and latency for each. Throughout, we compare v5 against…
Mux BlogCompany/Startup Blogs4 min read
Mux Robots-generated thumbnails and chapters, straight to your player
Mux Robots can now write AI-generated thumbnails and chapters back to your Mux Video assets, so viewers see them in Video.js v10 with no extra development.
Big MediumMore Front-end Bloggersread at source
Sentient Design @ Design+AI
This talk was the closing keynote at Design + AI conference in Brighton, England, on September 25, 2026. Download mp3 Download slides (PDF) The book Sentient Design (Rosenfeld Media) “Excellent, essential” —Don Norman “What an epic book” —John Maeda Need help? Big Medium provides product strategy, design, and development of intelligent interfaces. Get in touch. In this talk, Josh Clark and Veronika Kindred show how using AI as a design material, not just a production tool, enables designers to create meaningful new experiences that have only now become possible. Sentient Design is the practice of crafting intelligent interfaces, experiences that have the awareness and agency to adapt to users in the moment. These are dashboards that design themselves, apps that manifest on demand, agents that just get it done, and much more. What entirely new kinds of experiences can we create? What dramatic new value can they deliver? Josh and Veronika show examples and bring the receipts. Here’s the lightly edited transcript. Let’s look up from our tools Andreea Tufescu ." target="_blank"> Photo by Andreea Tufescu . Josh There’s a lot of talk right now about tools and process, including on this stage today. And this stuff is important, right? We’ve suddenly got a lot of new tools we can use, and they’re changing how we work, introducing new productivity and efficiency, and changing our roles. And I think all of that stuff is great. But that conversation leaves out something really important. When we talk about tools and process, what’s left out is the product itself: what we actually make and the experience we create. Ultimately, that’s the only thing that matters: What do we put in the hands of our customers, and what happens next? So for this session, let’s look up from our tools . Instead of talking about production, let’s talk about product , about the experiences we can create. We can create experiences that weren’t possible just a few years ago. We’ve been talking about adaptive interfaces and personalization for decades, right? But we suddenly have a technology that makes it all possible. And yet, as an industry, we’ve barely explored experiences beyond text-based chat and agents. We can create experiences that weren’t possible just a few years ago. What happens when you weave intelligence into digital interfaces, into the canvas itself? What becomes possible when the surface of our applications becomes collaborative? That’s what Sentient Design is about. More than generating assets, how do we use AI to create new kinds of experience? Veronika, you want to take us out? Our whoa moment Andreea Tufescu ." target="_blank"> Photo by Andreea Tufescu . Veronika I’m sure everyone in this room had the moment where you saw something that AI was able to do, and you said, Whoa, this is not like what came before. This is doing something I wasn’t able to do before. We’ll get to some more serious examples in a bit, but I want to start by sharing our “whoa moment.” This started with a little toy project that Josh and I created two years ago now. It’s called Sentient Scenes . You can give it a scene like, “the submarine descends.” And it starts to act it out. You could give it another prompt like “HAL 9000” from 2001: A Space Odyssey , and it will change form to act that out, too. So it’s changing its style, its mood, and its behavior based on the intent of the user’s prompt. ( Try it out here. ) There’s even this kind of personality in the square’s motion and the way it acts things out. The colors, the type it chooses, it’s all adapting to the mood of the scene. Like I said, this is just a little toy, but it really cracked something open for us: This is the entire interface adapting to the user’s intent without explicit instructions. Josh Four things really jumped out at us about it: First, it’s an intelligent interface that goes beyond chat. It’s still got an open-ended input, but the way that it responds is not about text, but about a change in the interface itself. Second, it has personality without anthropomorphism. It’s not pretending to be human, but it does have some personality to it, in the way that it moves, the tone that it has. There’s something that feels like intelligence in there, but it’s not human intelligence. Third, it has awareness of context and intent. It not only describes the scene, it becomes the scene . And it does it in a way that reflects mood and emotion, so it’s intuiting more than just what’s in the simple text description. And finally, it’s open-ended within constraints. I think this is the most exciting thing about this era of interaction design: it can take any input and respond in a way that makes sense. But also works within this constraint. It doesn’t turn into some kind of robot fever dream. It’s always this recognizable stage that the actor is on, but the stage dressing changes. We made this a couple of years ago, and of course the technology kept changing. We continue zooming into the future. So Veronika, take us to the future. A world built as you explore it Veronika Yeah, let’s do it! Here we go, the future, exactly as I pictured. Okay, maybe not. This is a painting by a French painter named Eugène Galien-Laloue. He painted this Paris street scene at the turn of the last century, and I think it looks like a cool place to go, so let’s go there, let’s do it. Now we’ve entered Mirage 2, which is a world model that takes an image and a text prompt to create a world on demand. It’s building the world frame by frame as you explore it. So anything not in view hasn’t been invented yet. So we can walk across this street here and explore. We’re inventing whole new city blocks in Paris just by walking in that direction. Until we turn that way, it literally doesn’t exist yet. It’s being conceived in the moment, but still following the rules suggested by that original image. It’s still following the coherent laws and physics of that Paris world… except for that riderless horse we’ve got going. Josh What the hell is on that horse? Veronika Ignore that part. Josh All right. So I mean that’s a pretty impressive technical feat, but I want to draw attention to its implications: the world is created as you explore it, based on your specific actions. So it’s a one-of-a-kind place. Like Veronika was saying: the world is created at the very moment you turn this way or that. It’s a different experience for every person who explores it. It begins the same for everyone, with that same painting of Paris, but it quickly becomes something that is unique to you, this utterly individualized experience that’s mediated by AI, but created by the choices that you make. What if any digital experience worked this way? Veronika What if any digital experience could work this way? This is an interface that bends to you instead of forcing the reverse. It brings you what you need and lets you manifest it in the moment. This is an interface that bends to you instead of forcing the reverse. What if websites were generated this way, invented as you explore them? Instead of climbing through navigation, what if the views that you needed simply came to you? When would that be helpful, and when would it be utterly confusing? How do we make sure it doesn’t feel like a crazy robot fever dream? How do we make it grounded enough to make sense to the user? Josh If it’s a different experience for everybody, when is that helpful and when is that a hassle? How do you share information with people? How do you get back to where you were before when it’s a completely dynamic experience? This shows the dial turned all the way up to 11. What are quieter forms of adaptive interfaces that we can introduce through this awareness of context and intent? LLMs are masters of manner Josh It’s not particularly new to say that LLMs are powerful but weird. And so these observations aren’t going to be new to you. But I want to cast them in the particular light of what it means for experience design. First, fluent in intent. It’s what I was talking about with the Sentient Scenes concept of open-ended input. LLMs are really good at making sense of arbitrary open-ended inputs. They just get what you mean, right? Understanding intent used to be hard; it used to be really brittle. With older versions of Alexa, if you said, “switch the lights on,” instead of “turn the lights on,” you wound up stuck in the dark. Now that’s entirely handled. The systems understand what you mean and can act on it. Next, expert at manner. It means that they’re very good and flexible in their output, too. We know this from using assistants, right? They can adopt the tone and role that you give to them. But it’s also true of the mode or format of communication. They can speak or communicate through video, images, handwriting, or any of the messy ways we communicate as human beings. And across systems, too. So LLMs are very, very flexible in the input that they accept, and also super flexible in the output that they give. The trouble is they’re a little shaky on facts, right? It’s hard to know when you can actually trust them with the truth. How do we take the benefits of LLMs and also treat the weirdness of these things as an asset instead of a liability? A thing that can help with that is this fourth characteristic: They play well with others. They get along with other systems. So you don’t have to trust LLMs with the facts. Instead, you can ground them with RAG databases and MCP servers as other trusted systems. So when you add all this up, it turns out that LLMs are great at presentation. So: we can use LLMs to make design decisions in the moment, according to the systems and guidelines that we create, but leave the facts to other systems. What we get is a really flexible way of communicating that can change interaction mode or content or structure or behavior on the fly—sometimes all of them at once—according to what’s needed and appropriate. So that’s pretty exciting. But it’s also a little bit heady. So we’re gonna bring this down to earth now: Who’s ready for enterprise software? Enterprise software! Veronika Let’s do it! This is Salesforce Generative Canvas . It’s a plugin for Salesforce that assembles dashboards and content based on implicit context—your calendar, for example—or explicit questions. Salesforce Generative Canvas. Here you can see it gathering information related to an upcoming meeting on your calendar. You can also ask it a question like, “What has my team been discussing with this customer?” and it assembles the right information and the right UI to answer the question. Now what’s very cool is it’s using familiar design patterns from the Salesforce design system, and it’s pulling data from the usual Salesforce data sources. It’s not making anything up, just assembling it on the fly. So you get this really custom experience, but all the content is safe and trusted. And so to come back to Josh’s list of LLM attributes, the system inferred the relevant data from the context because it’s fluent in intent . It found the data sources because it played well with others . And it formatted them in the right way because it’s expert at manner . And here we’re kind of sidestepping the whole “shaky on facts” thing by using AI to focus on the presentation rather than the generation of the content itself. Bespoke UI: shape-shifting interfaces Josh We call this the bespoke UI experience pattern. It’s this shape-shifting interface, conceived in real time. Bespoke UI experiences compose their own layout or content or controls. (Sometimes these are called “generative UI,” but there are lots of other kinds of UI and design decisions that can be generated, so we prefer the term “bespoke UI” here.) This is the most “step one” of intelligent interfaces. These experiences, like Veronika was saying, usually have a constrained set of components filled from data from trusted sources. So it’s not making up the UI on the fly; it’s composing it. We let AI make some very simple design decisions about what to assemble in real time. So design systems and best practices, particularly in this bespoke UI experience pattern, become more important than ever. Veronika, you’ve got another example? Veronika More enterprise software! Okay, so now we’re looking at Cisco’s AI Canvas. This is a platform to let you explore network incidents. Cisco’s AI Canvas generates a data-viz dashboard view at right and also collaborates to let you drag new charts from the chat at left. Here we have a specific network incident. I’ve asked the system to troubleshoot the ticket, and the system populates the canvas on the right over here with all of these chart widgets. Each of these widgets is itself interactive, but they’re all design system components that the system has selected to match the relevant context and the relevant content here. So you’re getting a totally bespoke dashboard. We can also follow up and ask questions in the sidebar on the left. “Can you look for a correlation between these metrics?” And it replies not only in text but also in data visualizations. I think this chart is helpful, so I drag it onto the canvas, and the canvas all of a sudden becomes this collaborative surface between me and the system to research and collect the evidence I need to figure out the problem. Guys, what a difference from traditional SaaS software! Normally, I’d have to climb through layers and layers of navigation to find all the content that’s being shown here. Instead, it’s the reverse: the UI comes to me. The intelligent canvas Josh With bespoke UI, the system creates layouts for you: “I think you need this, so here’s a UI for that.” This Cisco AI Canvas offers a glimpse of the intelligent canvas experience pattern. The intelligent canvas goes a step further by manifesting the content you describe or ask for, and then the system and user collaborate to create the interface and content experience. So what we’re seeing here blends the bespoke UI experience generating a dashboard to start, but then blends into an intelligent canvas that becomes collaborative. It’s a pattern that’s really good for exploration and discovery. We’ll look at another example of it in a minute. At our agency, Big Medium, we’ve got three different projects with Fortune 50 companies right now. These are big, complex organizations that have a million different use cases and user scenarios. And over years and years, their applications grow over time to serve all million of those cases. You know what the result looks like: a million different dashboards that you have to find yourself by navigating a horrible, dense information architecture and baroque navigation. These very big, complex companies are typically slow-moving, but we’ve found that they are jumping into these bespoke UI and intelligent canvas patterns very quickly. It’s because they feel the pain and weight of these million dashboards, and these solutions provide a real, immediate way for companies to modernize what has become a really slow and frankly torturous experience for their customers. These patterns let the system bring the interface to the user instead of forcing the reverse. When you really dial up the intelligent canvas even more, you can even manifest applications on demand. Some of this, of course, is becoming more familiar now. You’ve probably encountered this with chat assistants like Claude that let you make an app, and start using and improving it right away. Here, I told Claude that I wanted it to build an Asteroids game that I could play in the browser, and in seconds I was playing it during the chat. Then, you know, I made some additional updates, changed the scoring and the sound effects. And then, of course, I asked it to add zombies; I didn’t even know what that would mean. But then suddenly I had these green asteroids chasing me around, and I was very pleased with myself. On-demand interfaces, disposable software Veronika I also love Claude, and while Josh is playing his Gen X video games, I’m trying to get some real work done. So the other day I was using Claude, and I asked it to check the accessibility contrast between two colors. On its own, it decided to write up its own little application to do the calculation. I didn’t ask for an application, but it created it because it decided it was the best way to answer my request. It didn’t even keep it when it was done. So we’re starting to get these on-demand, in the moment, completely disposable applications. Josh I mean you know what this is, right? Just sort of like sketching out an idea and it becomes real? Yeah, it’s sort of like this guy. Wile E. Coyote tried this all the time: just gonna paint a tunnel on here, try to trick the Road Runner into running into the wall. But it becomes this real tunnel. It’s this magic, intelligent surface that worked for everybody except for poor Coyote, of course. (If I were him, I would sue Acme. I hear that’s in the works. ) Or maybe this guy, anyone? It’s this fundamental fantasy of conjuring what you want just by gesturing at it. Draw or say what you want to make it so. And it’s incredibly satisfying because the thing that you want or need just materializes. Many of us are already using AI to generate experiences as part of our traditional design production. But what happens when you put it directly in front of the user and let AI make those design decisions in real time? That’s the main quality of the intelligent canvas pattern. It can be a literal canvas or it can be sort of a metaphorical one, more like what we saw with Claude. Agents on the canvas Josh Here’s another example of an intelligent canvas. This is an application we’re creating with a client, a company called VIA, to explore data in a visual context. Think Figma or Canva, but for data. Somewhat similar to the Cisco example that we saw, you can ask for information, and it will draw the appropriate visualization on the canvas, an aspect of bespoke UI. But I’m going to show you something different, which is how we visualize an agent experience. You can ask the system for data, including asking it to do complex multi-step tasks: in this case, filling out a form to report energy usage at a facility. And if the system recognizes this as a task that it knows how to do, it will send in an agent to do the work. The agent appears just like another user in a multi-user environment, driving its own cursor on the canvas. If it has trouble, it will ask what to do. In this case, it notes there are three different buildings to analyze; what should it do? I tell it to do just one building. And then I’m following it as it works, in the same way that you would follow another user in Miro or FigJam. But I don’t have to. I could go off and use some other part of the canvas and do my own work. But here I can watch it and see what it’s doing to monitor its progress, and it’s showing its work as it goes. As it gets this data, it can show what it’s analyzing. The animation shows it sort of sniffing at the data as a way to indicate what it’s up to, what it’s processing. And then when it’s done, it generates this PDF. Thanks, see ya, it’s out of here. Then you can go through and see the tasks that it did, look at its reasoning, and of course see the finished result. I think what’s really interesting here, too, is that you can go back and follow its train of thought. This is a literal audit trail that it leaves behind—or any other user leaves as they work. Where did this data come from? What was the logic that got there? I can drill in and see what it’s doing, or continue with new tasks. It’s got those bespoke UI aspects of selecting the right component to display for each kind of data. It’s got collaborative aspects of an intelligent canvas. It’s got an agent that’s going off and just getting it done on its own. This is an intelligent interface that is very much not a chat experience. This is an intelligent interface that is very much not a chat experience. It’s a different kind of interaction model and mental model that we’re creating around the visual exploration of data. So Veronika, I think there’s a lot more to explore here. Sentient Design provides the map Veronika Absolutely. These are just a few examples, and they’re only scratching the surface. We’ve been working this into all of our client work at Big Medium. And of course we’re hardly the only ones doing this, but the work has been pretty unevenly distributed in the industry. It’s been kind of haphazard so far, and there’s really been no uniform vocabulary or framework for what types of experiences to create, or even what those types might be. As we explored this work, we needed a map. We wanted to identify all of the species of intelligent interfaces that we could find, experiences with the awareness and agency to respond to your users in the moment. Josh Friends, it took us two years to explore these intelligent interfaces and their patterns. But I think we cracked it, and we put it into a book. I give you: Sentient Design ! It’s available at all of your favorite booksellers. We hope you enjoy our book. We’ll get back to that map that Veronika mentioned in a moment. But first I want to say I could not have written this book without Veronika. So halfway into this thing, I think it’s probably past time for us to do some introductions. Veronika We might be overdue, honestly. Two generations of interaction design Josh Well, hello. I’m Josh Clark. I lead an agency called Big Medium. I’ve been a product designer and strategist for 30 years, running Big Medium for about 25 of them. I’ve written a bunch of books about user experience for O’Reilly and A Book Apart and now Rosenfeld Media. (I don’t know if I mentioned that we’ve got a new book? Yeah, it’s called Sentient Design ?) So with all this experience, my assumption coming into this era was that I’ve got this UX stuff figured out. I understand product design. But as I’ve worked with machine-generated results, with machine learning, and in the last few years with LLMs, I’ve realized that a lot of those hard-won best practices need revisiting. And that’s where this one comes in. Veronika Andreea Tufescu ." target="_blank"> Photo by Andreea Tufescu . Hi, my name is Veronika Kindred. I’m a designer and researcher at Big Medium with Josh, and I’m a zillennial or elder Gen Z. I grew up in this world beyond static websites: TikTok, Instagram, algorithmic feeds, all those things which have turned out to be so good for our mental health, right? But also in my career, I’m AI native. I started at Big Medium right after ChatGPT ushered in the proliferation of LLMs. And so for all of my career, my work has focused on the design applications of AI. Josh Veronika doesn’t yet have my experience, but she’s also not burdened by it. And so you’re looking at two generations of designers here, and very literally: Veronika is not only my colleague, but also my daughter. I’m very proud of her. (She loves this part of the talk.) For me, working together has been a really productive relationship both personally and professionally because it’s helped me to develop new perspectives about what this new generation of experience design can be. AI is weird. It offers lots of new possibilities and also lots of new problems. And so we need new perspective here. This is a moment we’re figuring out what this is, who it affects. So the way that we’ve always done things has to be revisited—in process, as we’ve been talking about a lot today, but also in interaction design. Why does it have to be that way? The answer has to be better than “because that’s how we’ve always done it.” Across generations, across disciplines, across classes, across all facets of humanity, we need to seek out more perspectives right now—to share, to teach, to let go of orthodoxies. This is an opportunity to revisit everything. Like I said, I couldn’t have written Sentient Design without you, Veronika—or seen it so clearly without your perspective. Veronika I always blush. We do this every time and I always get embarrassed. Josh This is the best dad moment. The Sentient Triangle Josh All of that collaboration let us make the map that we’ve been talking about. And here it is! The Sentient Triangle! The Sentient Triangle defines four essential experience postures of intelligent interfaces: tools, chat, agents, and copilots. The Sentient Triangle is based on the wonderful work of Matt Webb. Thank you, Matt, for all of your help with this. You really unlocked something for us with this, as well as your help with the book. The Sentient Triangle organizes intelligent interface experiences across three attributes: Grounded: how reliable and consistent the experience is Interoperable: not only across systems, but also across formats and modes of communication Radically adaptive: experiences that are conceived and delivered in real time Grounded and interoperable have been a big part of computing for decades. The radically adaptive experiences are what LLMs have unlocked in the strongest way we’ve yet seen. Andreea Tufescu ." target="_blank"> Photo by Andreea Tufescu . Four experience postures Josh As you map these three dimensions, four postures emerge. Postures represent the relationship that the system has to the user. The way that you use the system and the way that it communicates with you is different across all of these. Tools are the most traditional computing experiences. They’re very transactional and controlled: here’s an input, you get an output. Chat is conversational, of course, but it’s not necessarily literal text dialogue. It’s open-ended, turn-based communication with a peer: You say something, it responds, you respond to that, and together you craft a whole meandering journey that is unique to the experience and wasn’t designed as any one happy path. As the user, you have to manage tools and chat. You have to be involved at every step to keep them going. Agents, of course, you delegate to. You tell it what you want to happen, and the agent makes a plan, executes it, decides when it’s done, and if all goes well, comes back with what you’re looking for. Copilots support you. This is a posture that stands by and waits until it can be helpful. Otherwise, it stays out of your way. Spell check is part of the long history of the copilot posture. It’s very quiet and deferential; it says, here’s a little correction that you might consider, take it or not. It’s a background task that is supporting you constantly, ambiently. So you use tools, you talk to chat, you delegate to agents, and you’re supported by copilots. When you go down to a lower altitude in the Sentient Triangle, 14 different experience patterns become visible. Unfortunately, we don’t have time to talk about all of these today, but we’ve already talked about bespoke UI and intelligent canvas. (I don’t know if I mentioned we’ve got a whole book about this, though, friends.) The Sentient Triangle maps 14 experience patterns for intelligent interfaces. But with 14 different experience patterns, there is so much that we can explore. And you can also blend these, like we already saw with the Cisco example blending bespoke UI and intelligent canvas. But they all have a common theme, Veronika. Behavior design and creative direction Veronika Yes, absolutely. Designing these intelligent interfaces is ultimately about behavior design. It’s about teaching the systems to be able to make reliable design and interaction decisions in the moment. The effect is kind of like installing a designer right into everybody’s monitor so that anytime they visit any website, a designer can provide the right experience for the moment. The intelligent interface becomes collaborative between the system and the user. This is delegation, not abdication. This is delegation, not abdication. Designers might not be drawing every single pixel or designing every single interaction. We may not be designing fixed paths anymore, at least not at the level that we’re used to. Instead, we’re setting the system’s goals, its rules of engagement, the tools and interactions it may use, and when it may use them. These still all fall under the designer’s responsibility. You become the creative director who gives the system its brief. Josh Right. AI might be making real-time design decisions, but designers are creating the environment, the machinery that AI will work within, and humans too. In this aspect, it’s not all that different from the work that we’ve always been doing, where we create the interaction model, the mental model, the specific controls and tools that can be used. The new thing is that we’re also teaching AI to use, manipulate, or present content and interaction within that specific environment. This is behavior design, right? Interaction design has always been about behavior design—traditionally the design of user behavior. Now our design decisions define system behavior. And system behavior determines the experience. What we’re getting at is teaching systems autonomous behavior. That’s agentic behavior, so let’s talk a little bit about agents, Veronika. Agents and the manager experience Veronika Yeah, let’s do it. We already saw an agent at work in that VIA example we showed earlier. The point of agents is that you can delegate to them. You give them the mission, and then they go and do it. Now some people say that this might mean the end of the interface. “If the agents are doing everything, there’s no interface to show,” they say. Josh, I believe we have a technical term for that? Josh Yeah, let me see, what’s that technical term. Veronika The word is hoo-ha . Josh Right! That is hoo-ha, friends. Veronika We still need transparency and explainability when agents do their work. We do need experience and interface design for agent experiences, but its nature absolutely changes. The consulting firm BCG published a big study recently , and they basically found that people who manage agents intensively report deep cognitive exhaustion. The researchers call it brain fry . You’d think, hey, wait, agents are doing my job for me. It should be easier, not more exhausting. But instead, this group of heavy users of agents reported brain fog, buzzing, headaches, impatience. One of those reasons—and this matters for us here—is the ergonomics of the agent experience. The experience of managing agents has not yet been thoughtfully designed or considered. Josh The user experience gives way to the manager experience. If agents are doing a lot of the tasks that users used to do, we now have to figure out how to manage all those agents doing those tasks. At the moment, that generally consists of reading walls and walls of text going by, effectively watching the console as things happen. The user experience gives way to the manager experience. But even aside from the ergonomics, managing is simply hard. For those of you who have made the transition from independent contributor to manager, you know what I’m talking about. It’s a very different thing to suddenly have to keep track of the missions, tasks, plans, and progress of a whole bunch of people. The same thing is true of dealing with agents. That’s a really different skill, and it takes some new design to help people adapt. It’s just as true in the digital realm as it is in the physical. Veronika, we take this up a lot in the book. (I’m not sure I mentioned it, it’s called Sentient Design .) Veronika Yeah, that’s right. This idea of the manager experience is another area that we lean into. How do we help people manage these agents in intelligent interfaces? In the book we describe five phases of delegation that apply just as much to systems as they do to people. Not all of these phases always require user interaction; it depends on the complexity of the task. The five stages of managing agents (and people, too). These are the transitional seams where support can really be designed with intention: setting the mission; reviewing the plan; monitoring the work; interrupting or redirecting; and reviewing the result. We’ll focus here on monitoring the work. This is the part that the BCG study called out as particularly difficult. Right now the agent experience is overwhelmingly text-based, and managing the detailed communications of agents is just a lot to track as they do their work. The NPC pattern: agents as “just another user” Veronika How could we do that differently? The VIA example that we showed earlier was one example of a method we call the NPC experience pattern . NPC stands for non-player character, a gaming term for a character that’s run by the system rather than by a person. The agent does its work as another user, and you can monitor its work just as you would another user in the system. Josh Here’s another example of the NPC pattern. It’s a Chrome extension called Pointer that works in Google Docs. Here I’ve asked it to review my document for technical accuracy. It goes in and makes suggestions like a colleague or human editor would. I don’t have to go into some separate chat interface. It behaves as an NPC within the rules of the application. You can see the edits that it’s made. It’s doing this as my account, which I think is just a limitation of working as a Google Docs plugin. It would get extra points for making it clear that my robot was doing this work. But as an experience pattern, it’s solid: Instead of going off to some other place, another application or a sidebar to interact with the intelligence, it’s woven into the canvas of the application. It uses familiar “tracked changes” features that human users would use. The NPC pattern brings the intelligent interface into the same tools and channels that human users use. A simple version of that is in chat environments or Slack, where the robot is just present in the channel, posting and replying like human users. And you can make that even richer, as we saw in the earlier VIA intelligent canvas example. Now for something completely different Josh This is a prototype created by designer Filip Havlena to visualize agents—as Sims , basically. The model has lots of tools available to it; some of those tools manipulate the agents’ 3D bodies. And you can spawn new agents and put them to work with more traditional tools like Google Docs. Here you can see it using Google Calendar to create a new calendar event, but you can also use it to do work in word processing documents or spreadsheets too. As it works, you can see its progress puffing away above its head, showing you what the agent is thinking. When it’s finally done, you can see the result in the calendar. It’s a new way to show the agent’s progress. And again, you can just spawn a whole bunch more of these things and put them to work on a whole bunch of tasks all at once. And you can see them doing their work or glaring at you because they resent the crummy tasks that you’re giving them. This is obviously pretty whimsical, and the utility of this would have to be pretty specialized. But it’s worth imagining the potential use of spatially represented agents across a city or some geography. What are the possibilities of representing these things not as a churn of console logs, but actually representing their work in a more direct mental model? Another interesting question is what happens when they run into each other in the wild ? You know, will they get along? Will they compete? Will they ignore each other? Will they start crazy cybersecurity chat channels? Will they hack things? How do we design for this? We still have to figure all that out. But again, it’s ultimately about behavior design. At last, we get to invent again Josh There’s so much to invent and explore here. It’s been 15 years since mobile demanded that we explore new interaction paradigms. And that’s what AI is asking of us now. I think we’re a little rusty at it. The last 10 or 15 years of design innovation have mostly been about design ops. The questions that have dominated our industry have been: How do we work together? How do we do design at scale? How do we create design systems? We have done that at the expense of product innovation. We have had very little focus as an industry on new interaction design, new product design. At last, that’s the work ahead of us now. The opportunity and responsibility is to explore this new material and discover the truly new and meaningful experiences we can create. We get to invent again. It’s not the material or the tool that makes us designers. It’s our creativity and judgment and ability to understand the problems and people deeply. The work is not AI. The work is pointing AI at problems worth solving, imagining experiences that weren’t possible before that can answer those problems better than anything that we’ve had before. What are the thorny problems that intelligent interfaces can uniquely solve? The work is not AI. The work is pointing AI at problems worth solving. Let’s not do this for novelty, or because the market says “we need an AI solution.” Ask: How do we help people? How do we make their lives better? That is what designers do when we’re working at our best. These are design questions, and these are fun, hard questions to solve. Friends, I am excited. Can you tell that I am excited? I’m even excited about enterprise software. This is a rare moment that we have here. In my 30 years of doing this, this is the most excited and creative that I’ve felt as a designer. You are needed more than ever Josh I invite you to approach that excitement and enthusiasm with real thought and intention. All of us here, the people right here in this room, we have real influence and agency over how this rolls out. If we don’t decide the best way to use this strange and powerful technology, then the technology will decide for us—or the billionaires. The future should not be self-driving. This technology is being shaped right now, and so is its application. How it is used is up to us. We have this astonishing new design material that can really elevate our craft. There’s a lot of conversation about how to use AI to bring more productivity and speed to our craft. I think that’s important and useful. But in the rush to grind out new efficiencies, let’s not lose sight of the fact that we have real creative power with this material to create significant, meaningful value for our customers and for the businesses that we serve. Those creative opportunities are huge. They can elevate design—and designers!—if we do it right. That is up to you. You have the tools and this new technology, of course, but more important, you have the creative material right now—today!—to make something amazing. So Veronika and I invite you to please do that, friends. Make something amazing. Thanks a lot. Veronika Thank you, guys, so much. Thank you. We can help you. Big Medium helps solve complex problems with intelligent interfaces. Our Sentient Design practice includes product strategy and product design engagements, workshops, and Sentient Design sprints. Get in touch to learn more.
DigitalOcean BlogMulti Author Blogs3 min read
Virtualization, Responsible Disclosure, and CVE-2026-99312
The wall between you and your neighbor Every cloud customer gets the same promise: a bright-line boundary between your workload and your neighbors. Your virtual machine is yours, your neighbors’ are theirs, and the hypervisor keeps it that way. A hypervisor is large, complex…
Web Tools WeeklyMulti Author Blogsread at source
Web Tools Weekly Issue #696
Frameworks, Git/CLI, Uncats
Mux BlogCompany/Startup Blogs4 min read
Email support is dead, long live support by email!
Spam, AI agents, and auto-responder loops pushed Mux to move ticket creation to a web form. Here’s what changed, why, and how to reach our support team now.
David BushellMore Front-end Bloggers5 min read
Where we’re going, we don’t need chatbots
“You’ve been working hard, why not take a weekend vacation!” Your chatbot says, after a 72 hour unattended session. It says that New York is nice this time of year. You ask it to book the cheapest flights. Half the airlines respond with a 429 code because your residential IP is part of five botnets. […]