Why Do All Websites Look the Same? An Article by Boris Müller modus.medium.com On the visual weariness of the web. The Great Blight of DullnessWhat On Earth is a Brutalist Website?All Social Networks Look The Same NowAll websites are just digital movie theaters now wwwboredominterfaces
Menus, Metaphors and Materials: Milestones of User Interface Design An Article by Boris Müller medium.com Students traditionally learn art and design by studying the masters, analyzing, sketching and interpreting the grand visions of the past. In doing this, they get to understand the ideas, concepts and motivations behind the visual form. In user interface design, this practice is curiously absent. Interface design is ephemeralXerox StarMagic CapInformation LandscapesBeOS Icons+1 More The Mother of All DemosEssential vs. nice to haveMetaphors We Web By interfaceswwwhistorylearning
In Defence of Intuition An Essay by Boris Müller borism.medium.com Design, it seems, is not only becoming more methodical but also more scientific. This is not surprising. Design as a discipline has moved from “product beautification” to being a central part of product development. It has incorporated methodologies from human-computer interaction, sociology, and anthropology as well as advertising and management. And with the rise of design thinking, a wider range of professional disciplines are using creative methods. I don’t want to criticize design methodologies. But against the backdrop of an overly structured design process, it is important to remind our community that there is one fundamental aspect to design that cannot be formalized in a methodology. And that is intuition. We feel it in our fingers designintuitionprocess
Why we stopped breaking down stories into tasks An Article by Adam Silver adamsilver.io The Scrum process says to break down stories into tasks to make estimation easier, encourage collaboration and to be able to show more granular progress during a sprint. But after a few sprints, we decided to do the next sprint without creating tasks. As a result we drastically increased our velocity and never went back. Here I'll jot down some of the reasons we decided to do this: Breaking down stories into tasks is time consuming The tasks we came up with invariably would change as we worked on the stories Tasks are repetitive Tasks were often carried out in parallel Our estimates didn't improve It decluttered our task board It encouraged collaboration throughout the sprint While we started our process by following Scrum to the letter, we soon realised that breaking down stories into tasks was something that wasn’t worthwhile for us. In the end we realised that it was overplanning and poor use of our time. In the end we used that time to get on with the work and deliver at a significantly faster pace. Why We Don't Do Daily Stand-Ups at Supercede agile