<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>blog on kylemtravis.com</title><link>https://kylemtravis.com/blog/</link><description>Recent content in blog on kylemtravis.com</description><generator>Hugo</generator><language>en-us</language><copyright>Kyle Travis</copyright><lastBuildDate>Sat, 07 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://kylemtravis.com/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Write Code "By Hand"</title><link>https://kylemtravis.com/blog/why-write-code-by-hand/</link><pubDate>Sat, 07 Nov 2026 00:00:00 +0000</pubDate><guid>https://kylemtravis.com/blog/why-write-code-by-hand/</guid><description>&lt;p&gt;Here it is, the post that most everyone is writing some variation of right now: the basic function of my job seems to have changed, maybe permanently. Functioning code is now being produced at a rate far beyond what a human could manage, even beyond what can be reasonably reviewed by human engineers. Many are ready to accept this given the results that are now achievable (whether the short-term benefit will be sustainable in the long run is another unanswered question).&lt;/p&gt;</description></item><item><title>Custom Syntax Highlighting in (Neo)Vim</title><link>https://kylemtravis.com/blog/custom-highlighting/</link><pubDate>Sat, 17 Jan 2026 00:00:00 +0000</pubDate><guid>https://kylemtravis.com/blog/custom-highlighting/</guid><description>&lt;p&gt;&lt;em&gt;Hopefully this post can be found by someone trying to answer the same questions I was, and maybe save some time.&lt;/em&gt;&lt;/p&gt;&#10;&lt;p&gt;Recently while working on closer integration between &lt;a href="https://kylemtravis.com/blog/shadergen-pt1/"&gt;Rust and WGSL shader code&lt;/a&gt;, I looked into what it would take to get syntax highlighting working seamlessly. With a snippet like this:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-rust" data-lang="rust"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="k"&gt;fn&lt;/span&gt; &lt;span class="nf"&gt;do_something&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;-&amp;gt; &lt;span class="nb"&gt;Option&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="c1"&gt;// something&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nb"&gt;None&lt;/span&gt;&lt;span class="w"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="w"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="k"&gt;const&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="no"&gt;SHADER_SOURCE&lt;/span&gt;: &lt;span class="kp"&gt;&amp;amp;&lt;/span&gt;&lt;span class="nb"&gt;&amp;#39;static&lt;/span&gt; &lt;span class="nc"&gt;Shader&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="fm"&gt;wgsl!&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;r&lt;/span&gt;#&lt;span class="s"&gt;&amp;#34;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="s"&gt; struct VertexOutput {&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="s"&gt; @builtin(position) clip_position: vec4&amp;lt;f32&amp;gt;,&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="s"&gt; }&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="s"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="s"&gt; @vertex&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="s"&gt; fn vs_main(&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="s"&gt; vertex: ModelVertexData,&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="s"&gt; instance: InstanceDataWithNormalMatrix,&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="s"&gt; ) -&amp;gt; VertexOutput {&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="s"&gt; // ...&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="s"&gt; }&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="s"&gt;&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;&lt;span class="w"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;&amp;hellip;we want to be able to edit the &amp;ldquo;embedded&amp;rdquo; shader code as seamlessly as possible - it should look like this:&lt;/p&gt;</description></item><item><title>My Top Albums of 2025</title><link>https://kylemtravis.com/blog/top-albums-2025/</link><pubDate>Wed, 24 Dec 2025 00:00:00 +0000</pubDate><guid>https://kylemtravis.com/blog/top-albums-2025/</guid><description>&lt;p&gt;2025 has been another banner year for music, at least if you have my particular taste (and if so, we should be friends probably). I don&amp;rsquo;t really go for ranking art, but I felt like sharing my highlights, or some of the ones that brought me the most joy. To keep things contained, this list doesn&amp;rsquo;t include things I only &lt;em&gt;discovered&lt;/em&gt; in 2025 that were actually released in prior years.&lt;/p&gt;</description></item><item><title>Generating Shader Code (part 1)</title><link>https://kylemtravis.com/blog/shadergen-pt1/</link><pubDate>Sun, 21 Sep 2025 00:00:00 +0000</pubDate><guid>https://kylemtravis.com/blog/shadergen-pt1/</guid><description>&lt;p&gt;Recently I&amp;rsquo;ve been&amp;hellip;&lt;/p&gt;&#10;&lt;p&gt;&lt;img src="https://kylemtravis.com/images/blog/generating-shader-code-1/initial-commit-2023.png" alt="initial commit&amp;hellip; 2 years ago"&gt;&#10;Well that&amp;rsquo;s disturbing.&lt;/p&gt;&#10;&lt;p&gt;wow, ok, how about &lt;em&gt;&amp;ldquo;in the last couple of years&amp;rdquo;&lt;/em&gt; I&amp;rsquo;ve been working on a new project: a game engine written in Rust, mostly from scratch. &lt;strong&gt;To get the obvious out of the way&lt;/strong&gt;, I&amp;rsquo;m writing my own game engine because:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;I want to learn more about modern low-level 3D graphics programming, and&lt;/li&gt;&#10;&lt;li&gt;I &lt;strong&gt;like building the game engine part&lt;/strong&gt; more than I like putting the gameplay pieces together in an editor.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;If I wanted to actually ship something in an anywhere-reasonable amount of time, I would be using Godot, or Unreal, or even &lt;a href="https://bevy.org/"&gt;Bevy&lt;/a&gt;, which I really admire and will refer to later on (Not Unity though. Not again). This should hopefully be clear.&lt;/p&gt;</description></item><item><title>Blog Comments With GitHub</title><link>https://kylemtravis.com/blog/blog-comments/</link><pubDate>Wed, 09 Sep 2020 00:00:00 +0000</pubDate><guid>https://kylemtravis.com/blog/blog-comments/</guid><description>&lt;p&gt;&lt;em&gt;For more background, see my &lt;a href="https://kylemtravis.com/blog/blogging-with-github"&gt;previous post&lt;/a&gt; about GitHub Actions.&lt;/em&gt;&lt;/p&gt;&#10;&lt;p&gt;Now that it&amp;rsquo;s possible to follow the blog and be notified by &lt;a href="https://github.com/ktravis/kylemtravis"&gt;watching on GitHub&lt;/a&gt;, I wanted to incorporate a little more interactivity. As much as anyone enjoys shouting into the void, I do like the idea of getting feedback - so it&amp;rsquo;s time to incorporate comments.&lt;/p&gt;&#10;&lt;p&gt;I follow a &lt;a href="https://github.com/a327ex/blog"&gt;gamedev blog&lt;/a&gt; on github that uses issues for posts, which seems like a pretty elegant solution to me: you get comments, reactions, labels, and search &amp;ldquo;for free&amp;rdquo;. Plus, issues are written in markdown, which is already the format this blog uses for posts (mostly - foreshadowing). I wanted to maintain the independence of the static site, so that means mirroring each post to a GitHub issue, and then displaying comments on the site by retrieving them from GitHub&amp;rsquo;s API.&lt;/p&gt;</description></item><item><title>Blogging With GitHub</title><link>https://kylemtravis.com/blog/blogging-with-github/</link><pubDate>Fri, 28 Aug 2020 00:00:00 +0000</pubDate><guid>https://kylemtravis.com/blog/blogging-with-github/</guid><description>&lt;p&gt;&lt;em&gt;Obligatory &amp;ldquo;wow it&amp;rsquo;s been so long since I&amp;rsquo;ve written here!&amp;rdquo;&lt;/em&gt;&lt;/p&gt;&#10;&lt;p&gt;In an effort to reduce the (admittedly already low) friction of writing blog posts, I&amp;rsquo;m now hosting this site on&#10;&lt;a href="https://netlify.com"&gt;netlify&lt;/a&gt;, which makes it pretty effortless to generate site previews off of pull requests, as well&#10;as perform the usual tasks like updating DNS, provisioning a Let&amp;rsquo;s Encrypt cert, etc. I&amp;rsquo;m still using &lt;a href="https://github.com/ktravis/ssgen"&gt;my own static site generator&lt;/a&gt; which was easy to integrate with netlify&amp;rsquo;s GitHub App: I set my site&amp;rsquo;s &amp;ldquo;build command&amp;rdquo; to &lt;code&gt;make build&lt;/code&gt;, which runs:&lt;/p&gt;</description></item><item><title>Cultivate Post-Mortem</title><link>https://kylemtravis.com/blog/cultivate-post-mortem/</link><pubDate>Sun, 03 Jan 2016 00:00:00 +0000</pubDate><guid>https://kylemtravis.com/blog/cultivate-post-mortem/</guid><description>&lt;p&gt;Hello there! With just over a day remaining in the voting period, it seemed like a great time to finally write up a post-mortem for my experience this time around. I&amp;rsquo;ve included my favorites/recommendations of the entries that I&amp;rsquo;ve played so far &lt;strong&gt;at the end of this post.&lt;/strong&gt;&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Of course, if you haven&amp;rsquo;t played the game yet I would &lt;em&gt;love&lt;/em&gt; to get your feedback! Visit the &lt;a href="http://ludumdare.com/compo/ludum-dare-34/?action=preview&amp;amp;uid=28426"&gt;game page here&lt;/a&gt;.&lt;/strong&gt;&lt;/p&gt;&#10;&lt;figure&gt;&lt;a href="http://ludumdare.com/compo/ludum-dare-34/?action=preview&amp;amp;uid=28426"&gt;&lt;img src="https://kylemtravis.com/images/blog/cultivate-post-mortem/ld48-preview.gif"&#10;&#9;&#9;&#9;alt="Cultivate is an adventure/visual-novel-like game about a day of high school."&gt;&lt;/a&gt;&lt;figcaption&gt;&#10;&#9;&#9;&#9;&lt;p&gt;Cultivate is an adventure/visual-novel-like game about a day of high school.&lt;/p&gt;&#10;&#9;&#9;&lt;/figcaption&gt;&#10;&lt;/figure&gt;</description></item><item><title>Haxe and Google Play Services</title><link>https://kylemtravis.com/blog/play-haxe/</link><pubDate>Tue, 07 Oct 2014 00:00:00 +0000</pubDate><guid>https://kylemtravis.com/blog/play-haxe/</guid><description>&lt;p&gt;Recently I decided I wanted to integrate Google Play Services &amp;ndash; leaderboards, achievements, etc &amp;ndash; with a Haxe/OpenFL project targetting Android devices. I assumed this should be easy enough given the ability to hook into Android/Java frameworks via native extensions. Overall it was simple, but not necessarily straightforward, so I&amp;rsquo;m writing this post as a quick start guide for others.&lt;/p&gt;&#10;&lt;h3 id="setting-up-project-extensions"&gt;Setting Up Project Extensions&lt;a class="anchor" href="#setting-up-project-extensions" aria-label="Link to this section" data-pagefind-ignore&gt;#&lt;/a&gt;&lt;/h3&gt;&lt;p&gt;I settled on using the &lt;a href="https://github.com/sergey-miryanov/linden-google-play"&gt;linden-google-play&lt;/a&gt; extension, which sets up the JNI hooks to the Play Services library for you.&lt;/p&gt;</description></item><item><title>Trying Twine (TextJam)</title><link>https://kylemtravis.com/blog/trying-twine-textjam/</link><pubDate>Tue, 24 Jun 2014 00:00:00 +0000</pubDate><guid>https://kylemtravis.com/blog/trying-twine-textjam/</guid><description>&lt;p&gt;I was determined to participate in &lt;a href="http://textjam.tumblr.com"&gt;TextJam&lt;/a&gt; last weekend, and without much time to devote I thought it could be smart to give Twine a try. Starting with a solid framework meant that once I had learned the syntax (and installed a few essential macros,) I could devote my remaining time to content and styling.&lt;/p&gt;&#10;&lt;p&gt;Here is my entry, &lt;a href="http://philome.la/kmakai/you-are-mistaken"&gt;You Are Mistaken&lt;/a&gt;&lt;/p&gt;&#10;&lt;p&gt;I have a love-hate relationship with CSS, but I&amp;rsquo;m happy with the simple style I ended up with. Writing content with the Twine editor is pretty natural, and it wasn&amp;rsquo;t hard to keep things mostly organized once I got the hang of it.&lt;/p&gt;</description></item><item><title>Haxe Signals</title><link>https://kylemtravis.com/blog/haxe-signals/</link><pubDate>Fri, 16 May 2014 00:00:00 +0000</pubDate><guid>https://kylemtravis.com/blog/haxe-signals/</guid><description>&lt;p&gt;A common pattern I find myself following in game development is the message-subscription/callback model &amp;ndash; notifying a group of objects that a certain event has happened, at which point they all go about their business responding in the appropriate ways.&lt;/p&gt;&#10;&lt;p&gt;This can be really effective, especially for organization, but I rarely seem to fully implement the procedure, instead just hacking something together that works. Realizing that going the full distance wouldn&amp;rsquo;t require much more (and could mean having something more portable to work with) I put together a simple manager for a messaging system:&lt;/p&gt;</description></item><item><title>FlappyJam</title><link>https://kylemtravis.com/blog/flappyjam/</link><pubDate>Mon, 24 Feb 2014 00:00:00 +0000</pubDate><guid>https://kylemtravis.com/blog/flappyjam/</guid><description>&lt;p&gt;I&amp;rsquo;ve just submitted my entry to &lt;a href="http://itch.io"&gt;itch.io&lt;/a&gt;&amp;rsquo;s &lt;a href="http://itch.io/jam/flappyjam"&gt;FLAPPYJAM&lt;/a&gt;! See it/&lt;a href="http://kmakai.itch.io/flee-lethal-avian-pests"&gt;play it here&lt;/a&gt;.&lt;/p&gt;&#10;&lt;p&gt;The game was made in Haxe over a period of two weeks using HaxeFlixel, with &lt;a href="http://bfxr.net"&gt;BFXR&lt;/a&gt; for sound effects, and &lt;a href="http://distractionware.com/blog/2013/08/bosca-ceoil/"&gt;Bosca Ceoil&lt;/a&gt; for the music.&lt;/p&gt;&#10;&lt;p&gt;I&amp;rsquo;ll be writing up a longer-form post-mortem tomorrow morning, but that being said I&amp;rsquo;m quite satisfied with this as my first finished game jam entry. Two weeks went by fast!&lt;/p&gt;</description></item></channel></rss>