# dogfooding Published articles for dogfooding. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How Lovable Migrated lovable.dev from Next.js to TanStack Start DevFeed: [How Lovable Migrated lovable.dev from Next.js to TanStack Start]() Original publisher: [Read original article]() Author: Alexandre Zajac Published: 2026-08-24T15:30:50Z Content type: article Language: en Sources: [Hungry Minds]() Topics: [Next.js](), [Development](), [Software Engineering](), [dogfooding](), [Vercel](), [TypeScript]() Tags: [adapter-pattern](), [development](), [dogfooding](), [framework](), [next-js](), [software-engineering](), [trends](), [typescript](), [vercel]() ### AI overview The article describes Lovable's migration of lovable.dev from Next.js on Vercel to TanStack Start. It outlines a gradual rollout using parallel routing and feature flags, route grouping, shared framework-agnostic code, adapters, and AI-assisted migration. ### Source excerpt PLUS: Semantic layer at PostHog 🏗, AliExpress fingerprinting 🔎 , Git serving rebuilt at Datadog 📈 ## Dogfooding vs. QA vs. User Research DevFeed: [Dogfooding vs. QA vs. User Research]() Original publisher: [Read original article]() Author: Therese Fessenden Published: 2026-08-07T17:00:00Z Content type: article Language: en Sources: [NN/g latest articles and announcements]() Topics: [dogfooding](), [FIRST]() Tags: [article](), [bugs](), [development](), [dogfooding](), [qa](), [qc](), [quality-assurance](), [quality-control](), [user-research](), [user-testing]() ### AI overview Dogfooding--using a company's own products internally--can reveal bugs, broken flows, crashes, and missing features while building empathy and shared ownership. The article explains that it complements but cannot replace user research, because insiders understand the product too well to represent real users. It also distinguishes genuine dogfooding from performative displays of loyalty. ### Source excerpt Dogfooding, or using your own products internally, helps catch bugs, but it can't replace user research: your team knows too much to represent real users. ## How We Use Our Own Developer Portal DevFeed: [How We Use Our Own Developer Portal]() Original publisher: [Read original article]() Author: Mor Paz Published: 2026-07-22T11:37:29Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [Developer experience](), [dogfooding](), [internal developer platform](), [Deployment](), [code productivity](), [observability](), [Microservices](), [dashboards]() Tags: [dashboards](), [deployment](), [developer-experience](), [developer-portal](), [dogfooding](), [internal-developer-platform](), [internal-developer-portal](), [microservices](), [observability](), [productivity]() ### AI overview This article explains how Port uses its own internal developer portal as a form of dogfooding to improve developer experience and productivity. It describes the portal's software catalog and several use cases, with particular focus on deployment tracking and environment locks. ### Source excerpt How we use our internal developer portal for a better developer experience and productivity - specifically for deployment tracking and environment locks ## Dogfooding the Billable Actions metric: How granular observability improved our metering validation DevFeed: [Dogfooding the Billable Actions metric: How granular observability improved our metering validation]() Original publisher: [Read original article]() Author: Eric Chen Published: 2026-06-25T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [observability](), [dashboards](), [Cloud](), [API](), [Server](), [Time Series](), [benchmarking]() Tags: [account](), [api](), [cloud](), [cost](), [count](), [dashboard](), [dashboards](), [dogfooding](), [metric](), [observability](), [optimization](), [query](), [raw](), [server](), [temporal-voices](), [time-series](), [validation](), [visibility]() ### AI overview Temporal describes how its Billable Actions metric and OpenMetrics per-type breakdowns provide more granular cost visibility. Internally, the company uses the metric with a canary account and validation dashboards to verify metering accuracy, troubleshoot discrepancies, and identify optimization opportunities. ### Source excerpt See how Temporal uses the Billable Actions metric internally to validate metering, troubleshoot discrepancies, and improve cost observability. ## PM Brain OS: The Second Brain for Product Managers, Made of Markdown DevFeed: [PM Brain OS: The Second Brain for Product Managers, Made of Markdown]() Original publisher: [Read original article]() Author: Paweł Huryn Published: 2026-05-20T13:09:25Z Content type: tutorial Language: en Sources: [The Product Compass]() Topics: [Claude Code](), [MDX](), [Open Source]() Tags: [audit-trail](), [claude](), [claude-code](), [dogfooding](), [markdown](), [open-source](), [provenance](), [rag](), [repo]() ### AI overview The article presents PM Brain, an open-source second-brain system for product managers built from Markdown files in a Git repository. Claude reads and updates the files according to a CLAUDE.md operating manual, while weekly sweeps promote recurring, decision-relevant, or strategy-relevant information into a durable layer. The system intentionally avoids vector databases, embeddings, cloud storage, and automatic tagging, and includes installation guidance, commands, architecture details, provenance, and evaluation results. ### Source excerpt A folder of files on your laptop. Claude reads them before answering, writes to them after, sweeps them every Friday. Open source. 17 synthetic PM scenarios, 404 of 406 checks pass (~=99.5%). ## New Initializr and Build Server Migration Plan DevFeed: [New Initializr and Build Server Migration Plan]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-02-21T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [migration](), [Tooling](), [Deployment](), [Dark Mode](), [GitHub](), [ui](), [User Experience]() Tags: [android](), [dark-mode](), [deployment](), [dogfooding](), [github](), [infrastructure](), [ios](), [migration](), [server](), [tooling](), [ui](), [update](), [user-experience](), [ux-improvements]() ### AI overview Codename One announces a new Initializr built with Codename One that runs on the client machine and no longer depends on a backend service. The article also outlines staged Android and iOS build server upgrades, with Android beginning February 27-28, 2026, and iOS beginning March 5, 2026. ### Source excerpt We are launching a new Codename One Initializr and sharing the staged migration plan for Android and iOS build servers. ## Next.js 16.1 DevFeed: [Next.js 16.1]() Original publisher: [Read original article]() Author: Tim Neutkens Published: 2025-12-18T20:00:00Z Content type: release Language: en Sources: [Next.js Blog]() Topics: [Next.js](), [Caching](), [Tooling](), [debugging](), [Node.js](), [Core Web Vitals]() Tags: [caching](), [core](), [core-web-vitals](), [debugging](), [development](), [dogfooding](), [github](), [next-js](), [node](), [node-js]() ### AI overview Next.js 16.1 improves development workflows and stability through stable, default-on Turbopack file system caching, an experimental bundle analyzer, easier Node.js debugging, and better handling of transitive external dependencies. ### Source excerpt Next.js 16.1 introduces Turbopack file system caching for development, a new bundle analyzer, and easier debugging in Node.js. ## Shifting Left: Why I'm Building at Chainguard DevFeed: [Shifting Left: Why I'm Building at Chainguard]() Original publisher: [Read original article]() Published: 2025-09-30T00:00:00Z Content type: opinion Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [Security](), [Developer experience](), [dogfooding]() Tags: [chainguard](), [chainguard-containers](), [chainguard-jobs](), [chainguard-libraries](), [chainguard-product-organization](), [chainguard-vms](), [developer](), [developer-experience](), [dogfooding](), [security]() ### AI overview Chainguard SVP of Product Patrick Donahue explains why he joined Chainguard, connecting his security and infrastructure experience with the company's goal of reducing engineering toil and helping developers build on a trusted foundation. ### Source excerpt Chainguard SVP of Product Patrick Donahue shares why he is excited to join Chainguard and how he plans to help build products developers love. ## Founder Mode: How Windsurf builds product, from 0 to 1M users DevFeed: [Founder Mode: How Windsurf builds product, from 0 to 1M users]() Original publisher: [Read original article]() Author: Tiffany Chen Published: 2024-12-03T00:00:00Z Content type: opinion Language: en Sources: [Mintlify Blog]() Topics: [Development](), [dogfooding](), [Agentic development](), [developer tooling](), [GitHub Copilot](), [Visual Studio Code]() Tags: [agentic](), [agentic-development](), [article](), [discord](), [dogfooding](), [for-founders](), [github](), [github-copilot](), [vscode]() ### AI overview Kevin Hou describes how Windsurf, formerly Codeium, grew from an initial VS Code extension into a product used by more than one million users. The article attributes this growth to a free-first strategy, user feedback, dogfooding, vertical integration, and a focus on agentic development tools. ### Source excerpt [Note: This was published under Codeium, but the company has since rebranded to Windsurf. Edits have been made accordingly.] ## Behind the scenes: Launching On-call DevFeed: [Behind the scenes: Launching On-call]() Original publisher: [Read original article]() Author: Henry Course Published: 2024-07-09T14:33:22Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [dogfooding](), [incident](), [changelog]() Tags: [building](), [company](), [dogfooding](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [launch](), [on-call](), [outage](), [post-mortem](), [product-launch](), [slack-incident](), [support](), [testing](), [updates]() ### AI overview The article describes how incident.io developed and launched its On-call product in private over nine months. The team adapted its rapid-release culture, used internal dogfooding and company-wide feedback, and strengthened reliability, support, and product-response processes to handle the launch. ### Source excerpt We like to ship it then shout about it, all the time. Building On-call was different. ## Launching a Quadratic Funding round for SEA communities DevFeed: [Launching a Quadratic Funding round for SEA communities]() Original publisher: [Read original article]() Author: Devcon Published: 2024-06-14T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Open Source]() Tags: [announce](), [community](), [devcon](), [dogfooding](), [ethereum](), [events](), [funding](), [open-source](), [southeast-asia]() ### AI overview The Devcon team announces a quadratic funding round for Southeast Asian Ethereum communities organized with clr.fund, contributing $30,000 to the matching pool. The article also highlights local Road to Devcon activities and ways to participate. ### Source excerpt Dear Ethereum explorers, Announcements are coming one after another as we get closer to Devcon. Today we're thrilled to announce the launch of a quadratic funding round for SEA communities by clr.fund! We see the excitement and grassroots energy in Southeast Asia growing and have witness... ## Maximizing availability with Multi-region Namespaces DevFeed: [Maximizing availability with Multi-region Namespaces]() Original publisher: [Read original article]() Author: Nikitha Suryadevara Published: 2024-06-03T06:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [Availability](), [Cloud](), [Replication](), [reliability](), [migration](), [Deployment]() Tags: [announcements](), [availability](), [cloud](), [deployment](), [dogfooding](), [durability](), [failover](), [incident](), [preview](), [public](), [region](), [reliability]() ### AI overview Temporal introduces Multi-region Namespaces, formerly called Global Namespaces, in Public Preview. The feature uses active-standby replication across user-defined regions and automated failover to support 99.99% availability for critical workloads. ### Source excerpt Now in Public Preview: Multi-region Namespaces (formerly Global Namespaces) enable seamless failover and 99.99% availability--no manual config required. ## Exploring Support Tooling at Supabase: A Dive into SLA Buddy DevFeed: [Exploring Support Tooling at Supabase: A Dive into SLA Buddy]() Original publisher: [Read original article]() Author: Rodrigo Mansueli Published: 2024-04-25T07:00:00Z Content type: article Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [Support](), [Tooling](), [dogfooding](), [Slack](), [Database](), [PostgreSQL]() Tags: [blog-post](), [compliance](), [database](), [dogfooding](), [integration](), [management](), [monitors](), [operations](), [post](), [postgresql](), [slack](), [support](), [tool](), [tooling](), [tools]() ### AI overview This article explores Supabase's SLA Buddy, an internal support tool for enforcing service-level agreements. It describes how the tool uses Slack reminders, calendar checks, PostgreSQL functions, Edge Functions, and Slack threads to monitor deadlines, coordinate support responses, and manage escalations. The article also explains how dogfooding Supabase's own tools contributed to SLA Buddy's development. ### Source excerpt In this post, we explore the support tooling at Supabase, and how we use SLA Buddy to monitor our SLAs. ## Recapping our live event: On-call as it should be, present and future DevFeed: [Recapping our live event: On-call as it should be, present and future]() Original publisher: [Read original article]() Author: incident.io Published: 2024-04-19T17:24:52Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [incident](), [Slack](), [dogfooding]() Tags: [dogfooding](), [engineering](), [event](), [feature](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [launch](), [outage](), [overview](), [post-mortem](), [slack](), [slack-incident]() ### AI overview This article recaps a live virtual event about incident.io's On-call product. It explains why the company built the product, describes its six-month preparation and customer beta testing, and highlights foundations such as scheduling and escalation paths alongside features like Slack shift-change announcements. ### Source excerpt We recently hosted the live event On-call as it should be, present and future. Now, you can read the high-level overview, in addition to watching the full recording. ## The Astro Developer Portal DevFeed: [The Astro Developer Portal]() Original publisher: [Read original article]() Author: Elian Van Cutsem Published: 2024-03-13T00:00:00Z Content type: article Language: en Sources: [The Astro Blog]() Topics: [Astro](), [internal developer portal](), [Astro DB](), [dogfooding](), [web applications](), [Pull Request]() Tags: [astro](), [astro-db](), [bugs](), [build](), [building](), [catalog](), [community](), [content](), [core](), [creators](), [database](), [developer-portal](), [developers](), [discord](), [dogfooding](), [feature](), [integration](), [platform](), [themes](), [update]() ### AI overview Astro launches a Developer Portal for theme authors to submit, manage, and promote Astro themes. The portal replaces a manual catalog workflow and uses Astro Studio and Astro DB within an Astro web application to streamline approvals and updates. ### Source excerpt Today, we're launching the Astro Developer Portal, a platform where theme authors can submit, manage, and promote their themes built for Astro. ## Running projects for AI features DevFeed: [Running projects for AI features]() Original publisher: [Read original article]() Author: Aaron Sheah Published: 2024-01-23T13:00:00Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [Artificial Intelligence](), [Large Language Model](), [OpenAI](), [data](), [dataset](), [incident]() Tags: [ai](), [article](), [blog](), [building](), [data](), [dogfooding](), [experimental](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [llms](), [openai](), [outage](), [post-mortem](), [production](), [slack-incident](), [technical]() ### AI overview This article explains how AI feature projects differ from typical software projects. It recommends an experimental process: validate LLM capabilities with proof-of-concepts and historical data, iterate quickly, delay UI work, and then dogfood an early production MVP to gather feedback before investing in the full feature. ### Source excerpt In this article, Aaron the Technical Lead for the Post-incident team highlights the differences of running projects for AI powered features ## Introducing FeedFlow, a minimalistic and opinionated RSS Reader DevFeed: [Introducing FeedFlow, a minimalistic and opinionated RSS Reader]() Original publisher: [Read original article]() Author: Marco Gomiero Published: 2023-07-31T00:00:00Z Content type: release Language: en Sources: [Posts on Marco Gomiero]() Topics: [RSS Feed](), [App](), [multiplatform](), [Compose](), [compose-for-desktop](), [Kotlin](), [Kotlin Multiplatform](), [SwiftUI](), [dogfooding]() Tags: [android](), [article](), [compose-multiplatform](), [dogfooding](), [ios](), [kotlin](), [kotlin-multiplatform](), [macos](), [release](), [rss](), [swiftui]() ### AI overview The article announces FeedFlow, a minimalistic RSS reader built for Android, iOS, and macOS. It opens articles on their respective websites, supports OPML imports, and was created partly to dogfood the RSSParser Android library. ### Source excerpt After months of work, I can finally announce the release of FeedFlow, a minimalistic and opinionated RSS Reader that I've built for myself and that's now available on Android, iOS, and macOS. Motivation I've started (again) to stay up to date by building my own feed instead of relying on feeds ordered and decided by someone else. But I wasn't completely satisfied with the readers already out there ("I can build a better one"™). What I want for an RSS reader is the possibility of easily going through my feed and being able to open the article that I want to read on the respective website. Yes, you read it right. ## Multi-factor Authentication via Row Level Security Enforcement DevFeed: [Multi-factor Authentication via Row Level Security Enforcement]() Original publisher: [Read original article]() Author: Joel Lee; Kang Ming Tay; Stojan Dimitrovski Published: 2022-12-14T07:00:00Z Content type: article Language: en Sources: [Supabase Blog]() Topics: [MFA](), [Authentication](), [Security](), [Supabase](), [QR Code](), [SVG](), [Single sign-on (SSO)]() Tags: [auth](), [authentication](), [code](), [dogfooding](), [event](), [feature](), [flow](), [generate](), [identity](), [mfa](), [password](), [passwords](), [security](), [sso](), [svg](), [verification](), [verify]() ### AI overview Supabase introduces multi-factor authentication for all users and describes its implementation with Time-Based One Time Passwords (TOTP). The article explains enrollment, QR-code setup, challenge creation, and verification using six-digit codes, and mentions Single Sign On (SSO) on the dashboard as preparation for SAML. ### Source excerpt MFA Auth with enforcement via RLS ## Investigating Performance Bottlenecks With SQL & Statistics DevFeed: [Investigating Performance Bottlenecks With SQL & Statistics]() Original publisher: [Read original article]() Author: Xoel López Published: 2020-12-15T00:00:00Z Content type: opinion Language: en Sources: [Tinybird]() Topics: [SQL](), [dogfooding](), [Statistics](), [Google]() Tags: [customers](), [dogfooding](), [google](), [performance](), [product](), [scalable-analytics-architecture](), [sql](), [statistics]() ### AI overview The article describes investigating performance bottlenecks with the publisher's own product, SQL, statistics, and Google Sheets. It says dogfooding can reveal problems that customers do not report. ### Source excerpt We investigate performance bottlenecks using our own product and Google Sheets. Dogfooding reveals problems customers never report. ## Devcon: What is Ahead DevFeed: [Devcon: What is Ahead]() Original publisher: [Read original article]() Author: Devcon Published: 2020-03-02T00:00:00Z Content type: opinion Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Blockchain](), [dogfooding]() Tags: [blockchain](), [collaboration](), [community](), [conference](), [devcon](), [dogfooding](), [event](), [events](), [knowledge-sharing]() ### AI overview The Devcon team outlines goals for Devcon 6, including collaboration, knowledge sharing, teaching, communicating Ethereum's progress, experimenting with Ethereum-built tools, and growing the Ethereum ecosystem. ### Source excerpt ... ## Tales of a Part-time Sysadmin: Dogfooding Docker to test Docker DevFeed: [Tales of a Part-time Sysadmin: Dogfooding Docker to test Docker]() Original publisher: [Read original article]() Published: 2015-06-07T01:10:30Z Content type: article Language: en Sources: [Jessie Frazelle]() Topics: [Docker](), [Testing](), [ci](), [Jenkins](), [Server]() Tags: [ci](), [docker](), [dogfooding](), [jenkins](), [sysadmin](), [testing]() ### AI overview This article describes how Docker's core team uses Docker to run and test Docker. It explains the CI infrastructure, including Jenkins in a Docker container, storage-driver and Linux distribution matrices, and testing across multiple servers, kernels, Docker Windows clients, and pull requests. ### Source excerpt This is a tale about how we use Docker to test Docker. Yes, I am familiar with the meme. Puhlease. Many of you are familiar with the fact I work on the Docker core team. Which consists of fixing bugs, doing releases, reviewing PRs, hanging out on IRC, mailing lists etc etc etc. But what you may not know is that in addition to all these things I also manage our testing infrastructure. Now really this in itself could be a fulltime job. However it is not my fulltime job, nor would I ever want it to be. [insert gif about yak shaving here] This blog post is going to be about how I manage ~50 servers but don't do anything at all. Of course, I have my angry sysadmin moments when everything breaks and I could punch a whole in a wall... but who doesn't? Our CI First let me take a chance to familiarize you with how we test Docker. Docker's tests run in a Docker container. We use Jenkins as our CI mostly because we needed a lot of flexibility and control. Obviously everything in our infrastructure runs in Docker, so that even goes for Jenkins. We use the official image for our Jenkins container. Docker itself has 6 different storage driver options. These are aufs, btrfs, devmapper, overlay, vfs, and zfs. We have servers that use each of these hooked up to our Jenkins instance for testing. Along with all the storage driver options, Docker also runs on any linux distro and a world of different linux kernel versions. In order to be able to try and test all this differentiation, each server runs a different kernel and all major linux distros are accounted for. With every push to master on the docker/docker repo, we run tests on the entire storage driver matrix. We also trigger builds to test the unsupported lxc execdriver for Docker. And we trigger builds to test the Docker Windows client. Right there is three different jobs running on 8 different servers just for 1 push to master. Did I mention we have 9 Windows servers and 9 linux remote hosts paired with those servers for testing