<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:media="http://search.yahoo.com/mrss/"><channel><title><![CDATA[Mario's Blog on Productivity]]></title><description><![CDATA[Mario's Blog on Productivity]]></description><link>https://blog.blakeinc.de/</link><image><url>https://blog.blakeinc.de/favicon.png</url><title>Mario&apos;s Blog on Productivity</title><link>https://blog.blakeinc.de/</link></image><generator>Ghost 3.0</generator><lastBuildDate>Thu, 07 May 2026 19:40:19 GMT</lastBuildDate><atom:link href="https://blog.blakeinc.de/rss/" rel="self" type="application/rss+xml"/><ttl>60</ttl><item><title><![CDATA[How to Organize Your Email]]></title><description><![CDATA[I went from a very time-consuming, elaborate way of organizing my emails to a dead-simple one and managed to save time doing so – and so can you!]]></description><link>https://blog.blakeinc.de/how-to-organize-your-email/</link><guid isPermaLink="false">5d5dc03036e57a28f82a279f</guid><category><![CDATA[Productivity]]></category><dc:creator><![CDATA[Mario Dederichs]]></dc:creator><pubDate>Sun, 02 May 2021 22:14:00 GMT</pubDate><media:content url="https://blog.blakeinc.de/content/images/2019/08/mailbox.jpg" medium="image"/><content:encoded><![CDATA[<!--kg-card-begin: markdown--><img src="https://blog.blakeinc.de/content/images/2019/08/mailbox.jpg" alt="How to Organize Your Email"><p>Let's face it: if you think about how to organize your emails, chances are you receive a ton of them. The average number of emails an office worker receives per day is 121, <a href="https://expandedramblings.com/index.php/email-statistics/">according to DMR</a>. And while there is a <a href="https://tech.co/news/slack-replacing-email-workplace-2018-08">shift of communication to instant messaging</a> (e.g. Slack) or project management tools like Asana or Trello, the good old email is here to stay — at least for the foreseeable future.</p>
<p>So, how do we tackle this slew of messages flooding our inbox? We can't just leave them unattended, can we? And where do they go once we've dealt with them?</p>
<h2 id="overcategorizersanonymous">Overcategorizers Anonymous</h2>
<p>In the past, I was meticulous about sorting my emails. Everything <em>had</em> to have its place. I had a complex setup of categories, sub-categories, even sub-sub-categories. Every company I'd been in touch with had its own designated folder. How very German of me.</p>
<p>My train of thought was simple: instead of spending minutes painstakingly looking for a lost email, it's much easier to browse a perfectly organized folder and see the whole history of communication on a specific topic.</p>
<p>Now, guess how many times I've used these folders in the past twelve months?</p>
<p>Yup. Not once.</p>
<p>Because the search function of my email client is so quick and powerful, I haven't once felt the need to sift through my categories in search of the one mail I'm looking for. I spent all this time categorizing and not once did I ask myself if I actually <strong>need</strong> categorization.</p>
<h2 id="timenotwellspent">Time Not Well Spent</h2>
<p>The busier my job got, the less time I had to categorize. This lead to a bloated inbox with hundreds and, later, thousands of uncategorized emails. I completely lost track of which emails had already been attended to and which hadn't.</p>
<p><a href="https://xkcd.com/1783/"><img src="https://blog.blakeinc.de/content/images/2019/11/xkcd_emails.png" alt="How to Organize Your Email" title="As always, XKCD's comics are dead on."></a></p>
<p>My own system was failing me: I simply didn't have the time to uphold it anymore. It needed to go.</p>
<p>Categories, folders, labels – they are tools. If your tool <em>hinders</em> your progress instead of <em>fueling</em> it, you have to cast it aside. There is no price for best-organized inbox.</p>
<p>Look at these two graphs:</p>
<p><img src="https://blog.blakeinc.de/content/images/2019/12/emails_twographs.svg" alt="How to Organize Your Email" title="Tasks you do much more frequently should take the least amount of time possible."></p>
<p>Which of these two actions do you perform more often? Managing<sup class="footnote-ref"><a href="#fn1" id="fnref1">[1]</a></sup> emails or looking for past emails? For me, it's the former by a long shot. The best way to increase my efficiency is to pursue Graph B and cut down the time dedicated to each mail.</p>
<h2 id="threepurposesofemails">Three Purposes of Emails</h2>
<p>But first, let's zoom out a bit. Every email serves a purpose. It's either information to be absorbed, it triggers a reply, or it's a task you need to tackle.</p>
<h3 id="information">📄 Information</h3>
<p>Most emails are simple FYIs. It's information you need to process, no other action required. Once you have absorbed the information, the email has served its purpose. Even if you have to reference this information at a later date, it's much better to write it down elsewhere — a notebook, a note-taking software, a wiki, or a Word document.</p>
<h3 id="reply">💬 Reply</h3>
<p>Since email is, in theory, a tool for bi- or multilateral communication, many mails require a reply. If you're not in customer service (and not even then!), you don't need to reply to emails right away. That is especially true if they need a more thorough and thought-out answer.<sup class="footnote-ref"><a href="#fn2" id="fnref2">[2]</a></sup> Snoozing or tagging emails for a later reply is helpful so that nothing slips through the cracks.</p>
<h3 id="task">✅ Task</h3>
<p>It's also possible that mails want you to actually <em>do</em> something (boo!). While there are plenty of great ways to manage tasks, your email inbox is not it. If the email triggers a task (but not a reply) add it to your to-do list and throw the actual email away.</p>
<h2 id="sowhatisthebestway">So What <em>Is</em> the Best Way?</h2>
<p>Let me preface this question by saying the best system to organize your emails is one that helps <em>you</em>. Yes, boring, I know, but if you need a gazillion categories to work efficiently, more power to you! If you leave all your emails just sitting in the inbox, that's fine, too.</p>
<p>There are, however, a few tricks you can use to weed out time-wasters that unnecessarily clutter up your process.</p>
<h3 id="cleanupyourinbox">Clean Up Your Inbox</h3>
<p>Imagine opening your physical mailbox to find a new letter. You open the envelope, read the letter — and throw it right back through the mailbox slot. Pointless much? Still, this is the way a majority of us handle our email inbox. It becomes a graveyard for mails we've already dealt with.</p>
<p>To me, the inbox is restricted to emails I <em>haven't</em> had the chance to manage.</p>
<p>Once I <em>do</em> tackle an email, there are three steps:</p>
<ol>
<li>Read the mail</li>
<li>Do something with it (acknowledge, document, reply, forward, snooze)</li>
<li>Archive or delete it</li>
</ol>
<p><img src="https://blog.blakeinc.de/content/images/2019/11/inbox_zero.png" alt="How to Organize Your Email" title="Reaching inbox zero is a satisfying feeling, believe me."></p>
<h3 id="betriggerhappy">Be Trigger-Happy</h3>
<p>If you don't need an email anymore, delete it. This is not only great for keeping your mailbox clean but also advisable for data protection reasons<sup class="footnote-ref"><a href="#fn3" id="fnref3">[3]</a></sup>. If there is a justifiable reason to retain this mail, put it in a separate archive folder but be sure to move it out of your inbox.</p>
<p><img src="https://blog.blakeinc.de/content/images/2019/11/archive-button.png" alt="How to Organize Your Email" title="Gmail has an 'archive' function that does this neatly with a single click. Most of my emails go there directly after reading."></p>
<h3 id="reducecategories">Reduce Categories</h3>
<p>Take a long, hard look at what categories/labels you <em>really</em> need. In reference to the graph above: if you spend more time maintaining categories than actually using them, it's time to re-evaluate their usefulness.</p>
<p>If a category can easily be replicated by an automatic filter or a smart search query it serves no additional, real purpose. Sorting emails manually should be reserved for categories a machine <em>can't</em> assign.</p>
<h2 id="mysystem">My System</h2>
<p>So how do <em>I</em> manage my emails?</p>
<p>The system I came up with is a hybrid of <a href="https://flow-e.com/inbox-zero/">Inbox Zero</a> and a project planning method called <a href="https://medium.com/adventures-in-consumer-technology/getting-things-done-the-now-next-later-framework-9cc786b4fad8">&quot;Now, Next, Later&quot;</a>.</p>
<p>With that, I drastically reduced the number of categories from a whooping 64 to a manageable ... one. Two if you count the inbox.</p>
<p>In that, you have three buckets:</p>
<table>
<thead>
<tr>
<th style="text-align:left">Category</th>
<th style="text-align:left">Description</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left">Now</td>
<td style="text-align:left">Things that have to be tackled as soon as possible.</td>
</tr>
<tr>
<td style="text-align:left">Next</td>
<td style="text-align:left">Things that don't have to be handled right away but soonish.</td>
</tr>
<tr>
<td style="text-align:left">Later</td>
<td style="text-align:left">Things that are interesting/relevant but not pressing.</td>
</tr>
</tbody>
</table>
<h3 id="nowinbox">Now (Inbox)</h3>
<p>My <strong>Now</strong> bucket lives in my inbox. I typically don't leave the office without an empty inbox so this makes sure that urgent matters don't get thrown under the bus.</p>
<p>So whenever I see a read email in my inbox I know: this is something I should be taking care of – and <em>fast</em>.</p>
<h3 id="nextsnooze">Next (Snooze)</h3>
<p>Gmail has this handy feature that allows you to 'snooze' emails. You can define a date at which the mail gets thrown back into your inbox. If you know that an email will be relevant, say, next week, snooze it until week. If you have time to tackle it tomorrow, snooze until tomorrow!</p>
<p>There are two great strategies for using the snooze button:</p>
<ul>
<li>Set a recurring time slot each week (&quot;Friday at 2PM is when I manage emails&quot;)</li>
<li>Snooze to when you have the time (&quot;I'll have to time to care of mails tomorrow!&quot;)</li>
</ul>
<p>If your mail provider doesn't have a snooze function, you can create a '<strong>Next</strong>' category or label instead.</p>
<h3 id="latercategory">Later (Category)</h3>
<p>Some mails are interesting but not time-critical, like an interesting newsletter or an article that someone shared. These typically go to the one category that I use, the '<strong>Later</strong>' category.</p>
<p>If you reserve a certain time slot each day or week to tackle emails and you're running out of mails in the '<strong>Now</strong>' or '<strong>Next</strong>' buckets, it's great to take a look at the mails in the Later category.</p>
<h3 id="flowchart">Flowchart</h3>
<p>In order to visualize, I made this handy dandy flowchart:</p>
<p><img src="https://blog.blakeinc.de/content/images/2021/09/email-flowchart.svg" alt="How to Organize Your Email"></p>
<h2 id="tldr">tl;dr</h2>
<ul>
<li>Only use the categories you <em>really</em> need and use regularly</li>
<li>If a reply takes two minutes or less, answer right away</li>
<li>If the email triggers a task (but not a reply) put it on your to-do list and archive it right away</li>
<li>If there's no justifiable purpose to retain an email, delete it</li>
<li>Find a system that works for you, don't work for a system!</li>
</ul>
<hr class="footnotes-sep">
<section class="footnotes">
<ol class="footnotes-list">
<li id="fn1" class="footnote-item"><p>When I talk about &quot;managing&quot; emails I mean three things: reading, deciding what needs to be done as a follow-up (reply, task, forward), and sorting/archiving/deleting. <a href="#fnref1" class="footnote-backref">↩︎</a></p>
</li>
<li id="fn2" class="footnote-item"><p>I'm in touch with a lot of so-called 'Customer Success Managers'. I'd rather wait a day or two for a well-thought-out and comprehensive reply than having a lightning-fast answer that doesn't help me in any way and ends up causing more effort on my part. <a href="#fnref2" class="footnote-backref">↩︎</a></p>
</li>
<li id="fn3" class="footnote-item"><p>I live in the European Union, so I want to make sure to comply with GDPR. Deleting emails that serve no purpose (and where I can't comfortably rely on legitimate interest to retain them) is necessary. Please note that I'm not a lawyer and this blog post does not qualify as legal advice. <a href="#fnref3" class="footnote-backref">↩︎</a></p>
</li>
</ol>
</section>
<!--kg-card-end: markdown--><h2 id="image-credit">Image Credit</h2><ul><li>Header photo by <a href="https://unsplash.com/@alex19perz?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Alex Perz</a> on <a href="https://unsplash.com/search/photos/mail?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></li><li>Kitten image by <a href="https://unsplash.com/@yirage?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Andrii Podilnyk</a> on <a href="https://unsplash.com/s/photos/kitten?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></li></ul>]]></content:encoded></item><item><title><![CDATA[Why I Fell in Love with Markdown]]></title><description><![CDATA[Whenever I write longer, structured texts, I use Markdown. I'm convinced that you should, too. Here's what's so great about it.]]></description><link>https://blog.blakeinc.de/why-i-fell-in-love-with-markdown/</link><guid isPermaLink="false">5ddc493d714c8a42db02d808</guid><category><![CDATA[Productivity]]></category><category><![CDATA[Writing]]></category><dc:creator><![CDATA[Mario Dederichs]]></dc:creator><pubDate>Wed, 28 Apr 2021 20:54:00 GMT</pubDate><media:content url="https://blog.blakeinc.de/content/images/2019/11/markdown.jpg" medium="image"/><content:encoded><![CDATA[<!--kg-card-begin: markdown--><img src="https://blog.blakeinc.de/content/images/2019/11/markdown.jpg" alt="Why I Fell in Love with Markdown"><p>If you ask one hundred frequent writers to name their favorite writing tool, you'll get one hundred and one recommendations.</p>
<p>Here's some breaking news: what software you choose doesn't matter. What <em>does</em> is squeezing the right words out of your brain. That, and structuring your prose in a way that underlines the point. Most writing software distracts you from just that by offering dozens of features that may be great for formatting but are ultimately irrelevant for writing.</p>
<p>That's where Markdown comes into play.</p>
<h2 id="whatismarkdown">What Is Markdown?</h2>
<p>Simply put, Markdown is a markup language. Yep, that's why the name is so clever. So what's <em>that</em>? In short, it's a language that uses special characters (or tags) to structure information like text, images, tables — and so on. The beauty of markup languages is that both machines <em>and</em> humans can read it without effort.</p>
<p>Those who have dabbled in web development know the arguably most widely used markup language, HTML. Heck, it's even in the name: HyperText <strong>Markup Language</strong>. And even if you haven't, markup languages are commonly used in message boards (BBCode), scientific writing (LaTeX), wikis (Wikitext), or even Instant Messaging (Facebook Messenger, WhatsApp).</p>
<p>Here's how you'd make a text <strong>bold</strong> in different markup languages:</p>
<table>
<thead>
<tr>
<th>Markup Language</th>
<th>Bold Text</th>
</tr>
</thead>
<tbody>
<tr>
<td>HTML</td>
<td><code>How &lt;b&gt;bold&lt;/b&gt; of you.</code></td>
</tr>
<tr>
<td>BBCode</td>
<td><code>How [b]bold[/b] of you.</code></td>
</tr>
<tr>
<td>LaTeX</td>
<td><code>How \textbf{bold} of you.</code></td>
</tr>
<tr>
<td>Wikitext</td>
<td><code>How '''bold''' of you.</code></td>
</tr>
<tr>
<td>WhatsApp</td>
<td><code>How *bold* of you.</code></td>
</tr>
<tr>
<td>Markdown</td>
<td><code>How **bold** of you.</code></td>
</tr>
</tbody>
</table>
<p>You see? It's not rocket science. You have a certain tag that indicates bold text begins (e.g. <code>&lt;b&gt;</code> in HTML) and ends (<code>&lt;/b&gt;</code> in HTML). Most markup languages — and Markdown, too — use the same string of characters for &quot;opening&quot; and &quot;closing&quot; such a tag.</p>
<p>So, is it only something for geeks? No, not quite. There are plenty of uses for just about everyone who writes longer texts.</p>
<h2 id="whynotword">Why not Word?</h2>
<p>But what's the point? Why go through the hassle of learning a markup language if you can just select the text, hit bold and be done with it?</p>
<p><img src="https://blog.blakeinc.de/content/images/2019/11/wordbold.gif" alt="Why I Fell in Love with Markdown"></p>
<p>There's nothing wrong with that, of course, but there are three heavy drawbacks:</p>
<ul>
<li>You can't — at first glance — see what text is formatted and in which way</li>
<li>Taking off your mouse hand off the keyboard disrupts your typing<sup class="footnote-ref"><a href="#fn1" id="fnref1">[1]</a></sup></li>
<li><strong>Most importantly,</strong> plenty of options to distract you from what you should be doing: writing and structuring your text</li>
</ul>
<h2 id="writingstructuringandlayout">Writing, Structuring, and Layout</h2>
<p>Imagine you have the perfect idea and outline for a text you're going to write. There are three steps that follow:</p>
<ol>
<li>Writing</li>
<li>Structuring</li>
<li>Layout</li>
</ol>
<p>An alarming number of people confuse the latter two. Structuring your text isn't something <em>visual</em>, it's about <em>organizing</em> your writing. It's fleshing out <em>what</em> elements you have, the headings, emphases, images, and references — and not <em>how they look</em>.</p>
<p>Layout is what comes <strong>last</strong>. Why? Because it's distracting. Obsessing about finding the perfect font to suit your tone takes your focus away from what really matters: forging the strongest possible prose. This <a href="https://youtu.be/CAmiNMGIFWA?t=6">clip from BoJack Horseman</a> sums it up perfectly.</p>
<p>This is how most websites work: you use a markup language (like HTML) to structure the content and apply the visual design later (via CSS). Writing should be, in principle, the same.</p>
<p>Markdown is the perfect tool to separate structuring and layout because it's stupid, distraction-free, and portable.</p>
<h2 id="threereasonswhymarkdownisthebomb">Three Reasons Why Markdown Is the Bomb</h2>
<h3 id="markdownisstupidinagoodway">Markdown Is Stupid (in a Good Way)</h3>
<p>There's not a lot of things you can do with Markdown. You can add headings, emphases (bold, italics, underline, strikethrough), lists, images, tables, quotes, footnotes, links, code blocks, and horizontal rules.</p>
<p>That's it. That's the complete list. There are no colors, no fonts, no text sizes, no way to align text, no margins, paddings, or line heights.</p>
<p>That also means it's super easy to master. With the help of a <a href="https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet">Markdown cheat sheet</a>, you'll learn it in a matter of minutes and know it by heart in a matter of days.</p>
<h3 id="markdownisdistractionfree">Markdown Is Distraction-Free</h3>
<p>Humans aren't very good at resisting distraction. Having a full-fledged word processor like Word or LibreOffice isn't ideal because it invites the temptation of fiddling with the layout instead of focusing on what's important: writing.</p>
<p>Crafting compelling prose is a difficult task that needs deep focus. And in order to do this kind of &quot;deep work&quot;, we need a toolset that takes everything away but the bare necessities. Because of its strictly limited feature set, Markdown is the ideal language for distraction-free writing.</p>
<h3 id="markdownisportable">Markdown Is Portable</h3>
<p>What you need to use Markdown is:</p>
<ul>
<li>a plain text editor (Windows Notepad or Apple Notes will do)</li>
<li>an interpreter (something that makes **bold** text <strong>bold</strong>)</li>
</ul>
<p>There are specialized Markdown editors that can do both.<sup class="footnote-ref"><a href="#fn2" id="fnref2">[2]</a></sup> Since Markdown is a language, you don't need any additional scripts or plug-ins. It also means it's compatible to all operating systems and devices. If you can input text, it'll support Markdown. In theory, you could even use Markdown on a piece of paper (although the interpreting part would be difficult).</p>
<p>There's plenty of software available that can interpret and format Markdown, there's a <a href="https://wereturtle.github.io/ghostwriter/">free cross-platform application</a>, an <a href="https://apps.apple.com/de/app/pretext/id1347707000">iOS app</a>, an <a href="https://play.google.com/store/apps/details?id=com.underwood.monospace">Android app</a>, <a href="https://stackedit.io/">one that runs in your browser</a>, and even a <a href="http://www.writage.com/">Word add-in</a>.</p>
<p>A lot of other writing, journaling, and note-taking applications already support Markdown. Maybe even software you use on a daily basis. Try putting text between two pairs of **asterisks**. and see what happens. if it becomes <strong>bold</strong>, congratulations! The software supports Markdown.</p>
<p>Others are notably missing, including Microsoft Word<sup class="footnote-ref"><a href="#fn3" id="fnref3">[3]</a></sup>, Google Docs, and Apple Pages.</p>
<h2 id="youreingoodcompany">You're in Good Company!</h2>
<p>Most technical documentation today is written in Markdown (including that of Apple and Microsoft) but it's not only for geeks. An increasing number of non-tech people — such as myself — are jumping on board.</p>
<p>With an ever-increasing list of software that not only supports Markdown but is build around it, abandoning clunky word processors in favor of a distraction-free Markdown-based app has never been easier.</p>
<p>I switched to Markdown for all my writing and I never want to go back. As someone who writes a very diverse range of things from professional briefings to <a href="https://blakeinc.de/music-tutorials/">articles on music production</a> to <a href="https://zero-division.com/">song lyrics</a> to, well, this blog<sup class="footnote-ref"><a href="#fn4" id="fnref4">[4]</a></sup>, Markdown is my Swiss Army knife.</p>
<p>It can be yours, too. So why don't you try it, if just for a day?</p>
<hr class="footnotes-sep">
<section class="footnotes">
<ol class="footnotes-list">
<li id="fn1" class="footnote-item"><p>To be fair, Word has a keyboard shortcut for making text bold as well. It's CTRL+B. Or, if you're German, it's CTRL+Shift+F for some weird reason I will never fully understand. <a href="#fnref1" class="footnote-backref">↩︎</a></p>
</li>
<li id="fn2" class="footnote-item"><p>My tool of choice is <a href="https://ia.net/de/writer">iA Writer</a> but there are countless free alternatives. <a href="#fnref2" class="footnote-backref">↩︎</a></p>
</li>
<li id="fn3" class="footnote-item"><p>Interestingly, Microsoft <em>does</em> use Markdown for <a href="https://docs.microsoft.com/en-us/contribute/how-to-write-use-markdown">their documentation</a>. <a href="#fnref3" class="footnote-backref">↩︎</a></p>
</li>
<li id="fn4" class="footnote-item"><p>I even chose my blog software around its native Markdown capabilities, that's how much I love it. <a href="#fnref4" class="footnote-backref">↩︎</a></p>
</li>
</ol>
</section>
<!--kg-card-end: markdown--><h2 id="image-credit">Image Credit</h2><ul><li>Photo by <a href="https://unsplash.com/@charlesdeluvio?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Charles 🇵🇭</a> on <a href="https://unsplash.com/s/photos/typing?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></li></ul>]]></content:encoded></item><item><title><![CDATA[A Case Against the Caps Lock Key]]></title><description><![CDATA[Loved by few, hated by many: the caps lock key has the designation of being the most controversial key there is. Read why it needs to go.]]></description><link>https://blog.blakeinc.de/a-case-against-the-caps-lock-key/</link><guid isPermaLink="false">5d3db99f03c17813c1d40731</guid><category><![CDATA[Productivity]]></category><dc:creator><![CDATA[Mario Dederichs]]></dc:creator><pubDate>Thu, 15 Apr 2021 15:06:00 GMT</pubDate><media:content url="https://blog.blakeinc.de/content/images/2019/08/florian-krumm-1osIUArK5oA-unsplash.jpg" medium="image"/><content:encoded><![CDATA[<!--kg-card-begin: markdown--><img src="https://blog.blakeinc.de/content/images/2019/08/florian-krumm-1osIUArK5oA-unsplash.jpg" alt="A Case Against the Caps Lock Key"><p>When was the last time you deliberately used the <em>Caps Lock</em> key? You know, that little thing above the <em>Shift</em> key? The one that makes you yell on the internet or seem like someone who shouldn't be <a href="https://theoatmeal.com/pl/minor_differences/capslock">left around computers unsupervised</a>? If your typing habits are anything like mine, the answer is, well, never.</p>
<p>As for any controversial thing on the internet, there's a movement against it. In 2006, the late Pieter Hintjens started a campaign called <a href="http://capsoff.blogspot.com/">CAPSoff</a> with the goal of abolishing the much-hated key once and for all. A quick look at Amazon's top-selling keyboards<sup class="footnote-ref"><a href="#fn1" id="fnref1">[1]</a></sup> reveals that he didn't succeed.</p>
<p>That's not to say that the <em>Caps Lock</em> key doesn't have its proponents. Fields like engineering make heavy use of capital letters and some keyboard layouts (like the Swiss German one) utilize it as a secondary dead key / modifier. And then there's <a href="https://seanwrona.com/typing.php">Sean Wrona</a>. He is one of the world's fastest typists, and he uses <em>Caps Lock</em> instead of <em>Shift</em> to capitalize letters. The absolute madman.<sup class="footnote-ref"><a href="#fn2" id="fnref2">[2]</a></sup> But do these uses really justify a prominent position on every standard keyboard layout?</p>
<h2 id="usagedataorlackthereof">Usage Data — or Lack Thereof</h2>
<p>Now, my usual approach would be to bring cold, hard numbers into the matter. The team at IO Technologies <a href="https://medium.com/t-superpower/geeks-vs-writers-f81e77a5d3c9">tracked their keyboard usage for a week</a>. The result? <em>Caps Lock</em> was the least used key with only 0.1 % of keystrokes. Now, the low sample size (eight participants) makes this anything but a broad study. If we did the same analysis at an engineering company, results would look way different.</p>
<p>Sadly, a comprehensive analysis of key usage is nowhere to be found. And so, the mystery of which keys are really needed and which are relics from the typewriter era — that made their way into modern computer keyboards by sheer force of habit alone — remains unsolved.</p>
<p>But even if data suggested that a sizable chunk of the population used the Caps Lock key, it's not a feasible substitute for standard, single-letter capitalization (sorry, Sean!). So, let's judge it by its main purpose: reducing finger strain while typing longer stretches of capitalized text.</p>
<h2 id="lockkeysandplacing">Lock Keys and Placing</h2>
<p>All keys can be grouped into various functions. The Caps Lock key is part of the <em>lock keys</em> subset that can toggle certain modes of the keyboard. The idea is that you press a lock key, do what you need with the altered layout, then revert to standard mode. No part of this process makes it necessary for a lock key to be placed in an easily reachable spot. If you'd have to switch modes frequently, the purpose of a lock key would be defeated.</p>
<p><img src="https://blog.blakeinc.de/content/images/2019/11/lock_keys_us-keyboard.svg" alt="A Case Against the Caps Lock Key" title="Marked here: lock keys on a standard US-layout keyboard. AKA an arbitrary clusterfuck."></p>
<p>Its siblings, <em>Num Lock</em> and <em>Scroll Lock</em> respect that and are positioned rather unobtrusively. <em>Caps Lock</em>, however, is the black sheep of the family. Its position next to the left little finger (using a standard ten-finger system) makes it one of the most-prominently placed non-letter keys<sup class="footnote-ref"><a href="#fn3" id="fnref3">[3]</a></sup> on the whole keyboard. In that, it's easier to reach than keys like <em>Backspace</em>, <em>Return</em> or <em>Control</em>.</p>
<p>Imagine if your car had the <em>Disable Airbag</em> button on the steering wheel.<sup class="footnote-ref"><a href="#fn4" id="fnref4">[4]</a></sup></p>
<p>Users of the strangely popular text editor Emacs (that relies heavily on the <em>Control</em> key) suffer from repetitive strain injury so frequently it's also referred to as <a href="http://ergoemacs.org/emacs/emacs_pinky.html">Emacs pinky</a>. Their solution? Swap <em>Control</em> with a key that's both easier to reach and completely obsolete. Guess which?</p>
<h2 id="butbutmyworkflow">But, but ... My Workflow!</h2>
<p>But does it <em>hurt</em> anybody? Surely there must be users that rely heavily on Caps Lock. What about Sean Wrona!?</p>
<p><a href="https://xkcd.com/1172/"><img src="https://imgs.xkcd.com/comics/workflow.png" alt="A Case Against the Caps Lock Key"></a></p>
<p>Yes, adapting to change is difficult. Yes, it's hard to throw long-held standards overboard. But instead of forcing an unused key on 99 % of all users, let's remap it to a key that 100 % of all users use and let the few hardboiled Caps Lock aficionados be the one to remap their keyboard.</p>
<p>For decades now, the standard QWERTY keyboard layout has been in place. For decades now, it has remained mostly unchanged. We have evolved beyond typewriters, let's start evolving beyond a keyboard layout that was intended to prevent the jamming of type hammers.</p>
<h2 id="evilbegone">Evil Begone</h2>
<p>While an increasing amount of people are turning towards alternative, more modern keyboard layouts such as <a href="https://en.wikipedia.org/wiki/Dvorak_Simplified_Keyboard">Dvorak</a> (don't), <a href="https://colemak.com/">Colemak</a>, or <a href="https://workmanlayout.org/">Workman</a>, most people are so used to the classic QWERTY layout (or whatever regional variant you use<sup class="footnote-ref"><a href="#fn5" id="fnref5">[5]</a></sup>) that this is unlikely to change anytime soon.</p>
<p>Of course, there's the possibility to remap the Caps Lock key to any key you like (the favorites being <em>Backspace</em> and <em>Control</em>) — and there's nothing wrong with that — but if the only way to have a useful keyboard layout is to customize it, there's something inherently wrong with the standard we are using.</p>
<p>But instead of changing the standard keyboard layout in one fell swoop, let's go one key at a time. In 2010, Google replaced the Caps Lock key with a <em>Search</em> key on its Chromebooks while the popular Happy Hacking keyboard put the <em>Control</em> key in the same spot. There's hope.</p>
<hr class="footnotes-sep">
<section class="footnotes">
<ol class="footnotes-list">
<li id="fn1" class="footnote-item"><p>At the time of writing this article, the most-sold keyboard without a Caps Lock key ranks at #43. If you can call it that at all as it's a hideous TV-remote-shaped abomination. It's intended for use on a Fire TV stick but would feel right at home as an N-Gage accessory. <a href="#fnref1" class="footnote-backref">↩︎</a></p>
</li>
<li id="fn2" class="footnote-item"><p>Check out his <a href="https://www.youtube.com/channel/UCoQaCj77ZAyWX5gSn8dcvSA">YouTube videos</a>. That's quite a sight to behold. <a href="#fnref2" class="footnote-backref">↩︎</a></p>
</li>
<li id="fn3" class="footnote-item"><p>'Prominently placed non-letter keys' needs to be its own Wikipedia category if it isn't already. <a href="#fnref3" class="footnote-backref">↩︎</a></p>
</li>
<li id="fn4" class="footnote-item"><p>&quot;I didn't mean to kill my co-driver, but I accidentally hit the wrong button. Oops.&quot; <a href="#fnref4" class="footnote-backref">↩︎</a></p>
</li>
<li id="fn5" class="footnote-item"><p>I use the German QWERTZ layout and have to employ massive finger acrobatics just to CTRL+Z. Also, the German layout doesn't have <em>Caps Lock</em> but <em>Shift Lock</em>, which is even worse in that produces &quot;mARIO&quot; instead of &quot;MARIO&quot; when accidentally hit. Grrr. <a href="#fnref5" class="footnote-backref">↩︎</a></p>
</li>
</ol>
</section>
<!--kg-card-end: markdown--><hr><h3 id="image-credits-">Image Credits:</h3><ul><li>Header Image Photo by <a href="https://unsplash.com/@aaronburden?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Aaron Burden</a> on <a href="https://unsplash.com/search/photos/pen?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></li><li>'Workflow' by Randall Munroe for <a href="https://xkcd.com">XKCD</a></li><li>'Lock Key Layout' drawn by Mysid, modified by Mario Dederichs. [<a href="http://creativecommons.org/licenses/by-sa/3.0/">CC BY-SA 3.0</a>], <a href="https://commons.wikimedia.org/wiki/File:Qwerty.svg">via Wikimedia Commons</a></li></ul>]]></content:encoded></item></channel></rss>