<?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>Docs on Jake Worth</title><link>https://jakeworth.com/tags/docs/</link><description>Recent content in Docs 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>Tue, 07 Jul 2026 12:05:47 -0400</lastBuildDate><atom:link href="https://jakeworth.com/tags/docs/index.xml" rel="self" type="application/rss+xml"/><item><title>Unknown Value in Brackets</title><link>https://jakeworth.com/tils/unknown-value-in-brackets/</link><pubDate>Tue, 07 Jul 2026 12:05:47 -0400</pubDate><guid>https://jakeworth.com/tils/unknown-value-in-brackets/</guid><description>&lt;p&gt;I&amp;rsquo;m reading &lt;a href="https://howtoopensource.dev/"&gt;&lt;em&gt;How to Open Source&lt;/em&gt;&lt;/a&gt; by Richard
Schneeman (fantastic) and one of his tips is to show documentation code like
this (consider documenting &lt;code&gt;ls&lt;/code&gt;):&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;ls &amp;lt;desired-path&amp;gt;
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Rather than the common:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;ls /your/path/here
&lt;/code&gt;&lt;/pre&gt;</description></item><item><title>Rust Erroring Code Visual Aid</title><link>https://jakeworth.com/tils/rust-erroring-code-visual-aid/</link><pubDate>Mon, 06 Jul 2026 11:16:08 -0400</pubDate><guid>https://jakeworth.com/tils/rust-erroring-code-visual-aid/</guid><description>&lt;p&gt;Today while reading the &lt;a href="https://doc.rust-lang.org/"&gt;Rust Documentation&lt;/a&gt;, I
encountered a fantastic UX touch. The authors provide this image with each code
block that intentionally doesn&amp;rsquo;t compile:&lt;/p&gt;
&lt;figure&gt;
&lt;img loading="lazy" src="https://doc.rust-lang.org/book/img/ferris/does_not_compile.svg"
alt="Doesn&amp;#39;t Compile" width="300"/&gt;
&lt;/figure&gt;</description></item><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>Read the Docs</title><link>https://jakeworth.com/posts/read-the-docs/</link><pubDate>Wed, 19 Oct 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/read-the-docs/</guid><description>&lt;p&gt;When learning a new language or framework, the first thing I do is read the
official documentation cover-to-cover.&lt;/p&gt;</description></item><item><title>Improve Your API Documentation Workflow with Dash</title><link>https://jakeworth.com/posts/level-up-your-dash/</link><pubDate>Sun, 21 Aug 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/level-up-your-dash/</guid><description>&lt;p&gt;One of my all-time favorite programming tools is Dash by Kapeli. In this post,
I&amp;rsquo;ll share some tips for leveraging this fantastic program.&lt;/p&gt;</description></item><item><title>How to Read Postgres Docs</title><link>https://jakeworth.com/posts/how-to-read-postgres-docs/</link><pubDate>Mon, 21 Mar 2022 00:00:00 +0000</pubDate><guid>https://jakeworth.com/posts/how-to-read-postgres-docs/</guid><description>&lt;p&gt;Have you ever tried to read the documentation for a Postgres command? Although
many consider Postgres&amp;rsquo; docs best-in-class, they include conventions that might
challenge newbies. In this post, I&amp;rsquo;ll paraphrase Postgres&amp;rsquo; conventions page to
help us understand what the documentation for a command is saying.&lt;/p&gt;</description></item></channel></rss>