Live Recording Published December 16, 2019
I’ve been working on a new tune. I decided to capture myself doing some improv with pieces of the tune.
My blog. Personal thoughts, anecdotes, and musings.
I’ve been working on a new tune. I decided to capture myself doing some improv with pieces of the tune.
When I was in college, I spent hundreds of hours using ReBirth, a music-making app that emulated two Roland 303 bassline synths, an 808 drum machine, and a 909 drum machine. Rebirth also had a number of effects and filters included. Unfortunately, support for ReBirth died many years ago. It doesn’t even run on macOS. If you were lucky enough to buy an iPad version a few years ago, you can still use that, but it’s no longer supported since Roland threatened to sue them so they took it off the store.
About seven months ago, I began moving this site from a WordPress setup to a static site using Hugo, which I’m writing a book on right now. There’s still a ton of work to do, but it was bugging me that I didn’t have my own place to write. I’d been delaying writing a ton of content because my site wasn’t “ready”. But “ready” is a relative term anyway, so I pulled the trigger and made the swap.
In celebration of Hacktoberfest, which has a pretty great 80s theme, I composed a 5 song EP of synthwave tunes. I limited myself to virtual recreations of classic synths like the Roland 707 drum machine, the Yamaha DX-7 synth, and the Roland Jupiter-8. Give it a listen!
(Originally posted over at Medium)
In this post, the author, Dominic Pace, argues that we should teach “actual programming” instead of Scratch. I encourage you to read that first because it makes some great points. It’s written by a high school senior who’s hit upon something important: “Learn to code” tools like Scratch and Alice really are somewhat disconnected from software development. They do help with problem-solving, and they do help students work with the very basics of software development, but they create an unrealistic expectation of how we really build software.
Today marks one year with DigitalOcean, and I couldn’t be happier. I’m so unbelievably lucky to get to do what I do there. I work on the DigitalOcean Tutorials collection, where I help community authors get their articles published. It’s the perfect job for me, as I get to draw from my software development and system administration backgrounds, as well as my writing, editing, and teaching experiences. Writing software is fun, but DigitalOcean gives me the opportunity to help others get better at what they do.
I’m nearly two months into my new job. For those of you that haven’t heard, I am a Technical Editor at DigitalOcean, a fantastic startup based in New York City. I work with a great team of people, and I help open-source enthusiasts share their knowledge through written tutorials. I’m responsible for taking their submitted tutorials and testing them out, looking for inaccuracies, security problems, or other issues a reader might encounter.
I’ve had an amazing time teaching aspiring software developers. Over the course of the last four years I’ve had the privilege of teaching over 400 students how to use Linux, how to build their first web sites, and how to write their first software applications. I’ve met some truly incredible people and forged some great relationships which I hope continue on for many years. But today I turned in my letter of resignation and am looking forward to what lies ahead.
Measuring how long a software project will take is a futile endeavor. Unfortunately, people who hire software developers have a habit of asking for the impossible. Like when they want you to build a Facebook clone in two weeks for $200. So to appease my clients and managers over the years, I developed a formula to somewhat accurately address the “how long will it take” question. And despite it being a bit tounge-in-cheek, it’s startlingly accurate when you sit down and think about it.
I’ve been around software development a long time, and a reoccurring theme is to see this kind of feedback from peers: