<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Posts on Jethro Kuan</title>
    <link>https://blog.jethro.dev/posts/</link>
    <description>Recent content in Posts on Jethro Kuan</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 25 Dec 2021 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://blog.jethro.dev/posts/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Org-roam: A Year In Review</title>
      <link>https://blog.jethro.dev/posts/org_roam_2021/</link>
      <pubDate>Sat, 25 Dec 2021 00:00:00 +0000</pubDate>
      
      <guid>https://blog.jethro.dev/posts/org_roam_2021/</guid>
      <description>It&amp;rsquo;s been over two years since the inception of Org-roam, and with the year coming to an end I think a review is timely.
The Org-roam Rewrite In the earlier half of the year, I&amp;rsquo;d worked on and released version 2 of Org-roam. I&amp;rsquo;d touted it to be more performant, easier to understand and tweak from a power-user&amp;rsquo;s perspective. I think the feedback for version 2 was mixed with a slight positive lean.</description>
    </item>
    
    <item>
      <title>Releasing Org-roam v2</title>
      <link>https://blog.jethro.dev/posts/org_roam_v2/</link>
      <pubDate>Sat, 17 Jul 2021 00:00:00 +0000</pubDate>
      
      <guid>https://blog.jethro.dev/posts/org_roam_v2/</guid>
      <description>6 months and over 200 commits later, I&amp;rsquo;m finally releasing Org-roam v2!
Org-roam v2 is an overhaul of Org-roam. It is slimmer and more performant, and has first-class support for linking to headlines. It also features a revamped side-buffer, a rich completion interface and a clean public interface for community extensions to work with.
Org-roam in 2021? Over the course of the year, new plain-text note-taking apps have been developed.</description>
    </item>
    
    <item>
      <title>Taking Spaced Repetition Seriously</title>
      <link>https://blog.jethro.dev/posts/taking_srs_seriously/</link>
      <pubDate>Wed, 13 Jan 2021 00:00:00 +0000</pubDate>
      
      <guid>https://blog.jethro.dev/posts/taking_srs_seriously/</guid>
      <description>Spaced Repetition? As a maintainer of a project within the personal knowledge management space, spaced repetition is something I get asked about a lot. Do I use spaced repetition? How do I implement it within my workflows?
To be honest I could never get spaced repetition systems to stick. I&amp;rsquo;d already streamlined the process of creating cards for Anki, but it still required so much effort, with little tangible benefit.</description>
    </item>
    
    <item>
      <title>Computing TF transforms with AprilTag</title>
      <link>https://blog.jethro.dev/posts/camera_calibration_apriltag/</link>
      <pubDate>Mon, 26 Oct 2020 00:00:00 +0000</pubDate>
      
      <guid>https://blog.jethro.dev/posts/camera_calibration_apriltag/</guid>
      <description>Suppose we have designed a mount for a camera to be placed on the robot. We likely need to obtain the transform between the camera and the robot, so images obtained from the camera can be transformed into information the robot can act upon. One method is to use the mount design, to compute the translation and rotation of the camera. However, 3D printing is often imperfect, and can result in inaccurate calibration.</description>
    </item>
    
    <item>
      <title>Self-tracking in Plain Text</title>
      <link>https://blog.jethro.dev/posts/self_tracking_in_plain_text/</link>
      <pubDate>Fri, 09 Oct 2020 00:00:00 +0000</pubDate>
      
      <guid>https://blog.jethro.dev/posts/self_tracking_in_plain_text/</guid>
      <description>I recently decided to start doing more self-tracking. In my Org-mode workflow series, I gave a brief overview of how I did task management, but what I failed to mention then was that Org provides clocking capabilities, so I sort-of knew where I was spending my time. However, I wanted to track things that are unrelated to tasks. For instance, I wanted to track my mood at different times of the day, or what I ate.</description>
    </item>
    
    <item>
      <title>Random Thoughts on 4 Years of University</title>
      <link>https://blog.jethro.dev/posts/reflections_on_university/</link>
      <pubDate>Tue, 16 Jun 2020 00:00:00 +0000</pubDate>
      
      <guid>https://blog.jethro.dev/posts/reflections_on_university/</guid>
      <description>It&amp;rsquo;s been a long 4 years, but I&amp;rsquo;ve finally completed my undergraduate education in Computer Science at the National University of Singapore. It&amp;rsquo;s a wild time to graduate: Covid-19 has certainly brought about its fair share of woes (such as being harder to find jobs), but it has also given me time to think about how I spent my time in university, and about what&amp;rsquo;s next.
In truth, I didn&amp;rsquo;t think much of university when I first enrolled.</description>
    </item>
    
    <item>
      <title>Migrating To Doom Emacs</title>
      <link>https://blog.jethro.dev/posts/migrating_to_doom_emacs/</link>
      <pubDate>Sun, 15 Mar 2020 00:00:00 +0000</pubDate>
      
      <guid>https://blog.jethro.dev/posts/migrating_to_doom_emacs/</guid>
      <description>Yesterday, I spent some time migrating my vanilla Emacs configuration to Doom Emacs. The whole process took me about 2 hours, and then today I spent another hour or so figuring out why my original configurations felt different, and tweaked it back to my liking.
For reference, here is my original .emacs.d (now archived), and my current configuration lives in my home git repository.
Why Doom Emacs? Why did I bother?</description>
    </item>
    
    <item>
      <title>How To Take Smart Notes With Org-mode</title>
      <link>https://blog.jethro.dev/posts/how_to_take_smart_notes_org/</link>
      <pubDate>Fri, 14 Feb 2020 00:00:00 +0000</pubDate>
      
      <guid>https://blog.jethro.dev/posts/how_to_take_smart_notes_org/</guid>
      <description>While writing the documentation for Org-roam, it occurred to me that I have things to say that do not belong in the documentation. I wrote Org-roam because Org-mode simply didn&amp;rsquo;t have the utilities to enable the kind of note-taking workflow I wanted. I don&amp;rsquo;t want to be prescriptive about how note-taking should be done, but Org-roam is open enough to enable many note-taking styles, some of which (I feel) will be inferior to others.</description>
    </item>
    
    <item>
      <title>Introducing Org Roam</title>
      <link>https://blog.jethro.dev/posts/introducing_org_roam/</link>
      <pubDate>Fri, 07 Feb 2020 00:00:00 +0000</pubDate>
      
      <guid>https://blog.jethro.dev/posts/introducing_org_roam/</guid>
      <description>In a previous post, I described my note-taking workflow with zettelkasten and org. I extracted some of that logic out into a Github repository, and it sort of took a life of its own. Now that it&amp;rsquo;s gaining a bit of popularity and usage, I thought I&amp;rsquo;d do a more formal introduction to the package, and how I use it. It is not published on MELPA, and likely won&amp;rsquo;t be for a while, but you can find it on Github here.</description>
    </item>
    
    <item>
      <title>Experimenting with Remembrance Agents</title>
      <link>https://blog.jethro.dev/posts/remembrance_agents/</link>
      <pubDate>Mon, 06 Jan 2020 00:00:00 +0000</pubDate>
      
      <guid>https://blog.jethro.dev/posts/remembrance_agents/</guid>
      <description>Recently someone brought the concept of Remembrance Agents to my attention. Remembrance Agents are programs which augment the human memory by displaying documents, such as notes and emails, that are potentially relevant to the current context. This fascinated me, and I thought I could potentially incorporate something similar into my braindump workflow, so I set aside some hours to see how I could get a proof-of-concept out.
Existing Software A simple Github search reveals that any relevant software is dated and unmaintained.</description>
    </item>
    
    <item>
      <title>Machine Learning with Guild AI</title>
      <link>https://blog.jethro.dev/posts/machine_learning_with_guild_ai/</link>
      <pubDate>Tue, 31 Dec 2019 00:00:00 +0000</pubDate>
      
      <guid>https://blog.jethro.dev/posts/machine_learning_with_guild_ai/</guid>
      <description>Since I&amp;rsquo;ve been writing on the topic of workflows and tooling, I thought I&amp;rsquo;d give one of my favourite packages, Guild AI, a shout-out, and well-deserved exposure.
Guild AI is designed for managing machine learning experiments. It provides ways to track experiment runs, make runs reproducible, and compare runs with different hyperparameters, all in ways that are non-intrusive. Those who know me know I care a lot about my tools, and this is one of those tools that really spark joy.</description>
    </item>
    
    <item>
      <title>Org-mode Workflow Part 3: Zettelkasten with Org-mode</title>
      <link>https://blog.jethro.dev/posts/zettelkasten_with_org/</link>
      <pubDate>Fri, 20 Dec 2019 00:00:00 +0000</pubDate>
      
      <guid>https://blog.jethro.dev/posts/zettelkasten_with_org/</guid>
      <description>(Previous Post: Org-mode Workflow Part 2: Processing the Inbox)
Many of my tasks are articles, and online lectures that I need to go through for independent research. When going through these material, I like to record down notes for later reference.
Background I&amp;rsquo;m going to provide some history at how I arrived here, feel free to skip ahead if you&amp;rsquo;re not interested.
I&amp;rsquo;ve had a habit of note-taking since my secondary school days, which is more than a decade ago.</description>
    </item>
    
    <item>
      <title>Org-mode Workflow Part 4: Automatic Web Publishing</title>
      <link>https://blog.jethro.dev/posts/automatic_publishing/</link>
      <pubDate>Fri, 20 Dec 2019 00:00:00 +0000</pubDate>
      
      <guid>https://blog.jethro.dev/posts/automatic_publishing/</guid>
      <description>Some were curious about how I was automatically publishing my Org files, so I thought I&amp;rsquo;d try to give some insight into the process. You can find the Github repo here.
I prefer my tools to be as simple as possible, but I&amp;rsquo;m also somewhat lazy, so I tend to use whatever was easiest. Previously, I&amp;rsquo;d be using Org&amp;rsquo;s in-built HTML export, but it was missing a bunch of niceties that weren&amp;rsquo;t that trivial to implement, like RSS and sitemaps.</description>
    </item>
    
    <item>
      <title>Org-mode Workflow Part 2: Processing the Inbox</title>
      <link>https://blog.jethro.dev/posts/processing_inbox/</link>
      <pubDate>Tue, 17 Dec 2019 00:00:00 +0000</pubDate>
      
      <guid>https://blog.jethro.dev/posts/processing_inbox/</guid>
      <description>(Previous Post: Org-mode Workflow Part 1: Capturing in the Inbox)
There are many to-do lists that don&amp;rsquo;t include processing as part of the workflow. These workflows use a simple checklist, and one would check off items as they do them. Why would David Allen (and I) recommend having processing as a separate step?
Why process the inbox? When you&amp;rsquo;ve taken every open loop, and dump it onto a piece of paper, you may be surprised to see that you have many more to-do items than you expected.</description>
    </item>
    
    <item>
      <title>Org-mode Workflow Part 1: Capturing in the Inbox</title>
      <link>https://blog.jethro.dev/posts/capturing_inbox/</link>
      <pubDate>Sat, 14 Dec 2019 00:00:00 +0000</pubDate>
      
      <guid>https://blog.jethro.dev/posts/capturing_inbox/</guid>
      <description>(Previous Post: Org-mode Workflow: A Preview)
Have you ever sat down with nothing but a pen and a piece of paper, writing down everything you need to do? Recall how you felt right after. Did you feel more in control? Isn&amp;rsquo;t it strange that you feel better looking at the long list of work, knowing that your little exercise accomplished nothing on the list? What pushed you to do this little exercise?</description>
    </item>
    
    <item>
      <title>Org-mode Workflow: A Preview</title>
      <link>https://blog.jethro.dev/posts/org_mode_workflow_preview/</link>
      <pubDate>Fri, 13 Dec 2019 00:00:00 +0000</pubDate>
      
      <guid>https://blog.jethro.dev/posts/org_mode_workflow_preview/</guid>
      <description>This is going to be a multi-part series on Emacs and org-mode. This is also going to be a really long series, so before we begin I want to give you an idea of what to expect. What I&amp;rsquo;m about to present is a workflow I&amp;rsquo;ve tweaked over several years. It is a workflow that has constantly evolved to adapt to my varying needs. At the time of writing, I have completed 3478 todo items, and written over 29000 lines in my personal knowledge base.</description>
    </item>
    
    <item>
      <title>Using nix-buffer with Emacs</title>
      <link>https://blog.jethro.dev/posts/nix_buffer_emacs/</link>
      <pubDate>Fri, 13 Dec 2019 00:00:00 +0000</pubDate>
      
      <guid>https://blog.jethro.dev/posts/nix_buffer_emacs/</guid>
      <description>I do a lot of note-taking in Emacs, and have recently started using org-babel within my notes. Being on NixOS, this proved to be slightly problematic: org-babel requires the executables to be in PATH. In NixOS this is concerning: we don&amp;rsquo;t want the executables to be available globally.
My traditional approach would be to use the direnv integration in Emacs, populating my path in a certain directory. However, in this case I keep my notes in a flat hierarchy:</description>
    </item>
    
    <item>
      <title>Setting up OCaml and Emacs with Nix/NixOS</title>
      <link>https://blog.jethro.dev/posts/ocaml_emacs_nixos/</link>
      <pubDate>Sun, 27 Oct 2019 00:00:00 +0000</pubDate>
      
      <guid>https://blog.jethro.dev/posts/ocaml_emacs_nixos/</guid>
      <description>I&amp;rsquo;m learning OCaml via Real World OCaml, and getting a isolated OCaml development environment working with NixOS proved to be quite a struggle. This is a tutorial that describes my way of getting OCaml set up.
Obtaining the OCaml Libraries OCaml and the more popular libraries are available in Nixpkgs, so one can write a simple shell.nix file to make them available in a nix shell:
with import &amp;lt;nixpkgs&amp;gt; {}; let ocamlPackages = pkgs.</description>
    </item>
    
  </channel>
</rss>