Changing Our Development Mindset A Fragment by Michelle Barker www.smashingmagazine.com We simply can no longer design and develop only for “optimal” content or browsing conditions. Instead, we must embrace the inherent flexibility and unpredictability of the web, and build resilient components. Static mockups cannot cater to every scenario, so many design decisions fall to developers at build time. Like it or not, if you’re a UI developer, you are a designer — even if you don’t consider yourself one! ...Sometimes interpreting a design means asking the designer to further elaborate on their ideas (or even re-evaluate them). Other times, it means making design decisions on the fly or making recommendations based on our knowledge and experience. gridless.designWe are the ones who paved the pathEmbracing Asymmetrical Design interfacescssdesign
It passes by the river "Artists need to be in there from the start, making the argument for quality. The key to this thing is, for example, if you give an engineer a set of criteria which does not include a quality quotient, as it were—that is, if this sense of the quality, the character of the place, is not a part of his original motivation—he will then basically put the road straight down the middle. He has no reason to curve it. But if I can convince him that quality is absolutely a worthwhile thing and we can work out a way in which the road can be efficient and also wander down by the river, then we essentially have both: he provides his sort of expertise in that the road works, I provide quality in that it passes by the river. In that way, art gets built into the criteria from the beginning rather than being added on afterward." Lawrence Wechler & Robert Irwin, Seeing Is Forgetting the Name of the Thing One Sees We want you to work with an artistThe problem with ornament qualitydesignfunctioncollaboration