add: faster prs final

content/posts/faster-prs/index.md

@@ -1,7 +1,7 @@
 ---
 title: "Faster PRs Are High Touch"
 date: 2024-07-24T09:42:34+02:00
-draft: true
+draft: false
 lastmod:
 summary: 
 categories: [writing]

docs/archives/index.html

@@ -211,14 +211,20 @@ <h1>
 <div class="archive-year">
   <h2 class="archive-year-header" id="2024">
     <a class="archive-header-link" href="#2024">2024</a>
-    <sup class="archive-count">&nbsp;2</sup>
+    <sup class="archive-count">&nbsp;3</sup>
   </h2>
   <div class="archive-month">
     <h3 class="archive-month-header" id="2024-July">
       <a class="archive-header-link" href="#2024-July">July</a>
-      <sup class="archive-count">&nbsp;1</sup>
+      <sup class="archive-count">&nbsp;2</sup>
     </h3>
     <div class="archive-posts">
+      <div class="archive-entry">
+        <h3 class="archive-entry-title entry-hint-parent">Faster PRs Are High Touch
+        </h3>
+        <div class="archive-meta"><span title='2024-07-24 09:42:34 +0200 CEST'>July 24, 2024</span>&nbsp;·&nbsp;4 min&nbsp;·&nbsp;Conor Lamb</div>
+        <a class="entry-link" aria-label="post link to Faster PRs Are High Touch" href="https://c0n0.com/posts/faster-prs/"></a>
+      </div>
       <div class="archive-entry">
         <h3 class="archive-entry-title entry-hint-parent">Passing Thoughts Become Action
         </h3>

docs/categories/index.html

@@ -162,7 +162,7 @@ <h1>Categories</h1>
         <a href="https://c0n0.com/categories/retros/">retros <sup><strong><sup>6</sup></strong></sup> </a>
     </li>
     <li>
-        <a href="https://c0n0.com/categories/writing/">writing <sup><strong><sup>7</sup></strong></sup> </a>
+        <a href="https://c0n0.com/categories/writing/">writing <sup><strong><sup>8</sup></strong></sup> </a>
     </li>
 </ul>
     </main>

docs/categories/index.xml

@@ -11,7 +11,7 @@
     </image>
     <generator>Hugo -- 0.123.7</generator>
     <language>en-us</language>
-    <lastBuildDate>Fri, 05 Jul 2024 14:38:44 +0200</lastBuildDate>
+    <lastBuildDate>Sat, 27 Jul 2024 14:32:06 +0200</lastBuildDate>
     <atom:link href="https://c0n0.com/categories/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Writing</title>

docs/categories/writing/index.html

@@ -159,6 +159,25 @@ <h1>
   </h1>
 </header>
 
+<article class="post-entry tag-entry"> 
+<figure class="entry-cover">
+        <img loading="lazy" srcset="https://c0n0.com/posts/faster-prs/images/speed-holes_hubb2c42dd983400505df9cb25a25ad84d_3035728_360x0_resize_box_1.gif 360w ,https://c0n0.com/posts/faster-prs/images/speed-holes_hubb2c42dd983400505df9cb25a25ad84d_3035728_480x0_resize_box_1.gif 480w ,https://c0n0.com/posts/faster-prs/images/speed-holes.gif 480w" 
+            sizes="(min-width: 768px) 720px, 100vw" src="https://c0n0.com/posts/faster-prs/images/speed-holes.gif" alt="Simpson&#39;s Speed Holes Clip" 
+            width="480" height="366">
+</figure>
+  <header class="entry-header">
+    <h2 class="entry-hint-parent">Faster PRs Are High Touch
+    </h2>
+  </header>
+  <div class="entry-content">
+    <p>Reviewing pull requests is a pain in the hole, but a necessary one. It is also massive time sync if you’re actually doing it right.
+Normal PR Process It often looks like this:
+Get slack message: “pwetty pwease review my PR :3 pr link” Open in browser, scroll through the code a bit Inner Monologue: “This looks mostly understandable? Can I can get away without pulling this locally?” Decide to run it locally Stash current branch’s changes (remember that you have a stash saved!...</p>
+  </div>
+  <footer class="entry-footer"><span title='2024-07-24 09:42:34 +0200 CEST'>July 24, 2024</span>&nbsp;·&nbsp;4 min&nbsp;·&nbsp;Conor Lamb</footer>
+  <a class="entry-link" aria-label="post link to Faster PRs Are High Touch" href="https://c0n0.com/posts/faster-prs/"></a>
+</article>
+
 <article class="post-entry tag-entry"> 
 <figure class="entry-cover">
         <img loading="lazy" srcset="https://c0n0.com/posts/passing-thought-action/images/image_hu6ff37d106a8bed7fda725f6bf87d6650_71594_360x0_resize_q75_h2_box_2.webp 360w ,https://c0n0.com/posts/passing-thought-action/images/image_hu6ff37d106a8bed7fda725f6bf87d6650_71594_480x0_resize_q75_h2_box_2.webp 480w ,https://c0n0.com/posts/passing-thought-action/images/image_hu6ff37d106a8bed7fda725f6bf87d6650_71594_720x0_resize_q75_h2_box_2.webp 720w ,https://c0n0.com/posts/passing-thought-action/images/image_hu6ff37d106a8bed7fda725f6bf87d6650_71594_1080x0_resize_q75_h2_box_2.webp 1080w ,https://c0n0.com/posts/passing-thought-action/images/image_hu6ff37d106a8bed7fda725f6bf87d6650_71594_1500x0_resize_q75_h2_box_2.webp 1500w ,https://c0n0.com/posts/passing-thought-action/images/image.webp 1536w" 

docs/categories/writing/index.xml

@@ -11,8 +11,17 @@
     </image>
     <generator>Hugo -- 0.123.7</generator>
     <language>en-us</language>
-    <lastBuildDate>Fri, 05 Jul 2024 14:38:44 +0200</lastBuildDate>
+    <lastBuildDate>Sat, 27 Jul 2024 14:32:06 +0200</lastBuildDate>
     <atom:link href="https://c0n0.com/categories/writing/index.xml" rel="self" type="application/rss+xml" />
+    <item>
+      <title>Faster PRs Are High Touch</title>
+      <link>https://c0n0.com/posts/faster-prs/</link>
+      <pubDate>Wed, 24 Jul 2024 09:42:34 +0200</pubDate>
+      <guid>https://c0n0.com/posts/faster-prs/</guid>
+      <description>Reviewing pull requests is a pain in the hole, but a necessary one. It is also massive time sync if you&amp;rsquo;re actually doing it right.
+Normal PR Process It often looks like this:
+Get slack message: “pwetty pwease review my PR :3 pr link” Open in browser, scroll through the code a bit Inner Monologue: “This looks mostly understandable? Can I can get away without pulling this locally?” Decide to run it locally Stash current branch&amp;rsquo;s changes (remember that you have a stash saved!</description>
+    </item>
     <item>
       <title>Passing Thoughts Become Action</title>
       <link>https://c0n0.com/posts/passing-thought-action/</link>

docs/index.html

@@ -222,6 +222,25 @@ <h1>Hi, I&rsquo;m Conor 👋</h1>
     </footer>
 </article>
 
+<article class="post-entry"> 
+<figure class="entry-cover">
+        <img loading="lazy" srcset="https://c0n0.com/posts/faster-prs/images/speed-holes_hubb2c42dd983400505df9cb25a25ad84d_3035728_360x0_resize_box_1.gif 360w ,https://c0n0.com/posts/faster-prs/images/speed-holes_hubb2c42dd983400505df9cb25a25ad84d_3035728_480x0_resize_box_1.gif 480w ,https://c0n0.com/posts/faster-prs/images/speed-holes.gif 480w" 
+            sizes="(min-width: 768px) 720px, 100vw" src="https://c0n0.com/posts/faster-prs/images/speed-holes.gif" alt="Simpson&#39;s Speed Holes Clip" 
+            width="480" height="366">
+</figure>
+  <header class="entry-header">
+    <h2 class="entry-hint-parent">Faster PRs Are High Touch
+    </h2>
+  </header>
+  <div class="entry-content">
+    <p>Reviewing pull requests is a pain in the hole, but a necessary one. It is also massive time sync if you’re actually doing it right.
+Normal PR Process It often looks like this:
+Get slack message: “pwetty pwease review my PR :3 pr link” Open in browser, scroll through the code a bit Inner Monologue: “This looks mostly understandable? Can I can get away without pulling this locally?” Decide to run it locally Stash current branch’s changes (remember that you have a stash saved!...</p>
+  </div>
+  <footer class="entry-footer"><span title='2024-07-24 09:42:34 +0200 CEST'>July 24, 2024</span>&nbsp;·&nbsp;4 min&nbsp;·&nbsp;Conor Lamb</footer>
+  <a class="entry-link" aria-label="post link to Faster PRs Are High Touch" href="https://c0n0.com/posts/faster-prs/"></a>
+</article>
+
 <article class="post-entry"> 
 <figure class="entry-cover">
         <img loading="lazy" srcset="https://c0n0.com/posts/passing-thought-action/images/image_hu6ff37d106a8bed7fda725f6bf87d6650_71594_360x0_resize_q75_h2_box_2.webp 360w ,https://c0n0.com/posts/passing-thought-action/images/image_hu6ff37d106a8bed7fda725f6bf87d6650_71594_480x0_resize_q75_h2_box_2.webp 480w ,https://c0n0.com/posts/passing-thought-action/images/image_hu6ff37d106a8bed7fda725f6bf87d6650_71594_720x0_resize_q75_h2_box_2.webp 720w ,https://c0n0.com/posts/passing-thought-action/images/image_hu6ff37d106a8bed7fda725f6bf87d6650_71594_1080x0_resize_q75_h2_box_2.webp 1080w ,https://c0n0.com/posts/passing-thought-action/images/image_hu6ff37d106a8bed7fda725f6bf87d6650_71594_1500x0_resize_q75_h2_box_2.webp 1500w ,https://c0n0.com/posts/passing-thought-action/images/image.webp 1536w" 

docs/index.xml

@@ -11,8 +11,17 @@
     </image>
     <generator>Hugo -- 0.123.7</generator>
     <language>en-us</language>
-    <lastBuildDate>Fri, 05 Jul 2024 14:38:44 +0200</lastBuildDate>
+    <lastBuildDate>Sat, 27 Jul 2024 14:32:06 +0200</lastBuildDate>
     <atom:link href="https://c0n0.com/index.xml" rel="self" type="application/rss+xml" />
+    <item>
+      <title>Faster PRs Are High Touch</title>
+      <link>https://c0n0.com/posts/faster-prs/</link>
+      <pubDate>Wed, 24 Jul 2024 09:42:34 +0200</pubDate>
+      <guid>https://c0n0.com/posts/faster-prs/</guid>
+      <description>Reviewing pull requests is a pain in the hole, but a necessary one. It is also massive time sync if you&amp;rsquo;re actually doing it right.
+Normal PR Process It often looks like this:
+Get slack message: “pwetty pwease review my PR :3 pr link” Open in browser, scroll through the code a bit Inner Monologue: “This looks mostly understandable? Can I can get away without pulling this locally?” Decide to run it locally Stash current branch&amp;rsquo;s changes (remember that you have a stash saved!</description>
+    </item>
     <item>
       <title>Passing Thoughts Become Action</title>
       <link>https://c0n0.com/posts/passing-thought-action/</link>