Repetition texture Everyone got the same advice. Post every day. Ship every day. Protect the streak. Prove you showed up. Consistency is not the enemy. Treating the checkmark like the craft is. The mistake When the unit is "every day I did X," the work flattens into a calendar. Miss a day and the project feels broken. Hit every day and you can still produce nothing anyone would save, quote, or send with the line: this is what they do. Feeds love attendance. Tools gamify the streak. Peers ask if you are still posting as if the calendar were the portfolio. It is not. The reframe Treat anything you make in public as a growing, evolving body of work. Not a diary of days. A set of pieces that still make sense when someone meets you cold: essays, methods, products, systems, series. Things that form a shape next to each other. Harder question than "did I show up today?": If someone only saw what the internet still holds of me, what would they think I care about? That is the real portfolio. The remembered surface. Scale Scale is not "post more." Scale is corpus that compounds. A single post dies in the feed. A body of work grows doors. Someone enters through a tutorial, leaves through a doctrine, comes back months later with a problem that maps to a third piece. That only works if the work belongs together: - Series, not one-offs - Surfaces that point at each other - Reusable units you can teach again - Structure left open for the next chapter Scale without structure is landfill. Scale with structure is a library people can use. Curation Scale without curation is a hard drive with a public URL. Edit the corpus. Feature the spine. Group by meaning, not only by date. Retire without shame. Name the practice so a stranger knows what the body is for. People under-invest here because curation feels like "not making new things." It is how the work becomes legible. Without it, volume just makes the noise louder. Taste is not only what you make. Taste is what you keep in the frame.

Some in this group with too much time on your hands and have had some illness or disorder for not just reading but also commenting on my posts, have her me say more than once that that Jake is the Alex Hormozi of AI. Third-row, foam-finger, "just one more video at 1 AM while the whole house is asleep" levels of fandom. Then the ACTUAL Alex Hormozi drops a video titled "Why AI won't make you rich in 2026." https://www.youtube.com/watch?v=WttZ6b-KUP4 I clicked in with my chest out, ready to defend the family honor. Nine minutes later I'm sitting there like a kid who just found out Santa outsources and the tooth fairy are just the people who spawned you. Because the man's right. Dangit. His whole case, no chaser: AI is leverage. Real leverage. But it didn't repeal every OTHER kind of leverage that was already minting money before ChatGPT learned to talk. Capital. Media. A team. A sales process that actually closes. An offer that doesn't stink. AI showing up didn't delete a single one of those. Then he drops the part that made me put the cigar and whiskey down. (La Aroma de Cuba Mi Amor and Noah's Mill in case you're wondering what to send me on my birthday). He asked his richest, oldest friends how much they personally touch AI in a day. Off camera, the honest answer was basically "bro, I don't." Their teams do. They don't. The guys with the yachts, gently breaking it to the AI guy that the robots aren't driving the boat. And this is where it kicks those of us who LIVE in this stuff square in the tokens. (I laugh at my own jokes, even when they're in writing, you gotta admit, this one was funny). He says most owners have AI-maxed their capacity, so now they crank out more, faster. Except the extra stuff they're automating was the low-priority junk. So we've built a gorgeous machine that does the wrong thing at the speed of light, and we're out here refreshing Stripe wondering why it's so quiet. His punchline is the one I want tattooed on the inside of my eyelids: the highest-leverage move in a business is making good decisions. Higher leverage than AI. Deciding what NOT to do. He said it's more efficient to decide something isn't a priority than to automate something that isn't a priority. Go ahead, read that twice. I did, out loud, to nobody in particular. And here it is again in case you didn't actually go back to read it.

Go comment and like the video on YouTube as well ! Lots of cool ideas in this one.

EDIT: the use of copilot-instructions.md is very unreliable. Despite clear instructions to load the ICM workspace and read the setup.md at launch, 9 times out of 10 it fails with no meaningful error. Copilot itself tells me that these instructions are more like suggestions.🤣🤣 Instead I have built a skill in Copilot co-work and I have built an agent for the standard Copilot chat. Both of these will reliably launch into my ICM workspace. -------------------------------------------------------------------------------------------------------------------------------------------------------------- We've gone back and forth, here, on whether ICM can work inside Microsoft Copilot. I can now say it definitely does, and that Copilot Cowork is where it works best. I spent today rebuilding my own ICM workspace, currently in Claude, for Copilot — routing file, room context files, a voice file, branding, shared references — and it maps over almost one-to-one. The folders-and-markdown approach we use is almost exactly how Cowork is built to work. Your files live in OneDrive, Cowork reads them on demand, and you get the same context-on-demand behaviour we're used to. Two things make Cowork good for ICM, particularly in a business environment: - It reads your ICM folder tree straight from OneDrive, so you stop re-explaining yourself each session. - It has native access to Outlook, Teams, calendar and SharePoint, so rooms that interface with those apps or their data get easier - The adjustments were small: Copilot itself rewrote my Claude.md to a Setup.md, native M365 instead of connectors, and tightening the original markdown, which had grown, to keep token use down. NB: Copilot, to me, seems a smidgen slower than Claude (Yes, I have Opus 4.8 enabled in Copilot) Guide and blank template at RockfieldIT/icm-copilot-cowork: Implementing ICM in Microsoft Copilot Cowork

FreeCodeCamp just put this out for anyone who wants to master Claude Code. Have fun with this resource: https://youtu.be/7l6bXLAKyEI?si=q0JRHyg-jrxSce63