<story><title>Making Your Writing Work Harder For You</title><url>https://training.kalzumeus.com/newsletters/archive/content-marketing-strategy</url></story><parent_chain></parent_chain><comment><author>patio11</author><text>This was partly in response to a conversation Thomas and I have been having lately with some people from the Internets, about the value of blogging in one&amp;#x27;s professional capacity.  His take was &amp;quot;Have a blog, but don&amp;#x27;t call it a blog.&amp;quot;  I thought that was generalizable to a larger segment of the operations of product businesses than just blogging.  They&amp;#x27;re generally called &amp;quot;content marketing&amp;quot; these days but I hate that word -- if someone has a better one, please suggest it.&lt;p&gt;By the way, if you&amp;#x27;re a regular-ol&amp;#x27;-geek and wondering &amp;quot;I wonder if writing about technical topics could help me career-wise&amp;quot;, the answer is &amp;quot;Absolutely yes.&amp;quot;  You can use blogging &lt;i&gt;software&lt;/i&gt; but it probably isn&amp;#x27;t your benefit to adopt the blogging &lt;i&gt;format&lt;/i&gt; of 500 ~ 1,000 word articles displayed in reverse chronological order about disconnected topics.  Instead, you could make it a goal to write three pieces and polish them to a mirror shine.&lt;p&gt;(Related advice that I find myself saying frequently: If you publish OSS and expect to get anything via doing so, don&amp;#x27;t just drop the OSS on github.  Spend the extra bit of time packing it into a site with a getting-started guide, a visual identity distinct from &amp;quot;Github rendering a Readme file&amp;quot;, and the request that interested people $TAKE_THE_ACTION_YOU_WANT_THEM_TO_TAKE.</text></comment>
<story><title>Making Your Writing Work Harder For You</title><url>https://training.kalzumeus.com/newsletters/archive/content-marketing-strategy</url></story><parent_chain></parent_chain><comment><author>iamwil</author><text>I dislike coming upon writing where there&amp;#x27;s no date. Because then I can&amp;#x27;t judge for myself from what context or perspective the author wrote something. (Is the assertion that mobile market is growing in the context of pre 2008 iPhone, or after?)&lt;p&gt;There&amp;#x27;s many assumptions we take for granted, even when we try to write evergreen. And sometimes those assumptions turn out to be overturned after a while.&lt;p&gt;When I happen upon articles, essays, blog posts, etc without a date, I usually trust it much less, and try to find similar information with a date.&lt;p&gt;The only way you&amp;#x27;ll know if your writing is evergreen, is over the course of time. I&amp;#x27;ll read stuff from 2002, and find it&amp;#x27;s still relevant, but we need to judge whether it is for ourselves every year. And not timestamping it robs us of that.</text></comment>