~/talk

How developers can upgrade their visual design skills for better front end development

slides:none on file

Argues that developers gain real value by learning concrete visual rules and tools: use a modular scale for headline/body relationships, set line-height ≈1.5 and 45–75 chars per line (35–55 for narrow columns), attend microtypography and spacing for readability. Recommend tangible tooling and checks: open Sketch files, review in InVision and export assets with Zeplin, measure contrast ratios aiming for 4.5:1. Gives small UI swaps that work (toggle instead of two-item dropdown) and cites serial position, proximity, and Zeigarnik effects.

AI-written summary · about

  1. 0:00Intro
  2. 0:25Why am I here
  3. 2:43Help each other
  4. 2:54Why is it important
  5. 3:55Typography
  6. 5:04Spacing
  7. 6:07Line height
  8. 6:41Micro typography
  9. 7:10Visual hierarchy
  10. 7:41Keep it simple
  11. 8:44Good practice
  12. 9:24Tools
  13. 10:52Contrast
  14. 12:53Serial Position Effect
  15. 14:20Proximity
  16. 15:25Giant Effect
  17. 16:28Practical Case
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.