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.
During the 1960s and 1970s, light became the primary medium for a loosely affiliated group of artists working in Greater Los Angeles who were more intrigued by questions of perception than by the notion of crafting discrete objects.
...Often with modest means (a bolt of scrim, a sheet of glass, a bucket of resin, an open window) these artists engaged in a kind of aesthetic palate cleansing, shaking off the art-historical weight and heavy impasto of midcentury painting as it had been influentially practiced in New York and San Francisco.
This is not a catalogue because there is no list of works. The exhibition will comprise three spaces in which three artists will have made their art. At the moment of writing we are not sure exactly what they will do—and we cannot know how what they do will appear to us. Therefore we cannot attempt to help you perceive it. So this is also not truly an introduction to the art. It is not intended to be read until you have seen the exhibition.
In between these two extremes is a room with three constructions by Robert Irwin. These can be read as individual works of art but their function here is primarily that of creating a climate of fastidious ambiguity. Light turns into a new kind of material; new kinds of material are fused into light; a vaporous middle-world stands midway between total black (Bell) and total white (Wheeler)