Threads for wkmanire

  1. 3

    Seems like a fun DSL. Do you have any plans for a simplified notation for entering notes and durations once you’ve finished designing your instruments?

    1. 4

      Yep, that’s the plan! I don’t see why there needs to be a distinction between instruments and scores like CSound does it though. I’m hoping to figure out something that composes better (pun intended).

      1. 2

        VCV Rack does this pretty well IMO (its a totally different paradigm with one whole type - ‘wire’) I think what makes it work is that it turns 12-tone equal temperament (i.e. ‘notes’) into frequency (i.e. floating point hz) really high in the stack.

    1. 1

      I think this is kind of mixing together a couple of common needs.

      1. Taking notes about how to do something you do infrequently but is difficult to remember, and may be somewhat specific to your particular work environment
      2. Automating repetitive tasks that you do very frequently.

      In your example:

      REM Other useful argument combos
      REM -tcs -tsql -Txml
      

      This is kind of meaningless to me because I don’t use RipGrep. I would think that if for some reason you didn’t use this particular set of args for 6 or 7 months, that “useful argument combos” might not be that helpful to you either because it doesn’t actually tell you what it does or what it is for.

      Based on my interpretation of your use case, I have a little advice for you.

      • Keep well organized notes about how to do those complex but infrequent tasks. Write them as if you were writing them for someone else who had never done it before, because that extra detail might be helpful to you in the long-run.
      • When you do really need to write a script to automate a task, do your best to write the script in a way that the script doesn’t need to be edited frequently. If you have to open up the script and edit it in order for it to be useful, its justification for existence is somewhat dubious. You could have just copy and pasted a sample command from your notes and edited it on the command-line instead.

      Here is a relevant xkcd that you might find interesting, in case you haven’t seen it before:

      xkcd: Is It Worth the Time?

      1. 1

        As much as anything else, it’s also making easy to switch between different arguments for a given command, without forcing me to come up with some arbitrary names for the different combinations of arguments

        I didn’t add this as context in my post, but I have definitely explored up and down the scales of automating repetitive tasks, between building my own versions of things like a jumplist, and building various websites for my own use.

        Not everything is worth documenting in large amounts of detail, but I do think it’s worth trying to point out the small gains for other people from time to time. A small amount of simplicity can go a long way.

        You could have just copy and pasted a sample command from your notes and edited it on the command-line instead.

        One advantage the approach I lined out in my post has is that with a shorter command to type, you’re not having to use a relatively clumsy CLI editor to move things around. This is less of a pain point on bash and unix for a number of reasons.

        I’ll admit that this is far from my most polished blog article, and there are definitely cases where I don’t want to be editing a given script a lot. In my experience, I edit the 2 scripts I have set up with way 1-5 times a day when I’m using them, usually once to get it set up for the task I’m using it for, and then I process to use the script 10-50 times over the next hour or so. For me, anyway, the cost of creating a file and editing it far offsets the awkwardness of trying to get back to a given command in my history. But, for me, this is mostly a bit of an enhancement on a bash alias.