paritybit.ca

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | README | LICENSE

commit 2f5cbeaa3aa71d1517dbe19fc91fc563d9d1a9ae
parent 39198f3093df2f4482ff87ae1aca4e9a204f98b0
Author: Jake Bauer <jbauer@paritybit.ca>
Date:   Wed,  8 Jul 2020 22:24:35 -0400

Publish new blog post

Diffstat:
Mpages/blog.md | 1+
Apages/blog/my-todo-solution.md | 78++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Mpages/home.md | 4++--
Mpublic/feeds/sitewide-feed.xml | 25+++++++++++++++++++++++++
Mpublic/sitemap.xml | 1+
5 files changed, 107 insertions(+), 2 deletions(-)

diff --git a/pages/blog.md b/pages/blog.md @@ -27,6 +27,7 @@ href="https://social.paritybit.ca/@jbauer">Mastodon</a>. ### 2020 <ul> + <li>2020-07-08 <a href="blog/my-todo-solution">My TODO Solution</a></li> <li>2020-07-07 <a href="blog/are-todo-applications-a-waste-of-time">Are TODO Applications a Waste of Time?</a></li> <li>2020-07-06 <a href="blog/improving-blog-searching">Improving Blog Searching</a></li> <li>2020-07-05 <a href="blog/switching-to-cgit">Switching to cgit</a></li> diff --git a/pages/blog/my-todo-solution.md b/pages/blog/my-todo-solution.md @@ -0,0 +1,78 @@ +## My TODO Solution + +[//]: # "Yesterday I posted about why I don't think TODO lists or applications are useless. In this post, I describe what I do to keep myself organized." + +[//]: # "main.min.css" + +[//]: # + +<div class="byline"> +<b>Written By:</b> Jake Bauer | + <b>Posted:</b> 2020-07-08 | + <b>Last Updated:</b> 2020-07-08 +</div> + +Yesterday I posted about [why I don't think TODO lists or applications are +useless](https://www.paritybit.ca/blog/are-todo-applications-a-waste-of-time). +Today, I want to talk about my TODO solution or what I do to keep myself +organized. + +It all comes down to preferring simplicity over complexity. TODO applications or +web tools are very pretty and very easy to synchronize across devices, but they +suffer from the failing of being cumbersome and awkward to use. I find they get +in my way more than they help me usually because of some required format that I +have to structure my thoughts in, too many menus and clicks to do simple things, +or an interface that has more whitespace than the latest minimalist desk picture +on Pinterest. + +I prefer to make literal TODO lists in a physical journal or plain text file. In +fact, I typically do both and have multiple files at the same time. I have a +Leuchtturm1917 A5 DotGrid notebook with an <del>addiction</del> assortment of +fountain pens which I use to keep a physical TODO list and I have a 1970's +vintage vi which I use to finely craft my text files. + +By "literal TODO lists" I mean just that: a plain list of things to do and +appointments to keep with two different shapes of bullets depending on the type +of item in the list. The TODO lists in my physical task book follow this format: + +``` +Thursday, 1 January, 1970 +▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ +○ Lunch with Brian and Ken @ 12:30 +□ Create UNIX time +■ Refill TTY with paper +□ Destroy undergrads in Spacewar! +``` + +An empty square `□` represents a task that is yet to be completed. A filled in +square `■` represents a task that has been completed. Similarly, an empty circle +`○` and a filled circle `●` represent appointments yet to be attended and +appointments which have passed respectively. My task book is just page after +page of days with tasks written like this. + +At the beginning of school semesters, I will dedicate four pages (one for each +month) to listing out the days of the month so that I can note assignment due +dates, midterms, and exams in a single place. If I don't complete a task written +down on one day, I'll just write down the same task (or what's left to do for +that task) on the next day. Sometimes I write a few days ahead if I want to make +sure to remember something that I need to do in the near future. + +Digital TODO lists (aka text files) are typically much shorter-lived. I find +keeping track of things in digital form clunky and awkward to use, so I prefer +to do as much on paper as possible. However, when programming, quickly listing +and organizing a list of features I need to complete or bugs to fix can be +preferable. Once again, this is a plain list with bullet points in a plain text +file. When something is completed, it just gets removed from the list. + +So, that's how I stay organized and manage to get things done. No apps, no +special formats, just pen and paper or, more rarely, a plain text file and a +text editor. I'm interested in hearing about how other people stay organized and +whether or not you use something like a TODO application or just pen and paper. +Let me know by [sending me a link to a response blog +post](mailto:jbauer@paritybit.ca) or by [mentioning me on +Mastodon](https://social.paritybit.ca/@jbauer). + +_This is my sixty-fourth post for the +[#100DaysToOffload](https://social.paritybit.ca/tags/100DaysToOffload) +challenge. You can learn more about this challenge over at +[https://100daystooffload.com](https://100daystooffload.com)._ diff --git a/pages/home.md b/pages/home.md @@ -20,6 +20,8 @@ extent)! Access through `gopher://paritybit.ca` or `gemini://paritybit.ca`. src="/img/feed-icon.png" width="15" height="15" alt="Click for RSS Feed"/> </a> </div> +2020-07-08 <a class="feed-item" href="blog/my-todo-solution">My TODO Solution</a> + 2020-07-07 <a class="feed-item" href="blog/are-todo-applications-a-waste-of-time">Are TODO Applications a Waste of Time?</a> 2020-07-06 <a class="feed-item" href="blog/improving-blog-searching">Improving Blog Searching</a> @@ -37,8 +39,6 @@ extent)! Access through `gopher://paritybit.ca` or `gemini://paritybit.ca`. 2020-06-27 <a class="feed-item" href="blog/my-first-ctf">My First CTF</a> 2020-06-26 <a class="feed-item" href="blog/use-syncthing-to-sync-things">Use Syncthing to Sync Things</a> - -2020-06-26 <a class="feed-item" href="blog/why-dwm-swallowing-cant-swallow-tmux">Why dwm's Window Swallowing Patch Can't Swallow tmux</a> ### What is a Parity Bit? It is a bit (in the 1's and 0's sense) used in checking for errors in digital diff --git a/public/feeds/sitewide-feed.xml b/public/feeds/sitewide-feed.xml @@ -7,6 +7,31 @@ <description>The feed that covers all notable additions, updates, announcements, and other changes for the entire paritybit.ca website.</description> <item> + <title>My TODO Solution</title> + <link>https://www.paritybit.ca/blog/my-todo-solution</link> + <guid>https://www.paritybit.ca/blog/my-todo-solution</guid> + <pubDate>Wed, 08 Jul 2020 22:24:26 -0400</pubDate> + <description><![CDATA[<h2 id="my-todo-solution">My TODO Solution</h2> +<div class="byline"> +<p><b>Written By:</b> Jake Bauer | <b>Posted:</b> 2020-07-08 | <b>Last Updated:</b> 2020-07-08</p> +</div> +<p>Yesterday I posted about <a href="https://www.paritybit.ca/blog/are-todo-applications-a-waste-of-time">why I don’t think TODO lists or applications are useless</a>. Today, I want to talk about my TODO solution or what I do to keep myself organized.</p> +<p>It all comes down to preferring simplicity over complexity. TODO applications or web tools are very pretty and very easy to synchronize across devices, but they suffer from the failing of being cumbersome and awkward to use. I find they get in my way more than they help me usually because of some required format that I have to structure my thoughts in, too many menus and clicks to do simple things, or an interface that has more whitespace than the latest minimalist desk picture on Pinterest.</p> +<p>I prefer to make literal TODO lists in a physical journal or plain text file. In fact, I typically do both and have multiple files at the same time. I have a Leuchtturm1917 A5 DotGrid notebook with an <del>addiction</del> assortment of fountain pens which I use to keep a physical TODO list and I have a 1970’s vintage vi which I use to finely craft my text files.</p> +<p>By “literal TODO lists” I mean just that: a plain list of things to do and appointments to keep with two different shapes of bullets depending on the type of item in the list. The TODO lists in my physical task book follow this format:</p> +<pre><code>Thursday, 1 January, 1970 +▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ +○ Lunch with Brian and Ken @ 12:30 +□ Create UNIX time +■ Refill TTY with paper +□ Destroy undergrads in Spacewar!</code></pre> +<p>An empty square <code>□</code> represents a task that is yet to be completed. A filled in square <code>■</code> represents a task that has been completed. Similarly, an empty circle <code>○</code> and a filled circle <code>●</code> represent appointments yet to be attended and appointments which have passed respectively. My task book is just page after page of days with tasks written like this.</p> +<p>At the beginning of school semesters, I will dedicate four pages (one for each month) to listing out the days of the month so that I can note assignment due dates, midterms, and exams in a single place. If I don’t complete a task written down on one day, I’ll just write down the same task (or what’s left to do for that task) on the next day. Sometimes I write a few days ahead if I want to make sure to remember something that I need to do in the near future.</p> +<p>Digital TODO lists (aka text files) are typically much shorter-lived. I find keeping track of things in digital form clunky and awkward to use, so I prefer to do as much on paper as possible. However, when programming, quickly listing and organizing a list of features I need to complete or bugs to fix can be preferable. Once again, this is a plain list with bullet points in a plain text file. When something is completed, it just gets removed from the list.</p> +<p>So, that’s how I stay organized and manage to get things done. No apps, no special formats, just pen and paper or, more rarely, a plain text file and a text editor. I’m interested in hearing about how other people stay organized and whether or not you use something like a TODO application or just pen and paper. Let me know by <a href="mailto:jbauer@paritybit.ca">sending me a link to a response blog post</a> or by <a href="https://social.paritybit.ca/@jbauer">mentioning me on Mastodon</a>.</p> +<p><em>This is my sixty-fourth post for the <a href="https://social.paritybit.ca/tags/100DaysToOffload">#100DaysToOffload</a> challenge. You can learn more about this challenge over at <a href="https://100daystooffload.com">https://100daystooffload.com</a>.</em></p>]]></description> + </item> +<item> <title>Are TODO Applications a Waste of Time?</title> <link>https://www.paritybit.ca/blog/are-todo-applications-a-waste-of-time</link> <guid>https://www.paritybit.ca/blog/are-todo-applications-a-waste-of-time</guid> diff --git a/public/sitemap.xml b/public/sitemap.xml @@ -3,6 +3,7 @@ <url><loc>https://www.paritybit.ca</loc></url> <url><loc>https://www.paritybit.ca/home</loc></url> <url><loc>https://www.paritybit.ca/blog</loc></url> + <url><loc>https://www.paritybit.ca/blog/my-todo-solution</loc></url> <url><loc>https://www.paritybit.ca/blog/are-todo-applications-a-waste-of-time</loc></url> <url><loc>https://www.paritybit.ca/blog/improving-blog-searching</loc></url> <url><loc>https://www.paritybit.ca/blog/switching-to-cgit</loc></url>