music
The job of art is to chase ugliness away
I would want to be in that darkness
A haunting, syncopated music
Silence
A Book by John CageOur Comrade The Electron
A Talk by Maciej CegłowskiSonic architecture
An Article by Daisy AliotoBrian Eno is well-represented in iOS. His other apps like Bloom, Trope and Air invite listeners to touch the screen to make their own composition. Reflection ($30.99) is different, there is no interaction for the listener. The interface has three buttons: a pause button, a sleep timer, and AirPlay. Reflection produces endless permutations of Eno’s 2017 album, an hour and five minute long title track.
“Just calling it an app is akin to saying Falling Water is just a building,” writes one app store reviewer. “I would not call this an app,” agrees another, “Between the music and visuals it’s more like sonic architecture.” The visuals consist of slowly morphing rectangles that only seem to change in the split second you look away from the screen.
Don’t Play It Like the Flute
An Article by Matthias OttDon’t play it like the flute. Play it as if it was the wind whistling through the desert dunes.
No matter what you love to create, there is something to be learned from the way Hans Zimmer approached the Dune score. We are all striving to create work that is novel, innovative, memorable, and inspiring. To get there, however, we tend to focus on getting things right, on avoiding mistakes, on “being professional”. Yes, it is important to have the commitment, dedication, and attention to detail of a professional. But being right? That will only take you so far. What is much more important is to approach the problem in front of you with curiosity and an open mind. With an urge to explore what can be found beyond the ordinary, beyond the right way of doing things. If you want to create something that nobody has come up with yet, it is important that you try out all the crazy ideas others are afraid to try, that you build prototypes, improvise, and freely play with the materials and the technologies you have at hand.
Music and Imagination
A Book by Aaron CoplandThe Gifted Listener: Composer Aaron Copland on Honing Your Talent for Listening to Music
An Article by Maria PopovaThe poetry of music, Copland intimates, is composed both by the musician, in the creation of music and its interpretation in performance, and by the listener, in the act of listening that is itself the work of reflective interpretation. This makes listening as much a creative act as composition and performance — not a passive receptivity to the object that is music, but an active practice that confers upon the object its meaning: an art to be mastered, a talent to be honed.
Enjoying the garden together
A Quote by Brian EnoAnd essentially the idea there is that one is making a kind of music in the way that one might make a garden. One is carefully constructing seeds, or finding seeds, carefully planting them and then letting them have their life.
What this means, really, is a rethinking of one’s own position as a creator. You stop thinking of yourself as me, the controller, you the audience, and you start thinking of all of us as the audience, all of us as people enjoying the garden together. Gardener included.
tree.fm
A WebsiteTune Into Forests From Around The World. Escape, Relax & Preserve.
An audio professional's take on vinyl
An ArticleThe analog-digital debate in audio is a longstanding one, and while it is unlikely to be resolved anytime soon, I thought I might be able to offer some background as a longtime audio professional and musician. Recordings are a beautiful mix of technical and aesthetic concerns, and this post will attempt to tease out how to navigate these two framings of music recording, especially with regard to the often-oversimplified distinction between analog and digital recordings.
In Conversation With...
A Dialogue by Trent ReznorThe Microsoft Sound
A Quote by Brian EnoThe thing from the agency said, "We want a piece of music that is inspiring, universal, blah- blah, da-da-da, optimistic, futuristic, sentimental, emotional," this whole list of adjectives, and then at the bottom it said "and it must be 3 1/4 seconds long."
I thought this was so funny and an amazing thought to actually try to make a little piece of music. It's like making a tiny little jewel.
In fact, I made 84 pieces. I got completely into this world of tiny, tiny little pieces of music. I was so sensitive to microseconds at the end of this that it really broke a logjam in my own work. Then when I'd finished that and I went back to working with pieces that were like three minutes long, it seemed like oceans of time.
last.fm
A Profile by Nick TrombleyI've been tracking my listening habits with last.fm since I was in high school. As I'm about to turn 30, it's nice to be able to look back on almost my entire adult life – to see how I've changed and how my tastes have changed with me.
The small web is beautiful
I believe that small websites are compelling aesthetically, but are also important to help us resist selling our souls to large tech companies. In this essay I present a vision for the “small web” as well as the small software and architectures that power it.
Why aim small?
Why aim small in this era of fast computers with plenty of RAM? A number of reasons, but the ones that are most important to me are:
- Fewer moving parts. It’s easier to create more robust systems and to fix things when they do go wrong.
- Small software is faster. Fewer bits to download and clog your computer’s memory.
- Reduced power consumption. This is important on a “save the planet” scale, but also on the very local scale of increasing the battery life of your phone and laptop.
- The light, frugal aesthetic. That’s personal, I know, but as you’ll see, I’m not alone.
Features and complexity
Niklaus Wirth of Pascal fame wrote a famous paper in 1995 called A Plea for Lean Software. His take is that “a primary cause for the complexity is that software vendors uncritically adopt almost any feature that users want”, and “when a system’s power is measured by the number of its features, quantity becomes more important than quality”.
Solving the problem of software bloat
But instead of just complaining, how do we actually solve this problem? Concretely, I think we need to start doing the following:
- Care about size: this sounds obvious, but things only change when people think they’re important.
- Measure: both your executable’s size, and your program’s memory usage. You may want to measure over time, and make it a blocking issue if the measurements grow more than x% in a release. Or you could hold a memory-reduction sprint every so often.
- Language: choose a language that has a chance.
- Remove: cut down your feature set. Aim for a small number of high-quality features. My car can’t fly or float, and that’s okay – it drives well.
- Say no to new features: unless they really fit your philosophy, or add more than they cost over the lifetime of your project.
- Dependencies: understand the size and complexity of each dependency you pull in. Use only built-in libraries if you can.
Raw size isn't enough
A few months ago there was a sequence of posts to Hacker News about various “clubs” you could post your small website on: the 1MB Club, 512KB Club, 250KB Club, and even the 10KB Club. I think those are a fun indicator of renewed interested in minimalism, but I will say that raw size isn’t enough – a 2KB site with no real content isn’t much good, and a page with 512KB of very slow JavaScript is worse than a snappy site with 4MB of well-chosen images.
...[Instead, it's about] an “ethos of small”. It’s caring about the users of your site: that your pages download fast, are easy to read, have interesting content, and don’t load scads of JavaScript for Google or Facebook’s trackers.