User
Write something
Lyceum Webinar is happening in 10 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
Something is coming 👀
Been heads down on something the past month plus. Not a lesson, nor a Tea round but more like the layer under all of it. Kept seeing the same thing in comments and onboarding calls: People not knowing where to even start or if something’s already been covered somewhere in here. We're working on fixing that. Not ready to put it in your hands yet.
How important do you think a traditional visual interface will still be in the future?
Do we still need dashboards, menus, buttons and complex applications? Or will the AI itself become the main interface, with a simple visual layer only for things like monitoring, approvals and seeing what’s happening? I’m curious how you see this evolving over the next 5 years. Will we still use software, or will we mostly talk to software? @David McDermott @Ari Evergreen @Jake Van Clief @David Vogel @Matthew Creamer @Bas Rosario
Poll
8 members have voted
Don't know where to start.
Problem what I am facing is the bombardment of terminologies, vector, transformer, project, skills, claude code, etc. So, I am really confused whether I should start from the bottom conceptual or what.
How are you backing up your AI workspace?
I spent this week hardening my workspace setup and fell down the backup rabbit hole. Sharing the thought process because I want to know what everyone else is doing. My whole workspace lives under local git. I don't keep it there for code reasons. The win is auditing: every change is signed, human or agent, and I can see exactly what the AI did each session and roll any of it back. Once you let agents write into your folders, that flight recorder stops feeling optional. But git pulls a thread. A live repo can't sit inside OneDrive or iCloud. Sync engines fight the history layer: conflicted copies, placeholder files the agent can't actually read, endless re-upload of thousands of tiny .git objects. So the workspace has to move OUTSIDE the one backup most people already have. Which means backup now needs its own answer. The thing that clicked for me: a backup has to answer two different questions. "Give me my files back" and "give me my history back." Most setups only answer the first. OneDrive only answers the first. My own answer is three layers (external drive snapshot, remotes for the code, encrypted offsite for history) but I'm the nerd who enjoys that. The version I keep kicking around for everyone else: the agent zips the whole workspace, history included, and drops a dated zip into the OneDrive folder you already pay for. Keep the newest two, delete older. Sync can't host a live repo, but it carries a dead zip just fine. So what are you actually doing? Do you run git over a non-code workspace, and was the auditing worth the extra layers? What is your backup story for the folders your agents work in? Has OneDrive or iCloud alone ever actually saved you, or does it just feel safe?
1-30 of 3,036
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