Music with GregePorter

Ok, let me start off this post straight; this isn't a guide for how to make a module, but the starting point of what a module or writing a module even means. I am, by trade, a software engineer. Without getting into too too much detail about my past, for years I had an antagonistic relationship with my job. I think that might've been one of the reasons why I've been working to get into music because it isn't software development. That said, I know I can code and I have enjoyed it from time to time so it must not be all  of my job that I dislike.  In my other posts, I've been discussing Sonic Pi, a programming language based in Ruby that was design for music making. It's been a really cool way to use the coding skills that I have with a newfound appreciation of music theory. So, what if we take this a step further. What if I could be like paid to do something like this? I know this is something of a neoliberal sentiment but, hear me out. What are ways that I coul...

Analog Days: The Invention and Impact of the Moog Synthesizer Revised Edition by Trevor Pinch (Author), Frank Trocco (Author) ISBN-13:   978-0674016170 ISBN-10:   0674016173 For the past couple weeks, I've been reading Analog Days by Trevor Pinch and Frank Trocco. My wife got it for me as a gift because she knows I'm interested in synthesizers. My journey in synth and what they talk about in the book would make for a number of posts. For our purposes here, I'd like to discuss the differences between two pioneers of the synthesizer; Buchla and Moog. Without getting into too much of the details (it would spoil the fun of the book). Buchla made his synthesizers sans keyboards and, you may have guessed, Moog used the keyboard. I haven't gotten to the point in the book about why that propelled Moog to the powerhouse it is today but it got me thinkin'. As one who has struggled to learn the piano, do I really  need  it? Weeks ago, I loaded up a fresh ins...