User
Write something
Afternoon Tea is happening in 39 hours
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.
ICM Way before Linux
So typical evening. Reading posts, watching some videos, running through my 50th rework of an unfinished project. Something came to me. @Jake Van Clief says this is basically linux way of organizing. I think this way of thinking, working was way before then. It really sounds like Henry Fords assembly line. He broke things up so each station had a job and the process pushed through that job. each in a logical, predetermined order. Tires don't get put on 1st that's at the end. Isn't ICM the same thing? Each folder has a job and each folder has MD's telling it where to go in that structure and where to g next. Or what staton pits those ties on and that you don't route it there 1st thing. Am I crazy or doesn't that sound accurate?
ICM Way before Linux
Mini-Series Part 1: The "Manual Hell" Rebill Project
Following up on my previous post about automating month-end, I want to pull back the curtain on the project that really started it all. It involves a massive company reconstruction, a "manual hell" task, and a midnight breakthrough that tripled my productivity. The Problem: A Reconstruction Hangover On January 1, 2026, our company underwent a major reconstruction. Customers were assigned new sales reps, but the final list of who owned which account wasn't finalized until April. In the meantime, we kept invoicing as usual. The invoices were correct, but the Sales Rep field on the historical records was now wrong. To fix it, we had to go back and update thousands of already invoiced sales orders. The Manual Workflow (or: How to lose your mind): 1. Search for the Sales Order. 2. Click Invoice. 3. Click Rebill. 4. Change the Sales Rep. 5. Click OK. 6. Hit Esc to exit. 7. Repeat... hundreds (or thousands) of times. Enter Claude Code & Playwright I had just started using Claude Code on March 19th after watching @Jake Van Clief ’s videos. Two weeks later, this assignment landed on my desk in the middle of my usual accounting duties. Since I didn’t have backend API access to D365 F&O, I turned to the Playwright MCP. If I couldn't talk to the database directly, I’d have Claude "drive" the browser just like a human would. The Automation Logic: - Open Chrome to the D365 Sales Order URL. - Open the filters tab. - Add filter information (Customer account, dates for Q1 2026, and identifying which sales orders had the wrong rep). - Execute the "Rebill" click-path automatically. The "Aha!" Moment at 00:30 AM It worked, but it was real slow. D365 isn't exactly a speed demon. My boss was happy ("as long as we don't have to do it, I don't care how slow it is"), but I knew we could do better. Earlier that day, I was running it in one browser and it was taking forever. While the kids were finally asleep that night, I had an idea: Can I run this on more than one tab?
1-30 of 2,397
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