HN Books @HNBooksMonth

My favorite Eno essay, which also touches on similar themes, is "Composers as Gardeners".[1]

In the "Generative Music" essay, Eno mentions being influence John Cage. For a closer look at his thought, I highly recommend his book "Silence".[2]

[1] - https://www.edge.org/conversation/brian_eno-composers-as-gar...

[2] - https://www.amazon.com/Silence-Lectures-Writings-50th-Annive...

⬐ pdfernhout

You might also like "The Pragmatic Programmer: From Journeyman to Master" by Andrew Hunt and David Thomas. One of the ideas there is "Software Development as Gardening". From an interview with the authors (originally from here but it is no longer accessible easily: https://community.oracle.com/docs/DOC-982950 ):

    Bill Venners: In your book, The Pragmatic Programmer, you say, "Rather than construction, programming is more like gardening." I really like your gardening metaphor for software development. Can you elaborate on it?
    Andy Hunt: There is a persistent notion in a lot of literature that software development should be like engineering. First, an architect draws up some great plans. Then you get a flood of warm bodies to come in and fill the chairs, bang out all the code, and you're done. A lot of people still feel that way; I saw an interview in the last six months of a big outsourcing house in India where this was how they felt. They paint a picture of constructing software like buildings. The high talent architects do the design. The coders do the constructing. The tenants move in, and everyone lives happily ever after. We don't think that's very realistic. It doesn't work that way with software.
    We paint a different picture. Instead of that very neat and orderly procession, which doesn't happen even in the real world with buildings, software is much more like gardening. You do plan. You plan that you're going to make a plot this big. You're going to prepare the soil. You bring in a landscape person who says to put the big plants in the back and short ones in the front. You've got a great plan, a whole design.
    But when you plant the bulbs and the seeds, what happens? The garden doesn't quite come up the way you drew the picture. This plant gets a lot bigger than you thought it would. You've got to prune it. You've got to split it. You've got to move it around the garden. This big plant in the back died. You've got to dig it up and throw it into the compost pile. These colors ended up not looking like they did on the package. They don't look good next to each other. You've got to transplant this one over to the other side of the garden.
    Dave Thomas: Also, with a garden, there's a constant assumption of maintenance. Everybody says, I want a low-maintenance garden, but the reality is a garden is something that you're always interacting with to improve or even just keep the same. Although I know there's building maintenance, you typically don't change the shape of a building. It just sits there. We want people to view software as being far more organic, far more malleable, and something that you have to be prepared to interact with to improve all the time.

Anyway, interesting to me to see how the "gardening" theme can apply both to the design (and use) of software to make ambient music and also to the software development process itself.

True, "Silence" is actually a book: http://www.amazon.com/Silence-Lectures-Writings-Anniversary-...