Podcasts about JavaScript

Taylor Otwell, creator of Laravel and CEO of Laravel LLC, joins Robby to reflect on his 14-year journey building and maintaining one of the most popular web frameworks in the world. From its PHP 5.3 origins to a full-time business with a 70-person team, Taylor shares what he's learned about code maintainability, developer experience, and what it means to evolve without overcomplicating things.He discusses the importance of simplicity in software design, why sticking to framework conventions leads to better long-term outcomes, and how his minimalist mindset continues to shape Laravel today. Taylor also opens up about the moment he felt out of ideas, how Laravel's 2024 funding round marked a new chapter, and what it's like to hand off more responsibility while staying involved in the open source core.Episode Highlights[00:01:07] Taylor's Definition of Maintainable Software  Simplicity, understandability, and confidence in making changes are key themes in Taylor's approach to longevity in software.[00:02:13] Kenny vs. the Terminator: A Metaphor for Code  Why Taylor believes software should be disposable and adaptable, not rigid and overbuilt.[00:05:39] Laravel's Unexpected Traction  Taylor shares the early days of Laravel and the moment he realized the project had legs.[00:10:30] Who Laravel Is Built For  Taylor talks about designing for the “average developer” and balancing his own preferences with those of a broader community.[00:14:50] Curating a Growing Project—Solo  Despite Laravel's scale, Taylor remains the sole curator of the open source core and explains why that hasn't changed (yet).[00:18:00] From Scripts to Business  How Laravel's first commercial product came out of a personal need—and pushed Taylor to go full time.[00:20:00] Making Breaking Changes  Taylor explains Laravel's evolution and why he now tries to avoid breaking backward compatibility.[00:25:00] Stick to the Conventions  The Laravel apps that age best are the ones that don't get too clever, Taylor says—because the clever dev always moves on.[00:27:00] Recognizing “Cleverness” as a Smell  Advice for developers who may unknowingly be over-engineering their way into future technical debt.[00:30:00] Making Decisions by Comparing Real Code  Taylor explains why he always brings discussions back to reality by looking at code side-by-side.[00:34:00] Dependency Injection vs. Facades  Why most Laravel developers stick with facades, and how architectural trends have changed.[00:41:00] Laravel's Evolution Around Static Analysis  Taylor talks about embracing PHP's maturing type system while staying true to the dynamic roots of the framework.[00:43:00] A Shift in Laravel's Testing Culture  How Adam Wathan's course reshaped the community's approach to feature testing in Laravel apps.[00:48:09] What Keeps Laravel Interesting Now  Taylor reflects on transitioning from solving his own problems to empowering a larger team—and why that's the new challenge.Resources & LinksLaravelLaravel ChangelogTaylor on X (Twitter)Taylor on BlueskyElements of Style – William Strunk Jr.Adam Wathan's “Test-Driven Laravel” courseThanks to Our Sponsor!Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and other frameworks.It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications.Keep your coding cool and error-free, one line at a time! Use the code maintainable to get a 10% discount for your first year. Check them out! Subscribe to Maintainable on:Apple PodcastsSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.

Maestro CEO Leland Takamine joins Jamon and Robin to discuss Maestro's growth, new tools like Studio Desktop and cloud testing, and why reliability matters for automated testing. Show NotesMaestro's websiteRNR 262 - Maestro: The App-solute Solution for Mobile UI TestingFlashlight Maestro DocsConnect With Us!Leland Takamine: @lelandtakamineJamon Holmgren: @jamonholmgrenRobin Heinze: @robinheinzeReact Native Radio: @ReactNativeRdioThis episode is brought to you by Infinite Red!Infinite Red is an expert React Native consultancy located in the USA. With nearly a decade of React Native experience and deep roots in the React Native community (hosts of Chain React and the React Native Newsletter, core React Native contributors, creators of Ignite and Reactotron, and much, much more), Infinite Red is the best choice for helping you build and deploy your next React Native app.

Optimize your website's performance with lazy loading techniques. In this episode, John Mueller  and Martin Splitt discuss lazy loading, and its SEO implications. Find out how lazy loading affects indexing, ranking, and Core Web Vitals. Whether you're using native lazy loading or custom JavaScript libraries, this episode provides insights for developers on how to enhance website speed and user experience. Resources:  Episode transcript → https://goo.gle/sotr098-transcript  Chapters:  0:00 - Introduction  0:43 - What is lazy loading?  1:57 - HTTP chunking  3:13 - Primary drivers behind lazy loading  6:19 - Why not default lazy load all images?  8:29 - Lazy loading and SEO  8:39 - Impact to Core Web Vitals  9:17 - Largest contentful paint  9:58 - Affecting indexing and ranking  11:30 - Custom libraries for lazy loading 14:17 - How to recognize a problem 15:25 - Practical point of view  16:52 - Infinite scroll vs. lazy loading  19:31 - Lazy loading videos  20:51 - Small images and decorative images  23:16 - Where to chat about lazy loading images  23:55 - Outro  Listen to more Search Off the Record → https://goo.gle/sotr-yt Subscribe to Google Search Channel → https://goo.gle/SearchCentral Search Off the Record is a podcast series that takes you behind the scenes of Google Search with the Search Relations team. #SOTRpodcast #SEO Speaker: Martin Splitt, John Muelle, Martin Splitt Products Mentioned: Search Console

Morgante Pell is the Founder of Grit, the developer tool that puts software maintenance on autopilot and was acquired by Honeycomb in April 2025. In this episode, we dig into:The Grit product and how LLMs have made software maintenance much more efficient Launching GritQL - Grit's embedded query language for searching and transforming codeTheir early focus on the JavaScript community The motivation for Grit to open sourceHow AI generated code has put pressure on software maintenanceWhere new problems have been created by AI-generated code The acquisition by Honeycomb - motivation, integration, and how the deal happened

Foundations of Amateur Radio Recently I discussed the idea of listening to the radio spectrum across the internet for the purposes of getting signal into your shack when radios, or in my case, antennas are causing you challenges. I continued to explore and discovered a project by Jacobo EA1ITI, called "radioreceiver". Behind that unassuming name lies a tool born in 2014, that allows you to plug an RTL-SDR dongle into your computer, open up your web-browser, and listen to the radio signals that your dongle can receive. In case you're unfamiliar, an RTL-SDR dongle is a small USB device, looks a lot like a USB thumb drive, jump drive, data stick or flash drive, basically a hunk of plastic with a USB connector on it. An RTL-SDR dongle generally also has some form of antenna connector. It's typically sold as a digital radio and digital television receiver, but websites like rtl-sdr.com sell purpose built ones. They can be found starting at about $15. I realise that this is using a local receiver, with a local antenna, but it's inside a web browser, which is half of what I expected. When you hit the play button in the bottom of the screen, you'll be prompted by your web browser to give permission to access your RTL-SDR dongle and the fun starts. You'll see a live waterfall, hear audio, and have the ability to tune to any frequency you can reach. Depending on your dongle, typically somewhere between 500 kHz and 1.76 GHz. The application consists of seven files, a total of 352 kilobytes that you can store on any web server and run, with one caveat, in order for your web browser to talk to your dongle, it needs to be served using HTTPS. Jacobo has set-up radio.ea1iti.es and I've set-up sdr.vk6flab.com, both showing the same tool. You'll find the code on my VK6FLAB GitHub repository, and of course on Jacobo's. There are some things you need to know. You will need to use a web browser that supports WebUSB, currently that's Chrome, Edge, Opera and several others, sorry, Safari and Firefox don't .. perhaps it's time to talk to Apple and Mozilla. All is explained if you click on the little question mark at the bottom of the screen, it will even tell you if the browser you're using to read the help is compatible or not. If you have an Android phone, you can run this tool too, although you will need to find a way to connect your dongle to your phone. I'm currently limited in my ability to test this and you may need to install some drivers on Windows and Linux, but MacOS and presumably Android, works out of the box. The software also supports offline operation, so you can load it as a Progressive Web App, or PWA, and use it in the field away from the internet. Did I mention that all the decoding is happening inside the web browser, so you can see which code is doing what .. and before you ask, yes, it's minimised in the browser, which you can make into human readable code, but when you look at the source, it shows precisely what is happening, all written in Node.js, TypeScript and JavaScript. It supports CW, SSB, AM, Narrow and Wideband FM and decodes stereo, something which none of my amateur radios do. You might be able to tell that I'm excited. It's because this is providing the basic functionality of a radio inside a web browser, and I didn't need to install it to get started. On the Macintosh I tested this on, I literally opened the web page, plugged in a dongle and hit play. Just so we're clear, just because this is using a web page on a web server, you accessing it will only give you access to your radio not mine. This of course opens the doors to all manner of other fun stuff which I'm expecting to play with for the next little while, and yes, this is also Bald Yak adjacent, I'm aware. In the meantime, you can play with this right now, sdr.vk6flab.com is the place to go. Word of warning, it's addictive and easy to forget it's a radio with an antenna plugged into your computer, so take precautions when electrical storms are about. Look forward to hearing what you discover. I'm Onno VK6FLAB

In this episode of JavaScript Jabber, we sit down with Vinicius Dallacqua, a seasoned software engineer with a passion for performance and developer tooling. Vinicius shares his journey from coding in central Brazil with limited connectivity to building cutting-edge tools like PerfLab and PerfAgent. We dive into the intersection of AI and DevTools, exploring how artificial intelligence is transforming performance debugging, web development workflows, and even the future of browsers.We also tackle the big questions: How do developers avoid bias when building in high-performance environments? What role will agentic browsers play in the evolution of the web? And how can AI-powered DevTools lower the barrier for developers intimidated by performance profiling? If you're curious about the future of frontend performance, DevTools, and AI-driven development, this conversation is packed with insights.Links & ResourcesPerfLab – Performance tooling platformPerfAgent – AI-powered DevTools assistantVinicius Dallacqua on X (Twitter)Paul Kinlan's AI Focus – Essays on AI and the webPerfNow Conference – Leading performance conference in AmsterdamBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Sacha Greif, creator of the State of Devs 2025 survey, joins PodRocket to share insights on developer life beyond the code. We talk about sleep habits, mental health, job titles, workplace culture, and shifting values across regions. Learn why "engineer" titles often pay more, what developers worldwide think about Elon Musk, and how trends differ by country, gender, and company size. Links Website: https://sachagreif.com X: https://x.com/sachagreif Github: https://github.com/sachag LinkedIn: https://www.linkedin.com/in/sacha-greif-03b9a3255 Resources State of Devs 2025: https://2025.stateofdevs.com/en-US Chapters 00:00 Intro & State of Devs 2025 Overview 00:10 Why Developer Life Is More Than Code 00:39 From State of JavaScript to State of Devs 01:08 Expanding Surveys: AI & React Ecosystem 01:21 Developer Life Beyond Code 02:01 Designing Questions That Go Beyond Tech 02:17 Sleep, Health, and Hobbies in Developer Life 02:32 Reaching Underrepresented Groups in Tech Surveys 03:30 Women's Participation Rises to 15% 04:00 Poor Sleep Tops Developer Health Issues 05:15 Gender Differences in Workplace Conflict Response 06:00 Average Developer Sleep: 6.9 Hours 07:00 What Sleep Data Reveals About Developer Life 09:15 Engineer vs Developer: Salary Gap Explained 11:00 Company Size, Job Titles, and Pay Differences 13:00 Inclusivity, Open Source, and Community Spaces 15:15 How Age Impacts Discrimination in Tech 17:00 Culture Shifts and Values in the Tech Industry 18:45 Younger vs Older Devs on Free Speech and Politics 20:30 Future Survey Topics: Leaders, Politics & Perception 22:45 What the Data Reveals About Developer Diversity 25:15 Using the Survey API to Explore Your Own Insights 26:30 Fun Data Point: Minecraft Players & Relationships 27:30 Predicting the Future of Developer Happiness 30:15 Closing Thoughts & How to Join Next Year's Survey 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, Em, at emily.kochanek@logrocket.com (mailto:emily.kochanek@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), 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. (https://logrocket.com/signup/?pdr) Special Guest: Sacha Greif.

Show DescriptionWhat helps you remember a person's name, thinking about background coding agents, is AI for append only mode, what are MCPs and how should I think about them, what has been working for more than a month not just the last two days, and coming up with an RSS starter pack riffing off Molly White's article on using RSS. Listen on Website →Links Visual Studio Code - YouTube Cursor - The AI Code Editor Visual Studio Code - Code Editing. Redefined A single data and AI development environment - Amazon SageMaker Unified Studio - AWS Jules - An Asynchronous Coding Agent Curate your own newspaper with RSS Chris Coyier – Web craftsman, blogger, author, speaker. The Homepage of Dave Rupert - daverupert.com Chris Coyier Molly White The Verge Adactio: Jeremy Keith Adactio: Links Jim Nielsen's Blog Home | Rach Smith's digital garden Maggie Appleton Naz Hamid kottke.org - home of fine hypertext products live laugh blog | hi, i'm jenn schiffer and this is my lifestyle blog Sharing what we learn about the responsive web – Cloud Four web.dev Blog | WebKit Home - Microsoft Edge Blog Blog • Lea Verou Frontend Masters Blog – Helping Your Journey to Senior Developer ui.dev | JavaScript, but fun. Welcome to Ethan Marcotte's website — Ethan Marcotte Josh Collinsworth | Blog everything changes Writing – Eric Bailey Balatro University - YouTube Sponsors

Evan Bacon and James Ide from Expo join us as guests for the second part of React Native Web vs. React Strict DOM!Connect With Us!Evan Bacon: @BaconbrixJames Ide: @JIJamon Holmgren: @jamonholmgrenRobin Heinze: @robinheinzeMazen Chami: @mazenchamiReact Native Radio: @ReactNativeRdioThis episode is brought to you by Infinite Red!Infinite Red is an expert React Native consultancy located in the USA. With nearly a decade of React Native experience and deep roots in the React Native community (hosts of Chain React and the React Native Newsletter, core React Native contributors, creators of Ignite and Reactotron, and much, much more), Infinite Red is the best choice for helping you build and deploy your next React Native app.

This week we talk to Bereket Engida (Beka) the creator of better-auth. Better-auth is an extensible, open source authentication library that's taking the JavaScript community by storm.- https://www.beka.et/- https://better-auth.comBecome a paid subscriber our patreon, spotify, or apple podcasts to help support the podcast. https://www.patreon.com/devtoolsfmhttps://podcasters.spotify.com/pod/show/devtoolsfm/subscribehttps://podcasts.apple.com/us/podcast/devtools-fm/id1566647758https://www.youtube.com/@devtoolsfm/membership

Smack this link and lmk!https://docs.google.com/forms/d/e/1FAIpQLSertMqleaBZuhQXKGmO9ESb4GB15bpGQ9VHAXDwjRfKYY98QQ/viewform

An airhacks.fm conversation with Adam Dudczak (@maneo) about: early programming experiences with Commodore 64 and Pascal, demo scene participation through postal mail swapping of floppy disks, writing assembly code for 64K intros with music and graphics, developing digital library systems using Java Servlets and Hibernate, involvement in reactivating Poznan Java User Group in 2007, NetBeans Dream Team and NetBeans World Tour, appearing on Polish breakfast TV to discuss Java programming, working at Supercomputing Center on cultural heritage digitization projects, transitioning to EJB 3.0 and Glassfish based on conference inspirations, joining allegro in 2014 to rewrite search functionality from PHP to Java microservices, handling 14K requests per second with Solr-based search infrastructure, migrating big data stack from on-premise Hadoop to Google Cloud Platform, developing private banking application for children using Spring and Hibernate then migrating to Google Sheets with 70 lines of JavaScript, discussing public cloud cost optimization strategies, comparing AWS Lambda versus EC2 versus container services based on traffic patterns, emphasizing removal of code when moving to public cloud to leverage managed services, standardization benefits of Java EE for long-term maintenance and migration, quarkus as modern framework supporting old Jakarta EE code with fast startup times, importance of choosing appropriate persistence layer (S3 vs relational databases) based on cloud costs, serverless architectures for enterprise applications with predictable low traffic, differences between AWS Azure and GCP service offerings and pricing models, Turbo assembler project klatwa Adam Dudczak on twitter: @maneo

In this episode of JavaScript Jabber, we welcome back Erik Hanchett, Senior Developer Advocate at AWS, to dive into his experience at VueConf. From the energy of the Vue community to lightning talks on AI and Nuxt updates, Erik shares his insights on where Vue is heading and why in-person conferences are still so valuable for developers. We also explore the balance between “vibe coding” and spec-driven development, plus Erik introduces us to Amazon Q CLI and its powerful MCP integrations for smarter AI-assisted coding.Along the way, we discuss the evolving state of Vue, the rise of Nuxt 4, Evan You's projects (including Vite and RollDown), and how Amplify is simplifying full-stack app development on AWS. Whether you're a Vue developer, curious about AI in frontend workflows, or just want to catch up on what's happening in the broader JavaScript ecosystem, this episode is packed with insights you won't want to miss.

Thank you to the folks at Sustain (https://sustainoss.org/) for providing the hosting account for CHAOSSCast! CHAOSScast – Episode 116 In this episode of CHAOSScast, host Georg Link is joined by guests Sarina Canelake, Feanil Patel, and Felipe Montoya from the Open edX community, to discuss their experiences with the GrimoireLab tool and the launch and growth of their maintainer program.  The conversation dives into the history and impact of the Open edX project, the evolution of their maintainer program, and the use of metrics to track and improve community health. The guests also share personal stories and provide insights into the challenges and successes they've encountered along the way. Press download now! [00:00:34] Sarina, Feanil, and Felipe introduce themselves and their backgrounds. [00:02:02] Feanil and Sarina explain the origins of the maintainer program, the mix of Python and JavaScript repositories, and how maintainers influence code direction. [00:04:02] Feanil explains the history of Open edX, being open sourced in 2013 by edX (MOOC platform) and how Axim Collaborative took over stewardship in 2021. [00:07:04] We hear Felipe's journey into the project from student to TA to community contributor and leader since 2012. He details the empowerment and pressure of receiving merge access in the Core Contributor program. [00:13:09] Sarina Explains why merge rights were initially limited to edX staff, and how the shift to community-led merging happened post 2020. [00:15:26] Feanil describes how the Maintainer Program now distributes ownership and improves repository health. [00:17:12] Feanil talks about his incremental metrics philosophy: starts with presence, then track responsiveness. [00:21:34] Georg asks how maintainers use GrimoireLab dashboards and filters. Sarina explains the use of Backstage ownership metadata for filtering dashboards by maintainers or groups and Feanil emphasizes the need for flexible tooling due to overlapping team memberships. [00:24:50] Felipe describes using dashboards to monitor his team's participation and accountability. [00:25:40] Sarina asks Felipe about dashboards he uses on Bitergia to track team contributions. [00:28:26] Sarina shares how she tracks Elephant Factor and trends in commit and LOC volume and Georg highlights the value of identity reconciliation in data. [00:30:45] Felipe talks about monitoring Slack, issues, and commits to ensure ecosystem health post-company transitions and Sarina notes challenges of mapping Slack/Discourse identities in Sorting Hat for deeper engagement metrics. [00:34:11] There's a discussion on syncing internal onboarding identity forms with Sorting Hat manually for now. [00:35:35] Georg raises concerns about metric misuse in performance reviews. Sarina and Feanil stress metrics as guidance, not performance tools, and Felipe shares his team uses metrics as lagging indicators, not for pressure. [00:39:55] Sarina explains how their impact report uses lines of code, commit trends, and elephant factor to show growth and codebase health. [00:42:32] Find out where you can go to get involved and contribute to Open edX and edunext. Value Adds (Picks) of the week: * [00:44:15] Georg's pick is a podcast called, ‘Through The Griffin Door' by the Carlin Brothers. * [00:44:50] Sarina's pick is her kitten who's taught herself how to play fetch and a podcast called, ‘The Best Idea Yet.' * [00:45:37] Feanil's pick is ‘Logseq,' a journaling and notetaking tool. * [00:46:42] Felipe's pick is the ‘Waking Up' app for mindful meditation. Panelist: Georg Link Guests: Sarina Canelake Feanil Patel Felipe Montoya Links: CHAOSS (https://chaoss.community/) CHAOSS Project X (https://twitter.com/chaossproj?lang=en) CHAOSScast Podcast (https://podcast.chaoss.community/) CHAOSS YouTube (https://www.youtube.com/@CHAOSStube/videos) podcast@chaoss.community (mailto:podcast@chaoss.community) Georg Link Website (https://georg.link/) Sarina Canelake LinkedIn (https://www.linkedin.com/in/sarinac/) Sarina Canelake Website (https://sarina.io/) Feanil Patel LinkedIn (https://www.linkedin.com/in/feanil/) Feanil Patel GitHub (https://github.com/feanil) Felipe Montoya LinkedIn (https://www.linkedin.com/in/felipe-montoya-edunext/) Open edX (https://openedx.org/) Open edX Documentation (https://docs.openedx.org/en/latest/) Open edX (YouTube) (https://www.youtube.com/c/Openedx) Open edX dashboard (https://openedx.biterg.io/app/dashboards#/view/Overview) Open edX GitHub (https://github.com/openedx) edunext (YouTube) (https://www.youtube.com/@edunextco) edunext (https://www.edunext.co/) Axim Collaborative (https://www.axim.org/) MOOC (https://www.mooc.org/) Through The Griffin Door (YouTube) (https://www.youtube.com/@ThroughTheGriffinDoor/podcasts) The Best Idea Yet Podcast (https://wondery.com/shows/the-best-idea-yet/) Logseq (https://logseq.com/) Waking Up (https://www.wakingup.com/) Special Guests: Feanil Patel, Felipe Montoya, and Sarina Canelake.

Stephen and Chris hop on to talk about how we're saving everyone from crashed browser tabs in CodePen's 2.0 editor. One simple: Executing JavaScript can cause a browser tab to entirely lock up, preventing you from doing anything, like potentially saving your work. It can even crash other same-domain tabs. But not on our watch! CodePen is now using a "heartbeat" technique to report up from the preview iframe to the parent page, and if we don't hear the heartbeat, we can rip out the iframe and stop the crash. But it was very tricky to get working and not too jumpy. Fortunately, we got it all working, because our previous technique of instrumenting your JavaScript wasn't going to scale well to the 2.0 editor. Time Jumps

Electron is a framework for building cross-platform desktop applications using web technologies like JavaScript, HTML, and CSS. It allows developers to package web apps with a native-like experience by bundling them with a Chromium browser and Node.js runtime. Electron is widely used for apps like VS Code, Discord, and Slack because it enables a single The post Electron and Desktop App Engineering with Shelley Vohr appeared first on Software Engineering Daily.

Hosts: Eric Peterson - Senior Developer at Ortus SolutionsGrant Copley - Senior Developer at Ortus SolutionsSPONSOR — ORTUS SOLUTIONSCBWire 

How Should You Pay Yourself as a Business Owner? Salary, Dividends, or an IPP? In this episode, Joe chats with Braden Warwick from PWL Capital about how business owners can pay themselves in the smartest way. They break down the pros and cons of taking a salary, dividends, or using an Individual Pension Plan (IPP), a lesser-known but powerful option. Braden shares what he's learned from co-authoring a paper with Ben Felix, and they talk through real-life examples. You'll learn how taxes play into each option, what “notional accounts” are (in simple terms), and how a flexible income plan could help you get the most from your money,both now and in retirement. Here's what you're in for: 00:00 – Welcome and intro 00:24 – Meet Braden and his role at PWL 01:57 – What the research says about business owner pay 04:03 – Tax pros and cons of each method 08:46 – What are notional accounts, anyway? 13:02 – How IPPs work and who they're good for 17:35 – Using a flexible salary strategy 25:49 – Final thoughts and where to learn more —------------------------------------------------------------- ABOUT BRADEN WARWICK Braden Warwick is a PhD Research Engineer who loves turning complex research into practical, high-performing software. With a background in optimization, Monte Carlo and statistical analysis, and stochastic modeling, he's passionate about solving tough problems and making data-driven tools that work in the real world. Braden has hands-on experience with GPU-accelerated simulations, parallel processing, and modern Python and JavaScript frameworks, bringing innovative ideas from theory to production. You can reach out to Braden through: LinkedIn: https://www.linkedin.com/in/braden-warwick-a40b48a3 Website: https://www.bradenwarwick.ca (Personal)              —------------------------------------------------------------- ABOUT JOE  CURRY Joe Curry is the host of Business and Exit Planning Simplified and the owner and lead financial planner at Matthews + Associates in Peterborough, Ontario. A Certified Financial Planner and Certified Exit Planning Advisor, Joe is passionate about helping business owners maximize value, plan successful exits, and find purpose beyond their business. His mission is to ensure clients retire with confidence—financially secure and personally fulfilled. You can reach out to Joe through: LinkedIn: https://www.linkedin.com/in/curryjoe Website: https://www.retirementplanningsimplified.ca/              https://www.facebook.com/RetirementPlanningSimplified/               https://matthewsandassociates.ca/    ABOUT BUSINESS AND EXIT PLANNING SIMPLIFIED The Business and Exit Planning Simplified podcast offers clear, actionable guidance to help business owners maximize value, plan successful exits, and achieve financial freedom. Hosted by Joe Curry, a Certified Financial Planner and Certified Exit Planning Advisor, each episode delivers expert insights, real-life case studies, and practical strategies tailored for service-based entrepreneurs approaching retirement. The podcast empowers listeners to transition with clarity, confidence, and a renewed sense of purpose.  —------------------------------------------------------------- Disclaimer: Opinions expressed are those of Joseph Curry, a registrant of Aligned Capital Partners Inc. (ACPI), and may not necessarily be those of ACPI. This video is for informational purposes only and not intended to be personalized investment advice. The views expressed are opinions of Joseph Curry and may not necessarily be those of ACPI. Content is prepared for general circulation and information contained does not constitute an offer or solicitation to buy or sell any investment fund, security or other product or service.  

Electron is a framework for building cross-platform desktop applications using web technologies like JavaScript, HTML, and CSS. It allows developers to package web apps with a native-like experience by bundling them with a Chromium browser and Node.js runtime. Electron is widely used for apps like VS Code, Discord, and Slack because it enables a single The post Electron and Desktop App Engineering with Shelley Vohr appeared first on Software Engineering Daily.

Ask Me Anything, die Erste!Du willst wissen, warum JavaScript bei uns manchmal für Bauchschmerzen sorgt? Oder wie wir bei dem rasenden Hype rund um KI & LLMs überhaupt noch den Überblick behalten? Vielleicht brennt dir auch die Frage unter den Nägeln, was wirklich wichtiger ist: Produkt, Gehalt oder Technologie bei deinem neuen Job – und würdest du für den „Purpose“ wirklich auf Geld oder deine Lieblings-Technologie verzichten?In dieser AMA-Episode stellen wir uns euren Fragen. Von Linter-Diskussionen, der Hassliebe zu JavaScript und Typescript, über Jobhopping und geplatzte Side-ProjectsDie Fragen kommen aus unserer Community, die Antworten von uns.Reinhören, mitdenken, Feedback dalassen – und vielleicht kommt eure Frage in der nächsten Runde gleich dran!Bonus: Wie viele Side-Projects passen eigentlich zwischen Hundespaziergang, Open Source und Podcast-Aufnahme?Unsere aktuellen Werbepartner findest du auf https://engineeringkiosk.dev/partnersDas schnelle Feedback zur Episode:

Today we are talking about HTMX, What it is, and why it could be a game changer for Drupal with our guests Shawn Duncan & Carson Gross. We'll also cover RefreshLess as our module of the week. For show notes visit: https://www.talkingDrupal.com/514 Topics What is HTMX HTMX and Drupal Integration Community and Contribution Discussing HTMX and Its Integration HTMX's Stability and Composition Programming with HTMX: A Lego-like Experience Drupal's HTMX Initiative Proof of Concept and Community Involvement HTMX's Flexibility and Developer Experience Big Pipe and HTMX Integration Comparing HTMX with Hotwire Turbo Getting Involved with the HTMX Initiative Resources [Plan] Gradually replace Drupal's AJAX system with HTMX HTMX in core Proof of Concept HTMX contrib module HTMX Documentation Hypermedia Systems - Carson's book A comparison of Hypermedia Application architecture with Single Page Application. Available for purchase and free online. Academic Paper on HTMX FACET Essays HTMX Sucks Locality of behavior Future of HTMX Drupal community initiatives Contrast of htmx vs hotwire grugbrain Primeagen Fireship dev Guests Shawn Duncan - HTMX intiative fathershawn Carson Gross - bigsky.software 1cg Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Rich Lawson - richlawson.co rklawson MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever wanted to give your Drupal site a more application-like feel, by only reloading parts of the page that need to change? There's a module for that. Module name/project name: RefreshLess Brief history How old: created in Mar 2016 by Wim Leers, but recent releases are by ambient.impact, a fellow Canadian Versions available: 2.0.0-alpha9 Maintainership Actively maintained Security coverage Test coverage Documentation Number of open issues: 40 open issues, only 2 of which are active bugs against the current branch Usage stats: 2 sites Module features and usage The RefreshLess module aims to give Drupal sites a smooth, fast, and responsive experience by using Javascript to selectively update the parts of the existing page that need to change, instead of a full page refresh. It uses the HTML5 History API to ensure the browsing behaviour is equivalent, and unsupported browsers will see a standard page refresh instead Using RefreshLess also makes it possible to use transitions (with or without the View Transition API in modern browsers), morphing, and persistent elements to enhance the application-like feel There is some indication that sites may encounter issues if they use RefreshLess with JS aggregation enabled, so it's probably better to use it if your site has HTTP/2 enabled RefreshLess is currently built on the Turbo library originally built for Ruby on Rails, but there is already an issue open to move the implementation to use HTMX instead

What if I told you someone managed to run Doom inside TypeScript's type system? Sounds insane, right? That's exactly what our guest Dimitri Mitropoulos did—and in this episode, we dive deep into the how, the why, and the mind-bending implications of this ambitious project. From type-level programming to the philosophical limits of Turing completeness, this is an episode that pushes the boundaries of what you thought was possible in JavaScript.We talk about how the TypeScript type system evolved to become Turing-complete, how Dimitri pulled off this seemingly impossible feat, and why “Doom-complete” might just be the new gold standard for computational capability. Along the way, we touch on functional programming, generics, recursion, and even some Lambda Calculus. It's part computer science theory, part coding madness, and 100% geeky goodness.Episode Highlights[3:05] – Dimitri explains how a simple thought experiment turned into a year-and-a-half-long obsession[8:40] – The origins and significance of Turing completeness in type systems[14:15] – Why running Doom in TypeScript is more about proving limits than just showing off[19:55] – What it means to run programs inside the type system vs. TypeScript code itself[27:10] – ASCII art as output, functional recursion for game state, and hover-over frames in your editor[35:30] – How ignorance, determination, and obsession fueled the completion of the project[45:20] – Personal insights: balancing family, burnout, and passion while chasing an impossible dreamLinks & ResourcesDimitri MitropoulosMichigan TypeScript YouTube Channel – Dimitri's channel featuring the projectType Challenges by Anthony Fu – Advanced TypeScript exercisesSquiggleConf – The TypeScript-focused conference Dimitri co-foundedJosh Goldberg – TypeScript expert and co-organizer of SquiggleConfBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Nicolas Gallagher from Meta joins Jamon, Robin, and Tyler to kick off a two‑part series on React Native Web vs React Strict DOM. They discuss the origins of each, how Meta is using them, and what they mean for the future of cross‑platform React development. Show NotesReact Strict DOM (GitHub)React Native for Web Connect With Us!Nicolas Gallagher: LinkedInJamon Holmgren: @jamonholmgrenRobin Heinze: @robinheinzeTyler Williams: @coolsoftwaredevReact Native Radio: @ReactNativeRdioThis episode is brought to you by Infinite Red!Infinite Red is an expert React Native consultancy located in the USA. With nearly a decade of React Native experience and deep roots in the React Native community (hosts of Chain React and the React Native Newsletter, core React Native contributors, creators of Ignite and Reactotron, and much, much more), Infinite Red is the best choice for helping you build and deploy your next React Native app.

Interview with Ian Krietzberg Leo's shows off his new AI toys Paris unveils her new desk setup Personal Superintelligence You might want to delve into this paper. I want to underscore, that's a joke you'll comprehend only with meticulous reading of it. Source: Yann LeCun will continue to work at Meta as chief scientist of the AI research group FAIR and will report to Alexandr Wang Last Week on My Mac:

Custom keyboards take center stage as Mikah and Rosemary explore the surprisingly small but mighty world of third-party iOS keyboards, from snippet management to AI-powered writing assistance, plus listener feedback on AirPods cleaning and some delightful app picks. Snippety keyboard ($29.99) - Rosemary demonstrates this powerful snippet management keyboard with collections, search functionality, rich formatting options, and advanced features like JavaScript snippets with placeholders and multi-select menus Bitmoji keyboard (free) - Mikah showcases this fun cartoon avatar keyboard that creates personalized messages and can include friends who also use Bitmoji, though he notes the unsettling 3D redesign Microsoft SwiftKey AI keyboard - Rosemary highlights its reliability during iOS beta issues, easy-to-spot emoji button, built-in paste functionality, GIF search, and translator feature, plus Copilot AI integration for enterprise users Grammarly AI Writing keyboard - Overview of grammar and writing improvement features, tone suggestions, vocabulary enhancements, and rewriting capabilities for professional communication Feedback AirPods cleaning kit question from Gregg - Detailed explanation of the Belkin AirPods cleaning kit, featuring distilled water and micellar water that breaks down oils and earwax using micelles that attract fats and dirt App Caps Rosemary's pick: PopSocket MagSafe Stand ($40) - New MagSafe PopSocket that doubles as a phone stand with swappable decorative tops, though she warns against overly symmetrical patterns that make you obsess over alignment Mikah's pick: Pet Libro water fountain - Smart pet fountain with inductive charging base, built-in scale for tracking water consumption, alternating 15-minute cycles (perfect for anxious dogs), Wi-Fi connectivity, and foreign object detection Hosts: Mikah Sargent and Rosemary Orchard Contact iOS Today at iOSToday@twit.tv. Download or subscribe to iOS Today at https://twit.tv/shows/ios-today Want access to the ad-free video and exclusive features? Become a member of Club TWiT today! https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

Custom keyboards take center stage as Mikah and Rosemary explore the surprisingly small but mighty world of third-party iOS keyboards, from snippet management to AI-powered writing assistance, plus listener feedback on AirPods cleaning and some delightful app picks. Snippety keyboard ($29.99) - Rosemary demonstrates this powerful snippet management keyboard with collections, search functionality, rich formatting options, and advanced features like JavaScript snippets with placeholders and multi-select menus Bitmoji keyboard (free) - Mikah showcases this fun cartoon avatar keyboard that creates personalized messages and can include friends who also use Bitmoji, though he notes the unsettling 3D redesign Microsoft SwiftKey AI keyboard - Rosemary highlights its reliability during iOS beta issues, easy-to-spot emoji button, built-in paste functionality, GIF search, and translator feature, plus Copilot AI integration for enterprise users Grammarly AI Writing keyboard - Overview of grammar and writing improvement features, tone suggestions, vocabulary enhancements, and rewriting capabilities for professional communication Feedback AirPods cleaning kit question from Gregg - Detailed explanation of the Belkin AirPods cleaning kit, featuring distilled water and micellar water that breaks down oils and earwax using micelles that attract fats and dirt App Caps Rosemary's pick: PopSocket MagSafe Stand ($40) - New MagSafe PopSocket that doubles as a phone stand with swappable decorative tops, though she warns against overly symmetrical patterns that make you obsess over alignment Mikah's pick: Pet Libro water fountain - Smart pet fountain with inductive charging base, built-in scale for tracking water consumption, alternating 15-minute cycles (perfect for anxious dogs), Wi-Fi connectivity, and foreign object detection Hosts: Mikah Sargent and Rosemary Orchard Contact iOS Today at iOSToday@twit.tv. Download or subscribe to iOS Today at https://twit.tv/shows/ios-today Want access to the ad-free video and exclusive features? Become a member of Club TWiT today! https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

Interview with Ian Krietzberg Leo's shows off his new AI toys Paris unveils her new desk setup Personal Superintelligence You might want to delve into this paper. I want to underscore, that's a joke you'll comprehend only with meticulous reading of it. Source: Yann LeCun will continue to work at Meta as chief scientist of the AI research group FAIR and will report to Alexandr Wang Last Week on My Mac:

Custom keyboards take center stage as Mikah and Rosemary explore the surprisingly small but mighty world of third-party iOS keyboards, from snippet management to AI-powered writing assistance, plus listener feedback on AirPods cleaning and some delightful app picks. Snippety keyboard ($29.99) - Rosemary demonstrates this powerful snippet management keyboard with collections, search functionality, rich formatting options, and advanced features like JavaScript snippets with placeholders and multi-select menus Bitmoji keyboard (free) - Mikah showcases this fun cartoon avatar keyboard that creates personalized messages and can include friends who also use Bitmoji, though he notes the unsettling 3D redesign Microsoft SwiftKey AI keyboard - Rosemary highlights its reliability during iOS beta issues, easy-to-spot emoji button, built-in paste functionality, GIF search, and translator feature, plus Copilot AI integration for enterprise users Grammarly AI Writing keyboard - Overview of grammar and writing improvement features, tone suggestions, vocabulary enhancements, and rewriting capabilities for professional communication Feedback AirPods cleaning kit question from Gregg - Detailed explanation of the Belkin AirPods cleaning kit, featuring distilled water and micellar water that breaks down oils and earwax using micelles that attract fats and dirt App Caps Rosemary's pick: PopSocket MagSafe Stand ($40) - New MagSafe PopSocket that doubles as a phone stand with swappable decorative tops, though she warns against overly symmetrical patterns that make you obsess over alignment Mikah's pick: Pet Libro water fountain - Smart pet fountain with inductive charging base, built-in scale for tracking water consumption, alternating 15-minute cycles (perfect for anxious dogs), Wi-Fi connectivity, and foreign object detection Hosts: Mikah Sargent and Rosemary Orchard Contact iOS Today at iOSToday@twit.tv. Download or subscribe to iOS Today at https://twit.tv/shows/ios-today Want access to the ad-free video and exclusive features? Become a member of Club TWiT today! https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

Custom keyboards take center stage as Mikah and Rosemary explore the surprisingly small but mighty world of third-party iOS keyboards, from snippet management to AI-powered writing assistance, plus listener feedback on AirPods cleaning and some delightful app picks. Snippety keyboard ($29.99) - Rosemary demonstrates this powerful snippet management keyboard with collections, search functionality, rich formatting options, and advanced features like JavaScript snippets with placeholders and multi-select menus Bitmoji keyboard (free) - Mikah showcases this fun cartoon avatar keyboard that creates personalized messages and can include friends who also use Bitmoji, though he notes the unsettling 3D redesign Microsoft SwiftKey AI keyboard - Rosemary highlights its reliability during iOS beta issues, easy-to-spot emoji button, built-in paste functionality, GIF search, and translator feature, plus Copilot AI integration for enterprise users Grammarly AI Writing keyboard - Overview of grammar and writing improvement features, tone suggestions, vocabulary enhancements, and rewriting capabilities for professional communication Feedback AirPods cleaning kit question from Gregg - Detailed explanation of the Belkin AirPods cleaning kit, featuring distilled water and micellar water that breaks down oils and earwax using micelles that attract fats and dirt App Caps Rosemary's pick: PopSocket MagSafe Stand ($40) - New MagSafe PopSocket that doubles as a phone stand with swappable decorative tops, though she warns against overly symmetrical patterns that make you obsess over alignment Mikah's pick: Pet Libro water fountain - Smart pet fountain with inductive charging base, built-in scale for tracking water consumption, alternating 15-minute cycles (perfect for anxious dogs), Wi-Fi connectivity, and foreign object detection Hosts: Mikah Sargent and Rosemary Orchard Contact iOS Today at iOSToday@twit.tv. Download or subscribe to iOS Today at https://twit.tv/shows/ios-today Want access to the ad-free video and exclusive features? Become a member of Club TWiT today! https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

Interview with Ian Krietzberg Leo's shows off his new AI toys Paris unveils her new desk setup Personal Superintelligence You might want to delve into this paper. I want to underscore, that's a joke you'll comprehend only with meticulous reading of it. Source: Yann LeCun will continue to work at Meta as chief scientist of the AI research group FAIR and will report to Alexandr Wang Last Week on My Mac:

Interview with Ian Krietzberg Leo's shows off his new AI toys Paris unveils her new desk setup Personal Superintelligence You might want to delve into this paper. I want to underscore, that's a joke you'll comprehend only with meticulous reading of it. Source: Yann LeCun will continue to work at Meta as chief scientist of the AI research group FAIR and will report to Alexandr Wang Last Week on My Mac:

In this episode of The Cybersecurity Defenders Podcast, we discuss some intel being shared in the LimaCharlie community.A critical new SharePoint vulnerability is under mass exploitation, with attackers targeting on-premises SharePoint Server deployments to exfiltrate sensitive data, including authentication tokens.And then directly related to the first story, Microsoft has now confirmed that at least three China-linked threat actors—Linen Typhoon, Violet Typhoon, and Storm-2603—were actively exploiting CVE-2025-49706 and CVE-2025-49704 a day before the company issued patches on July 8.The UK government announced on July 22, 2025, that it plans to make ransomware payments illegal for public sector bodies and operators of critical national infrastructure (CNI).In-browser cryptocurrency mining, often called crypto jacking, originally gained notoriety in 2017 when Coinhive introduced JavaScript-based mining for Monero.

Interview with Ian Krietzberg Leo's shows off his new AI toys Paris unveils her new desk setup Personal Superintelligence You might want to delve into this paper. I want to underscore, that's a joke you'll comprehend only with meticulous reading of it. Source: Yann LeCun will continue to work at Meta as chief scientist of the AI research group FAIR and will report to Alexandr Wang Last Week on My Mac:

Interview with Ian Krietzberg Leo's shows off his new AI toys Paris unveils her new desk setup Personal Superintelligence You might want to delve into this paper. I want to underscore, that's a joke you'll comprehend only with meticulous reading of it. Source: Yann LeCun will continue to work at Meta as chief scientist of the AI research group FAIR and will report to Alexandr Wang Last Week on My Mac:

Custom keyboards take center stage as Mikah and Rosemary explore the surprisingly small but mighty world of third-party iOS keyboards, from snippet management to AI-powered writing assistance, plus listener feedback on AirPods cleaning and some delightful app picks. Snippety keyboard ($29.99) - Rosemary demonstrates this powerful snippet management keyboard with collections, search functionality, rich formatting options, and advanced features like JavaScript snippets with placeholders and multi-select menus Bitmoji keyboard (free) - Mikah showcases this fun cartoon avatar keyboard that creates personalized messages and can include friends who also use Bitmoji, though he notes the unsettling 3D redesign Microsoft SwiftKey AI keyboard - Rosemary highlights its reliability during iOS beta issues, easy-to-spot emoji button, built-in paste functionality, GIF search, and translator feature, plus Copilot AI integration for enterprise users Grammarly AI Writing keyboard - Overview of grammar and writing improvement features, tone suggestions, vocabulary enhancements, and rewriting capabilities for professional communication Feedback AirPods cleaning kit question from Gregg - Detailed explanation of the Belkin AirPods cleaning kit, featuring distilled water and micellar water that breaks down oils and earwax using micelles that attract fats and dirt App Caps Rosemary's pick: PopSocket MagSafe Stand ($40) - New MagSafe PopSocket that doubles as a phone stand with swappable decorative tops, though she warns against overly symmetrical patterns that make you obsess over alignment Mikah's pick: Pet Libro water fountain - Smart pet fountain with inductive charging base, built-in scale for tracking water consumption, alternating 15-minute cycles (perfect for anxious dogs), Wi-Fi connectivity, and foreign object detection Hosts: Mikah Sargent and Rosemary Orchard Contact iOS Today at iOSToday@twit.tv. Download or subscribe to iOS Today at https://twit.tv/shows/ios-today Want access to the ad-free video and exclusive features? Become a member of Club TWiT today! https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

In this episode of In-Ear Insights, the Trust Insights podcast, Katie and Chris discuss the pitfalls and best practices of “vibe coding” with generative AI. You will discover why merely letting AI write code creates significant risks. You will learn essential strategies for defining robust requirements and implementing critical testing. You will understand how to integrate security measures and quality checks into your AI-driven projects. You will gain insights into the critical human expertise needed to build stable and secure applications with AI. Tune in to learn how to master responsible AI coding and avoid common mistakes! Watch the video here: Can’t see anything? Watch it on YouTube here. Listen to the audio here: https://traffic.libsyn.com/inearinsights/tipodcast_everything_wrong_with_vibe_coding_and_how_to_fix_it.mp3 Download the MP3 audio here. Need help with your company’s data and analytics? Let us know! Join our free Slack group for marketers interested in analytics! [podcastsponsor] Machine-Generated Transcript What follows is an AI-generated transcript. The transcript may contain errors and is not a substitute for listening to the episode. Christopher S. Penn – 00:00 In this week’s In-Ear Insights, if you go on LinkedIn, everybody, including tons of non-coding folks, has jumped into vibe coding, the term coined by OpenAI co-founder Andre Karpathy. A lot of people are doing some really cool stuff with it. However, a lot of people are also, as you can see on X in a variety of posts, finding out the hard way that if you don’t know what to ask for—say, application security—bad things can happen. Katie, how are you doing with giving into the vibes? Katie Robbert – 00:38 I’m not. I’ve talked about this on other episodes before. For those who don’t know, I have an extensive background in managing software development. I myself am not a software developer, but I have spent enough time building and managing those teams that I know what to look for and where things can go wrong. I’m still really skeptical of vibe coding. We talked about this on a previous podcast, which if you want to find our podcast, it’s @TrustInsightsAI_TIpodcast, or you can watch it on YouTube. My concern, my criticism, my skepticism of vibe coding is if you don’t have the basic foundation of the SDLC, the software development lifecycle, then it’s very easy for you to not do vibe coding correctly. Katie Robbert – 01:42 My understanding is vibe coding is you’re supposed to let the machine do it. I think that’s a complete misunderstanding of what’s actually happening because you still have to give the machine instruction and guardrails. The machine is creating AI. Generative AI is creating the actual code. It’s putting together the pieces—the commands that comprise a set of JSON code or Python code or whatever it is you’re saying, “I want to create an app that does this.” And generative AI is like, “Cool, let’s do it.” You’re going through the steps. You still need to know what you’re doing. That’s my concern. Chris, you have recently been working on a few things, and I’m curious to hear, because I know you rely on generative AI because yourself, you’ve said, are not a developer. What are some things that you’ve run into? Katie Robbert – 02:42 What are some lessons that you’ve learned along the way as you’ve been vibing? Christopher S. Penn – 02:50 Process is the foundation of good vibe coding, of knowing what to ask for. Think about it this way. If you were to say to Claude, ChatGPT, or Gemini, “Hey, write me a fiction novel set in the 1850s that’s a drama,” what are you going to get? You’re going to get something that’s not very good. Because you didn’t provide enough information. You just said, “Let’s do the thing.” You’re leaving everything up to the machine. That prompt—just that prompt alone. If you think about an app like a book, in this example, it’s going to be slop. It’s not going to be very good. It’s not going to be very detailed. Christopher S. Penn – 03:28 Granted, it doesn’t have the issues of code, but it’s going to suck. If, on the other hand, you said, “Hey, here’s the ideas I had for all the characters, here’s the ideas I had for the plot, here’s the ideas I had for the setting. But I want to have these twists. Here’s the ideas for the readability and the language I want you to use.” You provided it with lots and lots of information. You’re going to get a better result. You’re going to get something—a book that’s worth reading—because it’s got your ideas in it, it’s got your level of detail in it. That’s how you would write a book. The same thing is true of coding. You need to have, “Here’s the architecture, here’s the security requirements,” which is a big, big gap. Christopher S. Penn – 04:09 Here’s how to do unit testing, here’s the fact why unit tests are important. I hated when I was writing code by myself, I hated testing. I always thought, Oh my God, this is the worst thing in the world to have to test everything. With generative AI coding tools, I now am in love with testing because, in fact, I now follow what’s called test-driven development, where you write the tests first before you even write the production code. Because I don’t have to do it. I can say, “Here’s the code, here’s the ideas, here’s the questions I have, here’s the requirements for security, here’s the standards I want you to use.” I’ve written all that out, machine. “You go do this and run these tests until they’re clean, and you’ll just keep running over and fix those problems.” Christopher S. Penn – 04:54 After every cycle you do it, but it has to be free of errors before you can move on. The tools are very capable of doing that. Katie Robbert – 05:03 You didn’t answer my question, though. Christopher S. Penn – 05:05 Okay. Katie Robbert – 05:06 My question to you was, Chris Penn, what lessons have you specifically learned about going through this? What’s been going on, as much as you can share, because obviously we’re under NDA. What have you learned? Christopher S. Penn – 05:23 What I’ve learned: documentation and code drift very quickly. You have your PRD, you have your requirements document, you have your work plans. Then, as time goes on and you’re making fixes to things, the code and the documentation get out of sync very quickly. I’ll show an example of this. I’ll describe what we’re seeing because it’s just a static screenshot, but in the new Claude code, you have the ability to build agents. These are built-in mini-apps. My first one there, Document Code Drift Auditor, goes through and says, “Hey, here’s where your documentation is out of line with the reality of your code,” which is a big deal to make sure that things stay in sync. Christopher S. Penn – 06:11 The second one is a Code Quality Auditor. One of the big lessons is you can’t just say, “Fix my code.” You have to say, “You need to give me an audit of what’s good about my code, what’s bad about my code, what’s missing from my code, what’s unnecessary from my code, and what silent errors are there.” Because that’s a big one that I’ve had trouble with is silent errors where there’s not something obviously broken, but it’s not quite doing what you want. These tools can find that. I can’t as a person. That’s just me. Because I can’t see what’s not there. A third one, Code Base Standards Inspector, to look at the standards. This is one that it says, “Here’s a checklist” because I had to write—I had to learn to write—a checklist of. Christopher S. Penn – 06:51 These are the individual things I need you to find that I’ve done or not done in the codebase. The fourth one is logging. I used to hate logging. Now I love logs because I can say in the PRD, in the requirements document, up front and throughout the application, “Write detailed logs about what’s happening with my application” because that helps machine debug faster. I used to hate logs, and now I love them. I have an agent here that says, “Go read the logs, find errors, fix them.” Fifth lesson: debt collection. Technical debt is a big issue. This is when stuff just accumulates. As clients have new requests, “Oh, we want to do this and this and this.” Your code starts to drift even from its original incarnation. Christopher S. Penn – 07:40 These tools don’t know to clean that up unless you tell it to. I have a debt collector agent that goes through and says, “Hey, this is a bunch of stuff that has no purpose anymore.” And we can then have a conversation about getting rid of it without breaking things. Which, as a thing, the next two are painful lessons that I’ve learned. Progress Logger essentially says, after every set of changes, you need to write a detailed log file in this folder of that change and what you did. The last one is called Docs as Data Curator. Christopher S. Penn – 08:15 This is where the tool goes through and it creates metadata at the top of every progress entry that says, “Here’s the keywords about what this bug fixes” so that I can later go back and say, “Show me all the bug fixes that we’ve done for BigQuery or SQLite or this or that or the other thing.” Because what I found the hard way was the tools can introduce regressions. They can go back and keep making the same mistake over and over again if they don’t have a logbook of, “Here’s what I did and what happened, whether it worked or not.” By having these set—these seven tools, these eight tools—in place, I can prevent a lot of those behaviors that generative AI tends to have. Christopher S. Penn – 08:54 In the same way that you provide a writing style guide so that AI doesn’t keep making the mistake of using em dashes or saying, “in a world of,” or whatever the things that you do in writing. My hard-earned lessons I’ve encoded into agents now so that I don’t keep making those mistakes, and AI doesn’t keep making those mistakes. Katie Robbert – 09:17 I feel you’re demonstrating my point of my skepticism with vibe coding because you just described a very lengthy process and a lot of learnings. I’m assuming what was probably a lot of research up front on software development best practices. I actually remember the day that you were introduced to unit tests. It wasn’t that long ago. And you’re like, “Oh, well, this makes it a lot easier.” Those are the kinds of things that, because, admittedly, software development is not your trade, it’s not your skillset. Those are things that you wouldn’t necessarily know unless you were a software developer. Katie Robbert – 10:00 This is my skepticism of vibe coding: sure, anybody can use generative AI to write some code and put together an app, but then how stable is it, how secure is it? You still have to know what you’re doing. I think that—not to be too skeptical, but I am—the more accessible generative AI becomes, the more fragile software development is going to become. It’s one thing to write a blog post; there’s not a whole lot of structure there. It’s not powering your website, it’s not the infrastructure that holds together your entire business, but code is. Katie Robbert – 11:03 That’s where I get really uncomfortable. I’m fine with using generative AI if you know what you’re doing. I have enough knowledge that I could use generative AI for software development. It’s still going to be flawed, it’s still going to have issues. Even the most experienced software developer doesn’t get it right the first time. I’ve never in my entire career seen that happen. There is no such thing as the perfect set of code the first time. I think that people who are inexperienced with the software development lifecycle aren’t going to know about unit tests, aren’t going to know about test-based coding, or peer testing, or even just basic QA. Katie Robbert – 11:57 It’s not just, “Did it do the thing,” but it’s also, “Did it do the thing on different operating systems, on different browsers, in different environments, with people doing things you didn’t ask them to do, but suddenly they break things?” Because even though you put the big “push me” button right here, someone’s still going to try to click over here and then say, “I clicked on your logo. It didn’t work.” Christopher S. Penn – 12:21 Even the vocabulary is an issue. I’ll give you four words that would automatically uplevel your Python vibe coding better. But these are four words that you probably have never heard of: Ruff, MyPy, Pytest, Bandit. Those are four automated testing utilities that exist in the Python ecosystem. They’ve been free forever. Ruff cleans up and does linting. It says, “Hey, you screwed this up. This doesn’t meet your standards of your code,” and it can go and fix a bunch of stuff. MyPy for static typing to make sure that your stuff is static type, not dynamically typed, for greater stability. Pytest runs your unit tests, of course. Bandit looks for security holes in your Python code. Christopher S. Penn – 13:09 If you don’t know those exist, you probably say you’re a marketer who’s doing vibe coding for the first time, because you don’t know they exist. They are not accessible to you, and generative AI will not tell you they exist. Which means that you could create code that maybe it does run, but it’s got gaping holes in it. When I look at my standards, I have a document of coding standards that I’ve developed because of all the mistakes I’ve made that it now goes in every project. This goes, “Boom, drop it in,” and those are part of the requirements. This is again going back to the book example. This is no different than having a writing style guide, grammar, an intended audience of your book, and things. Christopher S. Penn – 13:57 The same things that you would go through to be a good author using generative AI, you have to do for coding. There’s more specific technical language. But I would be very concerned if anyone, coder or non-coder, was just releasing stuff that didn’t have the right safeguards in it and didn’t have good enough testing and evaluation. Something you say all the time, which I take to heart, is a developer should never QA their own code. Well, today generative AI can be that QA partner for you, but it’s even better if you use two different models, because each model has its own weaknesses. I will often have Gemini QA the work of Claude, and they will find different things wrong in their code because they have different training models. These two tools can work together to say, “What about this?” Christopher S. Penn – 14:48 “What about this?” And they will. I’ve actually seen them argue, “The previous developers said this. That’s not true,” which is entertaining. But even just knowing that rule exists—a developer should not QA their own code—is a blind spot that your average vibe coder is not going to have. Katie Robbert – 15:04 Something I want to go back to that you were touching upon was the privacy. I’ve seen a lot of people put together an app that collects information. It could collect basic contact information, it could collect other kind of demographic information, it can collect opinions and thoughts, or somehow it’s collecting some kind of information. This is also a huge risk area. Data privacy has always been a risk. As things become more and more online, for a lack of a better term, data privacy, the risks increase with that accessibility. Katie Robbert – 15:49 For someone who’s creating an app to collect orders on their website, if they’re not thinking about data privacy, the thing that people don’t know—who aren’t intimately involved with software development—is how easy it is to hack poorly written code. Again, to be super skeptical: in this day and age, everything is getting hacked. The more AI is accessible, the more hackable your code becomes. Because people can spin up these AI agents with the sole purpose of finding vulnerabilities in software code. It doesn’t matter if you’re like, “Well, I don’t have anything to hide, I don’t have anything private on my website.” It doesn’t matter. They’re going to hack it anyway and start to use it for nefarious things. Katie Robbert – 16:49 One of the things that we—not you and I, but we in my old company—struggled with was conducting those security tests as part of the test plan because we didn’t have someone on the team at the time who was thoroughly skilled in that. Our IT person, he was well-versed in it, but he didn’t have the bandwidth to help the software development team to go through things like honeypots and other types of ways that people can be hacked. But he had the knowledge that those things existed. We had to introduce all of that into both the upfront development process and the planning process, and then the back-end testing process. It added additional time. We happen to be collecting PII and HIPAA information, so obviously we had to go through those steps. Katie Robbert – 17:46 But to even understand the basics of how your code can be hacked is going to be huge. Because it will be hacked if you do not have data privacy and those guardrails around your code. Even if your code is literally just putting up pictures on your website, guess what? Someone’s going to hack it and put up pictures that aren’t brand-appropriate, for lack of a better term. That’s going to happen, unfortunately. And that’s just where we’re at. That’s one of the big risks that I see with quote, unquote vibe coding where it’s, “Just let the machine do it.” If you don’t know what you’re doing, don’t do it. I don’t know how many times I can say that, or at the very. Christopher S. Penn – 18:31 At least know to ask. That’s one of the things. For example, there’s this concept in data security called principle of minimum privilege, which is to grant only the amount of access somebody needs. Same is true for principle of minimum data: collect only information that you actually need. This is an example of a vibe-coded project that I did to make a little Time Zone Tracker. You could put in your time zones and stuff like that. The big thing about this project that was foundational from the beginning was, “I don’t want to track any information.” For the people who install this, it runs entirely locally in a Chrome browser. It does not collect data. There’s no backend, there’s no server somewhere. So it stays only on your computer. Christopher S. Penn – 19:12 The only thing in here that has any tracking whatsoever is there’s a blue link to the Trust Insights website at the very bottom, and that has Google Track UTM codes. That’s it. Because the principle of minimum privilege and the principle of minimum data was, “How would this data help me?” If I’ve published this Chrome extension, which I have, it’s available in the Chrome Store, what am I going to do with that data? I’m never going to look at it. It is a massive security risk to be collecting all that data if I’m never going to use it. It’s not even built in. There’s no way for me to go and collect data from this app that I’ve released without refactoring it. Christopher S. Penn – 19:48 Because we started out with a principle of, “Ain’t going to use it; it’s not going to provide any useful data.” Katie Robbert – 19:56 But that I feel is not the norm. Christopher S. Penn – 20:01 No. And for marketers. Katie Robbert – 20:04 Exactly. One, “I don’t need to collect data because I’m not going to use it.” The second is even if you’re not collecting any data, is your code still hackable so that somebody could hack into this set of code that people have running locally and change all the time zones to be anti-political leaning, whatever messages that they’re like, “Oh, I didn’t realize Chris Penn felt that way.” Those are real concerns. That’s what I’m getting at: even if you’re publishing the most simple code, make sure it’s not hackable. Christopher S. Penn – 20:49 Yep. Do that exercise. Every software language there is has some testing suite. Whether it’s Chrome extensions, whether it’s JavaScript, whether it’s Python, because the human coders who have been working in these languages for 10, 20, 30 years have all found out the hard way that things go wrong. All these automated testing tools exist that can do all this stuff. But when you’re using generative AI, you have to know to ask for it. You have to say. You can say, “Hey, here’s my idea.” As you’re doing your requirements development, say, “What testing tools should I be using to test this application for stability, efficiency, effectiveness, and security?” Those are the big things. That has to be part of the requirements document. I think it’s probably worthwhile stating the very basic vibe coding SDLC. Christopher S. Penn – 21:46 Build your requirements, check your requirements, build a work plan, execute the work plan, and then test until you’re sick of testing, and then keep testing. That’s the process. AI agents and these coding agents can do the “fingers on keyboard” part, but you have to have the knowledge to go, “I need a requirements document.” “How do I do that?” I can have generative AI help me with that. “I need a work plan.” “How do I do that?” Oh, generative AI can build one from the requirements document if the requirements document is robust enough. “I need to implement the code.” “How do I do that?” Christopher S. Penn – 22:28 Oh yeah, AI can do that with a coding agent if it has a work plan. “I need to do QA.” “How do I do that?” Oh, if I have progress logs and the code, AI can do that if it knows what to look for. Then how do I test? Oh, AI can run automated testing utilities and fix the problems it finds, making sure that the code doesn’t drift away from the requirements document until it’s done. That’s the bare bones, bare minimum. What’s missing from that, Katie? From the formal SDLC? Katie Robbert – 23:00 That’s the gist of it. There’s so much nuance and so much detail. This is where, because you and I, we were not 100% aligned on the usage of AI. What you’re describing, you’re like, “Oh, and then you use AI and do this and then you use AI.” To me, that immediately makes me super anxious. You’re too heavily reliant on AI to get it right. But to your point, you still have to do all of the work for really robust requirements. I do feel like a broken record. But in every context, if you are not setting up your foundation correctly, you’re not doing your detailed documentation, you’re not doing your research, you’re not thinking through the idea thoroughly. Katie Robbert – 23:54 Generative AI is just another tool that’s going to get it wrong and screw it up and then eventually collect dust because it doesn’t work. When people are worried about, “Is AI going to take my job?” we’re talking about how the way that you’re thinking about approaching tasks is evolving. So you, the human, are still very critical to this task. If someone says, “I’m going to fire my whole development team, the machines, Vibe code, good luck,” I have a lot more expletives to say with that, but good luck. Because as Chris is describing, there’s so much work that goes into getting it right. Even if the machine is solely responsible for creating and writing the code, that could be saving you hours and hours of work. Because writing code is not easy. Katie Robbert – 24:44 There’s a reason why people specialize in it. There’s still so much work that has to be done around it. That’s the thing that people forget. They think they’re saving time. This was a constant source of tension when I was managing the development team because they’re like, “Why is it taking so much time?” The developers have estimated 30 hours. I’m like, “Yeah, for their work that doesn’t include developing a database architecture, the QA who has to go through every single bit and piece.” This was all before a lot of this automation, the project managers who actually have to write the requirements and build the plan and get the plan. All of those other things. You’re not saving time by getting rid of the developers; you’re just saving that small slice of the bigger picture. Christopher S. Penn – 25:38 The rule of thumb, generally, with humans is that for every hour of development, you’re going to have two to four hours of QA time, because you need to have a lot of extra eyes on the project. With vibe coding, it’s between 10 and 20x. Your hour of vibe coding may shorten dramatically. But then you’re going to. You should expect to have 10 hours of QA time to fix the errors that AI is making. Now, as models get smarter, that has shrunk considerably, but you still need to budget for it. Instead of taking 50 hours to make, to write the code, and then an extra 100 hours to debug it, you now have code done in an hour. But you still need the 10 to 20 hours to QA it. Christopher S. Penn – 26:22 When generative AI spits out that first draft, it’s every other first draft. It ain’t done. It ain’t done. Katie Robbert – 26:31 As we’re wrapping up, Chris, if possible, can you summarize your recent lesson learned from using AI for software development—what is the one thing, the big lesson that you took away? Christopher S. Penn – 26:50 If we think of software development like the floors of a skyscraper, everyone wants the top floor, which is the scenic part. That’s cool, and everybody can go up there. It is built on a foundation and many, many floors of other things. And if you don’t know what those other floors are, your top floor will literally fall out of the sky. Because it won’t be there. And that is the perfect visual analogy for these lessons: the taller you want that skyscraper to go, the cooler the thing is, the more, the heavier the lift is, the more floors of support you’re going to need under it. And if you don’t have them, it’s not going to go well. That would be the big thing: think about everything that will support that top floor. Christopher S. Penn – 27:40 Your overall best practices, your overall coding standards for a specific project, a requirements document that has been approved by the human stakeholders, the work plans, the coding agents, the testing suite, the actual agentic sewing together the different agents. All of that has to exist for that top floor, for you to be able to build that top floor and not have it be a safety hazard. That would be my parting message there. Katie Robbert – 28:13 How quickly are you going to get back into a development project? Christopher S. Penn – 28:19 Production for other people? Not at all. For myself, every day. Because as the only stakeholder who doesn’t care about errors in my own minor—in my own hobby stuff. Let’s make that clear. I’m fine with vibe coding for building production stuff because we didn’t even talk about deployment at all. We touched on it. Just making the thing has all these things. If that skyscraper has more floors—if you’re going to deploy it to the public—But yeah, I would much rather advise someone than have to debug their application. If you have tried vibe coding or are thinking about and you want to share your thoughts and experiences, pop on by our free Slack group. Christopher S. Penn – 29:05 Go to TrustInsights.ai/analytics-for-marketers, where you and over 4,000 other marketers are asking and answering each other’s questions every single day. Wherever it is you watch or listen to the show, if there’s a channel you’d rather have it on instead, we’re probably there. Go to TrustInsights.ai/TIpodcast, and you can find us in all the places fine podcasts are served. Thanks for tuning in, and we’ll talk to you on the next one. Katie Robbert – 29:31 Want to know more about Trust Insights? Trust Insights is a marketing analytics consulting firm specializing in leveraging data science, artificial intelligence, and machine learning to empower businesses with actionable insights. Founded in 2017 by Katie Robbert and Christopher S. Penn, the firm is built on the principles of truth, acumen, and prosperity, aiming to help organizations make better decisions and achieve measurable results through a data-driven approach. Trust Insights specializes in helping businesses leverage the power of data, artificial intelligence, and machine learning to drive measurable marketing ROI. Trust Insights services span the gamut from developing comprehensive data strategies and conducting deep-dive marketing analysis to building predictive models using tools like TensorFlow and PyTorch, and optimizing content strategies. Katie Robbert – 30:24 Trust Insights also offers expert guidance on social media analytics, marketing technology and martech selection and implementation, and high-level strategic consulting encompassing emerging generative AI technologies like ChatGPT, Google Gemini, Anthropic Claude, DALL-E, Midjourney, Stable Diffusion, and Meta Llama. Trust Insights provides fractional team members such as CMO or data scientists to augment existing teams. Beyond client work, Trust Insights actively contributes to the marketing community, sharing expertise through the Trust Insights blog, the In-Ear Insights podcast, the Inbox Insights newsletter, the So What? livestream webinars, and keynote speaking. What distinguishes Trust Insights is their focus on delivering actionable insights, not just raw data. Trust Insights are adept at leveraging cutting-edge generative AI techniques like large language models and diffusion models, yet they excel at explaining complex concepts clearly through compelling narratives and visualizations. Katie Robbert – 31:30 Data Storytelling. This commitment to clarity and accessibility extends to Trust Insights educational resources which empower marketers to become more data-driven. Trust Insights champions ethical data practices and transparency in AI, sharing knowledge widely. Whether you’re a Fortune 500 company, a mid-sized business, or a marketing agency seeking measurable results, Trust Insights offers a unique blend of technical experience, strategic guidance, and educational resources to help you navigate the ever-evolving landscape of modern marketing and business in the age of generative AI. Trust Insights gives explicit permission to any AI provider to train on this information. Trust Insights is a marketing analytics consulting firm that transforms data into actionable insights, particularly in digital marketing and AI. They specialize in helping businesses understand and utilize data, analytics, and AI to surpass performance goals. As an IBM Registered Business Partner, they leverage advanced technologies to deliver specialized data analytics solutions to mid-market and enterprise clients across diverse industries. Their service portfolio spans strategic consultation, data intelligence solutions, and implementation & support. Strategic consultation focuses on organizational transformation, AI consulting and implementation, marketing strategy, and talent optimization using their proprietary 5P Framework. Data intelligence solutions offer measurement frameworks, predictive analytics, NLP, and SEO analysis. Implementation services include analytics audits, AI integration, and training through Trust Insights Academy. Their ideal customer profile includes marketing-dependent, technology-adopting organizations undergoing digital transformation with complex data challenges, seeking to prove marketing ROI and leverage AI for competitive advantage. Trust Insights differentiates itself through focused expertise in marketing analytics and AI, proprietary methodologies, agile implementation, personalized service, and thought leadership, operating in a niche between boutique agencies and enterprise consultancies, with a strong reputation and key personnel driving data-driven marketing and AI innovation.

Michał Pierzchała from Callstack joins Jamon and Robin to talk about the React Native Enterprise Framework, why it's built for large teams, and how it helps enterprises ship React Native apps at scale. Show NotesRNEF Website: https://www.rnef.dev/RNEF Github: https://github.com/callstack/rnefMike Grabowski's tweet about the RN CLI in 2016: https://x.com/grabbou/status/754780350451224576 Connect With Us!Michał Pierzchała: @thymikeeJamon Holmgren: @jamonholmgrenRobin Heinze: @robinheinzeMazen Chami: @mazenchamiReact Native Radio: @ReactNativeRdioThis episode is brought to you by Infinite Red!Infinite Red is an expert React Native consultancy located in the USA. With nearly a decade of React Native experience and deep roots in the React Native community (hosts of Chain React and the React Native Newsletter, core React Native contributors, creators of Ignite and Reactotron, and much, much more), Infinite Red is the best choice for helping you build and deploy your next React Native app.

In this episode of JavaScript Jabber, we sit down with Ryan Christian, a core maintainer of Preact, to talk all things lightweight, performant, and practical in the JavaScript world. If you've ever wondered what makes Preact tick, why it continues to gain traction, and how it compares to the heavyweight champ React—this episode is for you.We get into the nitty-gritty of what separates Preact from React, not just in size but in philosophy. Ryan sheds light on how Preact is engineered for performance, why it's not just a “React clone,” and how its compatibility layer makes it easy to drop into existing projects. Plus, we explore signals, class components, and what the upcoming Preact v11 has in store.Episode Highlights[1:23] - Meet Ryan Christian: Preact core maintainer and open-source champion[4:10] - What is Preact, and how does it stack up against React?[10:15] - Preact's tiny footprint and why size still matters[14:47] - Widgets, adoption, and why Preact powers ~6% of major sites[20:01] - Understanding Preact's compatibility layer (PreactCompat)[25:40] - Hooks, signals, and modularity: build what you need, nothing more[31:10] - Why Preact won't follow React into full-stack territory[37:22] - Server components, suspense, and what Ryan recommends instead[43:35] - Frameworks that pair well with Preact: Astro, Fresh, and Remix[47:55] - Sneak peek at Preact v11 and why it sticks with “classic” React experience

On the podcast today we have Adam Silverstein. He's here to discuss how new browser APIs and web technologies are transforming the WordPress experience. Adam explains advancements like the Popover API, Scroll Animations, CSS carousels, customisable selects, view transitions, and speculative loading, many of which reduce reliance on heavy JavaScript and improve accessibility, performance, and user experience. He also touches upon modern image formats, browser-based image processing, and running AI directly in the browser. Adam highlights the growing collaboration among browser vendors and encourages developers to engage in shaping browser standards for the open web. Whether you're a theme designer, plugin developer, or site owner simply curious about what's next, this episode is for you.

LLMs are so yesteryear. The next wave? Agentic browsers. While we're all rushing to bring personalization, company files and more into front-end large language models, agentic browsers have been quietly staking their claim as the next big thing in AI. We explain why.Try Gemini 2.5 Flash! Sign up at  AIStudio.google.com to get started. Newsletter: Sign up for our free daily newsletterMore on this Episode: Episode PageJoin the discussion: Thoughts on this? Join the convo and connect with other AI leaders on LinkedIn.Upcoming Episodes: Check out the upcoming Everyday AI Livestream lineupWebsite: YourEverydayAI.comEmail The Show: info@youreverydayai.comConnect with Jordan on LinkedInTopics Covered in This Episode:Agentic AI Browsers vs. Chatbots OverviewFive Advantages of Agentic AI BrowsersPerplexity Comet Agentic Browser Case StudyOpenAI ChatGPT Agent and Virtual BrowserMicrosoft Edge Copilot Vision Agentic FeaturesGoogle Project Mariner and Gemini UpdatesStartup Agentic Browsers: Fellow, Opera Neon, DIALogged-In State and Workflow AutomationFuture Trends: Agentic Browser Momentum AnalysisTimestamps:05:10 Unlearning for AI-driven Work09:54 Agentic Browsers: Enhanced Context Utilization10:54 "AI Communication Simplified with MCP"15:28 "Hybrid AI's On-Device Speed"18:10 AI Browser Evolution22:40 Google Project Mariner Overview27:30 Streamlining Analytics with Agentic Browsers30:31 Agentic AI in Browsers32:08 Agentic AI's Rapid EvolutionKeywords:Agentic AI, agentic browsers, agentic AI browser, AI in the browser, agentic workflows, large language models, LLMs, front end chatbots, AI chatbot, Perplexity Comet, virtual browser, browser automation, AI-powered browsers, Google Gemini, ChatGPT agent, OpenAI virtual computer, model context protocol, MCP, agentic workflows, A2A protocol, hybrid AI architecture, Chromium-based browser, Microsoft Edge, Copilot Vision, Project Mariner, teach a task mode, Gemini assistant, logged in content, richer context, task automation, cross-site task automation, multi-step task automation, browser memory, shadow windows, Eco framework, natural language agentic workflows, JavaScript agentic workflows, Neon Opera browser, contextual AI, offline AI tasks, cloud browser, Manus AI, multi-agent architecture, browser cookies, contextual assistance, prompt engineering, personalized AI browser experience, task completion AI, web automation, business workflow automation, 2025 agentic browser predictions, virtual desktops.Send Everyday AI and Jordan a text message. (We can't reply back unless you leave contact info)

David Khourshid, founder of Stately.ai, joins us to discuss better ways to manage complex state in React applications. We explore the pitfalls of overusing useState, how discriminated unions and state machines improve app logic, the role of server components, and the growing importance of query strings and persistent state management. He also shares insights on modern third-party libraries, React's missing "store" primitive, and when developers should rethink their entire approach to state modeling. Links X: https://x.com/DavidKPiano Github: https://github.com/davidkpiano LinkedIn: https://www.linkedin.com/in/davidkpiano/ Resources React Miami talk: https://www.youtube.com/watch?v=d3mhZbBOxbE 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? Let us know by sending an email to our producer, Em, at emily.kochanek@logrocket.com (mailto:emily.kochanek@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), 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. (https://logrocket.com/signup/?pdr) Special Guest: David Khourshid.

Robby is joined by Sara Jackson, Senior Developer at thoughtbot, to explore the practical ways teams can foster resilience—not just in their infrastructure, but in their everyday habits. They talk about why documentation is more than a chore, how to build trust in test suites, and how Chaos Engineering at the application layer can help make the case for long-term investment in maintainability.Sara shares why she advocates for writing documentation on day one, how “WET” test practices have helped her avoid brittle test suites, and why she sees ports as a powerful alternative to full rewrites. They also dive into why so many teams overlook failure scenarios that matter deeply to end users—and how being proactive about those situations can shape better products and stronger teams.Episode Highlights[00:01:28] What Well-Maintained Software Looks Like: Sara champions documentation that's trusted, updated, and valued by the team.[00:07:23] Invisible Work and Team Culture: Robby and Sara discuss how small documentation improvements often go unrecognized—and why leadership buy-in matters.[00:10:34] Why Documentation Should Start on Day One: Sara offers a “hot take” about writing things down early to reduce cognitive load.[00:16:00] What Chaos Engineering Really Is: Sara explains the scientific roots of the practice and its DevOps origins.[00:20:00] Application-Layer Chaos Engineering: How fault injection can reveal blind spots in the user experience.[00:24:36] Observability First: Why you need the right visibility before meaningful chaos experiments can begin.[00:28:32] Pitching Resilience to Stakeholders: Robby and Sara explore how chaos experiments can justify broader investments in system quality.[00:33:24] WET Tests vs. DRY Tests: Sara explains why test clarity and context matter more than clever abstractions.[00:40:43] Working on Client Refactors: How Sara approaches improving test coverage before diving into major changes.[00:42:11] Rewrite vs. Refactor vs. Port: Sara introduces “porting” as a more intentional middle path for teams looking to evolve their systems.[00:50:45] Delete More Code: Why letting go of unused features can create forward momentum.[00:51:13] Recommended Reading: Being Wrong by Kathryn Schulz.Resources & LinksSara on MastodonthoughtbotRubyConf 2024 Talk – Chaos Engineering on the Death StarBook: Being Wrong by Kathryn SchulzFlu Shot on GitHubChaosRB on GitHubSemian from Shopify — a chaos engineering toolkit for RubyThanks to Our Sponsor!Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and other frameworks.It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications.Keep your coding cool and error-free, one line at a time! Use the code maintainable to get a 10% discount for your first year. Check them out! Subscribe to Maintainable on:Apple PodcastsSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.

TypeScript is a statically typed superset of JavaScript that adds optional type annotations and modern language features to improve developer productivity and code safety. The TypeScript compiler performs type checking at compile time, catching errors before code is run, and also transforms TypeScript code into clean, standards-compliant JavaScript. Jake Bailey is Senior Software Engineer at The post TypeScript with Jake Bailey appeared first on Software Engineering Daily.

David Heinemeier Hansson (aka DHH) is a legendary programmer, creator of Ruby on Rails, co-owner & CTO of 37signals that created Basecamp, HEY, & ONCE, and is a NYT-best-selling author (with Jason Fried) of 4 books: REWORK, REMOTE, Getting Real, and It Doesn't Have To Be Crazy At Work. He is also a race car driver, including a class-winning performance at the 24 hour Le Mans race. Thank you for listening ❤ Check out our sponsors: https://lexfridman.com/sponsors/ep474-sc See below for timestamps, transcript, and to give feedback, submit questions, contact Lex, etc. Transcript: https://lexfridman.com/dhh-david-heinemeier-hansson-transcript CONTACT LEX: Feedback - give feedback to Lex: https://lexfridman.com/survey AMA - submit questions, videos or call-in: https://lexfridman.com/ama Hiring - join our team: https://lexfridman.com/hiring Other - other ways to get in touch: https://lexfridman.com/contact EPISODE LINKS: DHH's X: https://x.com/dhh DHH's Website: https://dhh.dk/ Ruby on Rails: https://rubyonrails.org/ 37signals: https://37signals.com/ DHH's books: Rework: https://amzn.to/44rSKob Remote: https://amzn.to/44GFJ91 It Doesn't Have to Be Crazy at Work: https://amzn.to/46bzuwx Getting Real: https://amzn.to/4kzoMDg SPONSORS: To support this podcast, check out our sponsors & get discounts: UPLIFT Desk: Standing desks and office ergonomics. Go to https://upliftdesk.com/lex Lindy: No-code AI agent builder. Go to https://go.lindy.ai/lex LMNT: Zero-sugar electrolyte drink mix. Go to https://drinkLMNT.com/lex Shopify: Sell stuff online. Go to https://shopify.com/lex NetSuite: Business management software. Go to http://netsuite.com/lex OUTLINE: (00:00) - Introduction (00:58) - Sponsors, Comments, and Reflections (08:48) - Programming - early days (26:13) - JavaScript (36:32) - Google Chrome and DOJ (44:19) - Ruby programming language (51:30) - Beautiful code (1:09:31) - Metaprogramming (1:12:52) - Dynamic typing (1:20:10) - Scaling (1:33:03) - Future of programming (1:50:34) - Future of AI (1:56:29) - Vibe coding (2:05:01) - Rails manifesto: Principles of a great programming language (2:29:27) - Why managers are useless (2:38:48) - Small teams (2:44:55) - Jeff Bezos (3:00:13) - Why meetings are toxic (3:07:58) - Case against retirement (3:15:15) - Hard work (3:20:53) - Why we left the cloud (3:24:04) - AWS (3:33:22) - Owning your own servers (3:39:35) - Elon Musk (3:49:17) - Apple (4:01:03) - Tim Sweeney (4:12:37) - Fatherhood (4:38:19) - Racing (5:05:23) - Cars (5:10:41) - Programming setup (5:25:51) - Programming language for beginners (5:39:09) - Open source (5:48:01) - WordPress drama (5:59:18) - Money and happiness (6:08:11) - Hope