📊 You've probably seen this chart floating around LinkedIn and Twitter Each dot is 3.2 million people. ⬜ Grey is the 84% of humans who have never used AI 🟩 Green is the 16% who have used a free chatbot 🟨 Yellow is the 0.3% who pay for one 🟥 Red is the tiny sliver who use AI coding tools Most of the people sharing it have not actually said what it means. So here it is. 🔁 We live inside an algorithm. Mine shows me AI all day. Yours probably does too. Every reel, every post, every podcast clip, every ad. The feed makes it feel like the whole world has moved on without you and you are sprinting to keep up. Inside Clief Notes that feeling gets louder. You log in and see people building agents, shipping side projects, automating their inbox, talking about Claude Code and MCP servers like it is normal. In this room, it is. Step outside and almost nobody is doing any of it. 6.8 billion people have never opened a chatbot. Plenty of the ones who did opened it once, asked it something dumb, got a dumb answer, and decided the whole thing sucked. They are not coming back this year. Maybe not next year either. 🪖 When I was in the Marine Corps I never felt like I was doing anything special. I was surrounded by other Marines. Everyone around me could do what I could do. The standard was the standard. It was not until I left and stood next to people who had never served that I understood. The thing I thought was ordinary was rare. I just could not see it because I was inside it. That is what is happening to you in here. If you feel behind in this community, that is the right feeling to have. It means you are standing next to the people pushing the edge. Step outside this room and the thing you are calling behind is so far ahead of where most of the world is sitting that they cannot see you from where they are. And do not forget. The thing you built last week, the workflow you set up this morning, the conversation you just had with Claude. A version of you from two years ago would have paid good money to do any of it.

14 likes. Most in the comments. Community voted, and @Ian Barriopedro took it. $200 cash. Yours. Check out his entry here: https://iatoba72.github.io/ruffcuts/ He didn't just write a brand voice doc. He built a site for it. Structured the whole thing so anyone Dana hands it to can actually use it. That's the bar. For everyone who entered, real talk: the quality across the board was strong. This was a tight vote. If you didn't win this round, you've got another shot coming. What's next: Comp #2 drops soon. Heads up though, we said it in the rules and we meant it. The challenges get harder from here. More creative. More technical. This first one was the warmup. If you're a free member watching from the sidelines, this is your sign. Premium and VIP only for comps. $200 cash up for grabs every week or a free lyceum entry!! @Ian Barriopedro , congrats. Dm me so I know where to send the cash. Everyone else, get ready. Next one's coming!!

So in my daily work sometimes I run into brand new code bases that I have zero insights into. And given that I am not a developer by trade, I came up with this prompt and wanted to share it with you all and see what kind of results you got or how we could improve it. This is intended to map out the entire systems in a folder structure that creates permanent context for the agents, let me know your thoughts! I’ve used this structure to keep a 97k+ lines of code projects in check, and seems to work pretty well. Ps not sure why the markdown gets converted to a docx on my iPhone 🤣 .Agents/ └── Technical_Documentation/ ├── README_PROJECT_OVERVIEW.md ├── EXISTING_DATA_MODELS.md ├── API_REFERENCE.md ├── ARCHITECTURE_MAP.md ├── DEPLOYMENT_GUIDE.md ├── ONBOARDING_GUIDE.md └── diagrams/ ├── system-overview.md ├── data-flow.md └── api-flowcharts.md

Hey everyone, Last year when my pc died I made the switch to a MacBook Air M4, now I’m considering the next purchase. Should I go the Mac mini route? Or do a new PC build? What’s everyone running with? Thanks in advance!

Most software is built by people who will never use it. They are guessing what their users need, then guessing whether they got it right. That gap is why so many tools feel almost-right. Almost the workflow you wanted. Almost the shortcut you would have built yourself. The fingerprint is missing because the maker's hands were never in the work. Pushing Squares started from the opposite direction. I am a colourist and a director. CRUSH, CBA, FUZZ, SUBTRACKT, REFRAKT. These plugins exist because I needed them on a real timeline that day. The first user is always me. The shipping bar is "would I install this tomorrow on a paying job". This changes the design surface in three ways: 1. The defaults are right because the maker lived inside them. Setting a default is a guess about the most common case. If you are the most common case, you are not guessing. 2. Features earn their slot in the panel. Anything that does not save time on a real shot gets cut. There is no marketing reason to keep a feature the maker themselves never reaches for. 3. The bug list is short and honest. You feel every regression because you hit it the next morning at 2am. This is not a no-code argument. It is not "everyone should learn to ship code". It is a positioning argument. The closer the maker is to the work, the less translation has to happen between intention and tool. AI changes the cost of this. Building the thing you needed used to take a development team and six months. Now it takes a directed run with Claude and an afternoon. The bottleneck moves from technical capability to taste, judgment, and knowing what the work actually demands. So if you are using a tool every day and feeling the gap, the gap is the brief. The next person to fix it should be you. The closest hand to the work makes the truest tool_ // A<3