Been building an MVP for an app/service that turns business documents (or any documents) into interactive courses/lessons with visuals, personalized AI tutor upon deployment, skill checks, and role play scenarios. I initially thought this was a novel idea, but I recently discovered a service named "Honen" that does something very comparable. Was wondering if anyone else in this group has been creating something similar?

For a long time, I assumed the main thing stopping me from building software was simple: I wasn't a software engineer. AI changed that much faster than I expected. I can use it to write code, work through frameworks I don't know, debug problems, and understand what I'm looking at as I go. A few years ago, the amount of technical knowledge I'd have needed before even starting would probably have stopped me. But using AI to generate code was only part of what made the difference. The other part was learning how to structure the work. I've been using ICM, the Interpretable Context Methodology from Jake Van Clief, to organize my AI workspaces. Instead of throwing everything into one long conversation, I break the system into specific agents, references, instructions, logs, and clearly defined responsibilities. That changed how I build. The AI isn't expected to understand the entire application from a giant prompt. A QA agent has one job. A security agent has another. Development work has its own context. Shared information lives where the agents that need it can actually use it. Once I started working this way, I could take on much larger projects without feeling like every new session meant starting over. And that's when the questions got more interesting. How should the system be structured? Which parts should use an LLM and which should just be regular code? What happens when a user uploads something you didn't expect? How much context does an agent actually need? Where can it make a decision on its own, and where should a person approve it? Then there are all the less exciting parts that still have to work: authentication, APIs, databases, permissions, deployment, testing, security and error handling. I've had to learn a lot of that while building. ICM doesn't replace that learning. AI doesn't either. What they have changed is when I can start. Previously, I would have needed to learn much more of the implementation before I could realistically build anything substantial. Now I can run into a problem, learn the concept, understand why it matters, use AI to help implement it, test the result and keep going.

Intros for The Connection Hub - The Vault 👤 Who I am: (name + where you're based) 🛠️ What I actually do: (the specific work — not "I'm in real estate" but "I run a 3-agent team doing residential resale in Austin") 🤖 What I'm building with AI right now: (your current project, workflow, or the thing you're stuck on) 🎯 What I'm looking for connection-wise: (pick one or two) 💡 Someone who's solved [X] 🤝 A collaborator / accountability partner 👀 Just here to learn from people in my field 🧰 Trading workflows & systems 📬 Best way to reach me: (DM here / comment / link)

Intros for The Connection Hub - The Vault 👤 Who I am: (name + where you're based) 🛠️ What I actually do: (the specific work — not "I'm in real estate" but "I run a 3-agent team doing residential resale in Austin") 🤖 What I'm building with AI right now: (your current project, workflow, or the thing you're stuck on) 🎯 What I'm looking for connection-wise: (pick one or two) 💡 Someone who's solved [X] 🤝 A collaborator / accountability partner 👀 Just here to learn from people in my field 🧰 Trading workflows & systems 📬 Best way to reach me: (DM here / comment / link)

https://www.instagram.com/reel/DaYoXM5v8Xt/?igsh=ZHExa3NvOWx2MTJi