<?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>Communication on Jake Worth</title><link>https://jakeworth.com/tags/communication/</link><description>Recent content in Communication 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>Fri, 03 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://jakeworth.com/tags/communication/index.xml" rel="self" type="application/rss+xml"/><item><title>A Missing README Isn't a Missing README</title><link>https://jakeworth.com/posts/a-missing-readme-isnt-a-missing-readme/</link><pubDate>Sun, 29 Mar 2026 09:32:47 -0400</pubDate><guid>https://jakeworth.com/posts/a-missing-readme-isnt-a-missing-readme/</guid><description>&lt;p&gt;A missing README is rarely just missing documentation. It usually signals other
things, too.&lt;/p&gt;</description></item><item><title>"What's Wrong With This Idea?"</title><link>https://jakeworth.com/posts/whats-wrong-with-this-idea/</link><pubDate>Wed, 11 Feb 2026 09:43:43 -0500</pubDate><guid>https://jakeworth.com/posts/whats-wrong-with-this-idea/</guid><description>&lt;p&gt;One of my favorite problem-solving questions is: &amp;ldquo;What&amp;rsquo;s wrong with this idea?&amp;rdquo; It drives the conversation away from why the idea might work, and toward why it might fail. That perspective is invaluable when building.&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>Banishing "Random" for Better Software Communication</title><link>https://jakeworth.com/posts/nothing-is-random/</link><pubDate>Tue, 17 Jun 2025 12:19:04 -0400</pubDate><guid>https://jakeworth.com/posts/nothing-is-random/</guid><description>&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;I&amp;rsquo;m still getting this random 404.&amp;rdquo;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Want to sound pro? Banish &amp;ldquo;random&amp;rdquo; from your software engineering vocabulary.&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 I Approach Feature Requests</title><link>https://jakeworth.com/posts/how-i-approach-feature-requests/</link><pubDate>Wed, 14 May 2025 17:40:42 -0400</pubDate><guid>https://jakeworth.com/posts/how-i-approach-feature-requests/</guid><description>&lt;p&gt;Receiving feature requests is part of running a software team. Here&amp;rsquo;s how I handle them.&lt;/p&gt;</description></item><item><title>Your Software Is Confusing</title><link>https://jakeworth.com/posts/your-software-is-confusing/</link><pubDate>Mon, 07 Apr 2025 10:16:44 -0400</pubDate><guid>https://jakeworth.com/posts/your-software-is-confusing/</guid><description>&lt;p&gt;If something in your software is confusing to a customer, it &lt;em&gt;is&lt;/em&gt; confusing.&lt;/p&gt;</description></item><item><title>Two-Follow-Up Rule for Closing Support and Internal Tickets</title><link>https://jakeworth.com/posts/hit-it-twice/</link><pubDate>Tue, 04 Mar 2025 09:28:10 -0500</pubDate><guid>https://jakeworth.com/posts/hit-it-twice/</guid><description>&lt;p&gt;I recently learned a practice for customer communication that I&amp;rsquo;d like to document. It&amp;rsquo;s called &amp;ldquo;Hit It Twice.&amp;rdquo;&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>Deliver a Great Standup Report as an Engineer</title><link>https://jakeworth.com/posts/deliver-a-great-standup-report-as-an-engineer/</link><pubDate>Wed, 09 Nov 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/deliver-a-great-standup-report-as-an-engineer/</guid><description>&lt;p&gt;I&amp;rsquo;ve been lucky to have worked with some great engineers, and one thing that
they tend to do exceptionally well is reporting about their work at meetings.
Today I&amp;rsquo;d like to summarize what I think makes a great standup report.&lt;/p&gt;</description></item><item><title>How to Write a Perfect Bug Report (With Template)</title><link>https://jakeworth.com/posts/a-perfect-bug-report/</link><pubDate>Mon, 13 Jun 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/a-perfect-bug-report/</guid><description>&lt;p&gt;Bugs are part of software. Reporting bugs well is a necessary skill in an ever-growing number of job titles. In this post, I&amp;rsquo;d like to explain how to write a perfect bug report and offer some bug-reporting best practices.&lt;/p&gt;</description></item><item><title>The Problems With Code Screenshots</title><link>https://jakeworth.com/posts/on-code-screenshots/</link><pubDate>Tue, 19 Apr 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/on-code-screenshots/</guid><description>&lt;p&gt;Screenshots of code are common in developer communication, but they come with real drawbacks. Here&amp;rsquo;s why I try to avoid them.&lt;/p&gt;</description></item><item><title>Your Demo Doesn't Need Auth</title><link>https://jakeworth.com/posts/your-demo-doesnt-need-auth/</link><pubDate>Fri, 01 Apr 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/your-demo-doesnt-need-auth/</guid><description>&lt;p&gt;When building a demo application, I believe you can often skip authentication.&lt;/p&gt;</description></item><item><title>Bug Reports Are Gold</title><link>https://jakeworth.com/posts/bug-reports-are-gold/</link><pubDate>Sat, 15 Jan 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/bug-reports-are-gold/</guid><description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Me&lt;/strong&gt;: Hey, I&amp;rsquo;m experiencing an issue with your software. Here&amp;rsquo;s a &lt;a href="https://jakeworth.com/posts/a-perfect-bug-report/"&gt;detailed bug report&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;SAAS Engineer&lt;/strong&gt;: What you&amp;rsquo;re describing isn&amp;rsquo;t possible.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Narrator:&lt;/strong&gt; &lt;em&gt;But it was possible.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;This is a frustrating, unproductive snippet of a conversation I&amp;rsquo;ve had a few times in my
career. What can we learn? Treat bug reports like gold.&lt;/p&gt;</description></item><item><title>Comprehensive Instructions</title><link>https://jakeworth.com/posts/comprehensive-instructions/</link><pubDate>Mon, 09 Jul 2018 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/comprehensive-instructions/</guid><description>&lt;p&gt;A user opened an issue in Tilex last week that I spent a significant amount of
time thinking about and talking about (thanks JB) before responding to. Here&amp;rsquo;s
the truncated request:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;May I ask you to compile a step-by-step list to set up a running TIL
instance?&lt;/p&gt;
&lt;/blockquote&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>