The TidalCycles (or Tidal for short) live coding environment has been developed since around 2009, via several rewrites of its core representation. Rather than having fixed goals, this development has been guided by use, motivated by the open aim to make music. This development process can be seen as a long-form improvisation, with insights into the nature of Tidal gained through the process of writing it, feeding back to guide the next steps of development. This brings the worrying thought that key insights will have been missed along this development journey, that would otherwise have lead to very different software. Indeed participants at beginners' workshops that I have lead or co-lead have often asked questions without good answers, because they made deficiencies or missing features in the software clear. It is well known that a beginner's mind is able to see much that an expert has become blind to. Running workshops are an excellent way to find new development ideas, but the present paper explores a different technique - the rewrite.
翻译：自2009年以来,自2009年左右以来,通过几次重写其核心代表的代码,开发了潮流(或短期潮流)活编码环境。这一发展不是有固定的目标,而是以使用为指导,其动机是音乐的开放目的。这一开发过程可以被视为一种长期的即兴化,通过写作过程对潮流的性质有了深刻的认识,反馈到后面的发展步骤。这带来了一种令人担忧的想法,即在这个发展过程中,关键洞察力将会被错过,否则就会导致非常不同的软件。事实上,我领导或共同领导的初创者讲习班的参与者常常在没有很好答案的情况下提出问题,因为他们在软件中制造了缺陷或缺失特征。众所周知,初创者的思想能够看到一位专家变得盲目。举办讲习班是寻找新的发展想法的绝佳方法,但本文件探索了一种不同的技术,即改写方法。
相关内容
微信扫码咨询专知VIP会员