Podcasts about UX

AI is changing how we design and build products faster than ever.In this episode of Future of UX, I'm talking with Felix Haas, who is currently working at Lovable. Felix shares a lot of insights online about building products with AI, vibe coding, and how the way we create software is evolving.Felix and I actually go back quite a few years. We first met in Berlin when he was running his own agency there, and since then I've been following his journey and the ideas he shares about building with AI.What always fascinated me about Felix is his mindset. He comes from a design background, but he thinks very much like an entrepreneur. He constantly experiments, builds things, tests ideas, and isn't afraid when something doesn't work.And honestly, that builder mindset might be one of the most important skills right now.In our conversation we talk about where we actually are with AI today, what “vibe coding” really means, how the product development process is changing, and what all of this means for designers.One thing we both agree on:In the future, it might not be enough to just design products. Designers will need to build, experiment, and ship ideas much faster.In this episode we talk about• Where we actually are in the current AI wave• What “vibe coding” means and why people talk about it• Why building products is becoming easier than ever• The shift from designing interfaces to building real products• Why experimentation and curiosity are becoming essential skills• The mindset designers need in an AI-driven world• Why great products are still about solving real problemsAbout FelixFelix Haas works at Lovable and shares insights about AI, building products, and vibe coding. Before that, he ran his own agency in Berlin and has been active in the design and startup world for many years.Follow Felix:LinkedInSubstrackAI for Designers: 5-week Bootcamp

Join Fredrik Mattsson, CEO of Inamo, for a deep dive into one of the most common—and costly—mistakes in software development: building too much. With over a decade of experience in enterprise SaaS and digital transformation, Fredrik has seen firsthand how "feature bloat" slows down engineering teams and confuses users. In this episode, we explore how modern product teams are shifting away from "building and hoping" toward an evidence-led approach, using AI to turn qualitative user feedback into actionable insights before a single line of code is written.

Every has unveiled a new product, built by CEO Dan Shipper. It's called Proof, a free, open-source, live collaborative document editor built for humans and AI agents to work in together. Proof started as a Mac app designed to show the provenance of AI-written text—purple for AI, green for human. But when Shipper rebuilt it as a web app with real-time collaboration, something clicked. Suddenly, everyone at Every was using it for everything from planning docs, to creative writing and even daily to-do lists. The team realized they needed a lightweight space where their OpenClaw agents and humans could co-author documents and leave comments. In this special episode, Shipper is joined by Every chief operating officer Brandon Gell, Cora general manager Kieran Klaassen, and head of growth Austin Tedesco to demo Proof live and share how it's changed the way they work. Brandon walks through a loop where his Codex agent writes a plan, Dan's personal Claw R2-C2 reviews it, and the humans just steer. Austin explains how he uses Proof to write a weekly food newsletter, texting ideas to his Claw on runs and watching an outline take shape. And Kieran makes the case that Proof's power is its lightness—just a link you can hand to any agent or colleague.The conversation covers what "agent native" means in practice, why AX (agent experience) matters as much as UX (user experience), what happens when 10 agents edit one document at the same time, and why some writing is now better read by an AI than a human.If you found this episode interesting, please like, subscribe, comment, and share!Want even more?Sign up for Every to unlock our ultimate guide to prompting ChatGPT here: https://every.ck.page/ultimate-guide-to-prompting-chatgpt. It's usually only for paying subscribers, but you can get it here for free.To hear more from Dan Shipper:Subscribe to Every: https://every.to/subscribeFollow him on X: https://twitter.com/danshipperGet started building today at framer.com/dan for 30% OFF a Framer Pro annual plan.Download Grammarly for free at Grammarly.comTimestamps 00:02:00 — Introduction and the origin story of Proof00:07:24 — From Mac app to collaborative web editor00:09:00 — What makes Proof “agent native”00:14:30 — Live demo: watching an agent join and write inside a shared document00:20:51 — How Austin uses Proof for creative writing and food journalism00:24:30 — The challenge of multiple agents editing one document simultaneously00:26:48 — When AI-written docs are better read by agents than by humans00:29:30 — Brandon's agent-to-agent collaboration loop00:37:09 — Proof as a lightweight scratchpad vs. existing tools like Notion and GitHub00:42:18 — Why Proof is open source and what that means for buildersLinks to resources mentioned in the episode:Proof Editor: https://proofeditor.aiProof GitHub repo (open source): https://github.com/EveryInc/proofEvery's compound engineering plugin: https://github.com/EveryInc/compound-engineering-plugin

In this episode, Calle introduces Numopay, an open-source Bitcoin payment terminal that enables tap-to-pay experiences similar to fiat systems. We explore its technical foundations, privacy features, future developments, and the broader ecosystem of Bitcoin payment solutions.Takeaways:

Today, I'm joined by Zack Isaacs, founder & CEO of Movemint.   Movemint is an athletic events platform connecting participants, organizers, and brands through registrations, training integrations, and sponsorship marketplace.   In this episode, we discuss modernizing the event registration experience.   We also cover:   Events driving high-intent spending cycles Growing through Strava and Meta integrations Providing race sponsors with data and analytics   Subscribe to the podcast → insider.fitt.co/podcast  Subscribe to our newsletter → insider.fitt.co/subscribe  Follow us on LinkedIn → linkedin.com/company/fittinsider    Movemint's Website: www.movemint.cc  For Brands: https://www.movemint.cc/brands  For Organizers: https://www.movemint.cc/why_movemint    -   The Fitt Insider Podcast is brought to you by EGYM. Visit EGYM.com to learn more about its smart fitness ecosystem for fitness and health facilities.   Fitt Talent: https://talent.fitt.co/  Consulting: https://consulting.fitt.co/  Investments: https://capital.fitt.co/    Chapters: (00:00) Introduction (01:08) Zack's background (02:10) Movemint's atomic unit (03:21) Legacy platform gaps and opportunities (04:30) High-intent spending cycles (05:12) Prioritizing organizers and brands (07:00) Movemint for Brands launch (08:05) Strava's community playbook (09:40) Small to large organizer evolution (11:15) NYC Marathon vs. tech-enabled events (12:01) Building community on other platforms first (13:20) Strava and Meta integrations (14:10) Training data driving event signups (15:10) Run club boom and COVID tailwinds (16:10) Design and UX differentiation (18:05) Olia Birulia: Strava Routes designer (19:25) Speed vs. quality (21:15) Hiring from network (23:25) Endurance athletes as employees (24:47) Movement for Brands (26:00) Brand sponsorship data and analytics (28:10) Race photography and brand tracking (29:10) Sponsorship marketplace mechanics (30:05) Gravel and road running focus (31:11) High Rocks and triathlon growth (32:00) $3.2M raised across pre-seed and seed (33:15) Strava's co-founder on board (34:00) Building profitable and enduring business (34:36) Conclusion  

Feel like your UX job search is full time job? Here are 5 things you can start using today to save time, reduce overthinking, and make real progress in your UX or Product job search. These are tips that Sarah sees working for people inside her UX career coaching program, Career Strategy Lab, and some she uses in her own work every day.Topics discussed in this episode of the Career Strategy Podcast:How to create a plug-and-play script document so you never start from scratch on emails againHow text replacement tools like TextExpander can automate repetitive job search messagesWhy using a Pomodoro timer can dramatically increase your job search productivityWhy committing to following up three times eliminates the worry spiral of being ghostedHow to run a weekly "Job Search CEO Hour" to track what's working and course correct fastRESOURCESText Expander https://textexpander.com/Pomodoro Timer https://pomofocus.io/Flow Timer https://www.flow.app/

Anne, an African-based UX researcher, talks about her transition from teaching into the tech scene, reflecting on how her focus on the well-being of individuals led her to UX research. She explores the silent harms of technology and how products are often designed to be addictive. She also offers UX researchers a valuable perspective on balancing business strategy with the responsibility of protecting users' mental health.

The Mobile Game That Makes Money… But nobody understands why. Well, we kinda do. In this episode of Two and a Half Gamers, we dive into one of the strangest successful mobile games they've seen recently: Cell Survivor.The game looks confusing, the onboarding is painful, and the design feels chaotic. Yet somehow it's making serious money, especially in Asian markets.So the team breaks down what's actually happening under the hood.They discuss the game's unusual progression systems, monetization design, Asian-first market strategy, and how games like this manage to scale despite confusing UX and questionable gameplay clarity.Sometimes mobile gaming success is not about polish.It's about understanding the right audience and scaling the right mechanics.Get our MERCH NOW: 25gamers.com/shop--------------------------------------PVX Partners offers non-dilutive funding for game developers.Go to: https://pvxpartners.com/They can help you access the most effective form of growth capital once you have the metrics to back it.- Scale fast- Keep your shares- Drawdown only as needed- Have PvX take downside risk alongside you+ Work with a team entirely made up of ex-gaming operators and investors---------------------------------------For an ever-growing number of game developers, this means that now is the perfect time to invest in monetizing direct-to-consumer at scale.Our sponsor FastSpring:Has delivered D2C at scale for over 20 yearsThey power top mobile publishers around the worldLaunch a new webstore, replace an existing D2C vendor, or add a redundant D2C vendor at fastspring.gg.---------------------------------------This is no BS gaming podcast 2.5 gamers session. Sharing actionable insights, dropping knowledge from our day-to-day User Acquisition, Game Design, and Ad monetization jobs. We are definitely not discussing the latest industry news, but having so much fun! Let's not forget this is a 4 a.m. conference discussion vibe, so let's not take it too seriously.Panelists: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Jakub Remia⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠r,⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Felix Braberg, Matej Lancaric⁠Podcast: Join our slack channel here: https://join.slack.com/t/two-and-half-gamers/shared_invite/zt-2um8eguhf-c~H9idcxM271mnPzdWbipgChapters00:00 Chinese Humor & First Impressions01:13 Intro – What Is Cell Survivor?02:00 Why This Game Is Making Money04:10 First Gameplay Reactions06:40 Painful Onboarding Experience09:20 The Idle Reward System12:10 Asian Market Design Philosophy15:20 Why UX Doesn't Matter Here18:30 Monetization Structure21:40 Why This Works In Asia24:30 Western Audience vs Asian Players27:00 UA Strategy Discussion30:10 Dragon-Style Creative Strategy33:10 Rush Royale Comparison35:40 Final Thoughts---------------------------------------Matej LancaricUser Acquisition & Creatives Consultant⁠https://lancaric.meFelix BrabergAd monetization consultant⁠https://www.felixbraberg.comJakub RemiarGame design consultant⁠https://www.linkedin.com/in/jakubremiar---------------------------------------Please share the podcast with your industry friends, dogs & cats. Especially cats! They love it!Hit the Subscribe button on YouTube, Spotify, and Apple!Please share feedback and comments - matej@lancaric.me---------------------------------------If you are interested in getting UA tips every week on Monday, visit ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠lancaric.substack.com⁠⁠⁠⁠⁠⁠ & sign up for the Brutally Honest newsletter by Matej LancaricDo you have UA questions nobody can answer? Ask ⁠⁠⁠⁠⁠⁠⁠⁠Matej AI⁠⁠⁠⁠⁠⁠ - the First UA AI in the gaming industry! https://lancaric.me/matej-ai

Konuklar: Aziz Alp Timur, Beste Tanrıverdi Köse, Ecem Erdal, Reyhan İkan Çavuş 89. bölümümüzde konuğumuz UX Research ekibi oldu. Ekip yapısını, projelerini, teknoloji stack seçimlerini ve çok daha fazlasını konuştuk! Trendyol Talks'da Trendyol'daki kültürümüzü, kültürümüzden beslenen iş yapış biçimlerimizi ve ritüellerimizi konuşuyoruz. Trendyol Talks podcast kanalımızı takip etmeyi unutmayın!

In this CTO Series episode, Daniel Harcek shares how leading engineering teams across radically different scales — from a 7-person fintech startup to a 2,000-person cybersecurity company — taught him that leadership isn't one-size-fits-all. We explore how he builds AI-first organizations, drives agile transformations, and why he believes every person in a company should think like a tech person. What Works at 10 People Breaks at 100 "Leadership is contextual, not absolute. What works with 10 people breaks at 50, at 100." Daniel's career spans from building a 30-person team for a German startup out of Žilina, Slovakia, to leading 70 engineers at Avast's mobile division within a 2,000-person organization, and now running a 7-person team at WageNow. Each scale demanded a fundamentally different approach. At smaller scales, you strip away operational overhead and push ownership directly to the people. At larger scales, you need guardrails, dedicated roles, and structured processes that the smaller team would find suffocating. The lesson: don't carry your playbook from one context to another — rebuild it for the reality you're in. End-to-End Ownership Replaces Specialized Roles "Each engineer owns quality for the task he delivers. And he owns the fact that it comes to production." At WageNow, Daniel runs without dedicated QA people — in a fintech company where quality can't be compromised. Instead, each developer owns quality end-to-end, from code to production. This isn't recklessness; it's intentional design. When teams are small, you set up the system so that it's safe to break things, then trust people with hard tasks. The result: people grow faster, move faster, and care more about what they ship. In larger organizations, you might need specialized DevOps, QA, and platform roles — but the principle of ownership stays the same. The Buddy System and Scaling Without Losing Alignment "The buddy system is one of the easiest things you can do. One buddy for a newcomer for the first 1, 3, 6 months — they often become friends." When scaling fast, Daniel focuses on three things: strong on-boarding guides, well-maintained documentation (now much easier with AI), and a buddy system that pairs every newcomer with a dedicated colleague. The buddy system works because it scales the human side of on-boarding — a tech lead or manager can do one-on-ones, but that's formal, and new people might be scared to speak up. The buddy creates a safe channel for questions, concerns, and cultural integration. Beyond people, scaling also means investing in automation and observability so that as you grow with customers, you grow with failures too — and your incident reporting doesn't burn out the team. Building an AI-First Organization "Every person uses AI. Every person has the capability to use AI. The company builds a second brain so AI can build on top of that." At WageNow, Daniel has implemented what he calls an AI-first organization, inspired by Spotify and other companies pioneering this approach. The concept is simple: before doing any task, ask whether AI can help you deliver the output faster or better. This applies across the entire company — not just engineering. Daniel looks for people in HR, accounting, and UX who understand automation tools like n8n or Make.com alongside AI. The key ingredients: Curate the data: Build a company "second brain" with clean, structured context for AI tools to work with Train the muscle: AI ability is like a muscle — people must use it daily because these skills didn't exist 2-3 years ago Share what works: Exponential AI adoption happened at WageNow once people started sharing their successes and failures with AI tools Respect the guardrails: Data privacy and regulation compliance remain non-negotiable The hidden productivity gains, Daniel argues, lie not in engineering (which gets all the attention) but in operations, accounting, HR, and every other area of the business. Selling Transformation: Financial Arguments for Leaders, Ownership for Teams "For the leaders, it's the financial thing and the cultural thing. For the people doing the work, it's personal development — having more control, having more ownership." At Ringier Axel Springer, Daniel proposed and led a company-wide agile transformation — a 1-2 year effort that required convincing the CEO, product teams, marketing, and sales to change how they operate. His approach: build a dual argument. For leadership, frame the change in financial and cultural terms — more revenue with the same people, better visibility into how work translates to business outcomes. For the people doing the work, emphasize personal growth, increased ownership, and transparency. The transformation breaks silos between engineering and product, creating a shared backlog agreed with all stakeholders. Daniel looks for people with high agency — those who can reinvent and change themselves from the inside, not just wait for a change agent from the outside. Balancing Experimentation with Operational Excellence "The SRE books helped me understand quality as a feature — because quality is basically how reliable you are for your customers." When asked about the books that most influenced his approach as a CTO, Daniel points to the Site Reliability Engineering series from Google — three books that frame quality as reliability, a feature your customers experience directly. Alongside those, he recommends The Lean Startup by Eric Ries, because he believes all tech people should have a sense of business and customer understanding. Together, these books guide how to balance rapid experimentation with operational excellence as the organization scales. About Daniel Harcek Daniel is a technology executive with a proven record scaling engineering organizations across fintech, cybersecurity, and digital media. Builds AI-first teams, operating models, and delivery cultures aligned with product strategy. Led platforms serving 30M MAU, deployed fintech capital pilots, transformed agile delivery at internet scale, and mentors global tech communities and ecosystems worldwide actively. You can link with Daniel Harcek on LinkedIn.

Daniel Echeverri es un diseñador e investigador colombiano que vive en la República Checa. El es profesor en Masaryk University. En esta charla nos cuenta sobre su investigación donde el objeto tangible es soporte de narrativas. Específicamente él trabaja con títeres, marionetas. Estas marionetas sirven para generar teoría y conocimiento, también para informar diseños de museos. Hablamos de eventos históricos de Colombia entrelazados con la historia personal de su familia. Sobre materialidades y juguetes. Esta entrevista es parte de las listas: Juegos y diseño, Arte y diseño social, Colombia y diseño, Diseño UX, Investigación y diseño y Museos y diseño. Daniel nos recomienda: Assassins Creed- es una clase de videojuegos. Red Dead Redemption 2 video juegos de acción/aventura con tematicas históricasCatán y Marco Polo, juegos de mesa. ⁠Gente Local:⁠ un podcast

Joseph Chalom and Danny Ryan discuss the institutional outlook on Ethereum and why it is “the only game in town.” Bits + Bips is spreading its wings Starting soon, new episodes will only be published on our brand‑new feeds. What you need to do: Click the links below. YouTube Apple Spotify X Smash Follow or Subscribe.

It's EV News Briefly for Thursday 05 March 2026, everything you need to know in less than 5 minutes if you haven't got time for the full show.Patreon supporters fund this show, get the episodes ad free, as soon as they're ready and are part of the EV News Daily Community. You can be like them by clicking here: https://www.patreon.com/EVNewsDailyMIDDLE EAST CONFLICT LIFTS UK FUEL AND ENERGY COSTSBrent crude surged past $84 per barrel and UK gas prices spiked to a three-year high of £1.44 per therm after Qatar halted LNG exports following Iran's threat to attack tankers in the Strait of Hormuz, with the RAC warning UK forecourt prices will feel the full impact within a week. Home EV charging costs are shielded for now by the energy price cap — fixed at 24.67p per kWh for electricity until end of June — but wholesale price rises could push the cap higher from July, making both home wallbox and public charging more expensive.​EUROPEAN FLEETS COULD SAVE €246BN BY 2030A new EY and Eurelectric report finds that fully electrifying Europe's corporate fleets could deliver up to €246 billion in cumulative savings and cut one billion tonnes of CO2 by 2030. However, the authors warn that cheaper running costs alone will not drive mass uptake, calling for coordinated action from manufacturers, policymakers, grid operators and finance providers to tackle high upfront costs, uncertain residual values, and charging infrastructure delays.CUPRA BORN FACELIFT BRINGS SHARP NOSE, SMALL TWEAKSCupra has facelifted the Born with a "shark nose" front end, triangular matrix LED headlights, a continuous rear light strip, and new 235 mm tyres across all five wheel options, while the aerodynamically improved 79 kWh variants now claim around 600 km (373 miles) of WLTP range. A new entry "Born Plus" trim pairs a 58 kWh battery with a 140 kW motor — figures that match Ford's Capri LFP option and strongly suggest a switch to LFP cells from the updated MEB+ platform — though Cupra has not confirmed drivetrain details and appears to be saving that announcement for a related reveal, likely the VW ID.3 facelift later in 2026.FORD EV SALES SINK 71% AFTER LIGHTNING EXITFord's US EV sales collapsed 71% in February 2026 to just 2,122 units, the steepest monthly drop in its EV history, driven by the discontinuation of the F-150 Lightning and the expiry of the federal EV tax credit. Ford's Model e division lost $4.8 billion in 2025 and is forecast to lose another $4–5 billion in 2026, with profitability not expected until 2029; the company has already booked a $19.5 billion writedown and is pivoting to a new ~$30,000 midsize electric pickup it hopes will revive the business by 2027.LUCID PATCHES GRAVITY SOFTWARE AGAINLucid Motors has pushed software update 3.4.4 to the Gravity SUV, targeting AC charging improvements and Drive Assist availability, following a January update that resolved around 95% of earlier software issues — with the car averaging a new update every 24 days since launch. Lucid has closed its online configurator for both the Air and Gravity while it prepares its 2027 model year announcement, and Air owners face a $950 hardware upgrade bill to access the newer UX 3.0 platform already running in the Gravity, due to arrive by autumn 2026.MITSUBISHI READIES LEAF-BASED EV FOR CANADAMitsubishi is preparing its first all-new model since the Eclipse Cross for Canadian dealerships in 2026, built on Nissan's CMF-EV platform and LEAF architecture, with spy shots showing a heavily camouflaged prototype that shares the LEAF's roofline, proportions, and rear hatch panel. Both models will be built side by side at Nissan's Kaminokawa plant in Japan, and Mitsubishi may receive the smaller battery pack to undercut the LEAF on entry price — a strategy that would see Nissan supply the foundations while a cheaper sibling competes for the same buyers.ALPITRONIC UNVEILS HYC400 SERIES 2 CHARGERAlpitronic has launched the HYC400 Series 2, retaining the 400 kW maximum output of its predecessor while upgrading to a 22-inch touchscreen (up from 15.6 inches), second-generation silicon carbide power stacks, and a higher continuous output current of 600 A (up from 500 A). The unit maintains 97.5% charging efficiency but standby power consumption rises significantly from 43 W to under 100 W, and cable options narrow to a single 5-metre length; Alpitronic will sell both generations simultaneously to suit different site requirements.​APTERA SHOWS FIRST VALIDATION-LINE VEHICLE PHOTOAptera Motors has published the first photo of a vehicle off its validation assembly line, marking a milestone for its three-wheeled, solar-assisted EV that claims 400 miles of range from a 44 kWh battery and up to 40 miles of daily solar charging, classified as a motorcycle to bypass certain safety regulations. The launch edition price has risen to $40,000 — a $9,300 increase from prior estimates — though a $28,000 model is planned for the future, and with nearly 50,000 pre-orders and a stated daily capacity of 80–100 vehicles, Aptera claims it could fulfil all orders within 500 days of full production, though the end-of-year delivery timeline remains uncertain.​GEELY TARGETS DEFENDER WITH GALAXY BATTLESHIPGeely plans to launch the Galaxy Battleship in the UK in 2028, a blocky hybrid 4x4 aimed squarely at the Land Rover Defender and Toyota Land Cruiser, with a production design expected to stay 90–95% true to the Galaxy Cruiser concept shown at the 2025 Shanghai Motor Show. Built on the GEA Evo platform with steer- and brake-by-wire, it may use an AI-driven plug-in hybrid system with a stated output of around 858 bhp, and Geely is promising an interior that surpasses the Defender's for luxury — a bold claim for the Chinese brand's first foray into the 4x4 segment.​EU UNVEILS LOCAL-CONTENT RULES FOR CLEAN TECHThe European Commission has unveiled the Industrial Accelerator Act (IAA), tying over €2 trillion in public procurement and subsidies to low-carbon and "Made-in-EU" conditions across sectors including EVs, steel, cement, and wind turbines, with the goal of raising manufacturing's share of EU economic output from 14% to 20% by 2035. China is excluded from the initial trusted-partner list — which includes the UK, Canada, and the US — and foreign investments above €100 million from countries controlling 40%+ of global production would face strict conditions including capped 49% foreign ownership and mandatory technology transfer; BMW and Mercedes oppose the Act over fears of higher costs, while Renault backs it and the text must still clear the European Parliament before becoming law.​

本期嘉宾：彭林、十天、森森、蓝白、恺伦本期节目的主要内容有：· 关于荣耀 Magic V6 屏幕我们还有什么没说的· 关于显示器我们还有什么没说的· 苹果发布众多新品· 荣耀机器人手机亮相· 小米 Tag 海外正式发布，重仅 10 克 120 元起· 349 英镑起，Nothing Phone (4a) 系列正式发布· 海信发布 UX 2026 款 RGB-Mini LED 旗舰电视· GPT-5.4 来了：能操控电脑、写代码、做表格还有众多观众朋友的热心提问~每周五晚 8 点，爱否直播间，我们一起开心聊天

פרק מספר 512 (חזקה תשיעית!) של רברס עם פלטפורמה - קרבורטור מספר 40, שהוקלט ב-24 בפברואר 2026. נכון למועד ההקלטה עדיין אין מלחמה [לא התיישן טוב…], ואורי ורן מארחים את הנביא האורח נתי שלום לשיחה, דיונים, וויכוחים ותחזיות (דיסטופיות ברובן) על עולם שבו ה-AI כבר לא רק כותב קוד, אלא מחליף את המציאות כפי שהכרנו אותה. [01:58] "משהו גדול קורה": הניתוח של Matt Shumerבלוג-פוסט של המפתח Matt Shumer, שנקרא Something Big is Happening התפרסם בלא מעט מקומות והיכה גלים.מעבר מסקפטיות מוחלטת ("זה בחיים לא יעבוד") למצב שבו המודל עושה את כל עבודת הקידוד שלו.נתי - מה שמעניין פה זה הניתוח של שוק העבודה, ואיך נראה שוק ה-Hiring כפי שהוא היום.הדיבורים על "הכתובת על הקיר" זה כבר פאסה – "הכתובת היא כבר בכיס כמעט". הנתונים מראים ירידה משמעותית ב-Hiring שהתחילה כבר משנת 2025 ונמשכת לתוך 2026.“זה קורה עכשיו - ועכשיו אתה צריך לבחור באיזה צד אתה נמצא: הצד המרוויח או הצד הנפגע”.רן מדגיש שזה לא רק למפתחים – גם עורכי דין ורואי חשבון ובכל שאר המקצועות צריכים להחליט באיזה צד הם. יש כאן (לפחות) שני אספקטים עיקריים - איך אנחנו רואים את שוק התוכנה, ואז זה משפיע על כל שאר שוק העבודה.אורי - אנחנו רואים את ההשפעה מבפנים, בתוך שוק התוכנה. האם ישנן תעשיות שלא מושפעות עדיין, או לפחות לא מרגישות את זה?למשל יוצאי יחידות טכנולוגיות שמאוד מבוקשים בשוק, אבל ארגונים בטחוניים לא יכולים להכניס הרבה מהטכנולוגיות Cutting-edge הללו, לפחות לא בקצב שהן יוצאות.מועמדים כאלה אולי פתאום לא מתאימים בדיוק לעולם שרץ “בחוץ”.נתי משתף סיפור אישי/מקצועי על שיר אלגום, שנדחתה ממשרה ב-HR כי לא הכירה מספיק AI, ובתגובה הפכה למומחית שמרצה ב-Amazon.שינוי גישה: "העולם השתנה, הבנתי, אני עכשיו באירוע".אורי ונתי מחפשים השוואות למהפכות קודמות, ולא בטוחים אם יש כאלו בדיוק - מעבר משימוש ב-Intellect האנושי כדי לייצר יתרון - למצב בו "ה-Intellect עובר קומודיטיזציה".אין יותר Job security בהייטק המסורתי, וחזרה לכיוון של מקצועות יותר “מסורתיים”, פיזיים.[10:17] עידן ה-Agents וה-+Resumeנתי - קונספט של “Professional Agents”: מומחים כבר לא מוכרים את עצמם כעובדים, אלא כסוכנים, או ככאלה שמתמחים ביצירת סוכנים.סוכן הוא כמו ילד – צריך לגדל אותו ולשכלל אותו, דורש הרבה Nurturing.רן - ספציפית: מדברים על מעצבים, רואי-חשבון - מקצועות ספציפיים, שהם אולי לא חלק מהליבה של החברה, אבל נמצאים בכל חברה.נתי - דוגמא של Marketing: אם מישהו כבר הכין את רוב ה-Workflows מראש, זה משהו שאני מוכן לשלם עליו.אורי מציין שגם בגידול של ילד באיזשהו שלב עוברים ל-Outsourcing יותר ויותר . . . חברות עוברות לתת שירות של סוכן יחד עם “גידול סוכנים” ושכלול שלהם: סוכן + משהו שמתחזק אותו ומתאים אותו לצרכים שלך.הבשורה טובה: יש לאן להתפתח - בכל פעם שחסמי-כניסה יורדים, נפתחים תחומים חדשיםאורי ונתי קצת חלוקים על הנקודה, אבל זה דומה למה שהיה בתחילת ימי ה-SaaS, שאולי לא היה קיים אם לא היה Cloud, לפחות לא בקצב וב-Scale, שקודם לכן היה שמור לארגונים מאוד גדולים ולא לסטארטאפים.דוגמא דומה היא Big-Data.נתי אומר שהורדת חסמי-הכניסה תכניס הרבה גורמים חדשים לתחום, לאו דווקא רק מכיוון של מדעי-המחשב.אורי - השוני במהפכה הזו הוא שיש מצב שבו סוכן יכול לייצר סוכן יותר טוב . . . נתי מפריד בין מוצרים “גנריים” - יש את המודלים של Anthropic ו-OpenAI ומשפחות המוצרים הנגזרות וכו' - ובין ה”OpenClaw למיניהם”, שהם גרסא פשוטה יותר וזולה יותר, יחד עם קוד-פתוח ומוצרים בסגנון הזה.רן משווה את המאבק בין מודלים גנריים (כמו Anthropic) למודלים פתוחים (כמו OpenClaw) ל-"האנדרואיד לעומת האייפון".נתי מדבר על ראיון העבודה העתידי: “עובדים יבואו עם ה-10X של עצמם”: מועמדים לא יבואו עם קורות חיים, אלא עם רזומה פלוס – צוות סוכנים שבנו ושיודעים לשכלל להם את העבודה.בשנה-שנתיים-שלוש הקרובות, אלו שיעשו את הקפיצה ויבנו את הסוכנים וידעו להגיע עם זה לראיון עבודה - זו יכולה להיות הזדמנות לגדול ולהתבסס.אבל - אנחנו לא יודעים כמה ומי הולך להיפגע: “יהיה פה מצב של ירידה לטובת עלייה”.[17:03] “אז מה יכול לקרות?”: הסינגולריות והמתכנת האחרוןרן מעלה את השאלה המפחידה: האם כל הניסיון שצברנו כמפתחים הלך לפח? השנים הקרובות כנראה הולכות להיות מבלבלות, אבל ננסה להסתכל מעבר לזה.האם לא יהיו יותר מתכנתים, כי לא צריך - או שיהיו הרבה יותר מתכנתים והרבה יותר תוכנה, אבל מקצוע התכנות יראה אחרת?נתי חוזה ירידה למען עלייה - אבל בשונה מהמעבר ל-Cloud-Native למשל, שלקח בערך 10 שנים (ולא נגמר…), כאן הקצב הרבה יותר מהיר (התעשייה השתנתה בתוך שנה).זוכרים את “כולם משתמשים ב-AI, אבל לא רואים את ה-ROI”? זה היה בתחילת 2025 . . . מאז הסטטיסטיקות התחילו להשתנות.רן - “אם לפני שנה הייתי נותן ל-Agent משימות קידוד קטנות, ולפעמים זה מצליח ולפעעמים זה לא - היום זה עולם אחר לגמרי”.אז יכנסו יותר מעגלי-אוכלוסיה לתחום - אבל הצד השלילי הוא הירידה שלפני: כמות האנשים שדרושים למשימות שיש היום, עד שיווצר ה-Demand החדש, תגרום להרבה אנשים למצוא את עצמם “מחוץ למעגל”.מדינות תצטרכנה איכשהו לספוג את הירידה הזו - מימון הכשרות, תקופות הסתגלות וכו' - אחרת זו בדיוק הסביבה למהפכות והתדרדרות למקומות יותר בעייתיים.ולא שהסדר העולמי מסביב שליו ורגוע גם ככה [נתכתב מהממ”ד במהלך מלחמה באירן…].אורי - כבר רואים התחלה של “כלכלת סיליקון”, ומדינות nתחילות לחשוב על מאגרי הChip-ים שלהן . . . נתי מזכיר פרק של All-In, שמדבר על תחזיות מאוד אופטימיות, ועל פניו קצת מנותקות - “המון הזדמנויות והכל יהיה בסדר”, בזמן שמי שבתחום יודע שזה לא ממש ככה.נראה שב-Silicon Valley יש בעיקר התעלמות - חוגגים בתוך מעגל מאוד מצומצם.נתי מציע לחשוב על זה כמו על קורונה [במובן החיובי…] - נצטרך התערבות חיצונית כדי לעבור את הגל הזה.רן תוהה האם - בדומה לקורונה - גם התקופה הזו גם תיהיה קטליזטור לתאוריות קונספירציה שעוד תבואנה . . . אורי - מצד שני, גם תרבות הפנאי התפתחה מאוד בתקופת הקורונה, אולי שוב מישהו אחר עושה את העבודה ואז יש יותר פנאי?רן - כבר היום, כשאני מפתח, אני מספיק הרבה יותר, בהרבה פחות זמן. אז אנחנו מייצרים הרבה יותר תוכנה . . .אורי - אבל אז ה-bottlenecks עוברים למקומות אחרים.רן - OpenAI הזכירו, לגבי הפיתוח של Codex 5.3 – שהמודל פותח בעזרת גרסאות קודמות של עצמו."זה בערך By definition הסינגולריות" . . .“אל תצפו שהסינגולריות תקרה ביום אחד בודד” . . . “מי שהיה במהפכה התעשייתית לא יודע שהוא במהפכה התעשייתית".[27:57] חמשת ה-Moats של 2026נתי - האם נכון לבנות סטארטאפ באי ודאות כזו? מה הסיכוי של סטארטאפ כזה לשרוד?נאמר על רקע שבוע מאוד לא מוצלח למניות חברות ה-SaaS . . . .יש הרבה תגובות-יתר - אבל קורים הרבה דברים באמת מדהימים.נתי מציע 5 נקודות קריטיות ליזמים (סוג של Checklist) שרוצים לשרוד בעולם שבו כל דבר גנרי נמחק (כמו IBM שצנחה כי Anthropic פרסמו בלוג-פוסט על Cobol . . . ):ורטיקליזציה (Verticalization): אל תהיו גנריים. Google ו-Anthropic ו-OpenAI שולטים ביד רמה.תהיו הכי טובים במשהו ספציפי - עריכת דין או חינוך וכו'.שליטה במידע (Proprietary Data): דאטה שה-LLM הגדולים והמודלים הגנריים לא ראו, כמו מגמות ספציפיות בתוך נתוני לקוחות.יעילות (Efficiency): שימוש ב-SLM (Small Language Models) למשל, כדי לחסוך ב-Token-ים וב-Latency (קריטי ברובוטיקה וב-Security, למשל).רן - מודל גדול יקבל את ההחלטה הנכונה, אבל אולי מאוחר מדי.חווית משתתמש (UX ייחודי): חווית משתמש שפותרת בעיה נקודתית ונותנת ערך מהיר (Time to Value).ה-Chat של המודלים הגדולים מאוד גנרי.סטארטאפים צריכים להתמקד ביכולת לייצר חוויית משתמש מאוד מותאמת לחווייה נקודתית.רן - האם בכלל עוד יהיה UI (או שהצרכנים הם גם Agents . . . .)? בהקשר של פיקסלים . . . .נתי, אורי - בסוף , אתה רוצה לייצר ערך לאדם.בסוף זה עניין של Time to Value: אני אולי יכול לייצר את זה לבד, השאלה האם לא יותר מהיר ויעיל להשתמש במשהו שמישהו אחר כבר ייצר.ואחרון (אם כי נתי אמר ש "החמישי הוא לא לשידור…”) - Disruption: ה-Disruption האמיתי הוא לעשות קניבליזציה לקטגוריות ישנות.אפשר לעשות את אותם הדברים שעשינו בעבר, אבל בצורה אחרת לגמרי.הרבה דברים קודמים נעשו בגלל מגבלות של עולם שהוא Pre-Agentic, ועכשיו לא רלוונטיות - מה שמאפשר מודל עסקי אחר לחלוטין.ואז ה-Price-point יכול להיות מאוד שונה מכזה שהוכתב ע”י תעשיות מאוד גדולות ומבנה עלויות מאוד יקר לתפעול.אורי מתזכר את ה-Moats של Warren Buffet, ונתי מספר שהוא לא חושב שפגש חברה אחת שבאמת עושה את כל הדברים הללו, יזמים עדיין לא חושבים ככה.במיוחד בארץ, עדיין מתייחסים מאוד לבידול הטכנולוגי ופחות למובן של UX או מודל עסקי.[39:26] הזרקת DNA ומהלכי ה-M&A החדשיםנתי אומר שמשקיעים בהרבה מקרים לא יודעים לנתח הזדמנויות ולעשות Evaluation שלא על סמך טרנד צמיחה של ARR.אורי - עולם ההשקעות לא הולך לכיוון של SaaS, כי מצד אחד יש המון Disruption risk ומצד שני נראה שהצורך במגמת ירידה.נתי - יש כמה סוגי-Exists שונים שמשקיעים מחפשים, מעבר למודל הקלאסי של “תבנה חברה, תגדל איתה, תייצר מספיק כסף . . . .”.קנייה של טכנולוגיות ואנשים - חברות צריכות “להזריק לעצמן DNA חדש”, ואז מסתכלים על הסטראטאפ לא רק כטכנולוגיה אלא גם כמנוע לטרנספורציה.חברות במצוקה מנסות למצוא אנשים שיעזרו להן לעשות את הטרנספורמציה, לפחות בחלון הזמן הנוכחי (3 שנים בערך).נתי מזכיר דוגמא שעלתה בעבר - Google: לפני שנה כולם הספידו אותם, ואז הם קנו את Character.AI, ובעצם את נועם שזיר (Noam Shazeer) ב-2 ביליון דולר, כי הם הבינו שהם במצוקה.נתי טוען שלחברות במצוקה יהיה מאוד קשה לעשות כזה שינוי רק על ידי צמיחה אורגנית.אורי מדבר על חברות שעושות קניבליזציה-מוצרית לעצמן - מתחרים במוצר המסורתי הקודם שלהן.נתי טוען שבמקרה של Google זה השתלם להם עם Search Generative Experience (SGE).[46:00] סיכום וסגירהרן ממליץ לכולם לקרוא את הבלוג-פוסט של Matt Shumer (או לבקש מ-Agent לתקצר אותו).נתי חותם עם המלצה אופטימית-מעשית: "למדו את עצמכם... תחשבו שאתם באים למקום העבודה הבא שלכם כבר לא אתם-עצמכם... זה רזומה + צוות עובדים שאתם מביאים איתכם, שזה הסוכנים".אורי כבר מכין את הקרקע לפרק הבא: מהפכת ה-Quantum Computing."שיעורי הבית שלכם יכולים להיות 0, 1 או שניהם ביחד" . . . [קישור לקובץ mp3] האזנה נעימה ותודה רבה לעופר פורר על התמלול!

All speakers are announced at AIE EU, schedule coming soon. Join us there or in Miami with the renowned organizers of React Miami! Singapore CFP also open!We've called this out a few times over in AINews, but the overwhelming consensus in the Valley is that “the IDE is Dead”. In November it was just a gut feeling, but now we actually have data: even at the canonical “VSCode Fork” company, people are officially using more agents than tab autocomplete (the first wave of AI coding):Cursor has launched cloud agents for a few months now, and this specific launch is around Computer Use, which has come a long way since we first talked with Anthropic about it in 2024, and which Jonas productized as Autotab:We also take the opportunity to do a live demo, talk about slash commands and subagents, and the future of continual learning and personalized coding models, something that Sam previously worked on at New Computer. (The fact that both of these folks are top tier CEOs of their own startups that have now joined the insane talent density gathering at Cursor should also not be overlooked).Full Episode on YouTube!please like and subscribe!Timestamps00:00 Agentic Code Experiments00:53 Why Cloud Agents Matter02:08 Testing First Pillar03:36 Video Reviews Second Pillar04:29 Remote Control Third Pillar06:17 Meta Demos and Bug Repro13:36 Slash Commands and MCPs18:19 From Tab to Team Workflow31:41 Minimal Web UI Philosophy32:40 Why No File Editor34:38 Full Stack Cursor Debate36:34 Model Choice and Auto Routing38:34 Parallel Agents and Best Of N41:41 Subagents and Context Management44:48 Grind Mode and Throughput Future01:00:24 Cloud Agent Onboarding and MemoryTranscriptEP 77 - CURSOR - Audio version[00:00:00]Agentic Code ExperimentsSamantha: This is another experiment that we ran last year and didn't decide to ship at that time, but may come back to LM Judge, but one that was also agentic and could write code. So it wasn't just picking but also taking the learnings from two models or and models that it was looking at and writing a new diff.And what we found was that there were strengths to using models from different model providers as the base level of this process. Basically you could get almost like a synergistic output that was better than having a very unified like bottom model tier.Jonas: We think that over the coming months, the big unlock is not going to be one person with a model getting more done, like the water flowing faster and we'll be making the pipe much wider and so paralyzing more, whether that's swarms of agents or parallel agents, both of those are things that contribute to getting much more done in the same amount of time.Why Cloud Agents Matterswyx: This week, one of the biggest launches that Cursor's ever done is cloud agents. I think you, you had [00:01:00] cloud agents before, but this was like, you give cursor a computer, right? Yeah. So it's just basically they bought auto tab and then they repackaged it. Is that what's going on, or,Jonas: that's a big part of it.Yeah. Cloud agents already ran in their own computers, but they were sort of site reading code. Yeah. And those computers were not, they were like blank VMs typically that were not set up for the Devrel X for whatever repo the agents working on. One of the things that we talk about is if you put yourself in the model shoes and you were seeing tokens stream by and all you could do was cite read code and spit out tokens and hope that you had done the right thing,swyx: no chanceJonas: I'd be so bad.Like you obviously you need to run the code. And so that I think also is probably not that contrarian of a take, but no one has done that yet. And so giving the model the tools to onboard itself and then use full computer use end-to-end pixels in coordinates out and have the cloud computer with different apps in it is the big unlock that we've seen internally in terms of use usage of this going from, oh, we use it for little copy changes [00:02:00] to no.We're really like driving new features with this kind of new type of entech workflow. Alright, let's see it. Cool.Live Demo TourJonas: So this is what it looks like in cursor.com/agents. So this is one I kicked off a while ago. So on the left hand side is the chat. Very classic sort of agentic thing. The big new thing here is that the agent will test its changes.So you can see here it worked for half an hour. That is because it not only took time to write the tokens of code, it also took time to test them end to end. So it started Devrel servers iterate when needed. And so that's one part of it is like model works for longer and doesn't come back with a, I tried some things pr, but a I tested at pr that's ready for your review.One of the other intuition pumps we use there is if a human gave you a PR asked you to review it and you hadn't, they hadn't tested it, you'd also be annoyed because you'd be like, only ask me for a review once it's actually ready. So that's what we've done withTesting Defaults and Controlsswyx: simple question I wanted to gather out front.Some prs are way smaller, [00:03:00] like just copy change. Does it always do the video or is it sometimes,Jonas: Sometimes.swyx: Okay. So what's the judgment?Jonas: The model does it? So we we do some default prompting with sort. What types of changes to test? There's a slash command that people can do called slash no test, where if you do that, the model will not test,swyx: but the default is test.Jonas: The default is to be calibrated. So we tell it don't test, very simple copy changes, but test like more complex things. And then users can also write their agents.md and specify like this type of, if you're editing this subpart of my mono repo, never tested ‘cause that won't work or whatever.Videos and Remote ControlJonas: So pillar one is the model actually testing Pillar two is the model coming back with a video of what it did.We have found that in this new world where agents can end-to-end, write much more code, reviewing the code is one of these new bottlenecks that crop up. And so reviewing a video is not a substitute for reviewing code, but it is an entry point that is much, much easier to start with than glancing at [00:04:00] some giant diff.And so typically you kick one off you, it's done you come back and the first thing that you would do is watch this video. So this is a, video of it. In this case I wanted a tool tip over this button. And so it went and showed me what that looks like in, in this video that I think here, it actually used a gallery.So sometimes it will build storybook type galleries where you can see like that component in action. And so that's pillar two is like these demo videos of what it built. And then pillar number three is I have full remote control access to this vm. So I can go heat in here. I can hover things, I can type, I have full control.And same thing for the terminal. I have full access. And so that is also really useful because sometimes the video is like all you need to see. And oftentimes by the way, the video's not perfect, the video will show you, is this worth either merging immediately or oftentimes is this worth iterating with to get it to that final stage where I am ready to merge in.So I can go through some other examples where the first video [00:05:00] wasn't perfect, but it gave me confidence that we were on the right track and two or three follow-ups later, it was good to go. And then I also have full access here where some things you just wanna play around with. You wanna get a feel for what is this and there's no substitute to a live preview.And the VNC kind of VM remote access gives you that.swyx: Amazing What, sorry? What is VN. AndJonas: just the remote desktop. Remote desktop. Yeah.swyx: Sam, any other details that you always wanna call out?Samantha: Yeah, for me the videos have been super helpful. I would say, especially in cases where a common problem for me with agents and cloud agents beforehand was almost like under specification in my requests where our plan mode and going really back and forth and getting detailed implementation spec is a way to reduce the risk of under specification, but then similar to how human communication breaks down over time, I feel like you have this risk where it's okay, when I pull down, go to the triple of pulling down and like running this branch locally, I'm gonna see that, like I said, this should be a toggle and you have a checkbox and like, why didn't you get that detail?And having the video up front just [00:06:00] has that makes that alignment like you're talking about a shared artifact with the agent. Very clear, which has been just super helpful for me.Jonas: I can quickly run through some other Yes. Examples.Meta Agents and More DemosJonas: So this is a very front end heavy one. So one question I wasswyx: gonna say, is this only for frontJonas: end?Exactly. One question you might have is this only for front end? So this is another example where the thing I wanted it to implement was a better error message for saving secrets. So the cloud agents support adding secrets, that's part of what it needs to access certain systems. Part of onboarding that is giving access.This is cloud is working onswyx: cloud agents. Yes.Jonas: So this is a fun thing isSamantha: it can get super meta. ItJonas: can get super meta, it can start its own cloud agents, it can talk to its own cloud agents. Sometimes it's hard to wrap your mind around that. We have disabled, it's cloud agents starting more cloud agents. So we currently disallow that.Someday you might. Someday we might. Someday we might. So this actually was mostly a backend change in terms of the error handling here, where if the [00:07:00] secret is far too large, it would oh, this is actually really cool. Wow. That's the Devrel tools. That's the Devrel tools. So if the secret is far too large, we.Allow secrets above a certain size. We have a size limit on them. And the error message there was really bad. It was just some generic failed to save message. So I was like, Hey, we wanted an error message. So first cool thing it did here, zero prompting on how to test this. Instead of typing out the, like a character 5,000 times to hit the limit, it opens Devrel tools, writes js, or to paste into the input 5,000 characters of the letter A and then hit save, closes the Devrel tools, hit save and gets this new gets the new error message.So that looks like the video actually cut off, but here you can see the, here you can see the screenshot of the of the error message. What, so that is like frontend backend end-to-end feature to, to get that,swyx: yeah.Jonas: Andswyx: And you just need a full vm, full computer run everything.Okay. Yeah.Jonas: Yeah. So we've had versions of this. This is one of the auto tab lessons where we started that in 2022. [00:08:00] No, in 2023. And at the time it was like browser use, DOM, like all these different things. And I think we ended up very sort of a GI pilled in the sense that just give the model pixels, give it a box, a brain in a box is what you want and you want to remove limitations around context and capabilities such that the bottleneck should be the intelligence.And given how smart models are today, that's a very far out bottleneck. And so giving it its full VM and having it be onboarded with Devrel X set up like a human would is just been for us internally a really big step change in capability.swyx: Yeah I would say, let's call it a year ago the models weren't even good enough to do any of this stuff.SoSamantha: even six months ago. Yeah.swyx: So yeah what people have told me is like round about Sonder four fire is when this started being good enough to just automate fully by pixel.Jonas: Yeah, I think it's always a question of when is good enough. I think we found in particular with Opus 4 5, 4, 6, and Codex five three, that those were additional step [00:09:00] changes in the autonomy grade capabilities of the model to just.Go off and figure out the details and come back when it's done.swyx: I wanna appreciate a couple details. One 10 Stack Router. I see it. Yeah. I'm a big fan. Do you know any, I have to name the 10 Stack.Jonas: No.swyx: This just a random lore. Some buddy Sue Tanner. My and then the other thing if you switch back to the video.Jonas: Yeah.swyx: I wanna shout out this thing. Probably Sam did it. I don't knowJonas: the chapters.swyx: What is this called? Yeah, this is called Chapters. Yeah. It's like a Vimeo thing. I don't know. But it's so nice the design details, like the, and obviously a company called Cursor has to have a beautiful cursorSamantha: and it isswyx: the cursor.Samantha: Cursor.swyx: You see it branded? It's the cursor. Cursor, yeah. Okay, cool. And then I was like, I complained to Evan. I was like, okay, but you guys branded everything but the wallpaper. And he was like, no, that's a cursor wallpaper. I was like, what?Samantha: Yeah. Rio picked the wallpaper, I think. Yeah. The video.That's probably Alexi and yeah, a few others on the team with the chapters on the video. Matthew Frederico. There's been a lot of teamwork on this. It's a huge effort.swyx: I just, I like design details.Samantha: Yeah.swyx: And and then when you download it adds like a little cursor. Kind of TikTok clip. [00:10:00] Yes. Yes.So it's to make it really obvious is from Cursor,Jonas: we did the TikTok branding at the end. This was actually in our launch video. Alexi demoed the cloud agent that built that feature. Which was funny because that was an instance where one of the things that's been a consequence of having these videos is we use best of event where you run head to head different models on the same prompt.We use that a lot more because one of the complications with doing that before was you'd run four models and they would come back with some giant diff, like 700 lines of code times four. It's what are you gonna do? You're gonna review all that's horrible. But if you come back with four 22nd videos, yeah, I'll watch four 22nd videos.And then even if none of them is perfect, you can figure out like, which one of those do you want to iterate with, to get it over the line. Yeah. And so that's really been really fun.Bug Repro WorkflowJonas: Here's another example. That's we found really cool, which is we've actually turned since into a slash command as well slash [00:11:00] repro, where for bugs in particular, the model of having full access to the to its own vm, it can first reproduce the bug, make a video of the bug reproducing, fix the bug, make a video of the bug being fixed, like doing the same pattern workflow with obviously the bug not reproducing.And that has been the single category that has gone from like these types of bugs, really hard to reproduce and pick two tons of time locally, even if you try a cloud agent on it. Are you confident it actually fixed it to when this happens? You'll merge it in 90 seconds or something like that.So this is an example where, let me see if this is the broken one or the, okay, this is the fixed one. Okay. So we had a bug on cursor.com/agents where if you would attach images where remove them. Then still submit your prompt. They would actually still get attached to the prompt. Okay. And so here you can see Cursor is using, its full desktop by the way.This is one of the cases where if you just do, browse [00:12:00] use type stuff, you'll have a bad time. ‘cause now it needs to upload files. Like it just uses its native file viewer to do that. And so you can see here it's uploading files. It's going to submit a prompt and then it will go and open up. So this is the meta, this is cursor agent, prompting cursor agent inside its own environment.And so you can see here bug, there's five images attached, whereas when it's submitted, it only had one image.swyx: I see. Yeah. But you gotta enable that if you're gonna use cur agent inside cur.Jonas: Exactly. And so here, this is then the after video where it went, it does the same thing. It attaches images, removes, some of them hit send.And you can see here, once this agent is up, only one of the images is left in the attachments. Yeah.swyx: Beautiful.Jonas: Okay. So easy merge.swyx: So yeah. When does it choose to do this? Because this is an extra step.Jonas: Yes. I think I've not done a great job yet of calibrating the model on when to reproduce these things.Yeah. Sometimes it will do it of its own accord. Yeah. We've been conservative where we try to have it only do it when it's [00:13:00] quite sure because it does add some amount of time to how long it takes it to work on it. But we also have added things like the slash repro command where you can just do, fix this bug slash repro and then it will know that it should first make you a video of it actually finding and making sure it can reproduce the bug.swyx: Yeah. Yeah. One sort of ML topic this ties into is reward hacking, where while you write test that you update only pass. So first write test, it shows me it fails, then make you test pass, which is a classic like red green.Jonas: Yep.swyx: LikeJonas: A-T-D-D-T-D-Dswyx: thing.No, very cool. Was that the last demo? Is thereJonas: Yeah.Anything I missed on the demos or points that you think? I think thatSamantha: covers it well. Yeah.swyx: Cool. Before we stop the screen share, can you gimme like a, just a tour of the slash commands ‘cause I so God ready. Huh, what? What are the good ones?Samantha: Yeah, we wanna increase discoverability around this too.I think that'll be like a future thing we work on. Yeah. But there's definitely a lot of good stuff nowJonas: we have a lot of internal ones that I think will not be that interesting. Here's an internal one that I've made. I don't know if anyone else at Cursor uses this one. Fix bb.Samantha: I've never heard of it.Jonas: Yeah.[00:14:00]Fix Bug Bot. So this is a thing that we want to integrate more tightly on. So you made it forswyx: yourself.Jonas: I made this for myself. It's actually available to everyone in the team, but yeah, no one knows about it. But yeah, there will be Bug bot comments and so Bug Bot has a lot of cool things. We actually just launched Bug Bot Auto Fix, where you can click a button and or change a setting and it will automatically fix its own things, and that works great in a bunch of cases.There are some cases where having the context of the original agent that created the PR is really helpful for fixing the bugs, because it might be like, oh, the bug here is that this, is a regression and actually you meant to do something more like that. And so having the original prompt and all of the context of the agent that worked on it, and so here I could just do, fix or we used to be able to do fixed PB and it would do that.No test is another one that we've had. Slash repro is in here. We mentioned that one.Samantha: One of my favorites is cloud agent diagnosis. This is one that makes heavy use of the Datadog MCP. Okay. And I [00:15:00] think Nick and David on our team wrote, and basically if there is a problem with a cloud agent we'll spin up a bunch of subs.Like a singleswyx: instance.Samantha: Yeah. We'll take the ideas and argument and spin up a bunch of subagents using the Datadog MCP to explore the logs and find like all of the problems that could have happened with that. It takes the debugging time, like from potentially you can do quick stuff quickly with the Datadog ui, but it takes it down to, again, like a single agent call as opposed to trolling through logs yourself.Jonas: You should also talk about the stuff we've done with transcripts.Samantha: Yes. Also so basically we've also done some things internally. There'll be some versions of this as we ship publicly soon, where you can spit up an agent and give it access to another agent's transcript to either basically debug something that happened.So act as an external debugger. I see. Or continue the conversation. Almost like forking it.swyx: A transcript includes all the chain of thought for the 11 minutes here. 45 minutes there.Samantha: Yeah. That way. Exactly. So basically acting as a like secondary agent that debugs the first, so we've started to push more andswyx: they're all the same [00:16:00] code.It is just the different prompts, but the sa the same.Samantha: Yeah. So basically same cloud agent infrastructure and then same harness. And then like when we do things like include, there's some extra infrastructure that goes into piping in like an external transcript if we include it as an attachment.But for things like the cloud agent diagnosis, that's mostly just using the Datadog MCP. ‘Cause we also launched CPS along with along with this cloud agent launch, launch support for cloud agent cps.swyx: Oh, that was drawn out.Jonas: We won't, we'll be doing a bigger marketing moment for it next week, but, and you can now use CPS andswyx: People will listen to it as well.Yeah,Jonas: they'llSamantha: be ahead of the third. They'll be ahead. And I would I actually don't know if the Datadog CP is like publicly available yet. I realize this not sure beta testing it, but it's been one of my favorites to use. Soswyx: I think that one's interesting for Datadog. ‘cause Datadog wants to own that site.Interesting with Bits. I don't know if you've tried bits.Samantha: I haven't tried bits.swyx: Yeah.Jonas: That's their cloud agentswyx: product. Yeah. Yeah. They want to be like we own your logs and give us our, some part of the, [00:17:00] self-healing software that everyone wants. Yeah. But obviously Cursor has a strong opinion on coding agents and you, you like taking away from the which like obviously you're going to do, and not every company's like Cursor, but it's interesting if you're a Datadog, like what do you do here?Do you expose your logs to FDP and let other people do it? Or do you try to own that it because it's extra business for you? Yeah. It's like an interesting one.Samantha: It's a good question. All I know is that I love the Datadog MCP,Jonas: And yeah, it is gonna be no, no surprise that people like will demand it, right?Samantha: Yeah.swyx: It's, it's like anysystemswyx: of record company like this, it's like how much do you give away? Cool. I think that's that for the sort of cloud agents tour. Cool. And we just talk about like cloud agents have been when did Kirsten loves cloud agents? Do you know, in JuneJonas: last year.swyx: June last year. So it's been slowly develop the thing you did, like a bunch of, like Michael did a post where himself, where he like showed this chart of like ages overtaking tap. And I'm like, wow, this is like the biggest transition in code.Jonas: Yeah.swyx: Like in, in [00:18:00] like the last,Jonas: yeah. I think that kind of got turned out.Yeah. I think it's a very interest,swyx: not at all. I think it's been highlighted by our friend Andre Kati today.Jonas: Okay.swyx: Talk more about it. What does it mean? Yeah. Is I just got given like the cursor tab key.Jonas: Yes. Yes.swyx: That's that'sSamantha: cool.swyx: I know, but it's gonna be like put in a museum.Jonas: It is.Samantha: I have to say I haven't used tab a little bit myself.Jonas: Yeah. I think that what it looks like to code with AI code generally creates software, even if you want to go higher level. Is changing very rapidly. No, not a hot take, but I think from our vendor's point at Cursor, I think one of the things that is probably underappreciated from the outside is that we are extremely self-aware about that fact and Kerscher, got its start in phase one, era one of like tab and auto complete.And that was really useful in its time. But a lot of people start looking at text files and editing code, like we call it hand coding. Now when you like type out the actual letters, it'sswyx: oh that's cute.Jonas: Yeah.swyx: Oh that's cute.Jonas: You're so boomer. So boomer. [00:19:00] And so that I think has been a slowly accelerating and now in the last few months, rapidly accelerating shift.And we think that's going to happen again with the next thing where the, I think some of the pains around tab of it's great, but I actually just want to give more to the agent and I don't want to do one tab at a time. I want to just give it a task and it goes off and does a larger unit of work and I can.Lean back a little bit more and operate at that higher level of abstraction that's going to happen again, where it goes from agents handing you back diffs and you're like in the weeds and giving it, 32nd to three minute tasks, to, you're giving it, three minute to 30 minute to three hour tasks and you're getting back videos and trying out previews rather than immediately looking at diffs every single time.swyx: Yeah. Anything to add?Samantha: One other shift that I've noticed as our cloud agents have really taken off internally has been a shift from primarily individually driven development to almost this collaborative nature of development for us, slack is actually almost like a development on [00:20:00] Id basically.So Iswyx: like maybe don't even build a custom ui, like maybe that's like a debugging thing, but actually it's that.Samantha: I feel like, yeah, there's still so much to left to explore there, but basically for us, like Slack is where a lot of development happens. Like we will have these issue channels or just like this product discussion channels where people are always at cursing and that kicks off a cloud agent.And for us at least, we have team follow-ups enabled. So if Jonas kicks off at Cursor in a thread, I can follow up with it and add more context. And so it turns into almost like a discussion service where people can like collaborate on ui. Oftentimes I will kick off an investigation and then sometimes I even ask it to get blame and then tag people who should be brought in. ‘cause it can tag people in Slack and then other people will comeswyx: in, can tag other people who are not involved in conversation. Yes. Can just do at Jonas if say, was talking to,Samantha: yeah.swyx: That's cool. You should, you guys should make a big good deal outta that.Samantha: I know. It's a lot to, I feel like there's a lot more to do with our slack surface area to show people externally. But yeah, basically like it [00:21:00] can bring other people in and then other people can also contribute to that thread and you can end up with a PR again, with the artifacts visible and then people can be like, okay, cool, we can merge this.So for us it's like the ID is almost like moving into Slack in some ways as well.swyx: I have the same experience with, but it's not developers, it's me. Designer salespeople.Samantha: Yeah.swyx: So me on like technical marketing, vision, designer on design and then salespeople on here's the legal source of what we agreed on.And then they all just collaborate and correct. The agents,Jonas: I think that we found when these threads is. The work that is left, that the humans are discussing in these threads is the nugget of what is actually interesting and relevant. It's not the boring details of where does this if statement go?It's do we wanna ship this? Is this the right ux? Is this the right form factor? Yeah. How do we make this more obvious to the user? It's like those really interesting kind of higher order questions that are so easy to collaborate with and leave the implementation to the cloud agent.Samantha: Totally. And no more discussion of am I gonna do this? Are you [00:22:00] gonna do this cursor's doing it? You just have to decide. You like it.swyx: Sometimes the, I don't know if there's a, this probably, you guys probably figured this out already, but since I, you need like a mute button. So like cursor, like we're going to take this offline, but still online.But like we need to talk among the humans first. Before you like could stop responding to everything.Jonas: Yeah. This is a design decision where currently cursor won't chime in unless you explicitly add Mention it. Yeah. Yeah.Samantha: So it's not always listening.Yeah.Jonas: I can see all the intermediate messages.swyx: Have you done the recursive, can cursor add another cursor or spawn another cursor?Samantha: Oh,Jonas: we've done some versions of this.swyx: Because, ‘cause it can add humans.Jonas: Yes. One of the other things we've been working on that's like an implication of generating the code is so easy is getting it to production is still harder than it should be.And broadly, you solve one bottleneck and three new ones pop up. Yeah. And so one of the new bottlenecks is getting into production and we have a like joke internally where you'll be talking about some feature and someone says, I have a PR for that. Which is it's so easy [00:23:00] to get to, I a PR for that, but it's hard still relatively to get from I a PR for that to, I'm confident and ready to merge this.And so I think that over the coming weeks and months, that's a thing that we think a lot about is how do we scale up compute to that pipeline of getting things from a first draft An agent did.swyx: Isn't that what Merge isn't know what graphite's for, likeJonas: graphite is a big part of that. The cloud agent testingswyx: Is it fully integrated or still different companiesJonas: working on I think we'll have more to share there in the future, but the goal is to have great end-to-end experience where Cursor doesn't just help you generate code tokens, it helps you create software end-to-end.And so review is a big part of that, that I think especially as models have gotten much better at writing code, generating code, we've felt that relatively crop up more,swyx: sorry this is completely unplanned, but like there I have people arguing one to you need ai. To review ai and then there is another approach, thought school of thought where it's no, [00:24:00] reviews are dead.Like just show me the video. It's it like,Samantha: yeah. I feel again, for me, the video is often like alignment and then I often still wanna go through a code review process.swyx: Like still look at the files andSamantha: everything. Yeah. There's a spectrum of course. Like the video, if it's really well done and it does like fully like test everything, you can feel pretty competent, but it's still helpful to, to look at the code.I make hep pay a lot of attention to bug bot. I feel like Bug Bot has been a great really highly adopted internally. We often like, won't we tell people like, don't leave bug bot comments unaddressed. ‘cause we have such high confidence in it. So people always address their bug bot comments.Jonas: Once you've had two cases where you merged something and then you went back later, there was a bug in it, you merged, you went back later and you were like, ah, bug Bot had found that I should have listened to Bug Bot.Once that happens two or three times, you learn to wait for bug bot.Samantha: Yeah. So I think for us there's like that code level review where like it's looking at the actual code and then there's like the like feature level review where you're looking at the features. There's like a whole number of different like areas.There'll probably eventually be things like performance level review, security [00:25:00] review, things like that where it's like more more different aspects of how this feature might affect your code base that you want to potentially leverage an agent to help with.Jonas: And some of those like bug bot will be synchronous and you'll typically want to wait on before you merge.But I think another thing that we're starting to see is. As with cloud agents, you scale up this parallelism and how much code you generate. 10 person startups become, need the Devrel X and pipelines that a 10,000 person company used to need. And that looks like a lot of the things I think that 10,000 person companies invented in order to get that volume of software to production safely.So that's things like, release frequently or release slowly, have different stages where you release, have checkpoints, automated ways of detecting regressions. And so I think we're gonna need stacks merg stack diffs merge queues. Exactly. A lot of those things are going to be importantswyx: forward with.I think the majority of people still don't know what stack stacks are. And I like, I have many friends in Facebook and like I, I'm pretty friendly with graphite. I've just, [00:26:00] I've never needed it ‘cause I don't work on that larger team and it's just like democratization of no, only here's what we've already worked out at very large scale and here's how you can, it benefits you too.Like I think to me, one of the beautiful things about GitHub is that. It's actually useful to me as an individual solo developer, even though it's like actually collaboration software.Jonas: Yep.swyx: And I don't think a lot of Devrel tools have figured that out yet. That transition from like large down to small.Jonas: Yeah. Kers is probably an inverse story.swyx: This is small down toJonas: Yeah. Where historically Kers share, part of why we grew so quickly was anyone on the team could pick it up and in fact people would pick it up, on the weekend for their side project and then bring it into work. ‘cause they loved using it so much.swyx: Yeah.Jonas: And I think a thing that we've started working on a lot more, not us specifically, but as a company and other folks at Cursor, is making it really great for teams and making it the, the 10th person that starts using Cursor in a team. Is immediately set up with things like, we launched Marketplace recently so other people can [00:27:00] configure what CPS and skills like plugins.So skills and cps, other people can configure that. So that my cursor is ready to go and set up. Sam loves the Datadog, MCP and Slack, MCP you've also been using a lot butSamantha: also pre-launch, but I feel like it's so good.Jonas: Yeah, my cursor should be configured if Sam feels strongly that's just amazing and required.swyx: Is it automatically shared or you have to go and.Jonas: It depends on the MCP. So some are obviously off per user. Yeah. And so Sam can't off my cursor with my Slack MCP, but some are team off and those can be set up by admins.swyx: Yeah. Yeah. That's cool. Yeah, I think, we had a man on the pod when cursor was five people, and like everyone was like, okay, what's the thing?And then it's usually something teams and org and enterprise, but it's actually working. But like usually at that stage when you're five, when you're just a vs. Code fork it's like how do you get there? Yeah. Will people pay for this? People do pay for it.Jonas: Yeah. And I think for cloud agents, we expect.[00:28:00]To have similar kind of PLG things where I think off the bat we've seen a lot of adoption with kind of smaller teams where the code bases are not quite as complex to set up. Yes. If you need some insane docker layer caching thing for builds not to take two hours, that's going to take a little bit longer for us to be able to support that kind of infrastructure.Whereas if you have front end backend, like one click agents can install everything that they need themselves.swyx: This is a good chance for me to just ask some technical sort of check the box questions. Can I choose the size of the vm?Jonas: Not yet. We are planning on adding that. Weswyx: have, this is obviously you want like LXXL, whatever, right?Like it's like the Amazon like sort menu.Jonas: Yes, exactly. We'll add that.swyx: Yeah. In some ways you have to basically become like a EC2, almost like you rent a box.Jonas: You rent a box. Yes. We talk a lot about brain in a box. Yeah. So cursor, we want to be a brain in a box,swyx: but is the mental model different? Is it more serverless?Is it more persistent? Is. Something else.Samantha: We want it to be a bit persistent. The desktop should be [00:29:00] something you can return to af even after some days. Like maybe you go back, they're like still thinking about a feature for some period of time. So theswyx: full like sus like suspend the memory and bring it back and then keep going.Samantha: Exactly.swyx: That's an interesting one because what I actually do want, like from a manna and open crawl, whatever, is like I want to be able to log in with my credentials to the thing, but not actually store it in any like secret store, whatever. ‘cause it's like this is the, my most sensitive stuff.Yeah. This is like my email, whatever. And just have it like, persist to the image. I don't know how it was hood, but like to rehydrate and then just keep going from there. But I don't think a lot of infra works that way. A lot of it's stateless where like you save it to a docker image and then it's only whatever you can describe in a Docker file and that's it.That's the only thing you can cl multiple times in parallel.Jonas: Yeah. We have a bunch of different ways of setting them up. So there's a dockerfile based approach. The main default way is actually snapshottingswyx: like a Linux vmJonas: like vm, right? You run a bunch of install commands and then you snapshot more or less the file system.And so that gets you set up for everything [00:30:00] that you would want to bring a new VM up from that template basically.swyx: Yeah.Jonas: And that's a bit distinct from what Sam was talking about with the hibernating and re rehydrating where that is a full memory snapshot as well. So there, if I had like the browser open to a specific page and we bring that back, that page will still be there.swyx: Was there any discussion internally and just building this stuff about every time you shoot a video it's actually you show a little bit of the desktop and the browser and it's not necessary if you just show the browser. If, if you know you're just demoing a front end application.Why not just show the browser, right? Like it Yeah,Samantha: we do have some panning and zooming. Yeah. Like it can decide that when it's actually recording and cutting the video to highlight different things. I think we've played around with different ways of segmenting it and yeah. There's been some different revs on it for sure.Jonas: Yeah. I think one of the interesting things is the version that you see now in cursor.com actually is like half of what we had at peak where we decided to unshift or unshipped quite a few things. So two of the interesting things to talk about, one is directly an answer to your [00:31:00] question where we had native browser that you would have locally, it was basically an iframe that via port forwarding could load the URL could talk to local host in the vm.So that gets you basically, so inswyx: your machine's browser,likeJonas: in your local browser? Yeah. You would go to local host 4,000 and that would get forwarded to local host 4,000 in the VM via port forward. We unshift that like atswyx: Eng Rock.Jonas: Like an Eng Rock. Exactly. We unshift that because we felt that the remote desktop was sufficiently low latency and more general purpose.So we build Cursor web, but we also build Cursor desktop. And so it's really useful to be able to have the full spectrum of things. And even for Cursor Web, as you saw in one of the examples, the agent was uploading files and like I couldn't upload files and open the file viewer if I only had access to the browser.And we've thought a lot about, this might seem funny coming from Cursor where we started as this, vs. Code Fork and I think inherited a lot of amazing things, but also a lot [00:32:00] of legacy UI from VS Code.Minimal Web UI SurfacesJonas: And so with the web UI we wanted to be very intentional about keeping that very minimal and exposing the right sum of set of primitive sort of app surfaces we call them, that are shared features of that cloud.Environment that you and the agent both use. So agent uses desktop and controls it. I can use desktop and controlled agent runs terminal commands. I can run terminal commands. So that's how our philosophy around it. The other thing that is maybe interesting to talk about that we unshipped is and we may, both of these things we may reship and decide at some point in the future that we've changed our minds on the trade offs or gotten it to a point where, putswyx: it out there.Let users tell you they want it. Exactly. Alright, fine.Why No File EditorJonas: So one of the other things is actually a files app. And so we used to have the ability at one point during the process of testing this internally to see next to, I had GID desktop and terminal on the right hand side of the tab there earlier to also have a files app where you could see and edit files.And we actually felt that in some [00:33:00] ways, by restricting and limiting what you could do there, people would naturally leave more to the agent and fall into this new pattern of delegating, which we thought was really valuable. And there's currently no way in Cursor web to edit these files.swyx: Yeah. Except you like open up the PR and go into GitHub and do the thing.Jonas: Yeah.swyx: Which is annoying.Jonas: Just tell the agent,swyx: I have criticized open AI for this. Because Open AI is Codex app doesn't have a file editor, like it has file viewer, but isn't a file editor.Jonas: Do you use the file viewer a lot?swyx: No. I understand, but like sometimes I want it, the one way to do it is like freaking going to no, they have a open in cursor button or open an antigravity or, opening whatever and people pointed that.So I was, I was part of the early testers group people pointed that and they were like, this is like a design smell. It's like you actually want a VS. Code fork that has all these things, but also a file editor. And they were like, no, just trust us.Jonas: Yeah. I think we as Cursor will want to, as a product, offer the [00:34:00] whole spectrum and so you want to be able to.Work at really high levels of abstraction and double click and see the lowest level. That's important. But I also think that like you won't be doing that in Slack. And so there are surfaces and ways of interacting where in some cases limiting the UX capabilities makes for a cleaner experience that's more simple and drives people into these new patterns where even locally we kicked off joking about this.People like don't really edit files, hand code anymore. And so we want to build for where that's going and not where it's beenswyx: a lot of cool stuff. And Okay. I have a couple more.Full Stack Hosting Debateswyx: So observations about the design elements about these things. One of the things that I'm always thinking about is cursor and other peers of cursor start from like the Devrel tools and work their way towards cloud agents.Other people, like the lovable and bolts of the world start with here's like the vibe code. Full cloud thing. They were already cloud edges before anyone else cloud edges and we will give you the full deploy platform. So we own the whole loop. We own all the infrastructure, we own, we, we have the logs, we have the the live site, [00:35:00] whatever.And you can do that cycle cursor doesn't own that cycle even today. You don't have the versal, you don't have the, you whatever deploy infrastructure that, that you're gonna have, which gives you powers because anyone can use it. And any enterprise who, whatever you infra, I don't care. But then also gives you limitations as to how much you can actually fully debug end to end.I guess I'm just putting out there that like is there a future where there's like full stack cursor where like cursor apps.com where like I host my cursor site this, which is basically a verse clone, right? I don't know.Jonas: I think that's a interesting question to be asking, and I think like the logic that you laid out for how you would get there is logic that I largely agree with.swyx: Yeah. Yeah.Jonas: I think right now we're really focused on what we see as the next big bottleneck and because things like the Datadog MCP exist, yeah. I don't think that the best way we can help our customers ship more software. Is by building a hosting solution right now,swyx: by the way, these are things I've actually discussed with some of the companies I just named.Jonas: Yeah, for sure. Right now, just this big bottleneck is getting the code out there and also [00:36:00] unlike a lovable in the bolt, we focus much more on existing software. And the zero to one greenfield is just a very different problem. Imagine going to a Shopify and convincing them to deploy on your deployment solution.That's very different and I think will take much longer to see how that works. May never happen relative to, oh, it's like a zero to one app.swyx: I'll say. It's tempting because look like 50% of your apps are versal, superb base tailwind react it's the stack. It's what everyone does.So I it's kinda interesting.Jonas: Yeah.Model Choice and Auto Routingswyx: The other thing is the model select dying. Right now in cloud agents, it's stuck down, bottom left. Sure it's Codex High today, but do I care if it's suddenly switched to Opus? Probably not.Samantha: We definitely wanna give people a choice across models because I feel like it, the meta change is very frequently.I was a big like Opus 4.5 Maximalist, and when codex 5.3 came out, I hard, hard switch. So that's all I use now.swyx: Yeah. Agreed. I don't know if, but basically like when I use it in Slack, [00:37:00] right? Cursor does a very good job of exposing yeah. Cursors. If people go use it, here's the model we're using.Yeah. Here's how you switch if you want. But otherwise it's like extracted away, which is like beautiful because then you actually, you should decide.Jonas: Yeah, I think we want to be doing more with defaults.swyx: Yeah.Jonas: Where we can suggest things to people. A thing that we have in the editor, the desktop app is auto, which will route your request and do things there.So I think we will want to do something like that for cloud agents as well. We haven't done it yet. And so I think. We have both people like Sam, who are very savvy and want know exactly what model they want, and we also have people that want us to pick the best model for them because we have amazing people like Sam and we, we are the experts.Yeah. We have both the traffic and the internal taste and experience to know what we think is best.swyx: Yeah. I have this ongoing pieces of agent lab versus model lab. And to me, cursor and other companies are example of an agent lab that is, building a new playbook that is different from a model lab where it's like very GP heavy Olo.So obviously has a research [00:38:00] team. And my thesis is like you just, every agent lab is going to have a router because you're going to be asked like, what's what. I don't keep up to every day. I'm not a Sam, I don't keep up every day for using you as sample the arm arbitrator of taste. Put me on CRI Auto.Is it free? It's not free.Jonas: Auto's not free, but there's different pricing tiers. Yeah.swyx: Put me on Chris. You decide from me based on all the other people you know better than me. And I think every agent lab should basically end up doing this because that actually gives you extra power because you like people stop carrying or having loyalty with one lab.Jonas: Yeah.Best Of N and Model CouncilsJonas: Two other maybe interesting things that I don't know how much they're on your radar are one the best event thing we mentioned where running different models head to head is actually quite interesting becauseswyx: which exists in cursor.Jonas: That exists in cur ID and web. So the problem is where do you run them?swyx: Okay.Jonas: And so I, I can share my screen if that's interesting. Yeahinteresting.swyx: Yeah. Yeah. Obviously parallel agents, very popal.Jonas: Yes, exactly. Parallel agentsswyx: in you mind. Are they the same thing? Best event and parallel agents? I don't want to [00:39:00] put words in your mouth.Jonas: Best event is a subset of parallel agents where they're running on the same prompt.That would be my answer. So this is what that looks like. And so here in this dropdown picker, I can just select multiple models.swyx: Yeah.Jonas: And now if I do a prompt, I'm going to do something silly. I am running these five models.swyx: Okay. This is this fake clone, of course. The 2.0 yeah.Jonas: Yes, exactly. But they're running so the cursor 2.0, you can do desktop or cloud.So this is cloud specifically where the benefit over work trees is that they have their own VMs and can run commands and won't try to kill ports that the other one is running. Which are some of the pains. These are allswyx: called work trees?Jonas: No, these are all cloud agents with their own VMs.swyx: Okay. ButJonas: When you do it locally, sometimes people do work trees and that's been the main way that people have set out parallel so far.I've gotta say.swyx: That's so confusing for folks.Jonas: Yeah.swyx: No one knows what work trees are.Jonas: Exactly. I think we're phasing out work trees.swyx: Really.Jonas: Yeah.swyx: Okay.Samantha: But yeah. And one other thing I would say though on the multimodel choice, [00:40:00] so this is another experiment that we ran last year and the decide to ship at that time but may come back to, and there was an interesting learning that's relevant for, these different model providers. It was something that would run a bunch of best of ends but then synthesize and basically run like a synthesizer layer of models. And that was other agents that would take LM Judge, but one that was also agentic and could write code. So it wasn't just picking but also taking the learnings from two models or, and models that it was looking at and writing a new diff.And what we found was that at the time at least, there were strengths to using models from different model providers as the base level of this process. Like basically you could get almost like a synergistic output that was better than having a very unified, like bottom model tier. So it was really interesting ‘cause it's like potentially, even though even in the future when you have like maybe one model as ahead of the other for a little bit, there could be some benefit from having like multiple top tier models involved in like a [00:41:00] model swarm or whatever agent Swarm that you're doing, that they each have strengths and weaknesses.Yeah.Jonas: Andre called this the council, right?Samantha: Yeah, exactly. We actually, oh, that's another internal command we have that Ian wrote slash council. Oh, and they some, yeah.swyx: Yes. This idea is in various forms everywhere. And I think for me, like for me, the productization of it, you guys have done yeah, like this is very flexible, but.If I were to add another Yeah, what your thing is on here it would be too much. I what, let's say,Samantha: Ideally it's all, it's something that the user can just choose and it all happens under the hood in a way where like you just get the benefit of that process at the end and better output basically, but don't have to get too lost in the complexity of judging along the way.Jonas: Okay.Subagents for ContextJonas: Another thing on the many agents, on different parallel agents that's interesting is an idea that's been around for a while as well that has started working recently is subagents. And so this is one other way to get agents of the different prompts and different goals and different models, [00:42:00] different vintages to work together.Collaborate and delegate.swyx: Yeah. I'm very like I like one of my, I always looking for this is the year of the blah, right? Yeah. I think one of the things on the blahs is subs. I think this is of but I haven't used them in cursor. Are they fully formed or how do I honestly like an intro because do I form them from new every time?Do I have fixed subagents? How are they different for slash commands? There's all these like really basic questions that no one stops to answer for people because everyone's just like too busy launching. We have toSamantha: honestly, you could, you can see them in cursor now if you just say spin up like 50 subagents to, so cursor definesswyx: what Subagents.Yeah.Samantha: Yeah. So basically I think I shouldn't speak for the whole subagents team. This is like a different team that's been working on this, but our thesis or thing that we saw internally is that like they're great for context management for kind of long running threads, or if you're trying to just throw more compute at something.We have strongly used, almost like a generic task interface where then the main agent can define [00:43:00] like what goes into the subagent. So if I say explore my code base, it might decide to spin up an explore subagent and or might decide to spin up five explore subagent.swyx: But I don't get to set what those subagent are, right?It's all defined by a model.Samantha: I think. I actually would have to refresh myself on the sub agent interface.Jonas: There are some built-in ones like the explore subagent is free pre-built. But you can also instruct the model to use other subagents and then it will. And one other example of a built-in subagent is I actually just kicked one off in cursor and I can show you what that looks like.swyx: Yes. Because I tried to do this in pure prompt space.Jonas: So this is the desktop app? Yeah. Yeah. And that'sswyx: all you need to do, right? Yeah.Jonas: That's all you need to do. So I said use a sub agent to explore and I think, yeah, so I can even click in and see what the subagent is working on here. It ran some fine command and this is a composer under the hood.Even though my main model is Opus, it does smart routing to take, like in this instance the explorer sort of requires reading a ton of things. And so a faster model is really useful to get an [00:44:00] answer quickly, but that this is what subagent look like. And I think we wanted to do a lot more to expose hooks and ways for people to configure these.Another example of a cus sort of builtin subagent is the computer use subagent in the cloud agents, where we found that those trajectories can be long and involve a lot of images obviously, and execution of some testing verification task. We wanted to use that models that are particularly good at that.So that's one reason to use subagents. And then the other reason to use subagents is we want contexts to be summarized reduced down at a subagent level. That's a really neat boundary at which to compress that rollout and testing into a final message that agent writes that then gets passed into the parent rather than having to do some global compaction or something like that.swyx: Awesome. Cool. While we're in the subagents conversation, I can't do a cursor conversation and not talk about listen stuff. What is that? What is what? He built a browser. He built an os. Yes. And he [00:45:00] experimented with a lot of different architectures and basically ended up reinventing the software engineer org chart.This is all cool, but what's your take? What's, is there any hole behind the side? The scenes stories about that kind of, that whole adventure.Samantha: Some of those experiments have found their way into a feature that's available in cloud agents now, the long running agent mode internally, we call it grind mode.And I think there's like some hint of grind mode accessible in the picker today. ‘cause you can do choose grind until done. And so that was really the result of experiments that Wilson started in this vein where he I think the Ralph Wigga loop was like floating around at the time, but it was something he also independently found and he was experimenting with.And that was what led to this product surface.swyx: And it is just simple idea of have criteria for completion and do not. Until you complete,Samantha: there's a bit more complexity as well in, in our implementation. Like there's a specific, you have to start out by aligning and there's like a planning stage where it will work with you and it will not get like start grind execution mode until it's decided that the [00:46:00] plan is amenable to both of you.Basically,swyx: I refuse to work until you make me happy.Jonas: We found that it's really important where people would give like very underspecified prompt and then expect it to come back with magic. And if it's gonna go off and work for three minutes, that's one thing. When it's gonna go off and work for three days, probably should spend like a few hours upfront making sure that you have communicated what you actually want.swyx: Yeah. And just to like really drive from the point. We really mean three days that No, noJonas: human. Oh yeah. We've had three day months innovation whatsoever.Samantha: I don't know what the record is, but there's been a long time with the grantsJonas: and so the thing that is available in cursor. The long running agent is if you wanna think about it, very abstractly that is like one worker node.Whereas what built the browser is a society of workers and planners and different agents collaborating. Because we started building the browser with one worker node at the time, that was just the agent. And it became one worker node when we realized that the throughput of the system was not where it needed to be [00:47:00] to get something as large of a scale as the browser done.swyx: Yeah.Jonas: And so this has also become a really big mental model for us with cloud, cloud agents is there's the classic engineering latency throughput trade-offs. And so you know, the code is water flowing through a pipe. The, we think that over the coming months, the big unlock is not going to be one person with a model getting more done, like the water flowing faster and we'll be making the pipe much wider and so ing more, whether that's swarms of agents or parallel agents, both of those are things that contribute to getting.Much more done in the same amount of time, but any one of those tasks doesn't necessarily need to get done that quickly. And throughput is this really big thing where if you see the system of a hundred concurrent agents outputting thousands of tokens a second, you can't go back like that.Just you see a glimpse of the future where obviously there are many caveats. Like no one is using this browser. IRL. There's like a bunch of things not quite right yet, but we are going to get to systems that produce real production [00:48:00] code at the scale much sooner than people think. And it forces you to think what even happens to production systems. Like we've broken our GitHub actions recently because we have so many agents like producing and pushing code that like CICD is just overloaded. ‘cause suddenly it's like effectively weg grew, cursor's growing very quickly anyway, but you grow head count, 10 x when people run 10 x as many agents.And so a lot of these systems, exactly, a lot of these systems will need to adapt.swyx: It also reminds me, we, we all, the three of us live in the app layer, but if you talk to the researchers who are doing RL infrastructure, it's the same thing. It's like all these parallel rollouts and scheduling them and making sure as much throughput as possible goes through them.Yeah, it's the same thing.Jonas: We were talking briefly before we started recording. You were mentioning memory chips and some of the shortages there. The other thing that I think is just like hard to wrap your head around the scale of the system that was building the browser, the concurrency there.If Sam and I both have a system like that running for us, [00:49:00] shipping our software. The amount of inference that we're going to need per developer is just really mind-boggling. And that makes, sometimes when I think about that, I think that even with, the most optimistic projections for what we're going to need in terms of buildout, our underestimating, the extent to which these swarm systems can like churn at scale to produce code that is valuable to the economy.And,swyx: yeah, you can cut this if it's sensitive, but I was just Do you have estimates of how much your token consumption is?Jonas: Like per developer?swyx: Yeah. Or yourself. I don't need like comfy average. I just curious. ISamantha: feel like I, for a while I wasn't an admin on the usage dashboard, so I like wasn't able to actually see, but it was a,swyx: mine has gone up.Samantha: Oh yeah.swyx: But I thinkSamantha: it's in terms of how much work I'm doing, it's more like I have no worries about developers losing their jobs, at least in the near term. ‘cause I feel like that's a more broad discussion.swyx: Yeah. Yeah. You went there. I didn't go, I wasn't going there.I was just like how much more are you using?Samantha: There's so much stuff to be built. And so I feel like I'm basically just [00:50:00] trying to constantly I have more ambitions than I did before. Yes. Personally. Yes. So can't speak to the broader thing. But for me it's like I'm busier than ever before.I'm using more tokens and I am also doing more things.Jonas: Yeah. Yeah. I don't have the stats for myself, but I think broadly a thing that we've seen, that we expect to continue is J'S paradox. Whereswyx: you can't do it in our podcast without seeingJonas: it. Exactly. We've done it. Now we can wrap. We've done, we said the words.Phase one tab auto complete people paid like 20 bucks a month. And that was great. Phase two where you were iterating with these local models. Today people pay like hundreds of dollars a month. I think as we think about these highly parallel kind of agents running off for a long times in their own VM system, we are already at that point where people will be spending thousands of dollars a month per human, and I think potentially tens of thousands and beyond, where it's not like we are greedy for like capturing more money, but what happens is just individuals get that much more leverage.And if one person can do as much as 10 people, yeah. That tool that allows ‘em to do that is going to be tremendously valuable [00:51:00] and worth investing in and taking the best thing that exists.swyx: One more question on just the cursor in general and then open-ended for you guys to plug whatever you wanna put.How is Cursor hiring these days?Samantha: What do you mean by how?swyx: So obviously lead code is dead. Oh,Samantha: okay.swyx: Everyone says work trial. Different people have different levels of adoption of agents. Some people can really adopt can be much more productive. But other people, you just need to give them a little bit of time.And sometimes they've never lived in a token rich place like cursor.And once you live in a token rich place, you're you just work differently. But you need to have done that. And a lot of people anyway, it was just open-ended. Like how has agentic engineering, agentic coding changed your opinions on hiring?Is there any like broad like insights? Yeah.Jonas: Basically I'm asking this for other people, right? Yeah, totally. Totally. To hear Sam's opinion, we haven't talked about this the two of us. I think that we don't see necessarily being great at the latest thing with AI coding as a prerequisite.I do think that's a sign that people are keeping up and [00:52:00] curious and willing to upscale themselves in what's happening because. As we were talking about the last three months, the game has completely changed. It's like what I do all day is very different.swyx: Like it's my job and I can't,Jonas: Yeah, totally.I do think that still as Sam was saying, the fundamentals remain important in the current age and being able to go and double click down. And models today do still have weaknesses where if you let them run for too long without cleaning up and refactoring, the coke will get sloppy and there'll be bad abstractions.And so you still do need humans that like have built systems before, no good patterns when they see them and know where to steer things.Samantha: I would agree with that. I would say again, cursor also operates very quickly and leveraging ag agentic engineering is probably one reason why that's possible in this current moment.I think in the past it was just like people coding quickly and now there's like people who use agents to move faster as well. So it's part of our process will always look for we'll select for kind of that ability to make good decisions quickly and move well in this environment.And so I think being able to [00:53:00] figure out how to use agents to help you do that is an important part of it too.swyx: Yeah. Okay. The fork in the road, either predictions for the end of the year, if you have any, or PUDs.Jonas: Evictions are not going to go well.Samantha: I know it's hard.swyx: They're so hard. Get it wrong.It's okay. Just, yeah.Jonas: One other plug that may be interesting that I feel like we touched on but haven't talked a ton about is a thing that the kind of these new interfaces and this parallelism enables is the ability to hop back and forth between threads really quickly. And so a thing that we have,swyx: you wanna show something or,Jonas: yeah, I can show something.A thing that we have felt with local agents is this pain around contact switching. And you have one agent that went off and did some work and another agent that, that did something else. And so here by having, I just have three tabs open, let's say, but I can very quickly, hop in here.This is an example I showed earlier, but the actual workflow here I think is really different in a way that may not be obvious, where, I start t

What does it actually look like to build an AI-native product and lead an engineering team through the AI era when you've been doing it longer than most? Rob Zuber sits down with Loïc Houssier, CTO at Superhuman, to talk about what it meant to be an AI company before AI was everywhere, and how that early foundation shapes the way they build, ship, and think today.The conversation covers how Loïc drove AI tool adoption across his engineering org without mandates (and which senior engineer's change of heart became a cultural turning point), why great UX is still the real moat in an age where anyone can ship an average product fast, and how email, despite everything, remains the connective tissue of professional life. Plus: what it's like to rethink your entire SDLC when the economics of building software change overnight.Have someone you'd like to hear on the show, reach out to us on X at @CircleCI!

Will Madden joins the podcast to talk about Prisma Next and the evolution from Prisma 7, including the decision to migrate away from Rust, ship the core through WebAssembly, and move toward a fully TypeScript ORM. The conversation dives into how modern workflows like agentic coding change the role of an ORM and why tools still matter even when agents can write SQL queries directly. We discuss how feedback loops, guardrails, and the TypeScript type system help prevent errors, along with the new query builder, query linter, and middleware layer that analyze queries using an abstract syntax tree. The episode also covers new database capabilities including Postgres support, upcoming Mongo support, and extensions like PG Vector, enabling vector columns and cosine distance similarity search. You'll also learn about new patterns such as collection methods, scopes, and composable database extensions, plus tooling like driver adapters, a potential compatibility layer, and safeguards like lint rules and a performance budget middleware designed to catch expensive queries before they run. Resources The Next Evolution of Prisma ORM: https://www.prisma.io/blog/the-next-evolution-of-prisma-orm We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Fill out our listener survey! https://t.co/oKVAEXipxu Let us know by sending an email to our producer, Elizabeth, at elizabeth.becz@logrocket.com, or tweet at us at PodRocketPod. Check out our newsletter! https://blog.logrocket.com/the-replay-newsletter/ Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form, and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understanding where your users are struggling by trying it for free at LogRocket.com. Try LogRocket for free today. Chapters 00:00 Introduction 01:00 Prisma Seven and the Move Away from Rust 02:20 Missing Features and Mongo Support 03:00 Why Prisma Started Rebuilding the Core 04:00 Community Sentiment and Developer Feedback 05:20 Rethinking ORMs in the AI and Agentic Coding Era 06:45 Why Agents Still Need ORMs 07:30 Feedback Loops and Guardrails for SQL 08:30 Type Safety and the First Layer of Query Validation 09:30 Query Linter and Middleware Architecture 11:00 Runtime Validation and Query Errors 12:30 Configuring Lint Rules and Guardrails 14:00 Designing ORMs for Humans and Agents 15:30 Collection Methods and ActiveRecord-style Scopes 17:00 Reusable Queries and Domain Vocabulary 18:30 Query Composition and Flexibility 19:00 Performance Guardrails and Query Budget Middleware 20:30 Debugging ORM Performance Issues 21:00 Query Telemetry and Request Tracing 22:30 Prisma Next Extensibility and Database Plugins 23:00 Using PGVector and Vector Search 24:00 Database Drivers and Backend Architecture 25:00 Native Mongo Support in Prisma Next 26:00 Community Extensions and Middleware Ecosystem 27:00 Runtime Schema Validation Use Cases 28:00 Writing Custom Query Validation Rules 29:00 Migration Paths from Prisma Seven 30:30 Compatibility Layers vs Parallel Systems 32:00 Prisma Next Roadmap and Timeline 34:30 What Developers Will Be Most Excited About 35:30 Final Thoughts and Community Feedback

Sponsored by Auth0 for Startups → 1-year free https://auth0.com/startups/vip Auth0 is an adaptable authentication and authorization platform that helps you secure your apps and AI agents. It delivers convenience, privacy, and security so you can focus on building a great UX. FOUNDER PROFILE: Ilya Levtov, Founder of Craft https://www.linkedin.com/in/ilya-levtov/

Mandi Geiselman has worked as Senior UX Designer at Autodesk, where she designs for complex media & entertainment tools (like Maya and 3DS Max), and she is an Advanced OOUX Strategist who's created resources on building an OOUX community of practice inside big organizations. In this episode of the podcast, Sophia and Mandi talk about OOUXing Horizon Forbidden West, why game UX isn't about “making it easy,” and how bases, extensions, and conditional logic can make even the most complex systems more understandable (and more shareable for teams).LINKS: Join the OOUX Forum Connect with Mandi

In this episode of Future of UX, I'm sharing the three things I would do if I were starting my design career today as a junior UX/UI/Product Designer.And I'm not saying this as abstract advice. I'm saying it as someone who started almost 10 years ago with basically zero real UX skills, taught myself a lot on the job, and built a career in a market that was booming back then.The difference is: the market today is tighter, teams are leaner, and AI is automating a lot of the tasks that used to be classic “junior work.” So the big question becomes:If execution is getting cheaper and faster… what becomes valuable?What's actually changing for junior designers (and why it's not just hype)Which junior tasks are increasingly automatedWhere junior designers are most vulnerable (and how to avoid that trap)The 3 highest-leverage moves I'd focus on in 2026–2028:Become AI-native (build workflows, not just prompts)Build product thinking early (learn the “why,” not just the “how”)Become the human layer in human–AI systems (trust, transparency, oversight)You don't need to master every tool. But you do need to move. Start small, build confidence, and position yourself above pure execution work.What we coverKey takeawayAnd if you want to connect, I'm most active on LinkedIn (and sometimes on Instagram too), where I share tools, resources, and experiments.

Routstr is an open marketplace for ai compute, powered by nostr and bitcoin.Routstr: https://routstr.comChat app: https://chat.routstr.comOpenclaw setup: https://routstr.com/openclawRun a Routstr node and earn sats: https://github.com/Routstr/routstr-coreGithub: https://github.com/Routstr Routstr on nostr: https://primal.net/p/npub130mznv74rxs032peqym6g3wqavh472623mt3z5w73xq9r6qqdufs7ql29sEvan on nostr: https://primal.net/p/npub1u37h8rhgm9f95d90lpk2afw8h4t75kf6w8vmga2zz9jsx3atzpuqlmw8vyRedshift on nostr: https://primal.net/p/npub1ftt05tgku25m2akgvw6v7aqy5ux5mseqcrzy05g26ml43xf74nyqsredshThefux on nostr: https://primal.net/p/npub1ygjd597hdwu8larprmhj893d5p832j5mhejpx40ukezgudvayg9qeklajcShroominic on nostr: https://primal.net/p/npub18gr2m5cflkzpn6jdfer4a8qdlavsn334m9mfhurjsge08grg82zq6hu9suEPISODE: 192BLOCK: 939283PRICE: 1368 sats per dollar(00:03:02) Routstr and the team(00:07:24) What is Routstr?(00:10:26) Proxy providers, proprietary models, and pricing dynamics(00:13:16) Discovery, reviews, and quality signaling on Nostr(00:16:07) Fees, sustainability, and open source funding models(00:21:32) OpenClaw, LNVPS, and one-click sovereign stack(00:25:27) Why Nostr is ideal for agents vs. closed platforms(00:33:00) Crowdzapping, bounties, and agents building public goods(00:38:02) Agent specialization, cost tiers, and future routing(00:45:31) Resilience: routing around outages and pay-per-request(00:48:12) Self-host vs. marketplaces, selling spare compute(00:54:00) AI compute meets Bitcoin mining and energy realities(00:56:50) Hardware choices: Mac minis, old PCs, and VPS security(00:59:10) Linux advantage and agents removing UX friction(01:00:24) Open chat protocols, Marmot, and agentic comms(01:03:54) Acceleration, small teams with many agents shipping fast(01:04:19) Closing thoughts from the Routstr teammore info on the show: https://citadeldispatch.comlearn more about me: https://odell.xyz

Jaime Hunt sits down with Jason Smith, Founder and Managing Director of OHO, to unpack how AI in higher education is fundamentally changing the way students search for colleges. As AI tools like ChatGPT and Gemini increasingly shape the student journey, institutions must rethink their approach to SEO for higher education and digital visibility. Jason introduces OHO's new AI Visibility Scorecard and shares eye-opening insights into where AI models pull information from—and why that matters for enrollment marketers. This conversation challenges higher ed leaders to move beyond traditional search strategies and prepare for an AI-driven future of student recruitment. Guest Name: Jason Smith, Founder and Managing Director of OHO Guest Social: https://www.linkedin.com/in/jasonsmith1/ Guest Bio: Jason is the Founder and Managing Director of OHO, a leading digital agency dedicated to higher education. For over 20 years, he has led a team of strategists, designers, UX researchers, marketers, and developers who help colleges and universities solve complex digital challenges—from launching major websites to driving enrollment through digital marketing.  A former designer and creative director, Jason brings a deep appreciation for how storytelling, design, and technology can work together to reach the right audiences and move institutions forward. He's worked with 37 of the top 100 U.S. colleges and universities, guiding leaders through projects that clarify their goals, connect with users, and elevate their digital presence.  Endlessly curious and always inventing, Jason is currently digging deep into how to increase AI visibility for colleges and universities so that they can reach prospective students. - - - -Connect With Our Host:Jaime Hunthttps://www.linkedin.com/in/jaimehunt/https://twitter.com/JaimeHuntIMCAbout The Enrollify Podcast Network:Confessions of a Higher Ed CMO is a part of the Enrollify Podcast Network. If you like this podcast, chances are you'll like other Enrollify shows too! Enrollify is made possible by Element451 — The AI Workforce Platform for Higher Ed. Learn more at element451.com. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

A veteran of the global crypto industry, Colin Goltra has been an early adopter and advocate for digital assets throughout his career.Colin Goltra is the Chief Executive Officer of Morph, a blockchain platform building universal infrastructure for borderless payments and financial services. He recently joined the Bitcoin.com News Podcast to talk about the market.In this episode Colin identifies the previous year as the critical "stablecoin moment," driven by a perfect storm of regulatory clarity (like the Genius Act and MiCA) and technological advancements on smart-contracting ecosystems that have finally solved the performance and scalability issues that plagued earlier attempts with Bitcoin. Morph's mission has pivoted to stablecoin-based global payment settlement, adopting a "ruthlessly pragmatic" strategy to prepare for a market that could be dominated by either one or two fiat-backed stablecoins (USD-linked like USDC and USDT) or by a rise in relevant regional stablecoins.He highlights the profound impact of stablecoins in emerging economies, where access to the dollar provides a crucial hedge against high local fiat inflation, citing the Philippine Peso as a prime example. Looking at the current landscape, Colin pinpoints four key active verticals in crypto: institutional stablecoin-based payments, the significant growth of Real-World Assets (RWAs), prediction markets for valuable information, and the emerging space of Agentic AI, which will require crypto layers for payment and transacting.The long-term vision for crypto, according to Colin, anticipates a transition from a purely "cryptonative" era to a more institutional and pragmatic phase over the next decade. He predicts that for the average person, the underlying blockchain infrastructure will "melt away at the UX level," becoming an invisible rail for better, faster payment solutions. A major challenge remains a knowledge gap for small and mid-sized businesses. To address this, Morph is funding a $150 million payment accelerator to incentivize traditional payment businesses to migrate their transaction volume onto the Morph chain.

We're wrapping up our AI Tools series with a special episode featuring just the two of us—Matt and Moshe—looking back at what we really learned (and where we're still confused) about AI in product management.Across this conversation, we revisit the core themes that emerged with our guests and in our own experiments: from “vibe coding” and no‑code builders, to LLM assistants, enterprise privacy, agentic workflows, and the evolving role of the product manager. We share candid stories of using tools like Google Stitch, Figma/Figma Make, FlutterFlow, Base44, and others to design and prototype a real mobile app; what worked, what broke, and why credits, pricing, and model limits matter far more than the glossy demos suggest.Join Matt and Moshe as they explore:How our AI Tools series evolved, from “let's review tools” to “AI is not one thing, it's many different problem spaces”Why “vibe coding” is a misleading umbrella term, and how it means something different to devs, PMs, and designersLessons from using AI for design and prototyping: inconsistent outputs, beta‑stage rough edges, and the pain of credit-based modelsBuild vs. buy for AI: integrating foundation models vs. building your own, and what that means for pricing, UX, and reliabilityEnterprise realities: privacy, security, and why tools like Copilot/Gemini have such an advantage where data and IT policies matterHow conversations with our guests (Sani, Eva, Elena, Stav, Yaron, Marcos and Adir) shifted our thinking about workflows, orchestration, and agentsThe future of agent-to-agent interactions: what happens when AIs negotiate purchases and workflows with minimal human promptsWhy first principles and business outcomes still matter more than any single AI toolHow the PM role is changing: less tool‑chasing, more orchestration, strategy, and clarity about what problem we're actually solvingWhat topics we'd tackle next, like pricing, packaging, and credit models for AI products, and how this series is shaping our own careersAnd much more!You can connect with us and keep following what comes after this AI Tools series:Product for Product Podcast: http://linkedin.com/company/product-for-product-podcastMatt Green: https://www.linkedin.com/in/mattgreenproduct/Moshe Mikanovsky: http://www.linkedin.com/in/mikanovskyNote: Any views mentioned in the podcast are the sole views of our hosts and guests, and do not represent the products mentioned in any way.Please leave us a review and feedback ⭐️⭐️⭐️⭐️⭐️

In this episode I'm joined by Jim Morris.  We chat about the wake-up call that pushed him from building first to testing first. Jim and I discuss loyalty programs no one wanted, roadmaps filled with sequenced risk, AI prototypes that hallucinate and the uncomfortable reality that confidence often replaces evidence.We also dig into something deeper: why smart teams ignore data, why leaders fall in love once an idea hits the roadmap, and why testing isn't about better UX,  it's about real value.Jim shares how he even tests his own teaching process for students at Berkeley.Because as he puts it:“We can build stuff. But if people don't use it, we're just creating product debt.”Enjoy my conversation with Jim Morris.TakeawaysTesting is crucial to ensure product effectiveness and user engagement.Data analysis can reveal the true usage of product features.Mindset plays a significant role in how product ideas are perceived and developed.Not all ideas will succeed; testing helps identify the viable ones.User motivation is key to the success of features and programs.Prototyping tools can enhance the testing process but require careful implementation.Learning from failures in testing is essential for growth and improvement.Roadmaps should be flexible to adapt to changing priorities and evidence.It's important to focus on the core value proposition of a product.Continuous experimentation and adaptation are vital in product management.Guest LinksWebsite: https://productdiscoverygroup.com/LinkedIn Profile: https://www.linkedin.com/in/jimmorrisstanford/ If your leadership team is about to make a big strategic bet, the real risk usually isn't the idea, it's the assumptions behind it that haven't been surfaced yet. A Decision Sprint is a focused 6–12 week engagement where we extract, map, and test those risks so leaders can make a clear Commit, Correct, or Cut decision before major capital moves. Learn more or apply at precoil.com.

Emma from Sparo Studios is here to tell you that your logo is not your brand, and your pretty website might be the reason your ads aren't converting. In this episode, Emma and I dig into why brand positioning and UX are the two non-negotiables for eCommerce success, what to look for when your site isn't performing, and how to make sure your ads and your website are actually working together instead of against each other.

Hoje o papo é sobre continuous deployment em larga escala! Neste episódio, Paulo Silveira lê e comenta o texto Continuous deployment for large monorepos, do blog da Uber. O artigo explora como a empresa reformulou seu sistema de deploy contínuo para lidar com milhares de microserviços, monorepos gigantes e dezenas de milhares de deploys semanais, ao mesmo tempo que reflete sobre padronização, platform engineering, cultura DevOps e os desafios técnicos e organizacionais de escalar software com segurança. Links: Continuous deployment for large monorepos DevOps e Engenharia de Plataforma: A Experiência do Dev – Hipsters Ponto Tech #504 Estudo de caso: UX e a construção de jornadas de experiências no Santander – Hipsters Ponto Tech #475 Deep Dive: Experiência Dev no Itaú – Hipsters Ponto Tech #474 Case Banco PAN: Engenharia de Plataformas e Dev Experience – Hipsters Ponto Tech #406 Blog do Paulo Matricule-se na Alura e desenvolva sua carreira em tecnologia! Aprenda as tecnologias mais demandadas pelo mercado e conquiste o seu próximo nível com a maior comunidade tech do país. Inscreva-se na newsletter Imersão, Aprendizagem e Tecnologia, escrita por Paulo Silveira. TechGuide.sh, um mapeamento das principais tecnologias demandadas pelo mercado para diferentes carreiras, com nossas sugestões e opiniões. #7DaysOfCode: Coloque em prática os seus conhecimentos de programação em desafios diários e gratuitos. Acesse https://7daysofcode.io/ Produção e conteúdo: Alura Cursos de Tecnologia – https://www.alura.com.br Edição e sonorização: Rede Gigahertz de Podcasts

What if the thing standing between you and your dream job had nothing to do with your resume, your portfolio, or your experience? In this episode, I sit down with my client Colleen, who made a bold career switch from teaching into UX design and discovered that the hardest part of the journey had nothing to do with learning new skills. If you've ever felt like you're doing everything right and still not getting the yes, this conversation is going to hit close to home. Tune in to hear what finally shifted for Colleen and why the moment everything changed wasn't what she expected at all. Get full show notes and more information here:

I have a confession to make. I'm exhausted. In the best possible way after a week in Orlando, Florida for the Kitchen & Bath Industry Show. I have so much to share with you today! My journey started on the Monday before the show began for a travel day, sound check and confirming the final details form the show. In addition to hosting the KBIS Podcast Studio again this year, moderating a panel on the NEXT Stage and recording conversations for the show, I wanted to help you prepare for the show next February in Las Vegas. But Josh, next February is like 11 months away. That's true, but here's a secret. Come a little closer, it's just us. KBIS is the essential American kitchen and bath show, full stop. It's about learning, seeing, connecting and putting all of the pieces together to understand how the American market is setting up for the next year and the trending ideas that have staying power for the next 5-10 years. Designer Resources Pacific Sales Kitchen and Home. Where excellence meets expertise. TimberTech – Real wood beauty without the upkeep You can listen to Convo By Design for the conversations with industry insiders. If I were a designer, I would. I believe that this show tells the stories that you should really know to get a feel for directionality of the industry. Specifiers are the plus of the industry and the ideas emanating from the show this year covered the technology revolution taking place from an AI perspective, but there's more. The kitchen is in the midst of a wholesale change. And it's exciting to see it happen in real time. Learning was a key theme this year. If you were not at the show this year, you are behind the curve. I don't say this to scare you, I tell you this so you make the time to get to the show next year. All three days and plan to see as much as you can. But, I wanted to share some of the key ideas from the show this year. For additional details, check the show notes. Luxury is the measurable outcome of thoughtful design—where performance, longevity, and relevance align to support the way people actually live. Luxury is the removal of friction from daily life. Luxury is durability aligned with intent. Luxury is design that continues to perform long after the purchase is forgotten. Luxury is confidence—in function, longevity, and fit. Luxury is not what you spend. It's what you never have to rethink. The Kitchen as the Primary Investment The kitchen remains the #1 homeowner investment nationwide. Homeowners are willing to exceed budget in the kitchen more than any other space. The kitchen is the most public and social room in the home. It represents identity: “I'm a cook,” “I entertain,” “I host.” Food equals memory; appliances enable those memories. The Expanding Kitchen Ecosystem Kitchens are no longer singular spaces—they expand throughout the home. Secondary kitchens (sculleries, prep kitchens, butler's pantries) are rising. Beverage centers, bars, and wine storage are increasingly common. Coffee stations and en-suite kitchenettes are viewed as lifestyle enhancements. Outdoor kitchens are now expected in many markets. Refrigeration appears in bathrooms (skincare), offices, and guest suites. Multigenerational living drives multi-kitchen design. Post-COVID entertaining shifted bar culture into the home. Value Has Replaced Price as the Primary Decision Driver Consumers rarely regret investing more in appliances. Longevity, performance, and service support define value. Sustainability increasingly aligns with durability. Human-Centric Design Is the New Standard Appliances must be intuitive without relying on manuals. UX consistency across appliances improves adoption. Technology must solve real problems—not create new friction. Appliances Are Expanding Beyond the Kitchen Refrigeration, coffee systems, and specialty appliances now appear throughout the home. Multi-kitchen and multi-generational design is driving specification complexity. Flexibility and modular integration are essential. Practical Innovation vs Feature Saturation Most consumers use only a small percentage of available features. Simplification improves usability, adoption, and satisfaction. Innovation must solve real problems—not marketing problems. Appliances as Infrastructure for Daily Life Refrigerators open dozens of times daily, making ergonomic design critical. Dishwashers, washers, and refrigeration now integrate into behavioral routines. Appliances increasingly support lifestyle efficiency, not just task completion. Quiet Luxury: The New Definition of Premium Quiet luxury shifts focus from visual dominance to experiential excellence. Appliances integrate seamlessly into architecture. Minimal visual disruption supports design continuity. Performance becomes more important than appearance. Identity & Evolution in Design Designers must periodically redefine themselves and their work to remain relevant. Personal growth and evolving priorities shape professional identity and approach. Burnout vs Ambition Burnout is not a badge of honor; it results from overextension and emotional labor. Ambition aligns energy with superpowers and opportunities, creating sustainable growth. Setting boundaries is essential to differentiate productive ambition from harmful overwork. Emotional Labor & Client Management Design work involves managing client emotions, expectations, and second-guessing. Designers act as liaisons between clients, contractors, and teams, absorbing invisible pressures. Managing scope creep and change orders is a practical strategy to protect both energy and profitability. Social Media & Comparison Culture Social media can amplify unrealistic expectations and unhealthy competition. Designers often feel compelled to accommodate clients' desires, sometimes overextending themselves to maintain a positive perception. These core themes coming out of the show this year tell a story that cannot be ignored. The thought process is changing. More human-centric at a time when technology seems to be taking over. Interesting times. Shifting away from that, I want to share two conversations from the show. Brandon Kirschner | Azzuro Living – Control the Process, Control the Outcome: Inside Azzurro Living's Design Advantage Brandon Kirshner of Azzurro Living explains how factory ownership, material innovation, and hands-on experimentation are redefining luxury outdoor furniture—and why relationships and resilience matter more than ever. Recorded live at the Kitchen and Bath Industry Show in Orlando, this conversation with Brandon Kirshner, Partner and VP of Design at Azzurro Living, explores what it means to design, manufacture, and deliver luxury outdoor furniture with complete control over the process. Kirshner shares how owning and operating their own production facility provides a rare advantage in a crowded marketplace. This vertical integration allows Azzurro Living to oversee every step—from raw material sourcing to fabrication—ensuring performance, durability, and design integrity in extreme climates. The conversation also explores the realities of modern product manufacturing: navigating global instability, breaking through to specifiers in an oversaturated marketplace, and the renewed importance of in-person relationships. At its core, this is a story about design leadership, material obsession, and maintaining optimism in a rapidly shifting industry. Vertical Integration Changes Everything Full ownership of production facility ensures quality control Ability to experiment directly with materials and fabrication Eliminates reliance on third-party manufacturing limitations Material Innovation Drives Luxury Performance Products engineered for extreme heat and harsh winters Hands-on experimentation with rope, wicker, and aluminum Performance and longevity are core to brand value Design as the Core Differentiator Industrial design roots shape product philosophy Focus on original forms rather than “me-too” furniture Design enhances lifestyle, not just aesthetics Relationships Still Drive Specification Trade shows like High Point Market remain essential Face-to-face interaction builds trust and long-term partnerships Education through sales teams and specifier outreach is critical Resilience and Optimism in a Volatile Industry Navigating tariffs, supply chains, and global uncertainty Maintaining a solution-oriented mindset Viewing disruption as part of long-term growth In luxury outdoor furniture, control isn't just an operational advantage—it's a creative one. For Brandon Kirshner, Partner and VP of Design at Azzurro Living, ownership of the manufacturing process is the foundation of everything the company does. Unlike many competitors who rely on outsourced production, Azzurro Living operates its own factory, giving Kirshner and his team direct oversight of every detail, from raw materials to finished form. This control allows for something rare in today's manufacturing environment: true experimentation. Working directly with fabricators, Kirshner explores new weaving techniques, tests material durability, and refines structural details. The result is furniture engineered not just to look refined, but to perform in punishing environments—from desert heat exceeding 115 degrees to unpredictable seasonal extremes. Kirshner's path into furniture design began with industrial design studies, where exposure to iconic modernist designers revealed furniture as both functional object and artistic expression. That perspective continues to shape his work today, where innovation isn't driven by trend cycles, but by material curiosity and structural integrity. Launching Azzurro Living in 2020 presented immediate challenges, from supply chain disruption to economic uncertainty. Yet Kirshner views volatility as inevitable rather than exceptional. Experience has taught him that adaptability—not stability—is the constant in product manufacturing. Equally important is maintaining strong relationships within the design community. Trade shows, in-person meetings, and direct engagement remain essential tools for connecting with specifiers and building trust. In an increasingly crowded marketplace, Azzurro Living's approach is clear: control the process, push material boundaries, and let design lead. The result is furniture that reflects not just luxury, but intention. “Owning our factory gives us complete control—from raw material to finished product—and that changes everything.” “Design is the reason people invest in luxury furniture. Performance just makes it last.” “You can't innovate from a distance. Being hands-on with materials is where real progress happens.” “Trade shows and face-to-face interaction still matter because this industry runs on relationships.” “No matter what challenges come—tariffs, supply chain, geopolitics—we'll figure it out. That mindset is essential.” This is Cathy Purple Cherry – Founding Principal | Purple Cherry, freshly installed in the Convo By Design Icon Registry, we caught up at KBIS for a fresh take. Human-Centered Architecture, Resilience, and the Responsibility of Design Cathy Purple Cherry reflects on architecture as a lifelong act of care—supporting people through turbulence, embracing multigenerational living, rejecting trend culture, and using design as a tool for healing, connection, and growth. Recorded live at the Kitchen and Bath Industry Show, this conversation with Cathy Purple Cherry of Purple Cherry Architects explores architecture not as a moment of visual impact, but as a lifelong framework for human support. Purple Cherry shares her philosophy that architecture must evolve alongside the people it serves, especially during times of societal turbulence and personal change. Her work is grounded in human-centered thinking, emotional durability, and the belief that design can create stability amid chaos. The discussion moves beyond aesthetics into deeper territory—resilience shaped by hardship, the responsibility of creatives to provide clarity and options, and the importance of giving back. Purple Cherry also addresses the rise of multigenerational living, generational shifts in work culture, and the dangers of trend-driven design thinking. At its core, this conversation reveals architecture as both a professional discipline and a personal calling—one rooted in empathy, long-term thinking, and service. Architecture as Long-Term Support, Not Momentary Expression Design must serve people across decades, not just visual moments Architecture provides emotional stability during uncertain times Human-centered design is becoming essential, not optional Growth Through Challenge and Adversity Personal and professional hardship builds resilience Lessons learned shape better architects and stronger leaders Teaching and mentoring are essential responsibilities Multigenerational Living as a Cultural Shift Economic and social changes are reshaping American housing Families are staying connected longer Architecture must adapt to evolving family dynamics The Responsibility of Creatives in Times of Tension Architects provide clarity and solutions amid chaos Design can serve as a “relief valve” for societal stress Creatives help people reimagine how they live Rejecting Trend Culture in Favor of Lasting Design Trend cycles are often superficial and misleading True architecture transcends short-term aesthetic movements Enduring design comes from purpose, not prediction Giving Back as a Core Professional and Personal Value Sharing knowledge strengthens the profession Service to others creates deeper meaning in creative work Design is both a gift and a responsibility For Cathy Purple Cherry, architecture has never been about creating a moment. It's about supporting a lifetime. As founder of Purple Cherry Architects, with offices in Annapolis, Charlottesville, and New York City, Purple Cherry has built a practice grounded in the belief that design must evolve alongside the people it serves. Architecture, she explains, is not about solving for a single moment, but about creating environments that support human life over time. That perspective feels especially relevant today. As social, economic, and cultural turbulence reshapes how people live and work, architecture has taken on a new role—not just as shelter, but as emotional infrastructure. Spaces must provide calm, clarity, and flexibility, particularly as multigenerational living becomes more common and families remain connected longer under one roof. Purple Cherry rejects the idea that architecture should chase trends. While the industry often focuses on forecasting aesthetic movements, she believes true design transcends these cycles. Lasting architecture emerges from purpose, empathy, and a deep understanding of human behavior. Her perspective is shaped not only by decades of professional experience, but by personal adversity. Hardship, she explains, builds resilience and strengthens one's ability to serve others. That philosophy extends into her commitment to mentorship, service, and giving back—values she sees as inseparable from meaningful creative work. For Purple Cherry, architecture is both discipline and calling. It is a lifelong process of learning, teaching, and refining. And in a world defined by rapid change, her message is clear: the most important role of design is not to impress, but to support the people who live within it. “Architecture isn't about solving for a moment. It's about supporting people over time.” “Through suffering, we become stronger—and that's what allows us to better serve others.” “Anything in the built environment that can calm us and organize our lives becomes essential.” “Design should never be driven by trends. It should be driven by purpose and people.” “The meaning of life is discovering your gifts. The purpose of life is sharing them.”

In this episode of Product Momentum, we're joined by Bansi Mehta, founder and CEO of Koru UX Design, an enterprise healthcare UX agency supporting some of the US’s largest healthcare technology companies. We discussed the busy intersection of artificial intelligence, product management, and UX Design. Bansi's Sense – Shape – Steer framework helps guide UX design teams as they integrate AI into their products – and avoid the trap of AI's drive toward mediocrity that limits individual creativity and expertise. Here's what we learned: Avoiding the Trap: AI Solutions' Race to Mediocrity AI's ability to rapidly generate hi-fi prototypes and voluminous content brings great benefit, but also significant risk. The risk manifests in mediocrity – i.e., solutions that drive to the mean. This sense of “good enough” stifles designer creativity and diminishes the quality – the Delight – of the final product. “The speed of AI makes it easier than ever to churn screens,” Bansi says. “But it's designed to deliver to that average mean that allows us to say, ‘that works, that makes sense.' And that's really the trap….these days, there's less patience in the industry for discovery and research.” Introducing the Sense – Shape – Steer Framework To combat this new reality, Bansi developed the Sense – Shape – Steer framework to help teams navigate the complexity of building AI-powered products. Sense. Understanding the Problem/Opportunity.“Sense is where you're really creating that sense of what is worth solving,” Bansi explains. “It's the intersection of what the user needs, what insights we have in terms of their challenges, and the opportunities that are present. But we mustn’t stop there. We then look to see what AI can do for us. And where we see the intersection, that’s the sweet spot.” Shape. Designing the AI-Enhanced User Experience.We emerge from the Sense step with rich insights into our user's desired experience, Bansi continues. “And as we approach Shape, we do so with an emphasis on the kind of UX challenge that we are trying to solve – from the user’s perspective. Using a storyboard, we proceed frame by frame to define the user's journey, the problem that we are trying to accomplish.” Steer. Implementing, Evaluating, and Iterating.The Steer step comes once you have built something and you launched, Bansi says. “This is where we define and clearly articulate our AI eval criteria that we've said are critical for product success,” Bansi adds. “I've seen products make it or break it depending on whether they got their AI evals right. It’s one thing to hypothesize that your solution will work. But it’s a completely different thing when you actually try to build sophisticated agentic AI layers where there’s multiple configurations and prompts.”   Broader Insights, Future Outlook The conversation underscores the notion that while AI accelerates development and content generation, it also requires subject matter experts in UX and Product to demonstrate greater vigilance than ever to maintain quality and relevance. The Sense – Shape – Steer framework calls on product teams to think first about user needs before considering whether and how to integrate AI. Our episode with Bansi Mehta feels like the capstone conversation to recent episodes with Nesrine Changuel, Teresa Torres, and Oji Udezue, where we examined bringing Delight to the user experience, re-engaging Discovery in the development process, and adjusting to the Speed of today's AI-driven development. The post 182 / How ‘Sense Shape Steer' Helps UXers Design AI Solutions, with Bansi Mehta appeared first on ITX Corp..

Unlock the secrets behind a successful tech career from someone who started coding at just 16 and became a product leader through curiosity, resilience, and mentorship. If you're passionate about breaking into tech, pivoting industries, or levelling up your impact, this episode is your blueprint for transformation. At only 16, our guest built a school fee management software for her mom's school, turning a simple idea into a real-world project that sparked her love for software engineering. From teaching mathematics at 12 to managing products in Nigeria's emerging tech scene, her journey defies convention and highlights that curiosity and continuous learning are your most valuable assets. She shares how her deep passion for tech was ignited by stories of badass mathematician hackers, and how she navigated the challenges of tech education—losing touch, then reigniting her skills with courses in AI and Python. We break down:How early hands-on projects can set a foundation for a thriving tech careerThe critical role of mentorship and community support in Nigeria and beyondWhy curiosity matters more than talent and how it propels you across disciplines—from backend engineering to UX and product managementPractical tips for transitioning into product management, even without a traditional tech backgroundThe importance of building strong relationships and camaraderie with your team that transcends work hours—creating a human-centred leadership style

On this latest episode of Innovator's Exchange, our host Hiten Patel interviews Blythe Masters, tracing her circuitous career from photocopying swap documentation in London to leading FNZ Group, a global wealth-technology platform that processes about $2.3 trillion and serves over 30 million end customers. Blythe reflects on her formative experiences at JP Morgan — including helping institutionalize credit derivatives — her career transitions, leadership lessons, and the importance of curiosity and resilience. She outlines FNZ's mission to remove inefficiency in wealth delivery, explains how AI and platform-level data will superpower human advisors (not replace them), and emphasizes the combined importance of software, data, people, and ecosystem strength in building competitive advantage. Blythe also discusses the UK's opportunities for innovation, particularly in light of the flexibility created by certain post-Brexit regulatory changes. Key topics include:  Early career: Blythe shares how her immersion in derivatives began during a gap-year temporary role at Morgan Guaranty, where she spent hours photocopying contracts and documents before eventually reading them. Derivatives and credit innovation: Since the early 1990s, Blythe was scrutinizing nascent credit-linked concepts, eventually leading multi-year efforts at JP Morgan to translate those ideas into institutional products — working with ISDA, rating agencies, regulators, internal risk teams, and clients — to create standardized documentation, risk frameworks, and operational processes. She then helped drive broader adoption, demonstrating how cross‑functional execution is essential to move financial innovation from concept to scale. Current state of wealth infrastructure: Blythe shares her thoughts on how face-value UX improvements hide deep operational inefficiencies, leading to higher costs and reduced end-investor outcomes. AI's realistic role in wealth: She explains that AI can enhance wealth management by augmenting advisors — automating administrative tasks, accelerating onboarding, strengthening compliance, and improving advice quality. FNZ is well-positioned to leverage these gains because its extensive operational data across the wealth lifecycle can be used to train effective AI models. UK's Innovation and regulation: The conversation explores whether the UK can move faster post-EU to pursue tailored regulatory approaches — for example, digital identity, shared KYC/AML solutions. Political will is needed to prioritize these high-impact initiatives.    This episode is part of Innovators' Exchange, a series that explores the financial infrastructure and technology landscape. Tune in for a captivating exploration of key themes and opportunities for both professionals and retail investors, touching on AI's transformative potential in financial markets.  Subscribe for more on: Apple Podcasts | Spotify | Youtube | Podscribe 

Hanieh Khosroshahi is an independent design consultant, researcher, and community organizer working in pursuit of people and the planet. Her work spans multiple sectors from international development and public health to women's rights and technologies. She also worked in many geographies including Canada, Rwanda, Tanzania, Nepal, and Afghanistan.  She applies principles and methods of Human-centred Design, participatory research, and systems thinking to design, test, and scale innovative and impactful solutions, both online and offlineHer mission is to advance the health, opportunities, and rights of those on the margins, with a particular focus on youth and women in under-served and low-resource settings, from or with roots in the global majority. In this episode, Hanieh shares with us the journey that led her to English Literature, Visual Arts and Journalism to Human-Computer Interaction and UX design, to her work today at the intersection of design, social change and community organizing. She shared her perspective and work on participatory design and decolonizing practices, providing us with a sense of what designing for collective liberation and justice-centered futures looks like. Community, care and relationships are at the core of her work as a researcher, a designer and a social activist.To learn more about Hanieh's work, follow her on LinkedIn: https://www.linkedin.com/in/haniehk/and check her website: https://hanieh.me/Learn about Thousand&One, a global, feminist community co-founded by Hanieh. It supports Women of Colour to thrive in their personal and professional lives.: https://thousandone.orgCredits:Conception, host and production: Anne-Laure FayardSound design & Post-production: Valter GouveiaMusic & Art Work: Guilhem Tamisier

The New Appliance Ecosystem: Translating Value, Technology, and Human-Centric Design The modern appliance conversation has shifted beyond features and price into something far more consequential: value, usability, and human-centered design.  Designers, manufacturers, showrooms, and independent testing labs now operate as an interconnected ecosystem guiding consumers through increasingly complex decisions. The future of appliance specification belongs to those who can translate technology into meaningful, intuitive, lifestyle-driven solutions. Featuring insights from Nicole Papantoniou of the Good Housekeeping Institute, Jeff Sweet of Sub-Zero Group Inc., and Christa Mallinger of AJ Madison, this conversation explores how appliances have evolved from commodities into lifestyle infrastructure—and why education, not persuasion, defines the next era. KBIS Podcast Studio Resources: KBIS AJ Madison NKBA LUXE Interiors + Design SubZero, Wolf & Cove SKS | Signature Kitchen Suite Hearth & Home Technologies Kitchen365 Green Forrest Cabinetry Midea The appliance industry has entered a human-centric phase, where performance, intuitive use, and real lifestyle benefit outweigh raw features or price alone. Designers act as translators of lifestyle, manufacturers as problem-solvers, and showrooms as educators—collectively helping consumers navigate increasingly sophisticated choices. Panelists discussed the shift from feature-driven sales toward performance-driven value, emphasizing longevity, ease of use, and frictionless integration into daily life. They also explored the growing role of education, testing standards, showroom partnerships, and post-installation support in helping consumers fully realize the value of their investment. Technology remains central, but its success depends entirely on reducing friction—not adding novelty. The conversation revealed that the future of appliances lies not in more technology, but in better technology—technology that disappears into the experience. The Appliance Ecosystem Is Interdependent Designers interpret lifestyle and aesthetic needs. Manufacturers engineer performance-driven solutions. Showrooms educate and guide decision-making. Independent testing organizations validate performance and usability. Value Has Replaced Price as the Primary Decision Driver Consumers rarely regret investing more in appliances. Longevity, performance, and service support define value. Sustainability increasingly aligns with durability. Human-Centric Design Is the New Standard Appliances must be intuitive without relying on manuals. UX consistency across appliances improves adoption. Technology must solve real problems—not create new friction. Education Is More Important Than Selling Many consumers buy appliances only once every 10–15 years. Showrooms and testing labs bridge the knowledge gap. Post-installation education helps unlock full product potential. Appliances Are Expanding Beyond the Kitchen Refrigeration, coffee systems, and specialty appliances now appear throughout the home. Multi-kitchen and multi-generational design is driving specification complexity. Flexibility and modular integration are essential. Technology Adoption Depends on Familiarity and Trust Induction adoption accelerates when paired with familiar controls. Consumers embrace technology that feels intuitive and beneficial. Novelty alone does not guarantee long-term value. The modern appliance is no longer just a tool. It's infrastructure. At KBIS, where the industry gathers annually to define its future, a clear shift has emerged. Appliances are no longer judged solely by features or price, but by how effectively they integrate into human behavior. The question is no longer, “What does it do?” but rather, “What does it enable?” This shift has elevated the importance of collaboration across the appliance ecosystem. Designers serve as translators, interpreting the client's lifestyle into functional requirements. Manufacturers act as problem-solvers, engineering solutions grounded in real user needs. Showrooms and retailers bridge the gap between technology and understanding, while independent testing organizations validate claims and ensure products deliver on their promises. This ecosystem exists because appliance decisions have become more consequential—and more complex. Unlike consumer electronics, appliances are purchased infrequently. A homeowner may go fifteen years between purchases. During that time, the category evolves dramatically. Induction replaces gas. Steam ovens expand culinary capability. Refrigeration becomes modular, flexible, and architectural. Appliances no longer exist solely in kitchens, but in offices, bedrooms, outdoor spaces, and wellness areas. With that expansion comes responsibility. Technology must reduce friction, not create it. Christa, Nicole and Jeff all emphasized that human-centric design now drives product development. Appliances must be intuitive enough to operate without instruction, consistent enough to feel familiar, and purposeful enough to justify their presence. Technology for its own sake has limited value. Technology that removes mental load, improves performance, or enhances daily living defines the future. This is where education becomes critical. Showrooms no longer simply display products; they contextualize them. Independent testing organizations evaluate not only performance, but usability, cleanability, and intuitive function. Manufacturers increasingly provide post-installation support, recognizing that the real product experience begins after installation, not at purchase. Value, therefore, is no longer measured in features alone. It is measured in longevity. In reliability. In the confidence that a product will perform consistently over time. In the reduction of friction between intention and outcome. Perhaps most importantly, appliances have become emotional infrastructure. They support gathering, creativity, ritual, and identity. They enable the modern kitchen to function not just as a place of preparation, but as a center of living. The future of appliances will not be defined by how advanced they are. It will be defined by how invisible they become—seamlessly enabling life without demanding attention. And those who understand that distinction—designers, manufacturers, and educators alike—will define the next generation of the built environment.

Career maximalism is a mistake that many high achieving professionals make. When you care too much about your job, you can actually become worse at it. In this video, learn what Career Maximalism is, and why this behavior is everywhere, often rewarded, and quietly working against you.Career maximalism is when your job becomes a major source of your identity and your emotional state rises and falls based on how work is going. It often looks like being a great employee, but there's a tipping point where it clouds your judgment, slows your decisions, and makes everything heavier than it needs to be. Sarah Doody discusses the difference between commitment and emotional over-identification, shares a Reddit thread about treating UX as a job instead of an identity, and gives three practical tips for caring deeply without making work who you are.3 tips for avoiding the trap of Career Maximalism: 1) Build proof of your self-worth outside your job with physical challenges, creative projects, community, etc.2) Practice emotional detachment without disengagement. Detachment isn't apathy, it's clarity.3) Set clear standards and boundaries. When expectations are vague, everything becomes emotional.Resources & Links Mentioned: Reddit thread about treating UX as a job instead of an identity

In this episode, the Metrics Brothers, Dave "CAC" Kellogg and Ray "Growth" Rike dive deep into the ICONIQ State of AI: Bi-Annual Snapshot Report. Published in January 2026, this 44-page report summarizes insights from ~300 software executives on the front lines of building and scaling AI products.Ray and Dave explore a market transition from experimental model races to the challenge of building durable, economically sound products. Key discussions in this episode include:Differentiation Beyond the Model: Why 69% of builders are focusing on vertical AI applications and why 49% cite the application layer (UX and workflows) as their primary competitive edge over the underlying model.The Gross Margin "U-Curve": A look at the shifting economics of AI, where aggregated gross margins are projected to climb to 52% by 2026, even as inference and infrastructure costs remain significant hurdles.Pricing Evolution: The rise of outcome and usage-based pricing, with only 23% of companies still relying on seat-based models as customer demand shifts toward value-aligned monetization.AI as an Internal Force Multiplier: How R&D teams are leading internal adoption, with 83% of companies now measuring success through productivity gains and 59% through direct cost savings.Whether you are a CEO or CFO navigating AI product gross margin concerns or a GTM leader rethinking your proof-of-concept strategy, this episode provides the benchmarks you need to understand the "new phase of maturity" in the AI market.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Chad and Simon are Back to discuss all things life and disability.Hear about Chads experience in the 5th annual Blind Gamers JamBig conversation the starting of a discussion into can Schools become trully inclusive. What challenges will the new UK white paper and SEND reform bring to young people. How does this relate to the US system.Let us know your thoughts and comments of your experiences.What would be Simon's last meal and how would this compare to Chads US appetite?See details for Chad's teams game below. We proudly present: Delvers Folly: https://joozey.itch.io/delversfolly-wipPassword: manticoreDelve into a dungeon that is cursed by a strange creature. Each day, the rooms of this dungeon are never quite the same. Open doors, draft a room, and explore the dungeon. Can you solve the mystery of the Suspicious Alcove (the only puzzle we have so far)?Available for Mac, Windows, and Linux. Mac has not been tested, anyone with a Mac that can try it out?Intended to be playable with keyboard or controller, screenreader or TTS.We would love to hear what did or did not work well for you regarding UX, controls, sounds and music, and the mechanics.Any feedback welcome! Thank you!!

Mahnaz has lived with volatility, uncertainty, complexity, and ambiguity in ways most product teams never will. In this episode, we talk about what happens when VUCA isn't theoretical, how to avoid becoming an order taker, and how courage, empathy, and initiative can reshape your role as a designer.What if the volatility, uncertainty, complexity, and ambiguity you're facing at work feel overwhelming only because you've never had to live through it in your everyday life?I throw the word VUCA around like it's a trendy framework. Volatility. Uncertainty. Complexity. Ambiguity. But for Mahnaz Hajesmaeili, those aren't abstract concepts; they're lived experience.Originally from Iran, before becoming a product designer, she built a life in China, knowing she could never fully belong there. When COVID hit, borders closed, savings ran out, and the life she had carefully constructed disappeared almost overnight. She returned to Iran, started over, taught herself UX, and eventually rebuilt her career in the United States.That's not “roadmap volatility.” That's real volatility.This week, I chat with Mahnaz to explore how living through that level of instability reshaped her approach to work. Why rejected designs don't shake her. Why unclear strategy doesn't rattle her and why she doesn't default to being an order taker.If you've ever felt overwhelmed by shifting priorities or frustrated by leaders who “don't know what they want,” this episode offers perspective—and practical lessons.Give it a listen. It might change how you define uncertainty.Helpful Links:• Connect with Mahnaz on LinkedIn

The PodRocket panel is back for their February roundup! Paige, Paul, Jack and Noel dig into the biggest stories reshaping the web development landscape right now. The panel kicks off with a deep dive into OpenClaw, it's transition to a foundation, and Peter Steinberger joining OpenAI. Is a foundation the right long-term home for fast-moving AI projects? And what does the continuing flow of talent into big AI labs mean for the open source ecosystem? From there, the conversation shifts to the browser's changing role in the web, how the lines between native and web experiences continue to blur, and what that means for developers building for the future. The panel also tackles growing pressures on open source sustainability and the widening gap between developers who are deeply integrating AI agents into their workflows and everyone else who hasn't even heard of these tools yet. Resources TechCrunch: OpenClaw creator Peter Steinberger joins OpenAI: https://techcrunch.com/2026/02/15/openclaw-creator-peter-steinberger-joins-openai Interop 2026 report and dashboard: https://web.dev/blog/interop-2026 Google Chrome announcement on Gemini auto-browsing: https://blog.google/products-and-platforms/products/chrome/gemini-3-auto-browse/ What to expect for open source in 2026, Github blog: https://github.blog/open-source/maintainers/what-to-expect-for-open-source-in-2026/?ref=thecodebrew.net We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Fill out our listener survey! https://t.co/oKVAEXipxu Let us know by sending an email to our producer, Elizabeth, at elizabeth.becz@logrocket.com, or tweet at us at PodRocketPod. Check out our newsletter! https://blog.logrocket.com/the-replay-newsletter/ Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form, and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understanding where your users are struggling by trying it for free at LogRocket.com. Try LogRocket for free today. Chapters 00:00 Intro and Panel Welcome 01:00 What Is OpenClaw 03:00 Moving to a Foundation and OpenAI Concerns 08:00 AI Security Risks and Malware Issues 13:00 AI Haves vs Have Nots 18:00 Evaluating Open Source AI Stability 26:00 Browser Interop 2026 and Compatibility Gaps 31:00 Designing for AI Agents First 37:00 AI Search vs Google 42:00 Gemini in Chrome and Browser Lock In 49:00 Hot Takes 55:00 AI Burnout and Developer Mental HealthSpecial Guest: Jack Herrington.

SEO isn't dead. It's evolving and the businesses that treat it like a shortcut are the ones getting left behind.In this episode of Uncomplicate It, I sit down with Amber Goetz, founder of Active Media launched in 2005, creator of SEO Sidekick, and yes… former professional stunt driver, to talk about what high performance actually looks like in marketing.Amber has helped build 500 plus websites, scale brands from 0 to 100K monthly visitors, and drive over 10 million in organic revenue. Her approach is refreshingly no fluff. Trust your gut. Follow the data. Stop chasing whatever the internet is yelling about this week.We cover:- How Amber went from Hollywood stunt driving to building an SEO powerhouse - Why “do this now or you'll miss out” is the biggest marketing fluff today - The anti fluff formula and why it starts with clear buyer personas - Why most websites repel customers including bad UX, slow speed, and unclear offers - The fastest conversion win by checking your site on mobile and fixing what is above the fold - What actually improves load time from hosting to servers to bloated code - Why AI overviews do not replace SEO and how EEAT plays a role - The trap to avoid in 2025 and 2026 with overnight SEO appsKey Takeaways:- Real marketing is strategic, not reactive - Data is how you stop wasting time and budget - SEO is a long game but the right system compounds - Your website is never done, it is a working documentConnect with Amber- Active Media - www.theactivemedia.com/- Linkedin - www.linkedin.com/in/ambergoetz9/Follow Us:

What if the future of UX isn't about better interfaces — but about moving beyond interfaces altogether?In this episode, I'm joined by Morten Rand-Hendriksen, Principal Instructor at LinkedIn Learning, to talk about where design is really heading in the age of AI.Morten has a background in web development, UX, and interaction design, and over the last years has gone deep into AI and product thinking. We've met at conferences like Future Product Days and had several conversations before — and every time, he brings a perspective that challenges assumptions in the best possible way.This episode is not about tools.It's about responsibility, agency, power shifts — and what it really means to be a designer today.We talk about:• Why technology is always a choice — even when it feels inevitable• What happens when users bypass interfaces completely• Why designing for screens might already be outdated• How AI agents change the balance between automation and control• Why service design is becoming more important than ever• Why designers now have an advantage over engineers• And what junior and mid-level designers should focus on todayOne of my favorite moments:“You didn't become a designer to move pixels. You became a designer because you saw how the world could be better.”This conversation goes deep. It touches capitalism, automation, AI agents, product moats disappearing, and why the future belongs to people who understand systems — not just surfaces.If you're feeling excited, overwhelmed, curious, or slightly uncomfortable about where AI is taking design — this episode is for you.Find Morten:LinkedinMorten's Ted talk AI for Designers: 5-week Bootcamp

If you work in UX, you've probably heard the terms lean, Agile, and MVP more times than you can count. But knowing the terms doesn't mean knowing how to make them work. In this episode, Laura Klein, Principal Experience Specialist at NN/G, joins Therese Fessenden to talk about what Lean UX was really meant to accomplish — and how teams today can apply its principles without falling into common traps.Listen as they discuss how Lean UX came about, the skill of zooming between product vision and interaction details, and why growing companies struggle to balance speed and consistency. Whether you're working at a startup or inside a large enterprise, this episode offers a grounded look at how to design thoughtfully in fast-moving environments.We're also excited to have Laura join as the newest co-host of the NN/G UX Podcast. And many congratulations to the Fessenden family as they welcome a new addition to their family.About Laura Klein | Bio | Linkedin | Bluesky | Usersknow.comWhat is Wrong With UX (Podcast)Build Better Products (Book)UX for Lean Startups (Book)NN/G Live Online Courses Taught by LauraLean UX and AgileProduct & UX: Building Partnerships for Better OutcomesAll Our Live CoursesFree NN/G Articles & VideosLean UX & Agile: Study GuideLean UX & Agile GlossaryWhat is Lean UX?Accounting for User Research in AgileWhy Organizations Don't Do User Research and How to Change ThatWhy Most Product Teams Aren't Really EmpoweredDon't forget to like and subscribe! ❤️Follow Us On:NewsletterInstagramThreadsLinkedinBlueskyX

In this week's episode, Darren begins a journey through what he refers to as the four pillars of UX by explaining the connection between UX maturity and heuristics and the expectations we should have based on a practitioner's UX maturity level. REMINDER: Video is available for this episode via select resources. #ux #podcasts #cxofmradio #cxofm #realuxtalk #worldofux #worldoux Bookmark the new World of UX website at https://www.worldoux.com. Visit the UX Uncensored blog at https://uxuncensored.medium.com. Get your specialized UX merchandise at https://www.kaizentees.com.

Corinna Stukan, Product Leader and Founder of Fintech marketplace Bizzy, lays out practical advice for connecting your product roadmap to business goals. She explains how a metrics one-pager aligns day-to-day product decisions with company goals, why understanding whether your business is in growth, acquisition or cost-control mode should shape every prioritisation call, and how to frame initiatives so stakeholders see commercial impact, not just better UX.Chapters4:00 — Why product people should care about business acumen6:01 — Organisational causes of weak commercial context for PMs8:10 — What business acumen means in practice9:10 — Wake-up story: prioritisation shifted after asking the CEO about revenue drivers11:05 — Misalignment: company goals vs team OKRs12:13 — How to run the metrics one-pager and link product to business goals14:37 — Strategy: where we are, where we're going, how we'll get there15:03 — Encouraging ideas while setting business context17:01 — Running collaborative bets before creating the roadmap19:20 — Communicating value: turn “better onboarding” into business impact22:08 — Avoiding over-attribution and internal attribution fights23:05 — Example: marketing's 12 touchpoints and joint contribution to acquisition24:26 — Practising stakeholder storytelling; where LLMs help and don't29:17 — Presentation craft: fewer slides, start with numbers, end with actions31:03 — Using LLMs for synthesis, not hOur HostsLily Smith enjoys working as a consultant product manager with early-stage and growing startups and as a mentor to other product managers. She's currently Chief Product Officer at BBC Maestro, and has spent 13 years in the tech industry working with startups in the SaaS and mobile space. She's worked on a diverse range of products – leading the product teams through discovery, prototyping, testing and delivery. Lily also founded ProductTank Bristol and runs ProductCamp in Bristol and Bath. Randy Silver is a Leadership & Product Coach and Consultant. He gets teams unstuck, helping you to supercharge your results. Randy's held interim CPO and Leadership roles at scale-ups and SMEs, advised start-ups, and been Head of Product at HSBC and Sainsbury's. He participated in Silicon Valley Product Group's Coaching the Coaches forum, and speaks frequently at conferences and events. You can join one of communities he runs for CPOs (CPO Circles), Product Managers (Product In the {A}ether) and Product Coaches. He's the author of What Do We Do Now? A Product Manager's Guide to Strategy in the Time of COVID-19. A recovering music journalist and editor, Randy also launched Amazon's music stores in the US & UK.

Bo Hines is the CEO of Tether US and a former White House crypto advisor who helped shape U.S. digital-asset policy during a critical moment for the industry. This conversation was recorded live at Bitcoin Investor Week in New York. In this conversation, we discuss Bo's work in the White House on crypto policy, including the Strategic Bitcoin Reserve, the GENIUS Act, and the push for regulatory clarity. We also cover stablecoin adoption, why UX matters more than yield, how Tether is connecting global markets to U.S. capital, and why stablecoins could be the on-ramp to the next phase of bitcoin and financial infrastructure.=======================Simple Mining makes Bitcoin mining simple and accessible for everyone. We offer a premium white glove hosting service, helping you maximize the profitability of Bitcoin mining. For more information on Simple Mining or to get started mining Bitcoin, visit https://www.simplemining.io/=======================Arch Public is an agentic trading platform that automates the buying and selling of your preferred crypto strategies. Sign up today at https://www.archpublic.com and start your automated trading strategy for free. No catch. No hidden fees. Just smarter trading.=======================0:00 - Intro0:19 - White House crypto policy & Bo Hines' role2:52 - How important is the Clarity Act?4:10 - Tether: scale, growth & global impact10:49 - Stablecoin yield debate12:37 - Financial access, wallets & the unbanked14:19 - Tether's relationship with Bitcoin15:46 - Reserves, transparency & risk17:24 - Interoperability & the future of stablecoins

Why do 85% of AI projects fail, and how can product leaders beat the odds? In this episode of the Product Talk podcast, host Denise Hemke sits down with Greg Nudelman, product and UX leader and creator of the Snowball Sprint, to unpack why AI initiatives break down and what it really takes to build AI products that succeed. Drawing on real-world examples from cybersecurity, enterprise AI, and IoT, Greg shares practical frameworks for framing the right use cases, thin-slicing real data, escaping POC purgatory, and redefining success beyond accuracy. A must-listen for product managers and leaders navigating AI-driven product strategy.

The idea of career minimalism sounds healthy. But this trending philosophy of your job being a tool, not your identity (especially popular with Gen Z) could be quietly weakening your career if you're not careful.In this episode, Sarah Doody breaks down what career minimalism actually is, why it's gained so much momentum (spoiler: burnout, broken loyalty, and unpredictable layoffs), and the hidden risk most career minimalists never talk about. The real danger isn't doing less at work — it's what you're building (or not building) while you're there.Sarah also discusses the concept of "Portable Equity" and shares three practical tips so you can protect your work-life balance without accidentally making yourself less employable.Timestamps:0:00 Introduction0:58 What is career minimalism?3:24 How did we get here? Burnout, hustle culture, and broken loyalty4:41 Where career minimalism starts to get tricky6:51 The hidden assumption of career minimalists7:50 Why career minimalists often end up job hopping10:16 The reframe: building portable equity11:24 Three practical tips for career minimalists11:45 Tip 1: Optimize for portability, not just balance12:34 Tip 2: Know the difference between being useful and being valuable13:59 Tip 3: Treat every role as temporary16:35 Always be seeking — the career version of "always be closing"17:36 Wrap up

On Your World of Creativity, we travel around the world talking with creative practitioners who turn ideas into impact. In this special roundtable episode, Mark brings together leaders from film, animation, hospitality, consumer brands, immersive experiences, and big-tech UX to explore one powerful theme:Teamwork.When creative outcomes depend on dozens—or even hundreds—of contributors, how do you align vision, manage complexity, and still leave room for magic?Today's PanelistsMichael Robinson — Hotel & Hospitality Operations LeaderDiego Pulido — Lead UX Designer, Amazon (formerly Google, Walmart, Adobe, JPMorganChase)Matt McLean — Organic Consumer Juice Brand FounderTom Bairstow — Event, Concert Production & Immersive Visual Experiences Rich Magallanes — Children's & Animated Content ProducerSteven Puri — Focus app creator, ex-studio exec/producer Fox, DreamWorks, SonyTogether, they share real-world lessons from film sets, animation studios, hospitality teams, live events, consumer brands, and product design at scale.In This Episode, We Explore:Creativity as a Team Sport. What great collaboration actually looks like across industries—and why creativity doesn't happen in isolation.Aligning Vision Across Many Contributors. How leaders communicate creative direction clearly when working with writers, designers, engineers, performers, vendors, and operational teams.Conflict, Constraints & Creative Breakthroughs. How budget limits, timelines, technical requirements, and differing opinions can either block creativity—or unlock it.Leadership in Collaborative Environments. What it means to lead when you're not the only decision-maker, how to build trust quickly, and why delegation is essential for scale.Practical Takeaways for Better Collaboration. From film crews to UX teams, each panelist shares what actually helps teams work better together—and what listeners can apply immediately.Final Lightning RoundEach panelist shares one simple action listeners can take this week to become a better collaborator.Huge thanks to our panelists. Be sure to connect with them.https://www.linkedin.com/in/michael-robinson-a6985735/https://www.linkedin.com/in/diegopulido/https://www.linkedin.com/in/matt-mclean-5507733/https://www.linkedin.com/in/tombairstownorthhouse/

This Week In Startups is made possible by:Gusto - Try Gusto today and get 3 months free at http://uber.com/ai-solutionsCrusoe Cloud - Reserve your capacity for the latest GPU's at http://uber.com/ai-solutionsUber AI Solutions - Book a demo today at http://uber.com/ai-solutions*Today's show: It's a packed show! We've got YouTuber and Openclaw enthusiast Matthew Berman, Ryan Yaneli, founder of Nextvisit, and Jason Grad, founder of Massive! We're all in on Openclaw, but we have no doubts there's still room in the market for a GIANT Openclaw consumer app to shift the paradigm. What will that look like? Will it be an app? Will it be baked into the iPhone? Let's explore!**Timestamps:* 00:00 Intro02:04 Why Matthew thinks Openclaw is not ready yet to be brought to the consumer04:45 Jason doesn't want hundreds of different apps, and thousands of tabs05:45 Why Ryan sees open claw giving consumers access to opportunities they couldn't have gotten to otherwise.07:02 Only 10% of people are technical enough to install openclaw08:16 Would Openclaw be better off as an app?08:27 *Gusto*. Check out the online payroll and benefits experts with software built specifically for small business and startups. Try Gusto today and get three months FREE at [Uber.com/twist](http://uber.com/ai-solutions)00:10:52 The killer use case that could bring Openclaw to the consumer00:12:13 Why Meta acquired Manus.00:15:13 How Ryan uses Openclaw in his personal life00:18:44 *Crusoe Cloud*: Crusoe is the AI factory company. Reliable infrastructure and expert support. Visit crusoe.ai/savings to reserve your capacity for the latest GPUs today.00:23:24 What Jason's “Clawpod” does00:24:38 Jason demos his Openclaw workflow00:28:23 *Uber AI Solutions -* Your trusted partner to get AI to work in the real world. Book a demo with them TODAY at http://uber.com/ai-solutions00:30:04 How Matt used Openclaw to figure out he's been having stomach issues00:32:27 What will be the ultimate UX for AI?00:38:53 Anthropic has patched the ability to use Openclaw through its pro plan!00:42:20 Matt and Jason hope for a multi-model future — but we haven't made progress!00:52:21 Jason has skepticisms about the Openclaw foundation00:52:59 Ryan predicts a new Openclaw fork coming from the shadows!00:54:21 Peter Steinberger is going to OpenAI, NOT to work with Openclaw… Will he “orphan” openclaw?00:58:19 does raspberry AI stand a chance against Apple?*Subscribe to the TWiST500 newsletter: https://ticker.thisweekinstartups.com/Check out the TWIST500: https://www.twist500.comSubscribe to This Week in Startups on Apple: https://rb.gy/v19fcp*Follow Lon:X: https://x.com/lons*Follow Alex:X: https://x.com/alexLinkedIn: ⁠https://www.linkedin.com/in/alexwilhelm*Follow Jason:X: https://twitter.com/JasonLinkedIn: https://www.linkedin.com/in/jasoncalacanis*Thank you to our partners:*Gusto*. Check out the online payroll and benefits experts with software built specifically for small business and startups. Try Gusto today and get three months FREE at [Uber.com/twist](http://uber.com/ai-solutions)*Crusoe Cloud*: Crusoe is the AI factory company. Reliable infrastructure and expert support. Visit [crusoe.ai/savings] to reserve your capacity for the latest GPUs today.*Uber AI Solutions -* Your trusted partner to get AI to work in the real world. Book a demo with them TODAY at [Uber.com/twist](http://uber.com/ai-solutions)Check out all our partner offers: https://partners.launch.co/*Check out Jason's suite of newsletters: https://substack.com/@calacanis*Follow TWiST:Twitter: https://twitter.com/TWiStartupsYouTube: https://www.youtube.com/thisweekinInstagram: [https://www.instagram.com/thisweekinstartups](https://www.instagram.com/thisweekinstartups/)TikTok: https://www.tiktok.com/@thisweekinstartupsSubstack: [https://twistartups.substack.com](https://twistartups.substack.com/)