kfitz/kfitz-site
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

add writing

Browse Source
This commit is contained in:
Kathleen Fitzpatrick
2025-03-18 14:52:53 -04:00
parent 58c1f00ea2
commit c0ee637436
1875 changed files with 2643 additions and 1896 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
feed/feed.xml
View File

@@ -5,11 +5,26 @@
<subtitle>The long-running and erratically updated blog of Kathleen Fitzpatrick.</subtitle>
<link href="https://kfitz.info/feed/feed.xml" rel="self" />
<link href="https://kfitz.info/" />
<updated>2025-02-18T13:39:29Z</updated>
<updated>2025-03-18T00:00:00Z</updated>
<id>https://kfitz.info/</id>
<author>
<name>Kathleen Fitzpatrick</name>
</author>
<entry>
<title>Writing Again</title>
<link href="https://kfitz.info/writing-again/" />
<updated>2025-03-18T00:00:00Z</updated>
<id>https://kfitz.info/writing-again/</id>
<content type="html">&lt;p&gt;It happened this weekend.&lt;/p&gt;
&lt;p&gt;In the aftermath of turning in the final manuscript for &lt;a href=&quot;https://www.press.jhu.edu/books/title/12787/leading-generously&quot;&gt;&lt;em&gt;Leading Generously&lt;/em&gt;&lt;/a&gt;, I &lt;a href=&quot;https://kfitz.info/recalibrating-again/&quot;&gt;promised myself&lt;/a&gt; that I would not start working on a new writing project until I had some idea that absolutely would not leave me alone, that I&#39;d instead spend at least a year reading as omnivorously as I could through the ideas of others and see whether anything worth saying surfaced. &lt;a href=&quot;https://kfitz.info/reading/&quot;&gt;Almost exactly a year later&lt;/a&gt;, I was still delighting in the reading, but feeling the first glimmerings of an urge to write, if not with the focus of a project.&lt;/p&gt;
&lt;p&gt;Right after the second blog post linked above, though, I ended up in my &lt;a href=&quot;https://kfitz.info/new-jobs&quot;&gt;new position&lt;/a&gt; and my program of intensive reading and diffuse writing got utterly derailed. I figured it would be at least another year before things started to coalesce into a project.&lt;/p&gt;
&lt;p&gt;But it happened this weekend. I&#39;m not at all sure that the way I&#39;m framing the idea is right, whether the idea itself will have legs, but I&#39;m starting to do some noodling in a more purposeful fashion.&lt;/p&gt;
&lt;p&gt;And I&#39;m excited about the possibilities, for the first time in quite a while. The whole thing may yet fizzle, of course, but in a conversation yesterday I jokingly said something about quitting my day job and there was this immediate thought bubble that popped up saying &amp;quot;and then you would have time to work on That New Project!&amp;quot; And I felt a rush of excitement in the wake.&lt;/p&gt;
&lt;p&gt;On the one hand, I take this as an encouraging sign: I really do want to work on this thing!&lt;/p&gt;
&lt;p&gt;On the other, I recognize the temptations posed by the alluring project you don&#39;t have time for, and the ways that turning that project into your primary point of focus can take a lot of the shine off.&lt;/p&gt;
&lt;p&gt;But right here, right now, I long for a writing project to really wrestle with. And so I&#39;m looking forward to carving out the moments here and there to work on it, even if I don&#39;t quit my day job to do it.&lt;/p&gt;
</content>
</entry>
<entry>
<title>Leading Generously, the Audiobook!</title>
<link href="https://kfitz.info/leading-generously-audiobook/" />
@@ -129,17 +144,6 @@
&lt;p&gt;Productivity is a trap. Becoming more efficient just makes you more rushed, and trying to clear the decks simply makes them fill up again faster. Nobody in the history of humanity has ever achieved &amp;quot;work-life balance,&amp;quot; whatever that might be, and you certainly won’t get there by copying the &amp;quot;six things successful people do before 7:00 a.m.&amp;quot; The day will never arrive when you finally have everything under control—when the flood of emails has been contained; when your to-do lists have stopped getting longer; when you’re meeting all your obligations at work and in your home life; when nobody’s angry with you for missing a deadline or dropping the ball; and when the fully optimized person you’ve become can turn, at long last, to the things life is really supposed to be about. Let’s start by admitting defeat: none of this is ever going to happen.&lt;/p&gt;
&lt;p&gt;But you know what? That&#39;s &lt;em&gt;excellent&lt;/em&gt; news. (16)&lt;/p&gt;
&lt;/blockquote&gt;
</content>
</entry>
<entry>
<title>In Pursuit of the POSSE Pipedream</title>
<link href="https://kfitz.info/posse-pipedream/" />
<updated>2024-11-29T19:55:21Z</updated>
<id>https://kfitz.info/posse-pipedream/</id>
<content type="html">&lt;p&gt;Some months back, I set up the ability to push new blog posts (or at least summaries thereof) to &lt;a href=&quot;https://hcommons.social/@kfitz&quot;&gt;my hcommons.social account&lt;/a&gt;, using a service called &lt;a href=&quot;https://mastofeed.org&quot;&gt;Mastofeed&lt;/a&gt;. Now that I find myself using &lt;a href=&quot;https://bsky.app/profile/kfitz.info&quot;&gt;Bluesky&lt;/a&gt; at least a bit, I wanted to think about how it might fit into my workflows.&lt;/p&gt;
&lt;p&gt;I&#39;m a big fan of the &lt;a href=&quot;https://indieweb.org/POSSE&quot;&gt;IndieWeb POSSE&lt;/a&gt; mode of publishing here at &lt;a href=&quot;http://kfitz.info&quot;&gt;kfitz.info&lt;/a&gt; (thereby owning my content) and syndicating that content elsewhere. Mastofeed helped me do that, but it&#39;s of course Mastodon-specific. After a little searching around I ran across &lt;a href=&quot;https://www.raymondcamden.com/2024/11/05/automatically-posting-to-bluesky-on-new-rss-items&quot;&gt;this blog post by Raymond Camden&lt;/a&gt;, detailing how he used &lt;a href=&quot;https://pipedream.com&quot;&gt;Pipedream&lt;/a&gt; to push new blog posts to Bluesky. The post includes a link to &lt;a href=&quot;https://www.raymondcamden.com/2022/12/06/automatically-posting-to-mastodon-and-twitter-on-new-rss-items&quot;&gt;his prior use of Pipedream to do the same for Mastodon and Twitter&lt;/a&gt;, so I decided to see if I could build a single workflow that (1) listens to &lt;a href=&quot;https://kfitz.info/feed/feed.xml&quot;&gt;my RSS feed&lt;/a&gt; for new posts, (2) extracts the key stuff (in this case, the post title and link) from it, and (3) passes it to both Mastodon and Bluesky.&lt;/p&gt;
&lt;p&gt;Pipedream is nowhere near as no-/low-code as the long-lamented Yahoo Pipes, but it&#39;s pretty amazing nonetheless, and provides great &lt;a href=&quot;https://pipedream.com/docs&quot;&gt;documentation&lt;/a&gt; for the many, many things you can build with it. There was a pre-built step for Mastodon posting, so that was easy peasy, but Bluesky required a bit of coding to connect with its API (which is also &lt;a href=&quot;https://docs.bsky.app/docs/get-started&quot;&gt;pretty well documented&lt;/a&gt;). After a few &lt;a href=&quot;https://bsky.app/profile/kfitz.info/post/3lc4crk4laj25&quot;&gt;minorly amusing missteps&lt;/a&gt;, I&#39;ve now got a workflow up and running that should allow me to publish this post and have notifications about it go out to both hcommons.social and Bluesky within a few minutes.&lt;/p&gt;
&lt;p&gt;Now to go about the having-thoughts-worth-sharing part of the endeavor.&lt;/p&gt;
</content>
</entry>
</feed>