Working with Brian Eno on design principles for streets An Article by Dan Hill & Brian Eno medium.com Think like a gardener, not an architect: design beginnings, not endings Unfinished = fertile Artists are to cities what worms are to soil. A city’s waste should be on public display. Make places that are easy for people to change and adapt (wood and plaster, as opposed to steel and concrete.) Places which accommodate the very young and the very old are loved by everybody else too. Low rent = high life Make places for people to look at each other, to show off to each other. Shared public space is the crucible of community. A really smart city is the one that harnesses the intelligence and creativity of its inhabitants. collectionsurbanismstreetscitieswastegardens
The answer to a brief is not necessarily a building An Article by Dan Hill medium.com This brilliantly engaging book may actually be one of the first to describe and discuss what might be architecture’s true value at this pivotal point in our own history: seeing that everything is connected, and artfully hosting that complexity, before constructively plotting routes towards clarity, pinned up on broad civic, ethical foundations. So Architects after Architecture, as the title suggests, is not about buildings. Or at least not always, not directly. Buildings are simply one of the ways that this complex yet constructive sensibility might exert itself, but they are certainly not the only way, nor are they always the most potent – as muf’s Liza Fior makes clear here, when she says “the answer to a brief is not necessarily a building.” The Best Interface is No Interface architectureconnection
Agile is Dead (Long Live Agility) An Article by Dave Thomas pragdave.me The word “agile” has been subverted to the point where it is effectively meaningless, and what passes for an agile community seems to be largely an arena for consultants and vendors to hawk services and products. …Let’s abandon the word agile to the people who don’t do things. Instead, let’s use a word that describes what we do. Let’s develop with agility. You aren’t an agile programmer—you’re a programmer who programs with agility. You don’t work on an agile team—your team exhibits agility. You don’t use agile tools—you use tools that enhance your agility. / Individuals and Interactions over Processes and Tools Working Software over Comprehensive Documentation Customer Collaboration over Contract Negotiation, and Responding to Change over Following a Plan agile