<?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>Process on Jake Worth</title><link>https://jakeworth.com/tags/process/</link><description>Recent content in Process 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, 29 Oct 2026 09:27:01 -0400</lastBuildDate><atom:link href="https://jakeworth.com/tags/process/index.xml" rel="self" type="application/rss+xml"/><item><title>Dash for Pairing</title><link>https://jakeworth.com/tils/dash-for-pairing/</link><pubDate>Thu, 29 Oct 2026 09:27:01 -0400</pubDate><guid>https://jakeworth.com/tils/dash-for-pairing/</guid><description>&lt;p&gt;I&amp;rsquo;ve written about Kapeli Dash before: it&amp;rsquo;s a Mac program that lets you download
sets of documentation to your computer. This week I discovered a killer use
case: pair-programming.&lt;/p&gt;
&lt;p&gt;Recently I was pairing in a domain I didn&amp;rsquo;t know well. Before the session, I
loaded Dash with every docset I thought I might need. So, for Python, think:
Python, Django, and SaltStack, plus React and TailwindCSS for the frontend.&lt;/p&gt;
&lt;p&gt;When we needed docs, we could effortlessly explore these resources without
Googling. Opening a browser while a pairing can be distracting (Banner ads! AI
summary!), it can expose your personal information, and is a bit more clumsy
when you know what you need. I can find React&amp;rsquo;s &lt;code&gt;useMemo&lt;/code&gt; docs by typing
&lt;code&gt;useMemo&lt;/code&gt; into Dash and hitting enter— that&amp;rsquo;s it. There&amp;rsquo;s no path to that
resource online that&amp;rsquo;s as direct as that.&lt;/p&gt;</description></item></channel></rss>