I’m turning 58 this year, and if I’m honest… the resistance doesn’t get quieter. It gets louder. The voice changes. It’s no longer, “What if you fail?” Now it says, “You’ve already worked hard enough.” “It’s okay to slow down.” “You’ve earned the right to coast.” And yes… there’s truth in some of that. We all have permission to slow down. To choose quite. To redefine what success looks like. But sometimes that voice isn’t wisdom. Sometimes it’s just comfort trying to take over. Because I know there’s still more in me. I have a team counting on me. Goals I still want to hit. Work that still matters. I don’t want to look back and realize I backed off too soon. At this stage, it’s not about grinding harder. It’s about being honest with yourself. When do you truly need rest? And when are you just avoiding the next level? That line matters. Because the goal isn’t to burn yourself out. But it’s also not to talk yourself out of what you’re still capable of. Curious… where is resistance showing up for you right now?

Hey, I’m Eugene, and prompt engineering is something I take seriously. If there’s one piece of advice I’d give you, it’s this, build yourself a template. Something simple, flexible, and genuinely reusable. Think of it as a framework you can return to whenever you need it. You drop in the details for your current task, and it gives you exactly what you’re looking for, without starting from scratch. I run a community of prompt engineers, mostly people in their 20s to 40s, and this is the principle I come back to again and again. Build a strong template, one that’s reusable, reliable, and repeatable. Here’s what that looks like in practice. Reusable, it works across different situations and still delivers. Reliable, you can trust it even as tools evolve. Repeatable, it produces consistent results across platforms, and you can expand it without breaking the structure. So how do you actually apply this? Start with a simple structure like RTF, Role, Task, Format. Or take it a step further with RTCF, adding Context. Once you’ve got that foundation, build your template around it. For example: Role: You are a high-level copywriter Task: Write a landing page Context: Product is a beginner-friendly drum course for adults Format: Clear sections, persuasive tone, concise paragraphs Or: Role: Expert prompt engineer Task: Generate a YouTube script Context: Audience is beginners learning prompt engineering, tone is clear and engaging Format: Hook, main points, examples, closing summary Now, whenever you need a prompt, whether it’s for GPT, Claude, or Perplexity, you follow a simple process. Open your template, drop it in, and layer your context. For instance: “I need a prompt that writes a sales email for a digital product. It should feel personal, not pushy. It needs to highlight benefits clearly and include a soft call to action.” Or: “I need a prompt that generates Instagram captions for a photography page. It should match an outdoor, reflective tone and include subtle storytelling.”

I reviewed the amazing way we learned to convert content to a vivid image With 3 step process Molley taught us. I am amazed at the result: 1.First I uploading the source from YouTube videoAI Just Compressed 160 Years of Aging Research — Here's What They Found | Dr. David Sinclair ; :https://www.youtube.com/watch?v=tMYoiHSYgWw&t=212s: into the notebooklym AI: htps://notebooklm.google/ I then selected the infogenic with the right arrow and clicked on Scientific to create the image you see on the right below. Lastly I took the Image seen below and imported that in to Gemini and said- "Animate this. Abra Cadabra - it produced that cool video. So cool to learn this.

Hi there! I watched all of day 1 and it was very interesting, but I unfortunately wasn’t able to take any notes. Does somebody here perhaps have a summary they’d be willing to share? Thanks in advance!!