feat: contest today

posts/algorithms/competitive-programming-log.html

@@ -35,6 +35,60 @@
           <h1 class="post-title">Competitive Programming Log</h1>
         </header>
         <article class="post-article">
+          <h2>
+            <a href="https://codeforces.com/contest/1791" target="_blank"
+              >849 (div. 4)</a
+            >&mdash;8/94/2025
+          </h2>
+          <div>
+            Defeating. My speed is improving but I completely wasted my focus.
+            Div. 4 is too easy for me to take seriously now. This itself,
+            though, is a problem with discipline.
+          </div>
+          <blockquote>
+            I only practice for 2 hours a day. There's no point in practicing
+            problems and not trying&mdash;just go do something else.
+          </blockquote>
+          <ol>
+            <li>A = B = trivial</li>
+            <li>
+              C: lost focus on what was being asked, returning the number of
+              removals rather than the minimal length of the string. I want to
+              write code that works first try&mdash;<b
+                >validate your code is actually doing what you're saying before
+                running, both conceptually and in the fine-grained details</b
+              >. I move too fast. Still, I justified \(l\lt r\) instead of
+              \(l\leq r\), a small improvement.
+            </li>
+            <li>
+              D: Instantly saw the solution but rushed the implementation.
+              Eventually I slowed down and then considered the valid split
+              indices.
+              <b
+                >Consider edge cases first. Go through one iteration in your
+                head before coding.</b
+              >
+            </li>
+            <li>
+              E: Utter disaster.
+              <b
+                >Did not read the problem statement and answered a similar (but
+                very different) problem I'd done in the past</b
+              >. By the time I saw this after impatiently submitting ~5 WA, I
+              had lost mental focus. Never submit and hope for a correct answer&mdash;<i>know it</i>.
+            </li>
+            <li>
+              F: Then, I let my previous failure carry through to the next
+              problem. This happened in my last contest but I also dealt with it
+              well:
+            </li>
+            <blockquote>
+              When you're done with a problem (in contest), whether because you
+              solved it or simply gave up, forget about it. Don't obsess about a
+              better solution or put yourself down. Ceaselessly move forward
+              with confidence at all times.
+            </blockquote>
+          </ol>
           <h2>
             <a href="https://codeforces.com/contest/2093" target="_blank"
               >1016 (div. 3)</a
@@ -101,7 +155,9 @@
               F: I had seen a bitwise trie before and didn't review the problem.
               I didn't upsolve then, so I couldn't upsolve now, and getting this
               problem right would've made a massive difference in my
-              performance. These are the consequences&mdash;<b>upsolving is goated</b>.
+              performance. These are the consequences&mdash;<b
+                >upsolving is goated</b
+              >.
             </li>
           </ul>
           <h2>