Sonic Pi VS kubernetes

I have wondered what grooves it could come with using https://sonic-pi.net/

Something fascinating about seeing a 'score' for generative music written out as a sort of specification like that.

There's enough detail there that you can take those instructions and reimplement your own version of it, and you'll end up with essentially the same 'piece of music', but certainly a different interpretation of it. Because while the score lays out some details precisely, it leaves other choices less clear. What does 'all inversions' really mean when enumerating chords? Does it include open, spread voicings? What durations should we choose from for our random waveforms? How short is 'short' when deciding to repeat? And of course, what wave synths should you use, and how should you modulate them?

All those are similar to the decisions a traditional instrumentalist makes when interpreting a sheet music score for performance - here, a generative music coder can follow this 'score' and produce a program that represents their own interpretation of the piece.

Coding it up in Sonic Pi (https://sonic-pi.net/) was a fun exercise, and I feel like I was able to produce something along the lines of what the composer intended. It carries the same kind of mood that the recording in the video has. But it's my own 'performance' of the work, if that makes sense (even if it's actually Sonic Pi 'performing' it at runtime...)

All of which got me thinking about the relationship more generally between specification, and implementation. Considering different programmers' implementations of algorithms as individual 'performances' of scores from the overall design - and then thinking about developers building elements of a larger system architecture as individual performers working to deliver their part of the performance as part of a band or orchestra. Some groups, maybe they're directed by a conductor-architect; others maybe are improvisers, riffing off one another and occasionally stepping up to deliver a solo. And some are maybe solid session performers, showing up and delivering strong but unflashy performances to a producer's specification.

So overall, a nice meditative coding exercise for a Sunday afternoon, and a shift in perspective. Thanks for sharing it.

On a seriously light-hearted note, Herve Aniglo, talked about teaching children to code with music using Sonic PI, a language agnostic platform that helps you learn recursions, looping, circuit breaking and functional programming by creating simple tunes.

https://www.youtube.com/playlist?list=PLPYzvS8A_rTYEba_4SDvR...

- Sonic Pi is built on-top of SuperCollider, but it's MUCH easier to get started with making bleeps and bloops. Sam Aaron, who originally created Overtone (a Clojure front-end for SuperCollider) created Sonic Pi initially to teach kids computer programming and music, but now it's turning into a pretty nice live-coding setup. The language is basically a DSL extension of Ruby, and although it's very elegant, I feel like it's a little nerfed in terms of a full language when compared to SCLang, so I'm sticking with the latter for now. High recommend checking it out if you're new to making music or code. https://sonic-pi.net/

- This 'Intro To Live Coding' vid from Alex McLean is great. Gives a good overview of a few fun tools out there that I won't mention here for sake of time (check out Gibber and Hydra for web-based coding things. Gibber is really slick). Alex invented Tidal Cycles, which I feel is like god-tier in terms of power and conciseness. Maybe I'll tinker with Tidal someday, but I want to start with SC.

Strange dice that it seems to mostly be c++, sponsored by 3 prominent elixir shops, with an original OSC server implementation by Joe Armstrong.

https://github.com/sonic-pi-net/sonic-pi/tree/dev/app/server...

There is a programming language+IDE called SonicPI. It's designed to create music by writing code. You can install the program from the lin, then ask chatGPT to generate some sonic PI code that produces some nice melody. Then just copy the code and paste it into the sonicPI program, and run it by clicking the run button. Here's a conversation for example

In the field of software development, efficiency and agility are always sought after. In the era of cloud-native apps, traditional deployment techniques—which are frequently laborious and prone to errors—are starting to become obstacles. This is when Kubernetes and GitOps come in handy.

Are you looking for a hassle-free way to deploy Moodle™ Learning Management Systems (LMS) on Kubernetes? Look no further! Krestomatio presents the LMS Moodle Operator, an open-source Kubernetes Operator designed to simplify the deployment and management of Moodle instances on Kubernetes clusters. Let's dive into what makes this tool a great choice for Moodle administrators and developers alike.

Securing access to your Kubernetes clusters is crucial as inadequate security measures can lead to unauthorized access and potential data breaches. However, navigating the complexities of Kubernetes access security, especially when setting up strong authentication, authorization, and network policies, can be challenging.

Deploying AI models into production requires tools that can package applications and manage them at scale. Docker simplifies the deployment of AI applications by containerizing them, ensuring that the application runs smoothly in any environment. Kubernetes, an orchestration system for Docker containers, allows for the automated deployment, scaling, and management of containerized applications, essential for AI applications that need to scale across multiple servers or cloud environments.

To learn more, you can start by exploring the official Kubernetes documentation.

With the containerized Node.js/Express API, I could run multiple containers, scaling to handle more traffic. Using a tool called minikube, we can easily spin up a local Kubernetes cluster to horizontally scale Docker containers. It was possible to keep one shared instance of the database, and many APIs were routed with an internal Kubernetes load balancer.

This package is widely used for powerful CLI builds, it is used for example for Kubernetes CLI and GitHub CLI, in addition to offering some cool features such as automatic completion of shell, automatic recognition of flags (the tags) , and you can use -h or -help for example, among other facilities.

We closely monitor Kubernetes and cloud providers' updates by following official changelogsand using RSS feeds, allowing us to anticipate potential issues and adapt our infrastructure proactively.

"You are holding it wrong", huh?

From the homepage https://kubernetes.io/:

"Kubernetes, also known as K8s, is an open-source system for automating deployment, scaling, and management of containerized applications."

Do you see "not recommended for smaller-scale applications" anywhere? Including on the entire home page? Looking for "small", "big" and "large" also yields nothing.