Conversation

I've never had a dog or cat in the "should designers code" cage-fight. But it sure is useful when you're writing design specs in Figma to link to known techniques on how to implement things. Unsure how anyone could think in the medium of HTML/CSS/JS without building in it first

A figma layout of an article with an annotation on the side linking to a technique for how to implement images in layouts

A figma layout of a sidenote in an article with an annotation pointing to a way to implement the sidenotes with CSS

3:03 PM · Feb 7, 2022Twitter Web App

Replying to

@Mappletons

I think having that all-or-nothing debate in the abstract is next to meaningless too, but knowledge in both fields can inform each other and is def. an asset -- designers who code consider "implementability", coders who design aren't lost if smth. isn't 100% spec'd out, win-win

Replying to

Yes! Please! Thank you!

Replying to

Coders should design too. Cross over is good for everyone, but especially coders to design skills. A lack of basic sense makers coders bad documenters and prototypers

Replying to

Exactly! We design UIs in pixels(Figma) but the web is fluid. Someone has to translate between pixels to web, essentially design last ~5%. Not sure about any industries where you are not expected to know the medium we are building.

Replying to

save thread

First public save of this thread! 🏆 Readwise users: Like this reply to save Mappletons's thread to your account without cluttering their replies 📚 Stats: • 96 total saves of Mappletons's threads (ranked #464)

Replying to

For me, it simply comes down to personal experience. The best designers I've worked with could and did write HTML and CSS. That being said, it doesn't hurt for front-end devs to do some design work as well. The less space between these fields, the easier the handoff is.