Error converting content: marked is not a function
location:: Home - Ora, Boston victory-hour:: yes💪 pomodoro-blocks:: 12🍅 wake-up:: 4:30 AM day:: Monday icon:: ⚡️🌟🌟🌟🌟 - ## 09:28 AM Remember: - ⚡️🏃🙆 🧘 4:30 - 8:30 AM: practice/victoryroutine🌞 #log🪵/victoryHour💪 collapsed:: true - #nowPlaying🎵 #playlist/vibe-newdawn - 🏃 35 #Running 🏃 20 mins. - 🧘 10 mins meditation/invitation20 - 🧘 5 mins pranayama/478breath - Shower & Daily Six Skincare Stack AM Routine. That felt good. - 8:30 AM ☕️ #coffee with boo - 9 AM #sid/daki💦 - oh yeah. full - **Morning Pages** - Hardly 3.5H of sleep. 3 vodkas, 2 too many yesterday :) - Good morning. Solid run today at 6 AM -> yoga -> meditation -> shower -> and my awesome new #Daily Six Skincare Stack routine with new Skincuticle drops added. Then coffee with boo - spilled on Restoration Hardware couch, but we got performance fabric for a reason. - ### 9:30 AM #log🪵/ShutterUp🔓 - 🟩 *9:30 - 1:30 PM*: **4H** Misc Time 8🍅 - #log🪵/secondbrainrefactoring 5🍅 - #log🪵/WeeklyReview 3🍅 - 1:30 PM 🛏 😴 #powernap30😴 Solid 30 min power reset. - 🟪 *1:30 - 4:15 PM*: **2.75H** Misc Time - Catch-up call with Ercan about Renovate Studio beta launch - 🌟 🟩 *4:15 - 5:45 PM*: **1.5H** 🖥 P/Writing Expertise - Letter Writing Sprint. **Day 39** 3🍅 - #nowPlaying🎵 #playlist/purefocus - **Coach's Corner**: Today we're writing a compelling letter! - Created Writing/Passive Voice Testing note with 'by zombies' testing technique - Created template/writing - writing- - **Writing Plan - 90 Minute Sprint**: collapsed:: true - **0-60 min**: Clarify letter purpose and recipient (persuasive, informative, personal) 2🍅 collapsed:: true - I wanna write Vibecoding. Something I have been doing myself. Game changer in the new AI era. - Will write Personal letter using my Letters strategy. - Purpose - Reminder: Block Reference - **Core Questions** - **1. What am I really trying to say?** *(Central message in one sentence)* Vibecoding makes you follow the best industry practices. All of it. - **2. Why should people care?** *(Connection to reader's needs/interests)* You will be using AI to code, if not now then tomorrow. Which means you will need learn how 'manage' AI. We are gonna be mangers. So you better learn process and communication best practices. - **3. What is the most important point?** *(The one thing to remember)* Start with a PRFAQ - **Clarity & Impact** - **4. What is the easiest way to understand this point?** *(Metaphor/Story/Example/Data)* Example - a prfaq and the dev process and implementation plan - **5. How do I want the reader to feel?** *(Motivated/Concerned/Hopeful/Curious)* curious and engaged - **6. What should the reader do next?** *(Clear action step or takeaway)* Try claude code. Copy paste the prompt. - **Style Choices** - **Voice:** Friend. Big Brother. - **Pronouns & Tense:** First-person present. - **Tone:** Direct-conversational - **Attitude:** Passionate - **Scope** - **Include:** *(Specific areas to cover)* PRD and dev plan Claude Memory Wrapping session with next session.md Checklist - document updated, schemas, etc. - **Exclude:** *(Areas intentionally left out)* 1. Memory management outside of project 2. feature branches 3. Code review with another claude 4. Issue management - **One Provocative Thought:** *(The new idea reader should gain)* Amazon nailed vibecoding by treating humans like workhorse agents with no agency. Rule by operating principles. That's what you need. You need to micro manage AI. - **Notes** - A mini project idea that I can screen record? -> chrome extension to capture highlights from kindle. Complex enough. And useful enough for me :) - **Third pomodoro (5:15-5:45)**: Create outline structure - Create 3-5 section headings based on your key points - 5. Learning to AI to is learning to manage. Every dev will need process management skills. 1. Frustaion of sr dev with AI. "It writing node code on client side". "It forgets everything" 2. AI is like working to new hires, every day. Needs constant re retraining 3. It's solved problem. You do it by adding constraints nad curtailing degree of freedom. IT's a creating a process. Industry best practices - 10. Start with PRFAQ. Govern like Bezos - Amazon manager Operating Principles. Have yours. 1. AI needs context. Orient it at the highest level first. Like a new employee - the purpose and why is the orientation program. Nothing like making is purpose backwards from the customer. 2. Amazon PRFAQ forces it work backwards from the outcome. Then do in lower level details. You go from high level goal post that should NOT (ideally) change, to lower where taks and methods are constanlt refactored. Welcome to top down toxic management. We don't let our employees veer out of their lanes. - 20. The dev plan 1. There are no one shot solutions. That's for demos. A real feature would take you 3-5 sessiosn where each session could 2-4 hours long. So say it could a week until a PRFAQ is fully implented by the AI. It's hard work bro! Sorry. 2. The plan keeps the focus. Each task is mission which once complete makes the agent come back to post, report on outcome, which updates the plan. 3. Example of tracker update - 30. AI has amnesia - Memory 1. Did you AI has no memory? The a stateless function. In essence, models have knowledge cutoff, after that, they learn nothing. Today your entire life sotry, tomorrow woof, you are meeting your AI afriend againm, and it has forgeotten everything 2. memory is engineering on top. Momento. 3. Chatgpt give you an illusion of conitnuoys convo, bu copying the full thread, over and over again as context. 3.1. Claude code context limit screenshot 4. Here comes Claude.md, from claude code. This is your tatoo parlor. Like your body you have limited space - you can't have entire codebase into context. So - welcome to mangenet - now you need to decide what context to keep and what to discrad when. 5. Also remberber, conext switches are bad, you complained about it to your manger. Yyea, now help your AI. Keep it focused and avoid context switch. It won't complain. It just starts hallucinating. 6. - 40. List of best practices. Implementing vibecoding in your workflow 1. Session management. nad next session prompt. 2. update docs and memory after each session. 3. code review code. 4. opther teasers that we will go into full article - out of scope - Draft a hook that introduces the concept of Vibecoding - Create a closing CTA that encourages trying Claude Code - **To Continue Next Session (Day 40)**: - Draft the letter body with clear paragraphs for each point - Craft opening hook and meaningful conclusion - Edit for clarity, concision, and impact using Writing/Passive Voice Testing technique - Final polish (tone consistency, formatting) - **Success metrics**: - Minimal: Complete draft with all key points included - Target: Polished letter ready to send with compelling argument - Stretch: Add memorable metaphor or story element that elevates the writing - 🟪 *5:45 - 7:15 PM*: **1.5H** Misc Time - Sync with Ercan on launch timeline - Catch up on emails - 🍽️ *7:15 PM*: Dinner with boo - 8:30 PM - perfect #shower time. With #Daily Six Skincare Stack PM routine locked in. - 🟩 *9:30 - 10:00 PM*: **0.5H** Focus Time 🍅 - Implemented knowledge management structure upgrades - Created `/guides/` directory with detailed documentation - Updated CLAUDE.md with atomic rules and cleaner organization - Removed unused Zettelkasten ID system - 10:10 PM - Lights off. Going to bed. - 🌟️ Daily 5 - DONE Complete weekly review for Week 20 - DONE Complete Letter Writing Sprint for P/Writing Expertise Day 39 - DONE Add today's pomodoro count to journal properties (updated to 12🍅) - DONE Practice Mobility/Door-Frame Thoracic Opener between pomodoros (after each 25-min session) - DONE Update 2025/week21 and business follow-ups - DONE Review shopping lists in Closet Directory and Skincare Systems - decided against Meta Ray-Ban for brother, not the right time