Blog

From the Weekly Meeting

Short, practical write-ups from the AI for Life live sessions: second brains, local AI, protecting your ideas, and what actually works for people who are not developers.

Are you using system-building as an excuse to avoid real work?

  • Michael Wacht
  • Collin Thomas

Michael Wacht and Collin Thomas discuss the trap of endlessly tweaking and building your organization system instead of actually doing the work.

Can you safely use AI on intellectual property you can't afford to leak?

  • Herman Moore
  • Collin Thomas
  • Michael Wacht
  • Matthew Sutherland

Yes, but not with public models like ChatGPT or Google -- protecting IP you can't afford to leak means keeping the sensitive parts on infrastructure you control. Guest Herman Moore explains why he won't put his patented IP into public AI tools, and Collin Thomas, Michael Wacht, and Matthew Sutherland break down the actual architecture needed for data privacy: local models, hardware requirements, and deciding what runs on-machine versus what gets sent out.

How can AI help people who aren't developers?

  • Dena
  • Michael Wacht

AI can help people who aren't developers by working as a practical, jargon-free tool for everyday problems, not just programming. When Dena, a writer dealing with writer's block, asks how AI could help her process, Michael Wacht gives her exactly that: a plain-language answer built around real life instead of code.

If you understand RAG, are you already too technical?

  • Mike Thomson
  • Collin Thomas

Mike Thomson and Collin Thomas discuss why understanding technical concepts like Retrieval-Augmented Generation (RAG) might mean you've lost touch with how normal people use tools.

Join the AI for Life community.

  • Matthew Sutherland

Matthew Sutherland promotes the regular Wednesday session of AI for Life.

The one settings gotcha that will break all your file links.

  • Michael Wacht

Michael Wacht shares a specific settings gotcha that will break your file links if you miss it -- the kind of practical tip that saves hours of frustration.

What does 'intellectual sovereignty' actually mean?

  • Michael Wacht

Michael Wacht defines the concept of intellectual sovereignty -- maintaining control and ownership over your ideas and data in an AI-driven world.

What does a working AI operating system actually do all day?

  • Michael Wacht

Michael Wacht provides a screen-share walkthrough of a functional AI setup. He demonstrates how files are structured and shows the concrete daily automation -- including email and calendar triage, week-ahead previews, pulling drive times into calendar entries, and an article-writing pipeline.

What does it actually mean to build a second brain?

  • Mike Thomson
  • Matthew Sutherland
  • Collin Thomas

Building a second brain means moving past simple filing into a system where you actively capture, organize, and can retrieve what you know, instead of just storing it and hoping you remember where it is. Mike Thomson admits he's been too embarrassed to ask what everyone means by a 'second brain,' so Matthew Sutherland and Collin Thomas give him the complete beginner's breakdown, from basic filing systems to how a second brain actually functions in practice.

What happens when one formatting rule sends an AI into an endless loop?

  • Matthew Sutherland
  • Jacob Brodsky

Matthew Sutherland and Jacob Brodsky share a debugging horror story where a single formatting rule sent an AI into a six-hour endless loop at 2am, ending with the classic paperclip analogy.

What happens when you ask the wrong question about an AI tool?

  • Collin Thomas
  • Karen Widas
  • Michael Wacht

Karen Widas asks a question and receives a product demo instead of a direct answer. Michael Wacht and Collin Thomas step in to re-diagnose what she actually needed to know, turning a confusing moment into a clear, practical lesson.

What happens when you roast the expert?

  • Collin Thomas

Collin Thomas opens with a roast of Michael Wacht, turning a moment of conflict into a real, practical lesson about AI tools.

What is a second brain, and why is everyone afraid to ask?

  • Mike Thomson
  • Matthew Sutherland

A second brain is just a system, usually digital, for saving and organizing what you know so you don't have to hold it all in your head -- notes, files, and ideas kept somewhere you can actually find and use again. Mike Thomson admits he was too afraid to ask what a 'second brain' actually is, and Matthew Sutherland gives him that straightforward, one-line answer.

Why AI isn't just for programmers anymore.

  • Michael Wacht

Michael Wacht makes the case that AI is no longer just for developers -- it's a tool for real life and everyday work.

Why backups are like flossing -- everyone knows they should, but nobody does.

  • Collin Thomas
  • Mike Thomson

Collin Thomas and Mike Thomson discuss backups, why nobody actually does them, and why they are absolutely critical.

Why building a system so you understand it means you're doing it wrong.

  • Michael Wacht

Michael Wacht explains a contrarian approach to organization: if you build your system primarily so that you can understand it, you're building it incorrectly for an AI.

Why humans aren't going to read your data -- AI is.

  • Michael Wacht

Michael Wacht delivers a tight explanation on why the future of data organization is about machine readability, not human readability.

Why running local AI is like being a PC gamer.

  • Collin Thomas

Collin Thomas uses a vivid analogy, comparing the expertise needed to run local AI models to PC gamers overclocking their rigs.

Why you need to turn your training data off right now.

  • Michael Wacht

Michael Wacht gives a 17-second warning on why you should turn off training data sharing in your AI tools, and what companies retain if you don't.

Why you should build your organization system for the AI, not for yourself.

  • Jacob Brodsky
  • Collin Thomas
  • Michael Wacht
  • Matthew Sutherland

Jacob Brodsky, Collin Thomas, Michael Wacht, and Matthew Sutherland discuss why your current organization system will inevitably need to change. They explain why you should keep your core method stable while swapping the underlying parts, and why building structure for a machine to read is more important than building it for human readability.

Why you shouldn't just dump your existing files into an AI.

  • Michael Wacht

Michael Wacht explains why dumping your existing, disorganized files into an AI system will just create a mess, and shows what you should do instead.

Why your organization system is guaranteed to break.

  • Collin Thomas

Collin Thomas explains why your current system will inevitably need rebuilding, and how to prepare for it when it happens.

Community

Keep going with AI for Life

Learn alongside people working through the same lessons: ask questions at the live weekly session, share what you build, and get unstuck fast. Want something built for your exact situation? Request a custom lesson.