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
Clues for software design in how we sketch maps of cities An Article by Matt Webb interconnected.org Given there’s an explosion in software to accrete and organise knowledge, is the page model really the best approach? Perhaps the building blocks shouldn’t be pages or blocks, but neighbourhoods roads rooms and doors landmarks. Or rather, as a knowledge base or wiki develops, it should - just like a real city - encourage its users to gravitate towards these different fundamental elements. A page that starts to function a little bit like a road should transform into a slick navigation element, available on all its linked pages. A page which is functioning like a landmark should start being visible from two hops away. The Image of the City urbanismcitiessoftwareunderstanding