Fair point. To be more specific we’re somewhere in between. AI writes a lot of code for us, but there’s a developer in the loop who reads every line and understands what it’s doing. We still make the call on whether it stays unlike the traditional vibe coder who doesn’t know what to look for. Hope that clears things up a bit.

Thanks for asking. Yes, we use AI as a tool in our workflow. The difference between our workflow and ‘vibe coding’ is that we can catch and fix problems. We’re not just shipping whatever an AI produces and hoping it works.

You’re right that all metadata lives in markdown frontmatter, but it’s not uncached. The notes list also only reads around 2KB frontmatter, so it stays fast well past 10k notes. We do have some tweaks planned though to optimize this even further. This is a great suggestion, thank you!