cd /news/artificial-intelligence/ai-driven-development-means-test-dri… · home › topics › artificial-intelligence › article
[ARTICLE · art-104980] src=meiert.com ↗ pub= topic=artificial-intelligence verified=true sentiment=· neutral

AI-Driven Development Means Test-Driven Development

Jens Oliver Meiert, an engineering lead and web developer, advises that developers using AI should start with tests, as AI-driven development effectively requires test-driven development (TDD). He recommends explicitly asking AI models to first write tests for features or fixes before implementing them, which protects projects by confirming missing or broken functionality, preventing AI from veering off course, and verifying completed work. Meiert, who has worked at Google and contributed to web standards, emphasizes that this approach is safer than 'just shipping,' especially for those who are not strong programmers.

read2 min views34 publishedAug 19, 2026
AI-Driven Development Means Test-Driven Development
Image: Meiert (auto-discovered)

AI-Driven Development Means Test-Driven Development #

Published on Aug 20, 2026, filed under development, ai. (Share this post, e.g., on Mastodon.)

If you’re developing using AI, you need to start from tests.

If there’s one lesson I learned from developing, maintaining, and optimizing using all sorts of models—something I missed calling out in previous tips!—, then it’s this. Start from tests.

The way you do this—and you may need to be explicit as I’ve seen many models slap on tests after the fact—is by asking to first write tests for what you create or fix—and then develop the feature or implement the fix. Rinse and repeat—though this is intentionally open and may reflect TDD (test-driven development) more in spirit than in letter.

Starting with tests protects your project:

  • You confirm that the respective feature is missing or broken (and it’s recommended that you review and run the testsor, at least, take samples). - You put a guardrail in place so that any AI instance doesn’t veer off—any work it does should lead to developing or fixing the feature.
  • You confirm that the feature was indeed built or fixed.
  • It keeps yourself centered on the problem.

Now, I’m frontend developer first, web developer second, programmer last, and therefore look at some processes from an off-position. Still, working with AI has proven to me the value of test-driven development. If you’re working with AI, and aren’t a strong programmer, try starting with tests, too. While you will need to get used to testing, this is easier and safer than “just shipping.”

About Me #

I’m Jens (long: Jens Oliver Meiert), and I’m an engineering lead, guerrilla philosopher, and indie publisher. I’ve worked as a technical lead and engineering manager at various companies (e.g., Google); I’m an active web and tool developer (code optimization, digital defense), a contributor to web standards (like HTML, CSS, WCAG), and a book author (O’Reilly, Frontend Dogma).

I love trying things—in web development and engineering management, but also in politics and philosophy, where I hold to one idea in particular: that we can only be well if we take good care of everyone. Here on meiert.com I talk about some of my perspectives and experiences. (Interpret charitably but be critical—and share feedback and advice that makes my work better.)

── more in #artificial-intelligence 4 stories · sorted by recency
── more on @jens oliver meiert 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/ai-driven-developmen…] indexed:0 read:2min 2026-08-19 · —