Matt talks with Stathis Askaridis (We Know Data and Pineapple.gr) about his method of developing with FileMaker. Stathis shows examples of this workflow, which is a very simple FileMaker database with just a few scripts, NO RELATIONSHIPS, and a layout with a WebViewer. All the dev is done/assisted by Claude Code, Codex, etc. which delivers HTML / CSS / JavaScript. 

Data edits? Easily done with FileMaker card windows, or also in JavaScript.

But this isn't the cool part (well, it's kind of cool) It's the logging and bug tracking that are amazing. Stathis uses a tool that captures the user session and actually contains more metadata by far than the FileMaker database. This allows him and his team to see exactly what a user did when the bug (like writing data to a locked or invalid field, or any error at the UI or data level).

What impressed most is that the possibility exists for this bug to be routed to a tool that analyzes the layout, the data, the bug experienced, and actually fixes it! This is perhaps then deployed to the dev server and tested by a meat puppet (that's how SciFi AI thinks of humans) can review and confirm before putting into production – also with automated tools.

Stathis is an Otto evangelist, and rightly so. For any type of deployment that uses this level of sophistication, it's a must.