User
Write something
Afternoon Tea is happening in 3 days
Pinned
🚨 New one in the NLP Logix series is live 🚨
Sat down with Katie Bakewell, a data scientist who's been building this since 2011, back when it was still just called "natural language processing" 🧮 She came up through math (DNA computing, time series on commodities) and thinks about problems like proofs, not recipes. What we get into: 🪨 The Indiana Jones "build me a chatbot" boulder she ran from in 2023 🚨 The 7 neural nets that "found" a signal that was completely fake 🏎️ A $5M Pagani vs a $100 Toyota, and why "best" is a trap 🤖 The first chatbot was built in 1966 (ELIZA)... these aren't new ideas 🐬 Meta's SAM3 turning hours of labeling dolphin fins into a single prompt 🧠 Why half the companies asking for AI are solving the wrong problem ▶️ Go watch 💬 Then drop a comment: What surprised you most, or what would you have asked her? Happy learning 🙌
5
0
Pinned
Welcome to Clief Notes. Here's where to start.
1. Go check out 📚Navigating The Course to see how to get around and what's here. 2. Start with The Foundation. Concepts, folder architecture, prompting framework. Everything else builds on this. 3. Check in at the bottom of each lesson. Polls, discussion posts, other members working through the same stuff. Use them. 4. When you're ready to build real things join in on our Biweekly competitions and win some real cash. ⭐ Competitions Mega Thread 5. If you are wanting to dive into the masterminds, grab all the past templates, artifacts and resources. Upgrade and head into the The Vault for Premium and The Drawing Room (VIP) for VIP 6. Post your work. Ask questions. Help others when you can. What are you here to build?
Pinned
🤝 NEW: The Connection Hub is live
👋 Welcome to the Connection Hub - The Vault · Clief Notes So I was on the onboarding call this today, and one thing kept coming up that I couldn't stop thinking about: The biggest value of this new age isn't just the tools. It's the people. 👥 Specifically — people who understand AI the way THIS community teaches it. Not "prompt hacks" and not "10x your output" nonsense, but actually building systems, thinking in workflows, and treating AI like a real part of how you work. That's a rare group. And a lot of you told me the same thing: 💬 "I'd love to work with someone who gets this." 💬 "I want to break into [industry] but don't know anyone in it." 💬 "Who else here does what I do?" So instead of letting those connections happen by accident... I built a place for them. 👇 🗂️👋 Welcome to the Connection Hub - The Vault · Clief Notes It's a simple set of pages, split by industry. You find your corner, drop a quick intro about what you actually do and what you're looking for, and connect with people who speak your language.
The Most Honest Thing You Can Say
"I don't know." Three words. Nothing fancy about them. And they might be the most honest thing a person can say. Here's the thing though: AI doesn't really do this. Not the way we do. I was building out a folder agent last month for a topic I'm not an expert in (won't bore you with which one, but let's just say I was playing in a knowledge area way out of side of my knowledge base lol). And a few times, the answer it gave me sounded completely right to my ignorant butt. Confident. Clean. Delivered with the same tone it uses when it's telling me something I already know is true. Except it wasn't right. Not completely, anyway. And that's when it hit me: the model doesn't know that it doesn't know. That's not the same as "AI never says I don't know." It'll say that plenty. The problem is it doesn't always know WHEN it should say it. There's no internal alarm bell going off that says "hey, this one's shaky, tread carefully" versus "this one's rock solid, trust it." It's all delivered in the same voice. Same confidence. Same polish. At the end of the day, these things are pulling from a vector database, finding concepts that are linked together, and stitching together the most probable-sounding answer. Sometimes that's spot on. Sometimes it's wrong but close enough that it nudges you toward the right answer anyway. And sometimes it's just way off the mark, and you won't know until you've already built three layers of a folder structure on top of it. That's the PITA part. Why This Matters for Your ICM ICM folder structure is designed to run on trust. Your CLAUDE.md tells Claude who you are and what the project is. Your CONTEXT.md files tell it what good output looks like in each workspace. You're basically handing it a map and saying "go." But here's what nobody talks about enough: that map is only as good as what you actually know. If you're building a workspace for a topic you already understand, you'll catch it when it drifts. You'll read the CONTEXT.md draft and go "wait, that's not right" almost instantly. You know enough to catch the fumble.
0
0
Connection Hub:🌱 Solo, Student & Exploring
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)
1-30 of 2,383
Clief Notes
skool.com/cliefnotes
What we give away free beats most paid courses. Build durable AI systems with a Marine vet and Edinburgh researcher. 40+ lessons, growing.
Leaderboard (30-day)
Powered by