What’s your biggest bottleneck? For people building a personal brand/business, what’s currently the biggest bottleneck for you? Getting attention, creating content consistently, converting attention into leads, or something else?

I've been reading through the ICM discussions here, and something suddenly clicked with a paper I've been working on called The Larynx Problem. The basic idea is almost stupidly simple: The larynx produces speech. It doesn't produce thought. My argument in the paper is that we may be making a similar category mistake with LLMs. Large language models are extraordinarily good at language. They can reason through problems, write code, explain concepts, transform information and communicate across almost any domain. But they are trained on the linguistic traces of human cognition — what humans have written, explained, argued, coded and recorded. In that sense, we're modelling a lot of what comes out of human cognition. Not necessarily the entire architecture that produced it. And that made me look at ICM differently. A lot of conventional AI use effectively asks the model to do everything inside one context: Remember the project. Understand the rules. Know what stage we're in. Decide what information matters. Maintain state. Follow the process. And then do the actual reasoning. We keep asking the larynx to also be the brain. ICM changes that. The folder structure carries part of the architecture. Files preserve state. Routing determines what should be seen. Stage contracts constrain what should happen now. Context is selected instead of endlessly accumulated. And the LLM gets to operate inside that structure rather than having to reconstruct the structure every time we prompt it. That may sound like a small distinction, but I think it's a pretty profound one. We're moving memory, routing, state, boundaries and parts of the workflow outside the model and making them explicit, persistent and inspectable. The model can then concentrate on the part it is exceptionally good at: working with language and making judgments inside a well-defined context. It also made the 60/30/10 idea click differently for me. Maybe AI being the 10% isn't just a good engineering rule. Maybe it reflects something deeper about where the model actually belongs in the architecture.

ICM getting you down = @Don Roy Data = @Mira Bradshaw Video/Images/things I can't even pronounce = @Ari Evergreen Needing the human and knowledge = @Carla Bosteder and @Aaron Kruger Admin = too scared to tag them 😉😉 but you will know when you know. other things = classroom, videos and links there is even a Don's bookshelf and ari's space is out of this world (see what I did there). #checkitout Participate in comps (even if you suck... you learn - this is why you are here) Good housekeeping = search (many members have already been where you are) even better check out the legends it is the 11th commandment (Don will post about it -#nopressure Don) Don't be afraid to post but also don't get stuck on the likes and the climbing. Focus on the learning and you will find your place. Above all else... Embrace the 'dumb' it is the only way you truly make yourself teachable. Good luck, God speed, go into the light, break a leg, or whatever people say...

Anyone else getting pumped? I know I am. Mission Control setup and ready for countdown

A pad of scrap paper beside the keyboard has done more for my throughput than most of the tooling I changed this year. The minutes a model spends building are the minutes to spend deciding what happens after it lands. - The next sequence - the two or three work orders after this one, written while this one runs. - Notes on the output - what to keep and what to challenge, marked as you read rather than after. - Designs - page layouts, folder trees, flows. Faster to draw than to describe. The dead time in an agentic session is real. A job runs for a few minutes and there are three things you can do with that window: watch it, interrupt it, or think. Watching teaches you nothing and interrupting usually costs a rerun. Writing by hand does something a second chat window does not. The keyboard pulls you back into the work; paper keeps you above it, which is the seat you are supposed to be in while an agent is running. The reading half matters more than the planning half. Marking what to challenge as an output comes in, rather than reaching the end and reconstructing it, is the difference between a next instruction that corrects course and one that just says carry on. The bit I have not solved is getting any of it back into the system. Everything on that pad is orientation the workspace never sees. One of the synced writing tablets pointed at a folder would close that - handwriting arriving as context on the next prompt, and the notes logged as part of the record of how a build actually went. If anyone here has wired one up, I want to hear how. Genuinely think that is one of the more interesting unbuilt pieces sitting in plain sight...