I've always known computers, i have always felt more than comfortable inside my files and folders. When i saw what Jake was teaching, it was too good to be true. It almost felt like a matrix moment. Why did i think all of this was so complicated? How can one video completely explain the entire AI hallucination bubble that I have been stuck in since my life changed to a vibe coding addict? Either way, holy f*^&* s^*(!!!! This is a big deal for me, i have been so unorganized my whole life, now with the codex and claude apps, i just structured them to mirror whats in my folders, made the necessary md files in each, and i have not stopped being productive since. I used to be so scatter brained, but with this system, and the new codex and claude desktop apps allowing you to organize folder structures on the left panel, this was a match made in heaven with Jakes system. No dashboard, don't want one, i have been more productive in the morning by simply opening my app and looking at my folders, every conversation thats ongoing with full understanding of the project and what is needed every step of the way. I set up a system where i use the code word "pickup" or "handoff" Anytime i say handoff at the end of the night, the MD files already know that it triggers a process of writing to the memory files, doing a verification pass to make sure it was written succesfully, and if i am in an active app building project, it will commit and push to the github branch automatically. I can fully close the chat window with no worries of losing any progress, then in the morning, from any other app i want, any terminal window, any IDE, i just go back to that folder with my AI and say "pickup" it will wake up, not only get up to speed itself, but give me a summary of where we were and what we should do next. This solved the problem i had my whole life of forgetting my progress and leaving things undone. I haven't participated much in this community because I can't find time, but im finally finding time because I have done more work in 2 weeks than i have done all year.

came back after a week offline and spent an hour just reading posts. people are shipping. full agent teams, named specialists, live clients. and i'm still on the foundation. but here's the honest version of what's actually happening. i build something. it works. then i look at it and realise it's not what i actually wanted. so i break it and start again. then halfway through the rebuild, a new idea comes in and now i don't know if i should finish what i started or pivot to the thing that's clearly better. i've rebuilt the same system three times in a month. and the worst part.. each version was better than the last. so was the rebuilding wrong? or is that just what building actually looks like before it locks in? genuinely asking because i can't tell if this is a me problem or if everyone here is quietly doing the same thing and just posting the final version.

"The haters, the doubters are all drinking champagne in the top deck of the Titanic… and we are the iceberg." — Casey Neistat A couple of days ago I rediscovered one of my favorite YouTube videos, posted 9 years ago by Casey Neistat. The premise is simple: everyone will tell you what you can't do. In life, in business, in relationships. In our case, with AI. F*&% that. When I joined this community a month ago, I didn't know what a markdown file was. Couldn't build a workspace or a system. Had no idea what "IDE" stood for, let alone how to build and deploy skills in Claude. That being said, I did the thing anyway. And now I'm building and solving things in ways I never imagined. If you're new: welcome. Do what you can't. If you've been here a while: keep doing what you can't. This is one of the best communities on the internet. Grateful to be in it.

1. Watch the intro video and introduce yourself in the intro post here 2. Start with The Foundation (free course). 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, move to Implementation Playbooks (Level 2). When you're ready to build your own tools, Building Your Stack (Level 3). 5. Post your work. Ask questions. Help others when you can. What are you here to build?