Guidelines for Brutalist Web Design An Article by David Bryant Copeland brutalist-web.design Content is readable on all reasonable screens and devices. Only hyperlinks and buttons respond to clicks. Hyperlinks are underlined and buttons look like buttons. The back button works as expected. View content by scrolling. Decoration when needed and no unrelated content. Performance is a feature. What On Earth is a Brutalist Website?The split personality of brutalist web development brutalismwwwhtml
A grossly obese set of requirements Who advocates in the requirements process for the product itself—its conceptual integrity, its efficiency, its economy, it’s robustness? Often, no one. As often, an architect or engineer who can offer only opinion based on taste and instinct, unbuttressed as yet by facts. For in a classical Waterfall Model product process, requirements are set before design is begun. The result, of course, is a grossly obese set of requirements, the union of many wish lists, assembled without constraints. Usually, the list is neither prioritized nor weighted. The social forces in the committee forbid the painful conflicts occasioned by even weighting, much less prioritizing. Frederick P. Brooks, Jr., The Design of Design Requirements proliferationA Plea for Lean Software features