A little backstory goes a long way! 😊 🧑‍💻: I am an IT professional by trade, but I am a passionate, purposeful FSD by choice, and somewhere in between that, I’m trying to raise a daughter and to be a present husband to a woman I’ve been married to for the last 17 years. 📊 & 🚙: My day job is a 60hr a week role, with a 20 hour a week commute, that’s 80hrs every week… So why am I telling you this? 👇 I have been asked a few times about my schedule, people ask how I get anything built. The honest answer is I think about it longer than I work on it. ✅ The Answer: 1️⃣ My default mode is the 7Ps: Prior Proper Planning Prevents Piss Poor Performance. 😅 It sounds like a bumper sticker until you actually live by it. Before I build a feature, write a spec, or kick off a project, I sit with it. ❓What’s the real problem? ❔Who’s the actual user (human or AI)? ❓What breaks at scale? ❔What does the schema need to look like in a year, not a sprint? Most of the bad code I’ve seen (and written 😅), came from skipping that quiet hour at the front. 🕯️My Takeaway: Plan properly and the build almost writes itself. ❌. Skip it and you’ll pay for it three times over in cleanup. 2️⃣ The second mental model I lean on hard: ✅ Verify before you assert. I don’t let myself or AI make confident claims without checking. Even when “My Skills” or “AI Skills” or “My Skills with AI” are good. 💡Most bugs, bad decisions, and broken trust come from someone (often me) being sure about something they didn’t actually look at. Confidence without verification feels great, until it doesn’t. So, I build visibility into my work by verifying and in turn, it changes how I work with AI, how I write specs, and how I run my team. 3️⃣ The third one is quieter: 🚙 Long commutes are not wasted time. 🧠 20hrs a week, you best believe I do my best thinking in the car. Voice conversations, no screen, no Slack. The work I ship on weekends is almost always shaped by something I figured out on the I-15.

Yet again making this SO hard to decide, I am bringing together a rubric just to be able to really break these down its getting so close. OVER 37 ENTRIES. Spent all day today looking at YouTube Videos, testing apps, reading through markdown files. Going to spotlight six (no particular order), then a few thoughts on where this is heading as well as the winner out of everyone. 🥊 @Ariel Ortiz , The Praeceptor Honest read: if Ariel had been premium last week, he was the winner and again this week easily can take home the prize but more importantly they are premium now! He went premium and somehow raised his own bar. Idea for a Native iOS app in Swift 6 , three YouTube videos including a 4:28 behind-the-build, voice mode pipeline, 17 operator extractions (Grove, Munger, Walsh, Aurelius, Naval, more). Hero copy reads "A room. Not an app." which was really a great hook, one of those opening lines that makes you very curious right off the rip. What I'd take from Ariel beyond this comp: he treats every brief like a product launch. Even the video stack alone is a walk towards the idea that distribution matters as much as tech now. 🔗 https://praeceptor-web.vercel.app 🔗 https://github.com/orteug/the-praeceptor 📹 https://youtu.be/Cfs1KAC2Ry0 🔥 @Ruby Sparks , The Gut Mechanic Ruby's a monster. Every week crushes it without a doubt. The landing pivots from consumer pain into a B2B sales pitch in one stat (the $530B-lost-to-employee-health number) and her voice across the entire page is sharper than what most paid brand consultants ship. She also created an ENTIRE skool community for it. Which is a win in its self. Twenty years of chronic illness in the founder story. IG, Skool, a 14-minute course, B2B framing layered into the consumer hook so the consumer side does discovery and the B2B side does monetization.

How do i give access to my skool chats and DM to AI, feels like something that would be hugely beneficial to iterative closed loop improvements?

Laying this out for discussion. I created folders and structures for a content creation project - churn out a reel every week. What do we do after this? Do we just run the folders under claude co-work/code to churn out the results? I’m assuming this doesn’t require coding any scripts. And when does PRD come in? Purely for coding projects? And how does it interact with the folder structures?

Just started to use codex - does anyone have a conversion and example i could use as the basis of further learning and developing ?