Talks, videos and podcasts about Fallow.

I am Bart Waardenburg, and I build Fallow. I spent most of my career as a frontend developer and tech lead, and now I talk about what happens to a codebase when coding agents write more of it. This page lists my talks and the videos and podcasts other people made about Fallow, each with a link to its source. For an interview or a talk, email hello@fallow.tools.

Email hello@fallow.tools Download the logo (SVG)

Talks by Bart Waardenburg.

React Advanced London, October 23 and 26, 2026

Agentic Engineering for React Teams: Give Your Coding Agent a Map

A talk for React teams about giving a coding agent a map of the whole codebase before it changes anything.

View source

Frontmania, October 5 to 7, 2026

Fallow at Frontmania 2026

A talk about Fallow at the frontend conference in Utrecht.

View source

dotJS, September 18, 2026

Linters Check Files. TypeScript Checks Types. Who Checks the Codebase?

A 20-minute talk in Paris about problems that live between files, such as two route folders that disagree on a name. It ends where the code alone cannot tell you what production still runs.

View source

AI Coding Summit, July 6 and 7, 2026

Fast Code Generation Is Easy. Safe System-level Change Is Not.

GitNation recorded this session about checking the structure of a change that a coding agent makes, before it merges.

View source

FrontValue, June 16, 2026

Vibe Coding Doesn't Scale: Deterministic Tooling for Agentic Engineering

At this community meetup in Utrecht, I showed a coding agent that runs the same codebase checks on every change and gets the same answer each time.

View source

Videos and podcasts about Fallow.

Web Dev Simplified, June 2, 2026

This Tool Forces AI To Write Good Code

The video starts with setup and basic use, then moves into VS Code and a coding agent workflow.

View source

Better Stack, May 1, 2026

Fallow: The Code Intelligence Tool Every Claude User Needs

Better Stack runs Fallow against a repository and shows how its dependency graph exposes structural problems across files.

View source

Syntax, April 29, 2026

This Coding Tool Kills AI Code Slop

Scott Tolinski runs Fallow locally, then follows the same findings into his editor and CI, including the automatic fixes.

View source

Syntax, April 22, 2026

How to Fix Vibe Coding

Scott Tolinski and Wes Bos discuss where deterministic codebase checks fit in development with coding agents.

View source

Syntax, April 20, 2026

Rating and Roasting Your Projects

In this project review episode, the hosts look at Fallow and the codebase findings it gives developers and agents.

View source

Open-source projects that run Fallow.

These teams added Fallow to their own public repositories, as a CI step, a dependency or a config file. A public setup is not an endorsement of Fallow.

Teams at these companies use Fallow in their public repositories.

PopChoice, Required CI check

Fallow audit across a TypeScript monorepo

The PopChoice quality guide requires Fallow on every pull request. The check fails only on new findings, and the older findings are a separate cleanup task.

View source

ApexYard, Code review step

Static analysis inside an agent review workflow

An opt-in review pass in ApexYard runs Fallow on the changed files and returns structured findings for the reviewer to weigh.

View source

tweakcc-maint, Baseline report in CI

Health and dead-code changes in CI

tweakcc-maint committed Fallow baselines and added a CI job that reports each change against the cleaned-up state of the repository.

View source

Company facts.

Fallow B.V. makes Fallow Cloud, which counts the calls to each function in production and puts them on a map of the code. The map comes from the free Fallow scan, which is open source under MIT and built in public on GitHub.

Legal name: Fallow B.V.
Registration: KVK 42095869
Founded: 2026, in the Netherlands
Founder: Bart Waardenburg