<p>What happens when you stop collecting advice and start building systems.</p>
<hr>
<h2>The Starting Point</h2>
<p>I had notes everywhere. Notion pages about deep work techniques. Screenshots of training programs. Bookmarked podcasts about career growth. Scattered markdown files with engineering principles I wanted to remember. A graveyard of good intentions.</p>
<p>The problem was never lack of information. It was lack of structure. Every time I wanted to revisit my flow state protocol or check my training split, I spent 10 minutes trying to find where I wrote it down. Half the time I gave up and just Googled it again.</p>
<p>So I did what any engineer would do. I turned it into a repo.</p>
<h2>What Peak Self Is</h2>
<p><a href="https://github.com/Cyvid7-Darus10/peak-self">Peak Self</a> is a personal knowledge base for optimal human performance, organized into five domains:</p>
<table>
<thead>
<tr>
<th>Domain</th>
<th>What's Inside</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>Focus</strong></td>
<td>Flow state protocol, environment design, deep work scheduling, NSDR protocols</td>
</tr>
<tr>
<td><strong>Fitness</strong></td>
<td>Polarized training (80/20), Big 6 lifts, Zone 2 cardio, nutrition, sleep optimization</td>
</tr>
<tr>
<td><strong>Career</strong></td>
<td>Growth flywheel, T shape skill model, high income skills, networking systems</td>
</tr>
<tr>
<td><strong>Engineering</strong></td>
<td>SOLID, Gall's Law, Conway's Law, debugging mental models, DORA metrics, ADRs, RFCs</td>
</tr>
<tr>
<td><strong>Mindset</strong></td>
<td>Identity architecture, motivation vs discipline, environment design, operating identity</td>
</tr>
</tbody>
</table>
<p>Plus a curated resources section. The YouTube channels, podcasts, and books that actually shaped my thinking. Not a generic "top 10" list.</p>
<h2>Why a Git Repo</h2>
<p>A Notion page is where knowledge goes to feel organized. A git repo is where knowledge goes to be used.</p>
<p>The repo format gives me version history so I can see how my protocols evolved. My training split from 6 months ago was wrong. Git shows me exactly how and when I corrected it. It gives me pull requests, so when I update a protocol, I review the diff. That forces me to be intentional about changes instead of casually editing a paragraph.</p>
<p>Anyone can fork it and make it their own. My training protocol will not work for everyone. But the structure might.</p>
<p>And markdown just works. It renders on GitHub, works in any editor, is greppable, and plays nice with AI tools.</p>
<h2>The Core Philosophy</h2>
<blockquote>
<p>You don't rise to the level of your goals. You fall to the level of your systems.</p>
</blockquote>
<p>That quote from James Clear is the thesis of the entire repo.</p>
<p><strong>Elimination before optimization.</strong> Before adding a productivity tool, remove the phone from the room. Before adding a supplement, fix your sleep. The biggest gains come from removing friction, not adding tools.</p>
<p><strong>Identity over discipline.</strong> "I am someone who protects their deep work" is more durable than "I should focus more." The identity behavior loop, where identity shapes processes and processes produce outcomes, is the foundation of the mindset section.</p>
<p><strong>Systems over goals.</strong> A goal is "lose 10kg." A system is "train 6 days a week with polarized intensity." Goals are endpoints. Systems are the daily machinery that gets you there and keeps you there after you arrive.</p>
<p><strong>Compound returns.</strong> One 90 minute flow state session per day, 5 days a week, for a year is 390 hours of deep work. Most people do not get 390 hours of deep work in 3 years. Small daily inputs create exponential long term output.</p>
<h2>What Writing It Down Forced Me to Confront</h2>
<h3>My flow state protocol was aspirational, not actual</h3>
<p>When I wrote down my deep work protocol, I realized I was documenting the version I wanted to follow, not the one I actually followed. I wrote "phone in another room" but my phone was on the desk, face down. I wrote "one monitor" but I had two.</p>
<p>Writing it as a protocol, not a blog post, not a journal entry, but a literal step by step protocol, made the gap between aspiration and practice embarrassingly visible. I had to either change the document or change my behavior. I changed my behavior.</p>
<h3>My training had no periodization</h3>
<p>I was going to the gym consistently. But I had no structure. Some weeks were all upper body. Some weeks I skipped cardio entirely. I had no idea what my Zone 2 heart rate range was.</p>
<p>Writing the training protocol forced me to actually design a program. Polarized training with 80% Zone 2 and 20% high intensity. Three strength days. Clear progression scheme. The Big 6 lifts (squat, deadlift, bench, overhead press, pull up, row) became the non negotiable foundation.</p>
<h3>Career growth was accidental</h3>
<p>I had been promoted and changed jobs, but I could not articulate my growth system. Writing the career section made me realize I was relying on being good at my job and hoping people noticed. The growth flywheel gave me a framework to be deliberate about each link in the chain. Skills produce output. Output builds reputation. Reputation unlocks opportunities. Opportunities provide feedback. Feedback sharpens skills.</p>
<h2>The Engineering Section Is Different</h2>
<p>Most personal knowledge base projects are about habits and productivity. Peak Self also includes an engineering section because software engineering is my craft and I wanted my principles documented alongside everything else.</p>
<p>It covers the laws every senior engineer should know. Gall's Law, Conway's Law, Hyrum's Law, Goodhart's Law. It covers practical processes like ADRs, RFCs, postmortems, and documentation driven development. It includes DORA metrics and a debugging mental model.</p>
<p>The engineering section follows the same philosophy as the rest. Actionable protocols, not theory. Every principle includes what it actually looks like in daily work.</p>
<h2>What I Would Do Differently</h2>
<p>Start with fewer sections and go deeper. The initial version tried to cover everything at once. A focused flow state protocol and training program would have been more useful than five half developed sections. I ended up rewriting most of it anyway.</p>
<h2>The Bigger Realization</h2>
<p>The act of writing down how you operate reveals whether you actually have a system or just a collection of habits you fell into. Most of what I thought were deliberate choices turned out to be defaults I had never questioned.</p>
<p>Peak Self is not finished. It is a living document. But the structure is there, and having it in a repo means it evolves with me instead of rotting in a notes app.</p>
<h2>Links</h2>
<ul>
<li><strong>GitHub:</strong> <a href="https://github.com/Cyvid7-Darus10/peak-self">peak-self</a></li>
</ul>
