<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Writing on Jake Worth</title><link>https://jakeworth.com/tags/writing/</link><description>Recent content in Writing on Jake Worth</description><image><title>Jake Worth</title><url>https://jakeworth.com/twittercard.png</url><link>https://jakeworth.com/twittercard.png</link></image><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 18 Jun 2026 10:40:18 -0400</lastBuildDate><atom:link href="https://jakeworth.com/tags/writing/index.xml" rel="self" type="application/rss+xml"/><item><title>Leave a Trace</title><link>https://jakeworth.com/posts/leave-a-trace/</link><pubDate>Thu, 18 Jun 2026 10:40:18 -0400</pubDate><guid>https://jakeworth.com/posts/leave-a-trace/</guid><description>&lt;p&gt;Always leave something behind. If you find something interesting, leave a trace
that you were there.&lt;/p&gt;</description></item><item><title>A Talk on Twelve Factors</title><link>https://jakeworth.com/posts/a-talk-on-12-factors/</link><pubDate>Fri, 01 Aug 2025 13:48:58 -0400</pubDate><guid>https://jakeworth.com/posts/a-talk-on-12-factors/</guid><description>&lt;p&gt;Today I gave a talk to my team about the Twelve-Factor App Methodology.&lt;/p&gt;</description></item><item><title>Why I Write for Software Engineers and Engineering Leaders</title><link>https://jakeworth.com/posts/why-im-writing-to-you/</link><pubDate>Wed, 11 Jun 2025 09:47:19 -0400</pubDate><guid>https://jakeworth.com/posts/why-im-writing-to-you/</guid><description>&lt;p&gt;Eight years ago I wrote a post called &lt;a href="https://www.jakeworth.com/posts/you-should-blog"&gt;You Should Blog&lt;/a&gt;. In it, I made an argument that I still believe in: public, professional writing is something every engineer should try. Today, I want to share why &lt;em&gt;I&lt;/em&gt; write, and have for over a decade.&lt;/p&gt;</description></item><item><title>How to Start a Meetup Group (Lessons from Running One for 10 Years)</title><link>https://jakeworth.com/posts/how-i-organize-a-meetup/</link><pubDate>Mon, 03 Feb 2025 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/how-i-organize-a-meetup/</guid><description>&lt;p&gt;I&amp;rsquo;ve been organizing Meetups for a decade, starting with Vim Chicago and Chicago Elixir, and now running &lt;a href="https://mainejs.org/"&gt;Maine JS&lt;/a&gt; from Portland, Maine. In honor of our most recent Meetup, here&amp;rsquo;s my practical guide on how to start a Meetup group, based on what&amp;rsquo;s worked for me.&lt;/p&gt;</description></item><item><title>Practical Ways to 'Learn in Public' Now</title><link>https://jakeworth.com/posts/practical-ways-to-learn-in-public-now/</link><pubDate>Sun, 28 Jan 2024 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/practical-ways-to-learn-in-public-now/</guid><description>&lt;p&gt;I&amp;rsquo;ve been a practitioner of Shawn Wang&amp;rsquo;s &lt;a href="https://www.swyx.io/learn-in-public"&gt;&amp;lsquo;Learn in Public&amp;rsquo;&lt;/a&gt; for years.
In this post, I&amp;rsquo;ll share a list of ways I&amp;rsquo;ve found to learn in public.&lt;/p&gt;</description></item><item><title>My Feature Writing Template: Given/When/Then</title><link>https://jakeworth.com/posts/given-when-then/</link><pubDate>Tue, 20 Dec 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/given-when-then/</guid><description>&lt;p&gt;When preparing feature development work, I write Gherkin-style tickets,
which follow the &amp;ldquo;Given/When/Then&amp;rdquo; format. Many people call these stories, and
I do, too. This technique is incredibly effective! But why? In this post, I&amp;rsquo;ll try to answer that question.&lt;/p&gt;</description></item><item><title>How I Talk: My Guide to Tech Public Speaking</title><link>https://jakeworth.com/posts/how-i-talk/</link><pubDate>Wed, 09 Aug 2017 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/how-i-talk/</guid><description>&lt;p&gt;I&amp;rsquo;ve been giving technical talks for a few years, and I&amp;rsquo;m speaking at the Vim
Chicago Meetup next month about integrating React with Vim. In this post, I&amp;rsquo;m
going to use that opportunity as an excuse to document my speaking process.&lt;/p&gt;</description></item><item><title>You Should Blog</title><link>https://jakeworth.com/posts/you-should-blog/</link><pubDate>Sat, 11 Feb 2017 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/you-should-blog/</guid><description>&lt;p&gt;I created this blog to reflect on my code and development as a
programmer. In that spirit, I&amp;rsquo;d like to make a pitch to
anybody reading: you should blog.&lt;/p&gt;</description></item><item><title>Writing Elixir Sigils</title><link>https://jakeworth.com/posts/writing-elixir-sigils/</link><pubDate>Mon, 04 Jul 2016 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/writing-elixir-sigils/</guid><description>&lt;p&gt;Sigils are a mechanism for working with textual representations in Elixir. If
you&amp;rsquo;ve ever made an array of Strings in Ruby with &lt;code&gt;%w()&lt;/code&gt;, the API is similar.
A neat feature of sigils is that we can make custom variants, or override
existing Kernel variants. The latter is generally discouraged.&lt;/p&gt;</description></item></channel></rss>