
Specific design tactics for developers: spacing, type, colour and shadows.
Where most design books stay in the abstract, this one opens with specific visual decisions: spacing scales, type hierarchies, color palette construction, shadow systems. Written by developers who taught themselves visual design, it's unusually practical and works equally well for product designers who want stronger visual intuition.
Wathan and Schoger wrote this for developers who need to design interfaces and have no design training. It is organised as a set of specific, applicable tactics rather than as design theory, with before-and-after examples for each.
The substantive advice covers hierarchy, spacing, typography, colour, depth and imagery. On hierarchy they argue that most amateur interfaces fail because everything has the same visual weight, and they give concrete methods: use font weight and colour rather than size to create distinction, de-emphasise supporting text rather than emphasising primary text, and label content only when the label carries information. On layout they argue for starting with too much white space and removing it, for sizing elements by content rather than filling the available width, and for designing the mobile layout in a desktop-width window to avoid cramped thinking. On colour they set out how to build a palette using HSL, why lightness must be varied along with hue, and how to generate the eight to ten shades of each colour a real interface needs. On typography they cover choosing typefaces, line length, line height and the specific problem of vertical alignment.
The book is compact, entirely practical, and it produces visible improvement quickly, which is why it circulates among founders building their own products. It teaches tactics rather than design judgement, so it will not make a reader a designer. Its aesthetic is specific to the mid-2010s web application style, and interfaces built strictly by its rules look similar to each other. It also predates the current design systems and component library practice, though the underlying principles about hierarchy and spacing are not affected.
Founders and developers who build product interfaces without a designer and need immediately applicable tactics.
Chosen by shared topics, the entries that hold them, and the people who recommended both.
Web usability: why every page should be self-evident and how to test that it is.
“The classic book of web usability. Required reading for anyone who makes websites.” — Derek Sivers
Source: Derek Sivers book notes (primary, rated list) · Rating: 7/10
Recommended by: Brian Armstrong, Derek Sivers, Jeff Atwood and 8 others
A four-step model for habit-forming products: trigger, action, reward, investment.
Recommended by: David Cancel, Nat Eliason, Nir Eyal and 6 others
A five-day process for answering a business question by prototyping and testing.
Recommended by: Andy Budd, Jessica Hische, Marty Cagan and 1 other
Why objects confuse people, and how affordances, signifiers and feedback fix them.
“Designing software is difficult, to be sure, but designing a door is difficult too.” — Jeff Atwood
Source: Recommended Reading for Developers — Coding Horror
Recommended by: Andrew Chen, Jeff Atwood, Ran Segall and 10 others
Research on how people see, remember, decide and feel, applied to design.
Recommended by: Jan Losert, Johnnie Gomez, Nir Eyal
Goal-directed design and personas: fitting software to how users think it works.
Recommended by: Jeff Atwood, Patrick Collison