I was today years old when I realized I did not have some of the most important files that you need in the folder structure that Jake teaches. During today's video call with the VIP group, he went on a deep-dive rabbit trail about the ICM folder methodology that he teaches in his foundations course (free). As he was discussing it, I went to check what my root folder looked like and I did not have a Claude.md or context.md file!!! My productivity skyrocketed ever since I implemented his folder strategy over a month ago, but little did I know that I hadn't even implemented it correctly. 🤯 🤯 🤯 This goes to show that massive action beats over planning every time!

Before I get to the who and why, I want to say this plainly. Picking a winner this round was genuinely hard. I went through every submission. Pulled repos. Read identity files. Compared rules.md sections. Every entry did real work. A lot of you shipped something I would happily use, sell, or hand a client tomorrow. I can NOT explain to you how proud I am of everyone participating in these, you make this community worth and it and there is SO much potential for the future from just ONE competition let alone future ones. 💼 That part matters more than the prize. The $325 covers a year of Premium and that's great but... The portfolio piece is the real value here. A public repo of a working folder-based AI specialist with a clean README and receipts is a resume line that hiring managers can clone and test cold in five minutes. It is also something you can charge for. If you built a specialist that solves a real problem in a real domain, you already have most of what you need to license it to a peer in your industry, sell it as a service, or package it as a Done-with-You engagement. A few quick notes on that, because most of you did not realize what you actually built and I want to Highlight a few of you: 💸 @Nicolas Patron Uriburu USD Routing Coach AR could be sold to every Argentine indie consultor I know. Same playbook works for any country with FX restrictions. Subscription service, recalibrated annually, audit-pack included. It is a product. 🔗 https://github.com/Nicopatron/usd-routing-coach-ar 🔧 @Jannetje van Leeuwen RAMS specialist is a service business in waiting. Irish signage contractors will pay for this. Same model works for any trade with a regulatory documentation burden. Plumbing, electrical, fit-out, demolition. Each one needs its own folder. 🔗 https://github.com/JannetjeIQ/rams-irish-signage-installer

Just had a perfect reminder while building out a client workflow. Yeah, you could throw an LLM at generating a thumbnail for a PDF. Or... a little bash command: "magick bulletin-050326.pdf[0] -background white -alpha remove -alpha off bulletin-050326-tb.png" One line. One battle-tested tool. Instant result. This is the difference between hacking around with AI and actually shipping like an engineer. The Unix/Linux world is full of these quiet, rock-solid one-liners that have been refined for decades. ffmpeg, pdftk, exiftool, jq, ripgrep, parallel... the list goes on. Before you reach for the shiny new wrapper, ask yourself: what's the battle-tested command line way?(Pro tip: ask Claude or Grok to show you the classics. You'll be amazed how often the 20-year-old tool still wins.) Simple. Reliable. Fast. That's engineering. 🚀

I realized I have a bad habit of dropping abbreviations figuring the audience gets it. IYKYK kind of BS. I dropped IWKYM in a conversation with a friend who hasn't read "Dungeon Crawler Carl" and she called me out with a WTF. This group is getting large and people are coming at this (AI, large language models, programming, etc.) with varying degrees of comfort and familiarity. Feeling like I've coded since the stoneage, I grew up with this stuff. From vacuum-tube tape-drive building-sized mainframes to tiny little nano computers, I've been lucky enough to have some hand in things at a lot of layers. I see several posts where people are feeling discouraged when they hit a wall. They aim high and are frustrated when it lands low. Don't compare yourself against the rushing torrent of build posts (especially the successful build releases). You don't see the hours, weeks, months, of struggle - frustrations - and dead-ends hit to get past the pain and into the happy spot where things work (at least for a little while until they break and we go back to the basic(s)). So share your stupid here. Be vulnerable. Let others know the struggle is real and wide. Whether a total new player on the field or the top-tier champion, we all hit the wall. I put this under "General discussion" as it's less about looking for an answer and more just venting. I've learned that one late in life (ask my partner if she wants me to listen or problem solve when I notice she's unhappy about something... much better convo :)

@Aaron Quiroz been crushing it as our Community Triage Lead. Inbound across Instagram, Skool, and Discord has gotten genuinely out of hand, and Aaron stepped in and built real order out of the chaos. He's fast, he's thoughtful, and he actually reads what you send before responding. That matters Going forward, if you're trying to reach me about work, partnerships, projects, or anything that needs a real conversation, please send it to Aaron first. He has visibility into my calendar and priorities, and he'll get things routed correctly. If it needs me, I'll be there. If someone else on the team can handle it faster, even better. I'm still around and still reading. This just makes sure your message actually gets seen and answered instead of buried under hundreds of others. Thanks for rolling with the change. And seriously, thank you Aaron.