We are not here to make code
i’ve been thinking a bit about this comment by @apaleslimghost
in practice “let code die” often means “let someone from the ingroup kill your code”. if someone’s new at strudel/hydra and does something weird/unexpected/“wrong” it’ll get deleted by someone more experienced and they’re sitting there thinking “aww i was just playing around and now I can’t”. it comes across as “bad code only. no not like that”
i think a common misconception of #pastagang is that this experience changes once you somehow become part of the in-group.
this is very much my current experience too, and it always stings, which is why we say “let code die” - to numb the sting.
this is not a feeling that’s exclusive to beginners and this is not something that people try to avoid especially. rather they seek it out!
for sure, there was period of time where i hadn’t got used to it yet, and now i am more used to it, but the experience itself hasn’t changed.
i would say it is one of the more tell-tale signs that someone is new: if they don’t edit or touch or delete other people’s code at all, they’re often new (from my anecdotal experience) and it’s often characterised by someone making suggestions or requests nearby your code. it’s fun to be able to give them permission to “do it” themselves
for sure, different jammers have different ways of editing your code. some jammers, like eddyflux, tend to do the laser precise edit that has a large impact, like sticking one line on every pattern to change the pitch or tempo. other jammers are way more heavy handed and will come in and delete your entire block, and i remember switch angel being great at that. i’d look up in shock and she just gives me a cheeky/menacing smile lol
but yeah, either way, the point is not to make code!!! bad or otherwise, the point is not to make code: and i think that’s an interesting idea that can be shocking or off-putting at first
... continue reading