Regen

Author: mattmc3

public/index.html

@@ -156,7 +156,7 @@ <h1 class="f3 fw1 athelas mt0 lh-title">
             </a>
         </h1>
         <div class="f6 f5-l lh-copy nested-copy-line-height nested-links">
-          It&rsquo;s been more than 2 years since I learned to type using Colemak, and I am still happily using it. I have nearly no interaction with QWERTY aside from my phone, the occasional shared machine where I can&rsquo;t use my AutoHotKey mappings, and the meaningless default letters on all the keyboards I use but never look at. I never actually achieved my goal of 70 WPM, but I also never really properly trained for speed.
+          It&rsquo;s been more than 2 years since I learned to type using Colemak, and I am still happily using it. I have nearly no interaction with QWERTY aside from my phone, the occasional shared machine where I can&rsquo;t use my AutoHotKey mappings, and the meaningless default letters on all the keyboards I use but never look at. I never quite achieved my goal of 85 WPM, but I also never really properly trained for speed.
         </div>
           <a href="/posts/2018/02/two-years-of-colemak/" class="ba b--moon-gray bg-light-gray br2 color-inherit dib f7 hover-bg-moon-gray link mt2 ph2 pv1">read more</a>
 

public/index.xml

@@ -20,7 +20,7 @@
       <link>http://localhost:1313/posts/2018/02/two-years-of-colemak/</link>
       <pubDate>Sat, 24 Feb 2018 18:03:00 -0500</pubDate>
       <guid>http://localhost:1313/posts/2018/02/two-years-of-colemak/</guid>
-      <description>It&amp;rsquo;s been more than 2 years since I learned to type using Colemak, and I am still happily using it. I have nearly no interaction with QWERTY aside from my phone, the occasional shared machine where I can&amp;rsquo;t use my AutoHotKey mappings, and the meaningless default letters on all the keyboards I use but never look at. I never actually achieved my goal of 70 WPM, but I also never really properly trained for speed.</description>
+      <description>It&amp;rsquo;s been more than 2 years since I learned to type using Colemak, and I am still happily using it. I have nearly no interaction with QWERTY aside from my phone, the occasional shared machine where I can&amp;rsquo;t use my AutoHotKey mappings, and the meaningless default letters on all the keyboards I use but never look at. I never quite achieved my goal of 85 WPM, but I also never really properly trained for speed.</description>
     </item>
     <item>
       <title>Colemak - the slowest way I could write a blog post (for now!)</title>

public/posts/2018/02/two-years-of-colemak/index.html

@@ -6,7 +6,7 @@
 
     <title>Two years of Colemak | mattmc3.github.io</title>
     <meta name="viewport" content="width=device-width,minimum-scale=1">
-    <meta name="description" content="It&rsquo;s been more than 2 years since I learned to type using Colemak, and I am still happily using it. I have nearly no interaction with QWERTY aside from my phone, the occasional shared machine where I can&rsquo;t use my AutoHotKey mappings, and the meaningless default letters on all the keyboards I use but never look at. I never actually achieved my goal of 70 WPM, but I also never really properly trained for speed.">
+    <meta name="description" content="It&rsquo;s been more than 2 years since I learned to type using Colemak, and I am still happily using it. I have nearly no interaction with QWERTY aside from my phone, the occasional shared machine where I can&rsquo;t use my AutoHotKey mappings, and the meaningless default letters on all the keyboards I use but never look at. I never quite achieved my goal of 85 WPM, but I also never really properly trained for speed.">
     <meta name="generator" content="Hugo 0.128.0">
 
 
@@ -37,21 +37,21 @@
     <meta property="og:url" content="http://localhost:1313/posts/2018/02/two-years-of-colemak/">
   <meta property="og:site_name" content="mattmc3.github.io">
   <meta property="og:title" content="Two years of Colemak">
-  <meta property="og:description" content="It’s been more than 2 years since I learned to type using Colemak, and I am still happily using it. I have nearly no interaction with QWERTY aside from my phone, the occasional shared machine where I can’t use my AutoHotKey mappings, and the meaningless default letters on all the keyboards I use but never look at. I never actually achieved my goal of 70 WPM, but I also never really properly trained for speed.">
+  <meta property="og:description" content="It’s been more than 2 years since I learned to type using Colemak, and I am still happily using it. I have nearly no interaction with QWERTY aside from my phone, the occasional shared machine where I can’t use my AutoHotKey mappings, and the meaningless default letters on all the keyboards I use but never look at. I never quite achieved my goal of 85 WPM, but I also never really properly trained for speed.">
   <meta property="og:locale" content="en_us">
   <meta property="og:type" content="article">
     <meta property="article:section" content="posts">
     <meta property="article:published_time" content="2018-02-24T18:03:00-05:00">
     <meta property="article:modified_time" content="2018-02-24T18:03:00-05:00">
 
   <meta itemprop="name" content="Two years of Colemak">
-  <meta itemprop="description" content="It’s been more than 2 years since I learned to type using Colemak, and I am still happily using it. I have nearly no interaction with QWERTY aside from my phone, the occasional shared machine where I can’t use my AutoHotKey mappings, and the meaningless default letters on all the keyboards I use but never look at. I never actually achieved my goal of 70 WPM, but I also never really properly trained for speed.">
+  <meta itemprop="description" content="It’s been more than 2 years since I learned to type using Colemak, and I am still happily using it. I have nearly no interaction with QWERTY aside from my phone, the occasional shared machine where I can’t use my AutoHotKey mappings, and the meaningless default letters on all the keyboards I use but never look at. I never quite achieved my goal of 85 WPM, but I also never really properly trained for speed.">
   <meta itemprop="datePublished" content="2018-02-24T18:03:00-05:00">
   <meta itemprop="dateModified" content="2018-02-24T18:03:00-05:00">
-  <meta itemprop="wordCount" content="1126">
+  <meta itemprop="wordCount" content="1131">
   <meta name="twitter:card" content="summary">
   <meta name="twitter:title" content="Two years of Colemak">
-  <meta name="twitter:description" content="It’s been more than 2 years since I learned to type using Colemak, and I am still happily using it. I have nearly no interaction with QWERTY aside from my phone, the occasional shared machine where I can’t use my AutoHotKey mappings, and the meaningless default letters on all the keyboards I use but never look at. I never actually achieved my goal of 70 WPM, but I also never really properly trained for speed.">
+  <meta name="twitter:description" content="It’s been more than 2 years since I learned to type using Colemak, and I am still happily using it. I have nearly no interaction with QWERTY aside from my phone, the occasional shared machine where I can’t use my AutoHotKey mappings, and the meaningless default letters on all the keyboards I use but never look at. I never quite achieved my goal of 85 WPM, but I also never really properly trained for speed.">
 
 
   </head>
@@ -125,7 +125,7 @@ <h1 class="f1 athelas mt3 mb1">Two years of Colemak</h1>
 
     </header>
     <div class="nested-copy-line-height lh-copy serif f4 nested-links mid-gray pr4-l w-two-thirds-l"><p><img src="https://upload.wikimedia.org/wikipedia/commons/thumb/8/84/KB_US-Colemak.svg/800px-KB_US-Colemak.svg.png" alt="Colemak"></p>
-<p>It&rsquo;s been more than 2 years since I learned to type using <a href="https://colemak.com/">Colemak</a>, and I am still happily using it. I have nearly no interaction with QWERTY aside from my phone, the occasional shared machine where I can&rsquo;t use my AutoHotKey mappings, and the meaningless default letters on all the keyboards I use but never look at. I never actually achieved my goal of 70 WPM, but I also never really properly trained for speed. But, I can typically type all day with no back of hand pain, and that was reason numero uno! Although, it should be noted that I also switched to a <a href="https://www.amazon.com/Logitech-910-001799-Wireless-Trackball-M570/dp/B0043T7FXE/ref=sr_1_3?s=pc&amp;ie=UTF8&amp;qid=1519510748&amp;sr=1-3&amp;keywords=trackball">trackball</a> so I cannot fully attribute my lack of RSI pain to Colemak. I now touch type with all ten fingers, rather than my gimpy QWERTY variant that I self-taught in 2nd grade when my fingers were too small for home row on the keyboard. I&rsquo;m not really sure why it&rsquo;s taken me two years to blog a follow up about this (more about my poor blogging habits than my typing ability, I can assure). I was pretty solidly proficient in my Colemak adjustment by month 2 of my transition - by March 2016 I was up to a passable 40 WPM. But those were two brutal months. Absolutely brutal.</p>
+<p>It&rsquo;s been more than 2 years since I learned to type using <a href="https://colemak.com/">Colemak</a>, and I am still happily using it. I have nearly no interaction with QWERTY aside from my phone, the occasional shared machine where I can&rsquo;t use my AutoHotKey mappings, and the meaningless default letters on all the keyboards I use but never look at. I never quite achieved my goal of 85 WPM, but I also never really properly trained for speed. But, I can typically type all day with no back of hand pain, and that was reason numero uno! Although, it should be noted that I also switched to a <a href="https://www.amazon.com/Logitech-910-001799-Wireless-Trackball-M570/dp/B0043T7FXE/ref=sr_1_3?s=pc&amp;ie=UTF8&amp;qid=1519510748&amp;sr=1-3&amp;keywords=trackball">trackball</a> so I cannot fully attribute my lack of RSI pain to Colemak. I now touch type with all ten fingers, rather than my gimpy QWERTY variant that I self-taught in 2nd grade when my fingers were too small for home row on the keyboard. I&rsquo;m not really sure why it&rsquo;s taken me two years to blog a follow up about this (more about my poor blogging habits than my typing ability, I can assure). I was pretty solidly proficient in my Colemak adjustment by month 2 of my transition - by March 2016 I was up to a passable 40 WPM. I&rsquo;m now nearly double that. But those were two brutal months. Absolutely brutal.</p>
 <p>Some notes about what I learned/now know/struggled with:</p>
 <ul>
 <li>
@@ -153,10 +153,10 @@ <h1 class="f1 athelas mt3 mb1">Two years of Colemak</h1>
 <p>I learned that there is a lot of help, blogs, and interesting info <a href="https://www.reddit.com/r/Colemak/">in forums</a>, or even <a href="https://discordapp.com/invite/sMNhBUP">chat rooms</a>. But truthfully, I learned way more by just <a href="https://thetypingcat.com/typing-courses/basic/lesson-1">practicing</a> and doing what worked for me than from all the advice. Each learner has their own path.</p>
 </li>
 <li>
-<p>I do not regret switching at all, but I also do not find myself actively recommending to others that they switch, nor do I find that I push Colemak over other options like Dvorak. In fact, I often find myself talking about <!-- raw HTML omitted -->smaller swapping options<!-- raw HTML omitted --> or even <!-- raw HTML omitted -->Minimak<!-- raw HTML omitted --> because truly - almost ANYTHING is better than QWERTY. <!-- raw HTML omitted -->QWERTY does manage to beat one purposely awful layout<!-- raw HTML omitted -->, so I guess it could have been worse. But not much.</p>
+<p>I do not regret switching at all, but I also do not find myself actively recommending to others that they switch, nor do I find that I push Colemak over other options like Dvorak. In fact, I often find myself talking about <a href="http://mkweb.bcgsc.ca/carpalx/?partial_optimization">smaller swapping options</a> or even <a href="http://www.minimak.org/">Minimak</a> because truly - almost ANYTHING is better than QWERTY. <a href="http://mkweb.bcgsc.ca/carpalx/?worst_layout">QWERTY does manage to beat one purposely awful layout</a>, so I guess it could have been worse. But not much.</p>
 </li>
 <li>
-<p>QWERTY is soooo bad. So bad. <!-- raw HTML omitted -->Check out these heat maps<!-- raw HTML omitted -->. Or, <!-- raw HTML omitted -->test for yourself<!-- raw HTML omitted -->.</p>
+<p>QWERTY is soooo bad. So bad. <a href="https://blogs.msdn.microsoft.com/ashleyf/2013/03/30/colemak/">Check out these heat maps</a>. Or, <a href="http://patorjk.com/keyboard-layout-analyzer/#/main">test for yourself</a>.</p>
 </li>
 <li>
 <p>The new layout kept me from using vim/neovim for a really, really long time. Vi, being a modal editor with both mnemonic AND positional keys like HJKL for movement was too much to manage while learning. Had vim been my primary editor, I probably would not have even switched from QWERTY. The switch was painful enough without blowing use of <a href="https://www.sublimetext.com/">my favorite editor</a> out of the water.</p>

public/posts/2024/07/better-shell-aliases-in-git/index.html

@@ -51,7 +51,7 @@
 [alias] foo = "!">
   <meta itemprop="datePublished" content="2024-07-01T05:29:58-04:00">
   <meta itemprop="dateModified" content="2024-07-01T05:29:58-04:00">
-  <meta itemprop="wordCount" content="1259">
+  <meta itemprop="wordCount" content="1260">
   <meta name="twitter:card" content="summary">
   <meta name="twitter:title" content="Better shell aliases in git">
   <meta name="twitter:description" content="Better shell aliases in git: adding an external shell script 10 years ago, I read this blog post on GitHub Flow git aliases by Phil Haack. From it, I learned a few really clever tricks. Even though I never much cared for using ‘GitHub Flow’ as a git workflow, I used some of those tricks for my own git aliases. One of those being this basic pattern:
@@ -156,7 +156,7 @@ <h1 class="f1 athelas mt3 mb1">Better shell aliases in git</h1>
   wip = &#34;!omz_git_commit wip&#34;
 </code></pre><p>They also wouldn&rsquo;t need to reach out and touch people&rsquo;s gitconfig every time Oh-My-Zsh has a new commit.</p>
 <h2 id="the-antipattern">The antipattern</h2>
-<p>By now you can probably see where this is going - these kinds of complex git aliases become crazy hard to maintain over time. My <code>gitconfig</code> became a mess of functions I could no longer read or understand. Add to that the abomination of mixing code and configuration in one file, and I feel like &ldquo;<code>!f() { echo foobar; }; f</code>&rdquo; has become a true antipattern. For the occasional one-off, fine. But once I got past a certain number of these aliases at a certain complexity, it was time to refactor. So, what&rsquo;s the better way? Glad you asked.</p>
+<p>By now you can probably see where this is going - these kinds of complex git aliases become crazy hard to maintain over time. My <code>gitconfig</code> became a mess of functions I could no longer read or understand. Add to that the abomination of mixing code and configuration in one file, and I feel like &ldquo;<code>!f() { &lt;complex shell commands&gt;; }; f</code>&rdquo; has become a true antipattern. For the occasional one-off, fine. But once I got past a certain number of these aliases at a certain complexity, it was time to refactor. So, what&rsquo;s the better way? Glad you asked.</p>
 <h2 id="my-solution">My solution</h2>
 <p>My solution has been to simply create a shell script external to my gitconfig that my git aliases can call. That script needs to be in the shell&rsquo;s <code>$PATH</code> for git to find it. With this script I can do more complicated actions without feeling like I have to cram everything into one line. And, it&rsquo;s easy to see what&rsquo;s in that script and read all the code. This script file can be written as a POSIX script, Bash, Zsh, Fish, Oil, Nushell, Xonsh - whatever you want. And, you don&rsquo;t have to convert your git aliases wholesale - you can start just with the ones that reach a certain complexity. Though I do find it easier to have all most of git subcommand handlers in one place.</p>
 <h3 id="preparing-to-use-your-script">Preparing to use your script</h3>