Been sitting on this for a few weeks and figured it's time to show you. 👀 Over the last month, three companies have reached out asking the same thing. How do we hire people from Clief Notes. They've seen what folks here are building with ICM and they want that on their teams. Not LinkedIn AI experts. Not Coursera grads. People who can actually ship. So we're building it. 🛠️ talent.eduba.io Heads up, that's a demo. No real backend, no signups, no live data. Click around and you'll see what the full thing is going to be. A private platform where you list yourself with a real portfolio, companies browse, and they request an intro through us. We make the intro. You take it from there. Few things worth knowing. 🔍 Every profile gets reviewed by the Eduba team before it goes live. The quality bar is the whole point. 🔒 Companies don't see your last name, your employer, or your contact info until we make a formal intro. You can block your current employer too, plus five more companies if you want. Nobody you don't want seeing you sees you. You can list as actively looking, open to offers, or not looking. Passive welcome. Honestly most of the strongest people we've trained are employed and plan to stay that way until the right thing shows up. That's fine. Sit on the platform, see what comes through. 💰 When a placement happens you get a $500 to $1,000 bonus after 90 days in the role. On top of whatever you negotiate. We pay you for staying. This is why the community matters. Companies aren't asking us for resumes. They're asking us for the people who already get it. ICM, agent architecture, knowing when not to use AI. That's not on a LinkedIn profile. Go click around. Tell me what's missing, what's confusing, what you want to see when the real thing ships. We're already building it. 🚀

Like many young people today, I started my AI journey with ChatGPT. I am not a software engineer and have always preferred less tech in my life in general, I still prefer to read physical books today. For me, ChatGPT was first just a fancy Google, helping me find information a little quicker and answering random questions that I would think of. But it also turned into a gateway drug for what AI could do, and it wasn't until a friend told me about agentic AI that those lightbulb moments started to happen. Suddenly I could create my own website or app. I could create specific things to make MY life easier. And then it hit me, NOW I CAN DO THIS FOR SOMEONE ELSE... AND GET PAID! And like that I dove head-first, oblivious and clueless, but motivated and excited about the possibilities. Did I find Grok or Claude? NO I found MANUS AI, and after 4 months, 6 websites and 2 apps, I decided it was time to learn about Claude, I mean, all the "techies" I see can't stop talking about it! So I find Clief Notes... Now I'm realizing just how much this agentic AI has been doing for me... And I can also see how easily it could make AI models like Claude obsolete. Could I be wrong? ABSOLUTELY! But while the right person could do everything in Claude that Manus can do, I'm left wondering what happens when the next update just destroys everything else and if I should solely focus on agentic AI instead. I know I seem like a "doomsdayer", and I am no engineer or AI expert, but I can't help wondering what Claude can do that some of these high-end agentic AI models can do I would love to know your thoughts and PLEASE prove me wrong so that I can know!

How did i do?

What ICM, 60-30-10, and a lot of GitHub stalking taught me. Six weeks ago, I was using Claude to produce daily content artifacts — Instagram squares, captions, blog posts. A publishing operation with a workflow that mostly held together. Today, four public ICM-structured AI repositories live under github.com/NFTYoginis. Three more shipping this week. Each one is a fork-able starter that demonstrates a working architecture: orchestrator dispatches, workers build, briefs serve as contracts, memory persists across sessions. The path between those two states isn't "I learned to code." It's a six-week stretch of reading public repositories, trying patterns, deleting most of them, and slowly understanding what ICM (Internal Coherence Maximization, from Jake Van Clief) actually means when you stop treating it as theory. This is the tour: where I started, what changed, what I built, and where you can fork it. Where I started Six weeks ago, my Claude workflow looked like this: - One Claude session per task. Each session loaded brand-voice files, content samples, and whatever else seemed relevant. Context bloated by lunch. - I'd ask Claude to do something. It would produce something close. I'd correct it. Repeat. - "Memory" was telling Claude "remember our convention is X" at session start, which it forgot the next session. - The token bill kept growing without the output growing proportionally. That setup works at small scale. It collapses under any real production load. The collapse moment, when it came, was specific. I caught one of my daily routines burning roughly 800,000 tokens — for a routine that needed to do one thing: write three dispatch briefs and hand them off. The actual creative work happened in the workers being dispatched. The orchestrator was just routing. Eight hundred thousand tokens for routing. That was the first time I read about ICM. What ICM actually says (the part that mattered) Most "AI architecture" content I'd been reading was either too high-level to act on, or too tied to a specific framework I'd have to adopt wholesale.

Hopefully this is helpful for those overwhelmed not knowing where to start. There's a fair amount of posts from inexperienced non-tech folks asking where to start and you can quickly see the motivation is money and ease. Essentially: What are ya'll doing and whats the easiest/quickest way for me to get there with the least amount of work and make the most amount of money? Don't get me wrong, I'm a business owner, I get it you don't want to waste time on unprofitable ventures. My unsolicited $0.02. Don't try to shortcut or hack the process. If you're just getting started with 0 tech knowledge and experience, stop asking what's most profitable with least effort and just start building something you'd find useful. Keep your day job, build on the side. I like the way @David Vogel puts it as "garage tinkering". I genuinely look this tech stuff the same way when I started "garage tinkering" with woodworking tools. I didn't go in my garage and think hmm what can I build that has the best profit margins? I just starting building things I had a need for and thought were useful and that's where the learning happened. I guess what I'm getting at is if you're struggling where to start: 1. Watch, read, learn 2. Get your hands dirty and apply 3. Repeat Happy building!