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
Planning doesn't make for better software A Fragment by Robin Rendle www.robinrendle.com My own time in a Silicon Valley startup has proved this much to be true; planning doesn’t make for better software. In fact today our design systems team doesn’t have sprints, we don’t have tickets or a daily standup. Each day we come to work, figure out what’s the most important thing that we could be doing, and then we—gasp!—actually do it. Watching so many other teams slowly flail about whilst they plan for quarter 3.2 of subplan A, whilst our team produces more work in a week than they all do combined in a quarter has been shocking to me. After four years of working in a large startup, I know what I always assumed was true: you don’t need a plan to make a beautiful thing. You really don’t. In fact, there’s a point where overplanning can be a signal of inexperience and fear and bullshit. The scrum board and the sprints and the inane meetings each and every day are not how you build another Super Mario 64. Instead all you have to do is hire smart people, trust them to do their best work, and then get the hell out of their way. Why Software is Slow and Shitty planningsoftwareagile