flâneur — a map of the web's best reading

The Case for Design Engineers - Jim Nielsen’s Blog

blog.jim-nielsen.com · 489 words · saved by 1 readers

Controls the level of style and functionality of the site, a lower fidelity meaning less bandwidth, battery, and CPU usage. Learn more. If I had to put myself into one of the buckets that constitute job titles, “Design Engineer” might be closest to my own sense of self-identification. That or just plain old “Web Designer”—there’s just so many jobs when it comes to building software. Anyhow, I recently read “Traditional Web Design Process is Fundamentally Broken” by Jason Grigsby and it resonated with me so much! For responsive design, there are Too. Many. Artifacts. You’ve got sketches and wireframes and mockups and prototypes. And for each of those you need at least three variations: “desktop”, “tablet” and “mobile” (whatever those mean). As the article suggests, you could be looking at up to 60 artifacts per design iteration. It’s ludicrous. Worse, the designs are misleading. There is no one size for mobile, tablet, or desktop. Current generati

If I had to put myself into one of the buckets that constitute job titles, “Design Engineer” might be closest to my own sense of self-identification. That or just plain old “Web Designer”—there’s just so many jobs when it comes to building software. Anyhow, I recently read “Traditional Web Design Process is Fundamentally Broken” by Jason Grigsby and it resonated with me so much ! For responsive design, there are Too. Many. Artifacts. You’ve got sketches and wireframes and mockups and prototypes. And for each of those you need at least three variations: “desktop”, “tablet” and “mobile” (whateve

Explore this link on the map →

related reading