It’s live. Starting today, everyone in Clief Notes has access to the new Clief Notes AI. The easiest way to use it? Don’t overthink it. Ask it the question you would normally ask me. “Where should I start?” “What should I focus on next?” “Where did you talk about [topic]?” It’ll use what’s already inside Clief Notes to help answer you and point you toward the right lesson or resource when there’s something worth going deeper on. The goal isn’t to give you another AI tool to play with. It’s to make everything already inside this community easier to actually use. If you want Access to it Comment "READY" and we'll send you access to it!

(even better through an ICM lens) https://youtu.be/tuY2ChJIx48?is=lO5DpqxE79utM7J3

If anyone's curious if the methods I'm teaching here will last long enough. Just know that y combinator is now asking for solutions we built years ago. https://www.ycombinator.com/rfs

This community is large and it moves fast. That's the good part and it's also the problem: valuable posts get buried, the same questions get re-asked instead of found, and spammers show up wherever there's an audience. These guidelines are what keeps the room worth showing up to. Read them once. You won't need them again, because most of this is what you'd do anyway. New here? Start with Jake's welcome post and the Foundation course. This post is about how we behave, not where to begin. 1. Build in public. Post the thing while it's half working. A half-finished build is more useful to everyone else than the polished writeup you'll never get around to, and you'll get corrected before you've spent a week going the wrong way. 2. Teach what you learn. The day you figure something out is the day you're best at explaining it, because you still remember exactly what confused you. A month later you've forgotten the hard part and your explanation gets worse. If you cracked something this week, that's a post. Nobody has to earn the right to ask a question here, but this place only works because people come back and answer them once they can. 3. Ask good questions. Specific beats polite. "How should I structure this?" gets three vague answers. "I have a 40 file client folder, the model keeps loading the wrong context file, here's my CLAUDE.md" gets a real one. Say what you tried, what happened, and what you expected instead. A more in depth guide: https://dontasktoask.com The flip side of this: "Anyone here?", "Help please", and one line questions with no context may get removed. Not to be harsh, but because nobody can answer them. 4. Give credit. If you built on someone's skill, template, folder structure or comment, tag them. It costs you nothing and it's the reason people keep publishing their work here instead of keeping it. A lot of the best material in this community started as somebody's reply on somebody else's post.

Despite all the ai hubbub and second brains someone asked what I read and IF I read at all anymore. The answer is most certainly YES. You can make connections that might be missed by a million questions with AI by diving into books and reading your self. Some books may not even have most of their pages on the web especially older ones and those are often my favorite. Here are 4 of my current favorite readings to prepare me for the future (by looking at the past) 1. Mythical Man Month (1972 by Fred Brooks) 2. Psychology of Computer Programing (1971 by Gerald M Weinberg) 3. Augmenting Human Intellect (1962 Douglas Engelbart) 4. The Creative Act: A Way of Being (2023 by Rick Ruben) Rick Rubens book is just great in general for business and creative acts.