What do you do when managing context takes longer than doing everything by hand? For example, for an existing project where reading a Jira ticket may not suffice and you need to examine unbounded amount of something else, which is usually kept in developer head? Do you begin to treat that as new kind of code/documentation debt that only matters with these new tools who are always amnesiac? How much do MDs really scale?
I’d tweak it to say that a foolish consistency is the absolute worst design principle. All things being equal, consistency is a good thing, but it sometimes gets prioritized to the point of absurdity and becomes counterproductive.
I think the core issue here is that consistency bounds are arbitrary and some people tend to push to much on these. Finding the middle is hard and is political. Arguing with UX or QA whether previously unrelated features on different screens should behave the same is exhausting. That's why I prefer small projects where I am the only customer or all users are extremely aligned (internal developer tooling).
It definitely isn’t. It’s good in many contexts, but zealous adherence to some pithy design principle without consideration is bad engineering and bad design.
yeah, but somehow consistency was not a concern when picking icons for menu items. as pointed out by some previous discussions on this matter.
i also hate this "consistency" idea. was working on mobile app for android/ios. and a requirement was for apps to look identical on both platforms. whyyyyy. sure for designer it looks nice, but as a user who uses either ios OR android im used to conventions of particular platform. why throw that all away just to look identical an both platforms.
Phones are just an easy target. Dumb phones still have address books, these are social networks too that can be exploited. In fact, that's how Chechnya prosecutes and kills unwanted people, like gays or regime opponents - by unraveling phone contacts.
reply