<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Notes on Tend and Flow</title>
		<link>https://tendandflow.com/tags/notes/</link>
		<description>Recent content in Notes on Tend and Flow</description>
		<generator>Hugo</generator>
		<language>en-gb</language>
		
		
		
		
			<lastBuildDate>Mon, 10 Aug 2026 12:03:50 +0100</lastBuildDate>
		
			<atom:link href="https://tendandflow.com/tags/notes/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>The New Site Is Live</title>
				<link>https://tendandflow.com/journal/new-site-is-live/</link>
				<pubDate>Mon, 10 Aug 2026 12:03:50 +0100</pubDate>
				<guid>https://tendandflow.com/journal/new-site-is-live/</guid>
				<description>&lt;p&gt;I just finished a &lt;a href=&#34;https://en.wikipedia.org/wiki/Retrospective&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;retrospective&lt;span class=&#34;visually-hidden&#34;&gt; (opens in a new tab)&lt;/span&gt;&lt;/a&gt; with Claude and asked it how I did. It started as a funny idea to see what would happen, but it actually turned up some useful stuff!&lt;/p&gt;&#xA;&lt;h2 id=&#34;some-context&#34;&gt;Some context&lt;/h2&gt;&#xA;&lt;p&gt;Last week, I rebuilt the site for Tend and Flow.  It had been a placeholder and mid-Summer seemed like a perfect time to do it properly.  I used Opus 5 in VSCode as my main workbench (everything is happening in either VSCode or Cowork these days!).  Based on my brief to make the attack surface as small as possible, we ended up deciding to orientate around markdown files (it&amp;rsquo;s a low volume site).  I used Claude Design to decide the type, palette and wireframe.  We built the first version to check the content workflow.  Then, again in Design, created and implemented a more thematic aesthetic based on my branding.  After the release of v1, I created a specific maintenance skill for ongoing checks, did the tidy up and compacting.  Nothing particularly innovative, but it took about three days (of which 60% of the time was really spent on content).&lt;/p&gt;</description>
			</item>
			<item>
				<title>Is AI Dismantling the Skills Ladder</title>
				<link>https://tendandflow.com/journal/dismantling-the-skills-ladder/</link>
				<pubDate>Sat, 13 Jun 2026 19:45:01 +0100</pubDate>
				<guid>https://tendandflow.com/journal/dismantling-the-skills-ladder/</guid>
				<description>&lt;figure class=&#34;pullquote&#34;&gt;&#xA;    &lt;blockquote&gt;&lt;p&gt;“Apprentices spend months just learning how to wring out hot towels. After that, they are taught how to prepare the fish. And then, finally, they are allowed to cook the rice. It is not an easy path.”&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;    &lt;figcaption class=&#34;pullquote-attrib&#34;&gt;Jiro Dreams of Sushi (2011), &lt;a href=&#34;https://www.imdb.com/title/tt1772925/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;IMDB&lt;span class=&#34;visually-hidden&#34;&gt; (opens in a new tab)&lt;/span&gt;&lt;/a&gt;&lt;/figcaption&gt;&#xA;  &lt;/figure&gt;&lt;p&gt;The framework is this: mastery develops in three stages. The Apprentice follows instructions - recipes and algorithms, the explicit steps that produce a known result. The Journeyman has internalised enough of those recipes to begin modelling behaviour - adapting, blending, responding to context with a working knowledge of what good looks like. The Master operates from principles. They are no longer following a map or copying a pattern. They are navigating from a deep, internalised understanding of why things work the way they do.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
