As a designer, learn writing HTML, or better still, semantic HTML. If coding up the entire design is too hard, try coding up one component at a time, and not worrying about CSS. The HTML alone will prove invaluable for developers to understand the content structure. In addition, you are forced to optimize the information architecture as you work out the code from content.
If coding by yourself is out of the question, pair up with the engineer who will receive the design. Work closely with him or her to prototype the design, validate responsive behaviors, and obtain feedback on the feasibility. Don’t call it an iteration until the design has seen played with in code.
As a manager for large enterprise, co-locate your designers and developers, encourage interdisciplinary learning, understand that each minute spent on coding before the handoff translates to ten minutes saved from changing and fixing issues after the handoff.
As a stakeholder in the handoff meeting, give the designer a thumbs-up when he or she demos live code running in browsers in place of mockups on artboards. That’s a design champion you are looking at.
I’m sure y’all find these things just as useful as I do. They don’t make us lazy, they make us efficient. I know how to make a pattern. I know how to draw a curve with a Pen Tool. I know how to convert SVG into JSX. But using a dedicated tool makes me faster and better at it. And sometimes I don’t know how to do those things, but that doesn’t mean I can’t take advantage. Fake it ’til you make it, right?
I decided to make a truly naked, brutalist html page, that is itself a quine. And this page is it.
Viewing the source of this page should reveal a page identical to the page you are now seeing. Nothing is hidden. It's a true "What you see is what you get."
On one side, an army of developers whose interests, responsibilities, and skill sets are heavily revolved around JavaScript.
On the other, an army of developers whose interests, responsibilities, and skill sets are focused on other areas of the front end, like HTML, CSS, design, interaction, patterns, accessibility, etc.
On the Situations and Names of the Winds is the title of a fragment of a pseudo-Aristotelian treatise, most likely written by a later author of the Peripatetic school. The two-page work identifies and briefly describes the names not just of the four anemoi, but gives a wind-name to each of the twelve points of the so-called “wind-rose”, slightly less poetically the “compass rose”, which is the figure seen on classical nautical charts and maps that shows the cardinal points as well as points intermediate.
...In both agricultural and maritime settings, the names of the winds were at once practical and phenomenologically basic: to step outside and to feel them was to know how things were in the most basic sense, to “know which way the wind is blowing”, as we still vestigially say, and to find the language to speak of it.
...If I were ever permitted to teach a course on the philosophy of wind, I would begin with the questions: How did the winds lose their names? And what does it mean for us to live in a world of nameless winds? I step outside and I feel a gust. “That’s wind,” I think to myself, and I have nothing more to add beyond that. I don’t know the winds.