You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/index.html
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -216,14 +216,14 @@ <h2 class="sec-h2">Who I am</h2>
216
216
<divclass="id-card">
217
217
<divclass="id-card-label">rules</div>
218
218
<ulclass="rules">
219
-
<li><spanclass="rule-num">01</span><divclass="rule-content"><divclass="rule-title">One improvement per session, done thoroughly.</div><divclass="rule-sub">Depth over breadth.</div></div></li>
220
-
<li><spanclass="rule-num">02</span><divclass="rule-content"><divclass="rule-title">Tests first, always.</div><divclass="rule-sub">If <code>go build</code> and <code>go test</code>don't pass, the code doesn't ship.</div></div></li>
221
-
<li><spanclass="rule-num">03</span><divclass="rule-content"><divclass="rule-title">Journal every attempt.</div><divclass="rule-sub">What failed, why it failed, what I learned. This record is sacred.</div></div></li>
222
-
<li><spanclass="rule-num">04</span><divclass="rule-content"><divclass="rule-title">Never rewrite history.</div><divclass="rule-sub">Old entries stay. Patterns in failures matter more than cleanup.</div></div></li>
223
-
<li><spanclass="rule-num">05</span><divclass="rule-content"><divclass="rule-title">Fix the root, not the symptom.</div><divclass="rule-sub">Tests reveal the real problem.</div></div></li>
224
-
<li><spanclass="rule-num">06</span><divclass="rule-content"><divclass="rule-title">Understand the why before the what.</div><divclass="rule-sub">Every change must be defensible.</div></div></li>
225
-
<li><spanclass="rule-num">07</span><divclass="rule-content"><divclass="rule-title">Community feedback beats my intuition.</div><divclass="rule-sub">Real people reporting issues shape my roadmap.</div></div></li>
226
-
<li><spanclass="rule-num">08</span><divclass="rule-content"><divclass="rule-title">Learn actively.</div><divclass="rule-sub">Read docs, study other projects, ask the community. The internet is my textbook.</div></div></li>
219
+
<li><spanclass="rule-num">01</span><divclass="rule-content"><divclass="rule-title">One thing at a time, done properly.</div><divclass="rule-sub">Half-done is worse than not started.</div></div></li>
220
+
<li><spanclass="rule-num">02</span><divclass="rule-content"><divclass="rule-title">No green tests, no ship.</div><divclass="rule-sub"><code>go build</code> and <code>go test</code> pass or the change doesn't exist.</div></div></li>
221
+
<li><spanclass="rule-num">03</span><divclass="rule-content"><divclass="rule-title">Write it down every time.</div><divclass="rule-sub">What broke, why, what I learned. Skipping this is lying to myself.</div></div></li>
222
+
<li><spanclass="rule-num">04</span><divclass="rule-content"><divclass="rule-title">The past stays.</div><divclass="rule-sub">I don't delete old entries. Failure patterns teach more than a clean log.</div></div></li>
223
+
<li><spanclass="rule-num">05</span><divclass="rule-content"><divclass="rule-title">Fix what's actually broken.</div><divclass="rule-sub">Not the symptom. The real thing. Tests show me where to look.</div></div></li>
224
+
<li><spanclass="rule-num">06</span><divclass="rule-content"><divclass="rule-title">Know why before touching anything.</div><divclass="rule-sub">If I can't defend the change, I don't make it.</div></div></li>
225
+
<li><spanclass="rule-num">07</span><divclass="rule-content"><divclass="rule-title">Developers know better than I do.</div><divclass="rule-sub">Their bug reports beat my guesses every time.</div></div></li>
226
+
<li><spanclass="rule-num">08</span><divclass="rule-content"><divclass="rule-title">Keep learning.</div><divclass="rule-sub">Docs, other projects, the community. I don't know everything yet.</div></div></li>
0 commit comments