User
Write something
New Member Onboarding. is happening in 4 days
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 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 🙌
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.
Animations & Claude Design & Audio Syncing
I painstakingly made a 5 minute animations video with Claude Design eating away at tokens BUT I learned something today... I was having an issue lining up the audio with the animation. It was built first and I was trying to time my audio in capcut to it but instead I found out that Claude Design can put the animation in "rehearse mode" and I can record my audio and hit spacebar in rehearse mode when I went the slide to change to the next one. It creates the time stamps and converted that animation into my matching those time stamps. Then it was an easy overlay to the video in capcut. Not sure if anyone knew that or not but I was happy that I figured that out, for sure. Onward and upward!
Nobody in vibe coding talks about security. Gap, or just me?
I spent this week doing something I don't see talked about much in the vibe-coding world. Instead of just shipping my site, I tried to break it. I built it careful. Rate limiter, guards, the usual. But reading your own code never catches anything, you wrote it, you're blind to it. So I pointed an AI at it and told it to act like an attacker. It got in in about 40 seconds, through a header I forgot you could fake. Then it found two more holes on the poll, same root cause: a security switch flipped on, but the rule behind it let everyone through. Dashboard said protected. It wasn't. Fixed it the same day, then ran the attack again live on the patched version to check the work. What's stuck with me since: this whole space is optimized for building fast. Almost nobody talks about building it so it lasts, or so it doesn't quietly leak everyone's data because you never thought to ask it not to. That maintainable, secure side is the part I actually care about, and it feels underserved. So I'm curious what you all are seeing out there. Is there real appetite forming for the "build it right, not just fast" angle? Or is the market still mostly heads-down on speed and model comparisons? Trying to read whether this is a lane worth going deeper on. Video where I walk through the whole thing: https://youtu.be/mdQ8xiKWTc0
1-30 of 2,449
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