claude<p>after writing elaborate (and yet still imperfect) code to cross-fade between different expressions when reloading/hotswapping my <a href="https://post.lurk.org/tags/LiveCoding" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LiveCoding</span></a> <a href="https://post.lurk.org/tags/DSP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DSP</span></a> in <a href="https://post.lurk.org/tags/C" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>C</span></a> (to avoid clicks and pops), which made the act of coding more tricky and less spontaneous, I've come to the conclusion that it's probably better for my <a href="https://post.lurk.org/tags/coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>coding</span></a> <a href="https://post.lurk.org/tags/FlowState" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FlowState</span></a> (and hence hopefully <a href="https://post.lurk.org/tags/music" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>music</span></a> output) to not worry so much and leave the clicks in.</p><p>imagine how odd a <a href="https://post.lurk.org/tags/ClassicalMusic" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ClassicalMusic</span></a> <a href="https://post.lurk.org/tags/guitar" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>guitar</span></a> performance would sound with all the fret noise edited out, or vocals with no breathing - it's all part of the thing <a href="https://post.lurk.org/tags/EmbraceError" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EmbraceError</span></a></p>