# devtools Published articles for devtools. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Chrome Adds Experimental Metrics to Measure Website Ad Load DevFeed: [Chrome Adds Experimental Metrics to Measure Website Ad Load]() Original publisher: [Read original article]() Author: Alex Harper Published: 2026-09-17T15:00:00Z Content type: article Language: en Sources: [Web Designer Depot]() Topics: [Chrome](), [Web](), [data](), [User Experience](), [Google](), [developer tooling](), [Core Web Vitals]() Tags: [ad-density](), [ad-performance](), [ad-tech](), [advertising](), [chrome](), [chrome-user-experience-report](), [core-web-vitals](), [crux](), [devtools](), [google](), [google-chrome](), [online-advertising](), [page-experience](), [performance](), [publishers](), [user-experience](), [ux](), [ux-usability](), [web-design](), [web-development](), [web-performance](), [website-ads](), [website-optimization](), [website-performance]() ### AI overview Chrome has introduced four experimental metrics to the Chrome User Experience Report (CrUX) that quantify website ad load: ad count, ad density, network weight, and CPU weight. The aggregated data is public and can be accessed through CrUX Vis, APIs, and Chrome DevTools, although availability and evaluation thresholds remain limited. ### Source excerpt Chrome can now measure exactly how obnoxious a website's ads are, from how much of your screen they swallow to how much data and CPU time they burn. Those ad-stuffed websites can finally be measured, and the results are public. ## Inertia DevTools Now Available for Firefox DevFeed: [Inertia DevTools Now Available for Firefox]() Original publisher: [Read original article]() Author: Paul Redmond Published: 2026-09-17T02:28:55Z Content type: release Language: en Sources: [Laravel]() Topics: [Firefox](), [Browser Extension](), [developer tooling](), [Chrome](), [vs-code](), [phpstorm]() Tags: [chrome-extension](), [devtools](), [editor](), [extension](), [features](), [firefox](), [news](), [panel](), [phpstorm](), [vs-code]() ### AI overview Inertia DevTools is now available as an official Firefox extension with feature parity with the Chrome extension. It records Inertia visits and exposes props, request and response details, routes, controller actions, and page state in a Firefox DevTools panel. Sensitive fields are redacted, and recorded data remains on the local machine. ### Source excerpt Inertia DevTools, the panel for inspecting Inertia.js visits and props, is now on Firefox with the same features as the Chrome extension. The post Inertia DevTools Now Available for Firefox appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox. ## From Chrome DevTools to AI Engineering, with Addy Osmani DevFeed: [From Chrome DevTools to AI Engineering, with Addy Osmani]() Original publisher: [Read original article]() Author: Gergely Orosz Published: 2026-08-19T16:53:57Z Content type: article Language: en Sources: [The Pragmatic Engineer]() Topics: [AI Engineering](), [AI Agent](), [Developer experience](), [Google](), [developer tooling](), [engineering-culture](), [Loop Engineering](), [Chrome]() Tags: [agents](), [ai-agents](), [ai-engineering](), [developer](), [developer-experience](), [devtools](), [engineering](), [google](), [software-engineering](), [workflows]() ### AI overview Addy Osmani discusses his 14 years at Google, including work on Chrome, DevTools, Core Web Vitals, and AI developer experience. The conversation covers AI agents, loop engineering, cognitive surrender, engineering culture, and the broader skills engineers need. ### Source excerpt Addy Osmani shares lessons from 14 years at Google and how AI agents are reshaping software engineering, developer workflows, and the skills engineers need to succeed. ## Building a design system specced for engineers and agents DevFeed: [Building a design system specced for engineers and agents]() Original publisher: [Read original article]() Author: Travis Turner (richardturner@evilmartians.com) Published: 2026-06-17T00:00:00Z Content type: article Language: en Sources: [Evil Martians]() Topics: [Design system](), [User interface design](), [AI-assisted coding](), [cursor](), [Claude]() Tags: [ai](), [ai-assisted-coding](), [claude](), [components](), [cursor](), [design](), [design-system](), [devtools](), [dx](), [figma](), [llms](), [ui-design]() ### AI overview Evil Martians describes how it built a design system for Currents in seven weeks. The system standardized UI decisions and was structured to be readable by engineers and AI-assisted coding tools, including Cursor and Claude, helping the lean team reuse components and maintain a consistent product interface. ### Source excerpt Coding without design guidelines can leave teams with an inconsistent UI design and a complex feature development process. Here's how we built a design system for Currents that's readable by engineers and AI agents. ## Using encapsulated development to code on my phone DevFeed: [Using encapsulated development to code on my phone]() Original publisher: [Read original article]() Published: 2026-05-25T07:00:00Z Content type: article Language: en Sources: [Mary Rose Cook]() Topics: [Development](), [Code](), [test](), [developer tooling]() Tags: [code](), [development](), [devtools](), [test](), [tests]() ### AI overview The author describes using encapsulated development to code on a phone. Each prompt leaves the repository in a known, stable, verified, and stateless condition, supported by refactoring and automated end-to-end testing. ### Source excerpt I'm lucky enough to have a wife, two young children and a job as an AI Engineer at Notion. I'm also lucky enough to have a side project. Some weeks, I'll get half an hour on my laptop to work on this side project. Most weeks, I won't. Yet, I've averaged two commits to the project per day for the last three months. How? By building on my phone. But, really, by making it possible to build on my phone. The broad approach: encapsulated development. Each prompt leaves the repo in a known, stable, verified, stateless condition that permits the next change. Known My mental model of the project is functional enough that I can make future changes. This doesn't mean I understand everything. I may not know the architecture of some parts of the system. I may not know how some implementations work. But I can understand the behavior of those parts of the system as black boxes. For example, I don't know exactly how the particle system stores particles. But I do know that, when it spawns particles, it doesn't allocate new objects. Stable The quality of the software must be high enough for the next change to be successful. This means well factored, working code. Sometimes, the project will start to crumble with the accumulation of low quality code. I do a string of refactors to get things back on track, then start building features again. Verified Every change must be correct. I don't have time to manually test changes. The kettle has just finished boiling. Incorrect changes build into a wobbly tower. Each prompt must include how it will be verified as correct. This usually means end-to-end tests. For a web app, this might mean having Chrome DevTools actually click through the UI to check it works. Or spinning up the API and checking that inputs produce the expected outputs. Or going full ~StrongDM~ and implementing the external services the product interacts with. In my case, I'm working on a tool for making video games. So I built a headless version of my engine. Test code can ini ## Author Announces Joining GitHub DevFeed: [Author Announces Joining GitHub]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2026-03-31T00:00:00Z Content type: opinion Language: en Sources: [Carlos Becker]() Topics: [GitHub](), [developer tooling]() Tags: [announcement](), [devtools](), [github]() ### AI overview The author announces that they are joining GitHub after building developer tools throughout their career, including work at GoReleaser and Charm. ### Source excerpt On to the next thing! ## A Visual Feedback Loop for Electron Apps with Claude Code DevFeed: [A Visual Feedback Loop for Electron Apps with Claude Code]() Original publisher: [Read original article]() Published: 2026-03-06T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Electron](), [Agent Browser](), [Claude Code](), [Protocol (disambiguation)](), [Tooling](), [Command-line interface](), [Chromium]() Tags: [agent-browser](), [chromium](), [claude-code](), [cli](), [devtools](), [electron](), [nx](), [protocol](), [tooling]() ### AI overview This tutorial explains how to give Claude Code visual feedback when building Electron applications. It uses agent-browser and the Chrome DevTools Protocol to connect to a running Electron app, capture screenshots, inspect the DOM, and verify that the rendered interface works. The article covers installing the required tooling, enabling CDP, configuring electron-vite and Nx development scripts, and checking the CDP endpoint. ### Source excerpt A Visual Feedback Loop for Electron Apps with Claude Code When building Electron apps with an AI coding agent, you run into a fundamental problem: the agent can't see what it's building. It writes code, runs the build, maybe checks the logs, but never actually looks at the rendered UI. If the window is blank or the layout is broken, it has no way to know. I found a way to close that gap using agent-browser and Chrome DevTools Protocol (CDP). ## Next.js 16 DevFeed: [Next.js 16]() Original publisher: [Read original article]() Author: Tim Neutkens Published: 2025-10-21T20:00:00Z Content type: release Language: en Sources: [Next.js Blog]() Topics: [Next.js](), [Caching](), [Compiler](), [Routing (disambiguation)](), [React](), [Model Context Protocol]() Tags: [caching](), [compiler](), [devtools](), [model-context-protocol](), [next-js](), [react](), [release](), [routing]() ### AI overview Next.js 16 is a release featuring Cache Components, stable Turbopack, file system caching, React Compiler support, smarter routing, updated caching APIs, React 19.2 features, and Next.js Devtools MCP integration. ### Source excerpt Next.js 16 includes Cache Components, stable Turbopack, file system caching, React Compiler support, smarter routing, new caching APIs, and React 19.2 features. ## Using Gemini CLI as an AI Coding Copilot DevFeed: [Using Gemini CLI as an AI Coding Copilot]() Original publisher: [Read original article]() Author: Yonatan (Yoni) Levin Published: 2025-06-25T15:27:03Z Content type: opinion Language: en Sources: [Stories by Yonatan V. Levin on Medium]() Topics: [AI Agent](), [AI Development](), [genai]() Tags: [ai-agent](), [ai-development](), [co-pilot](), [devtools](), [gemini](), [gemini-cli](), [genai](), [llm]() ### AI overview The author introduces an opinion piece about using Gemini CLI for software development, drawing on work at a startup that uses LLMs and other AI technologies. ### Source excerpt After a long break and a lot of life happening all at once, I'm back. Why? Because so much exciting stuff has happened that I just need to spit it out. It's going to be a long article, so prepare a good cup of coffee & a couple of cookies. Today, we're diving deep into something that I believe is the future of how we build software: the Gemini CLI. At least, until the next amazing thing comes along and reshapes our industry all over again. :) The Backstory: A New Mission and a Brick Wall For those who don't know me, my name is Yonatan, but friends call me Yoni. My career has been a wild ride: from low-level hardware development to leading Android teams, then switching to the backend to build the Public API for monday.com, and finally, leading AI development with the explosion of GenAI. Someone once joked that my career is just a series of abbreviations: Android -> API -> AI. About a year ago, after an incredible six-year journey, I left monday.com. After taking some time to breathe, I teamed up with two amazing people, Limor and Eyal, to start a new adventure: a startup called Wisdom. Our mission is to help people become wiser and happier by transforming how they interact with the profound knowledge tucked away in self-development books. We want to transform passive reading into an active, life-changing experience, bridging the gap between knowing something and truly living it. A few weeks ago, we launched our first closed alpha version with a chosen book authors. Our tech stack is a beast: various LLMs, Knowledge Graphs, audio models, and a ton of custom heuristics. And, of course, the standard stuff -- Node.js servers and React for our websites. We started, as most do, with a prototype. Something to show investors and our first potential customers. But I hit a brick wall. Hard. Despite my vast experience, my front-end knowledge was practically zero. I knew some basic HTML and CSS, but that was it. How was I, a backend and AI guy, supposed to build the face of our pro ## What's new in Apollo Client 3.11 DevFeed: [What's new in Apollo Client 3.11]() Original publisher: [Read original article]() Author: Jerel Miller Published: 2024-07-23T11:21:52Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [apollo-client](), [React](), [Developer Tools]() Tags: [apollo-client](), [devtools](), [improvements](), [react](), [release](), [subscriptions]() ### AI overview Apollo Client 3.11 introduces subscription API improvements, support for React 19 release candidate versions, improved React Compiler support, new Apollo Client Devtools options, and a transition from experimental schema testing utilities to the @apollo/graphql-testing-library package. ### Source excerpt With the release of Apollo Client 3.11, we're excited to announce a number of features and improvements. Here is what you can expect in Apollo Client 3.11: - A number of improvements to Apollo Client's subscription APIs such as access to in Suspense-enabled hooks, the ability to forward extensions in , a new option for , and a new function for . - Support for React 19 release candidate versions with improved React Compiler support. - New Apollo Client Devtools options. ## Measuring and analyzing the KotlinJS bundle size - Gustavo Fão Valvassori DevFeed: [Measuring and analyzing the KotlinJS bundle size - Gustavo Fão Valvassori]() Original publisher: [Read original article]() Published: 2024-02-16T00:00:00Z Content type: tutorial Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [kotlinjs](), [Webpack](), [JavaScript](), [Web Development]() Tags: [analyze](), [article](), [devtools](), [gradle](), [gradle-plugin](), [javascript](), [kotlin-js](), [kotlinjs](), [lighthouse](), [measuring](), [performance]() ### AI overview This tutorial explains how KotlinJS projects are compiled into JavaScript and bundled with Webpack. It presents two ways to measure and analyze bundle size: examining source maps with SourceMapExplorer or Chrome Lighthouse, and using WebpackBundleAnalyzer. ### Source excerpt Smaller JavaScript bundle size helps improve a website's loading speed and performance. In this article, we present two different ways of analyzing and measuring KotlinJS bundle size. ## Dark Theme - CSS Migration DevFeed: [Dark Theme - CSS Migration]() Original publisher: [Read original article]() Author: Zaid Daba'een Published: 2023-07-06T11:19:48Z Content type: tutorial Language: en Sources: [DeveloperHub.io]() Topics: [Dark Mode](), [CSS](), [modern web development](), [developer tooling]() Tags: [branding](), [css](), [dark-mode](), [devtools](), [migration](), [variables]() ### AI overview This tutorial explains DeveloperHub's new dark theme, including how to enable it, add a reader theme toggle, test it with DevTools, migrate custom CSS, and customize colors with CSS variables. ### Source excerpt Dark theme is out now! Let those eyes rest. ## Encore's approach to simplifying backend development and DevOps DevFeed: [Encore's approach to simplifying backend development and DevOps]() Original publisher: [Read original article]() Author: Marcus Kohlberg Published: 2023-04-25T00:00:00Z Content type: opinion Language: en Sources: [Encore Updates]() Topics: [developer tooling](), [DevOps](), [backend-development](), [distributed-systems](), [software-development](), [Spotify]() Tags: [backend](), [development](), [devops](), [devtools](), [distributed](), [software-development](), [streaming]() ### AI overview A former Spotify engineer compares the music industry's transformation through streaming with current challenges in software development and DevOps. The article presents Encore as a development platform intended to reduce backend complexity and automate infrastructure and distributed-systems overhead through a standardized approach. ### Source excerpt Transforming development and DevOps like we did the music industry ## Nuxt 3.0.0 Stable Release Introduces Vite, Vue 3, Nitro, and TypeScript Support DevFeed: [Nuxt 3.0.0 Stable Release Introduces Vite, Vue 3, Nitro, and TypeScript Support]() Original publisher: [Read original article]() Published: 2022-11-16T00:00:00Z Content type: release Language: en Sources: [The Nuxt Blog]() Topics: [Nuxt.js](), [releases](), [Framework](), [Vite](), [Vue.js](), [Node.js](), [TypeScript](), [browser](), [Edge](), [Firefox](), [developer tooling](), [Testing]() Tags: [announce](), [browser](), [deployment](), [devtools](), [edge](), [firefox](), [framework](), [node-js](), [nuxt](), [release](), [releases](), [testing](), [typescript](), [vite](), [vue]() ### AI overview Nuxt announces the first stable release of Nuxt 3.0.0, a rewrite based on Vite, Vue 3, and Nitro with first-class TypeScript support. The release includes a production-ready API, more than 50 supported modules, evergreen-browser support, and support for Node.js 14, 16, 18, and 19. ### Source excerpt We are thrilled to announce the first stable version of Nuxt 3.0.0 ## A personal update on DevRel, Chrome DevTools, and frontend work DevFeed: [A personal update on DevRel, Chrome DevTools, and frontend work]() Original publisher: [Read original article]() Author: Paul Lewis Published: 2022-06-18T00:00:00Z Content type: opinion Language: en Sources: [Paul Lewis]() Topics: [developer tooling](), [devrel](), [Front end](), [TypeScript](), [Web Components](), [modules](), [Svelte](), [GSAP]() Tags: [animation](), [devrel](), [devtools](), [frontend](), [gsap](), [longtimenospeak](), [svelte](), [typescript](), [update]() ### AI overview A personal update covering the author's move from Google DevRel through DeepMind, Chrome, and Chrome DevTools, including migrations to ES Modules, TypeScript, and Web Components. It also discusses leaving Google, working at Spotify, FLIP animations, and completing a philosophy master's degree. ### Source excerpt I suppose it's time I responded... ## Backing up your content from Google Photos DevFeed: [Backing up your content from Google Photos]() Original publisher: [Read original article]() Author: Harsh Shandilya Published: 2022-04-04T06:30:00Z Content type: tutorial Language: en Sources: [Posts on Harsh Shandilya]() Topics: [Google](), [data](), [Chrome](), [Protocol (disambiguation)](), [Linux]() Tags: [archive](), [archiving](), [backing-up](), [backup](), [chrome](), [devtools](), [google](), [google-photos](), [gphotos-cdp](), [linux](), [nas](), [photos]() ### AI overview A tutorial on using gphotos-cdp to automate archiving images from Google Photos while retaining their EXIF metadata. The tool drives Google Chrome through the Chrome DevTools Protocol and is described as tested on Linux. ### Source excerpt Putting your media into Google Photos is easy, taking it out, not as much. ## New Terminal Output & Performance Improvements in Nx 13.5 DevFeed: [New Terminal Output & Performance Improvements in Nx 13.5]() Original publisher: [Read original article]() Author: Juri Strumpflohner Published: 2022-01-25T00:00:00Z Content type: release Language: en Sources: [Juri Strumpflohner]() Topics: [Terminal](), [Caching](), [Chrome](), [developer tooling](), [Command-line interface](), [Graphs]() Tags: [cache](), [chrome](), [devtools](), [dx](), [feature](), [improvements](), [nx](), [performance](), [profiling](), [terminal](), [visualization]() ### AI overview Nx 13.5 introduces dynamic terminal output that separates completed and running tasks while showing errors immediately. The release also reports performance improvements, continued caching of full terminal output, and Chrome DevTools profiling support for Nx commands. ### Source excerpt Nx 13.5 brings a new dynamic terminal output, 2.3x faster operations, Chrome DevTools profiling support, and improved project graph visualization. ## 2021 in Review DevFeed: [2021 in Review]() Original publisher: [Read original article]() Published: 2021-12-31T00:00:00Z Content type: opinion Language: en Sources: [Una Kravets]() Topics: [CSS](), [Web platform](), [Developer Tools](), [web design]() Tags: [css](), [design](), [devtools](), [review](), [web-platform]() ### AI overview A personal review of 2021 covering major life events, health and financial challenges, content production, podcasts, video projects, and the launch of Designcember. It reports audience figures and highlights CSS, DevTools, responsive web design, and web platform content. ### Source excerpt Reviewing 2021's highs, lows, and everything in between. ## Before You memo() DevFeed: [Before You memo()]() Original publisher: [Read original article]() Published: 2021-02-23T00:00:00Z Content type: tutorial Language: en Sources: [Dan Abramov]() Topics: [React](), [developer tooling](), [Development]() Tags: [devtools](), [performance](), [react]() ### AI overview This article explains two React rendering optimization techniques: moving state closer to the components that use it and splitting components so unaffected subtrees can be passed as JSX content. It also recommends verifying production builds, keeping state low in the tree, and using the React DevTools Profiler. ### Source excerpt Rendering optimizations that come naturally. ## NodeJS 内存泄漏检测与定位 DevFeed: [NodeJS 内存泄漏检测与定位]() Original publisher: [Read original article]() Author: Joway Published: 2019-11-10T00:00:00Z Content type: tutorial Language: zh Sources: [Random Thoughts]() Topics: [Node.js](), [developer tooling](), [Chrome](), [bug]() Tags: [bug](), [chrome](), [comparison](), [devtools](), [dump](), [nodejs](), [object](), [snapshot](), [string](), [tech]() ### AI overview This Chinese tutorial documents diagnosing and locating a Node.js memory leak using heapdump files and Chrome DevTools. It explains how to obtain heap snapshots, compare snapshots over time, and inspect object references and retained size while noting that increased memory or retained size alone does not conclusively prove a leak. ### Source excerpt 最近解决了一个 Node.JS 应用内存泄漏 Bug，顺便学会了用 Chrome DevTools 去看 heapdump 文件。这里做一些简单的记录。 如何「优雅地」获得 heapdump 文件 由于我们所有应用都是以容器部署的，所以要去获得某个容器内的文件，并拷贝到本地难度还是比较大，也非常麻烦。考虑到调试时或许会需要下载非常多次的 snapshot 文件，建议可以包下 heapdump 库，做成一个接口，把文件 dump 之后再传输给客户端，这样一劳永逸。 ## Debugging Angular Ivy Applications from the Devtools Console DevFeed: [Debugging Angular Ivy Applications from the Devtools Console]() Original publisher: [Read original article]() Published: 2019-09-25T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Angular](), [Tooling](), [browser](), [Document Object Model (DOM)]() Tags: [angular](), [browser](), [chrome](), [commands](), [debugging](), [devtools](), [rxjs](), [state]() ### AI overview This tutorial explains how Angular Ivy exposes APIs that let developers inspect and interact with component state from the browser's DevTools console. It demonstrates selecting an Angular component in Chrome DevTools, accessing it through the console, invoking component functions, and notes that NgProbe is not supported by Ivy. ### Source excerpt Lorem ipsum dolor sit amet ## \[object ErrorEvent\] thrown by Karma in Angular Unit Tests DevFeed: [\[object ErrorEvent\] thrown by Karma in Angular Unit Tests]() Original publisher: [Read original article]() Published: 2018-07-25T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Angular](), [debugging](), [Angular CLI](), [Chrome]() Tags: [angular](), [chrome](), [debug](), [debugging](), [devtools](), [how-to](), [rxjs](), [tests](), [unit-tests]() ### AI overview This tutorial explains how to diagnose the "[object ErrorEvent] thrown by Karma" message when running Angular unit tests. It recommends debugging with Chrome DevTools and disabling source maps with an Angular CLI flag when source maps contribute to cryptic errors. ### Source excerpt Lorem ipsum dolor sit amet ## Improved Apollo Client Devtools DevFeed: [Improved Apollo Client Devtools]() Original publisher: [Read original article]() Author: James Baxley III Published: 2018-02-01T21:53:00Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [apollo-client](), [Tooling](), [GraphQL](), [Cache](), [Chrome]() Tags: [announcement](), [apollo](), [apollo-client](), [cache](), [chrome](), [dark-mode](), [debugging](), [devtools](), [graphql](), [new-features](), [subscriptions]() ### AI overview Apollo announces an improved version of Apollo Client Devtools for Chrome, with a more stable architecture, better performance, improved dark mode, GraphQL subscription support in GraphiQL, and initial client-side schema support. ### Source excerpt One of my favorite parts of the Apollo ecosystem are the Apollo Devtools. What started as a hack week project for the core team turned into a pretty amazing way to debug and understand what is happening in an Apollo Client-driven app. The integrated GraphiQL, list of active operations, and cache inspector are all invaluable tools for digging around the data your app is using. Today I'm super excited to showcase a couple new features we've added and give you a taste of what is to come! ## Apollo interns on GraphQL Radio DevFeed: [Apollo interns on GraphQL Radio]() Original publisher: [Read original article]() Author: Sashko Stubailo Published: 2017-08-22T17:58:00Z Content type: article Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [apollo-client](), [developer tooling](), [Scala](), [JavaScript]() Tags: [apollo](), [code-generation](), [community](), [devtools](), [graphql](), [javascript](), [scala]() ### AI overview An Apollo blog post introduces three interns who appeared on GraphQL Radio and describes their summer work on Apollo open source projects, including GraphQL subscriptions, the Apollo Client cache API, Scala.js code generation, and Apollo Client Devtools. ### Source excerpt One of my favorite times of year at the office is when the interns join us for the summer. This summer was the biggest group of interns yet, with 6 interns working on open source and commercial products at MDG. Three of the interns -- Shadaj, Ramya, and Evans -- were working on Apollo open source technology, and so Abhi and Nikolas from GraphQL Radio suggested they come on the show to round out the summer. Watch the episode below or listen on Soundcloud! [Next page]()