<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Terrence Ho</title><link>https://terrenceho.dev/</link><description>Recent content on Terrence Ho</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 30 Jun 2019 18:15:00 -0700</lastBuildDate><atom:link href="https://terrenceho.dev/index.xml" rel="self" type="application/rss+xml"/><item><title>Writing My Blog Posts with Org</title><link>https://terrenceho.dev/post/org-blog-posts/</link><pubDate>Sun, 30 Jun 2019 18:15:00 -0700</pubDate><guid>https://terrenceho.dev/post/org-blog-posts/</guid><description>&lt;p&gt;Hugo is an awesome blog generator. However, it&amp;rsquo;s primary content mode is
Markdown, and writing in &lt;code&gt;org-mode&lt;/code&gt; feels much better than writing in Markdown.
&lt;code&gt;org-mode&lt;/code&gt; can automatically convert to Markdown, but then I have to edit the
generated Markdown file to add YAML front-matter that Hugo consumes, which is
annoying.&lt;/p&gt;
&lt;p&gt;Enter &lt;a href="https://www.gnu.org/software/emacs/"&gt;&lt;code&gt;ox-hugo&lt;/code&gt;&lt;/a&gt;. It allows you to maintain and generate Hugo-compatible Markdown
in &lt;code&gt;org-mode&lt;/code&gt;, and automatically generates the necessary metadata Hugo requires.
However, like all good things in life, you have to work a little to configure it
to your liking. (What&amp;rsquo;s an extension without spending a couple hours of life
figuring out exactly how to make it conform to your workflow in the pursuit of
&amp;ldquo;optimization&amp;rdquo;). This is how I configure &lt;code&gt;ox-hugo&lt;/code&gt; to write all my blog posts
(including this blog post!).&lt;/p&gt;</description></item><item><title>How I Started Using Emacs</title><link>https://terrenceho.dev/post/how-i-started-using-emacs/</link><pubDate>Mon, 17 Jun 2019 16:53:00 -0700</pubDate><guid>https://terrenceho.dev/post/how-i-started-using-emacs/</guid><description>&lt;p&gt;This is how I started using GNU Emacs with no prior experience. This is intended
to help those who want to start using Emacs as well. I&amp;rsquo;ll start from a base
setup, show you where I looked around for help, show you how I found myself
using my current configuration. While this post goes through the steps to get
started with Emacs, I definitely omitted the steps that didn&amp;rsquo;t help or the parts
where I floundered around not knowing what I was doing.&lt;/p&gt;</description></item><item><title>Benchmarking Fib with Go</title><link>https://terrenceho.dev/post/benchmarking-fibonacci/</link><pubDate>Wed, 22 Aug 2018 00:00:00 +0000</pubDate><guid>https://terrenceho.dev/post/benchmarking-fibonacci/</guid><description>&lt;p&gt;Go has a really nice testing suite built into its compiler tool chains. It&amp;rsquo;s as
simple as running &lt;code&gt;go test&lt;/code&gt; in your package, and all files marked *_tests.go
will be executed. We can also run benchmarks during testing, by adding the
&lt;code&gt;-bench&lt;/code&gt; flag to the &lt;code&gt;go test&lt;/code&gt; command. I never really benchmarked anything
before, so I decided to explore Go&amp;rsquo;s benchmarking utilities, and flex some of my
algorithm skills in the process. Naturally I decided implement the Fibonacci
sequence many, many times over.&lt;/p&gt;</description></item><item><title>From Object Oriented To Functional</title><link>https://terrenceho.dev/post/objected-oriented-to-functional/</link><pubDate>Sat, 21 Oct 2017 00:00:00 +0000</pubDate><guid>https://terrenceho.dev/post/objected-oriented-to-functional/</guid><description>&lt;p&gt;Many coders have heard of the term &amp;ldquo;functional programming&amp;rdquo;, but have often never really used it or its properties. Especially if they came from Java, where there are no real functions, only methods each function has to be attached to an object, and cannot stand by itself. Functions are commomly thought of as defining behavior. However, functions can also be thought of as data, instead of just instructions. They are data that define your instructions.&lt;/p&gt;</description></item></channel></rss>