engineering
Live your ten years
I'm sorry, I love engineers
Strength from both mass and form
Warmed by the afternoon sun
Textbooks on water-system engineering state that supply mains are generally installed on the north side of the street in the Northern Hemisphere and on the south side in the Southern Hemisphere, so that the sun will warm them. In both hemispheres they are supposed to be on the east side of north-south streets, on the premise that the afternoon sun is warmer than the morning sun.
An emblem of friendship
Bridges make connections; they bring people together—a role that has made them a traditional emblem of friendship. Consider the town of Mostar in Bosnia-Herzegovina. When fighting between ethnic factions broke out there in the 1990s, nothing symbolized the social disintegration more clearly than the destruction of a sixteenth-century stone-arch bridge that had linked the two parts of the town on opposite banks of the Neretva River. And the emblem of efforts to heal the divisions is a rebuilt bridge, opened with fireworks and fanfare in July of 2004.
Routine design
When we think of bridges, it is the dramatic and monumental long spans that come to mind first, especially the lithe suspension bridges such as the Golden Gate and the pure geometric arches such as Sydney Harbour. But the majority of bridges are not such spectacular structures. Most of them are ordinary overpasses, with spans of 30 or 40 feet, carrying roadways or rails across other thoroughfares or over small streams. You see such bridges by the dozen on any drive down the Interstate. They may be lacking in glamour, but they are more representative of a bridge builder's art.
The engineering and construction of girder bridges are pretty routine these days, but the bridges are not quite standard items you order from a catalogue. The girders, whether of steel or concrete, are custom-build for each bridge, then trucked to the site and hoisted into place with a crane. The designer still has scope for variation and creativity, and it shows out on the highways: some overpasses are prettier than others.
The Art of Doing Science and Engineering: Learning to Learn
A Book by Richard HammingThe Art of Doing Science and Engineering is the full expression of what "You and Your Research" outlined. It's a book about thinking; more specifically, a style of thinking by which great ideas are conceived.
Design Links & Learning
A Blog by Nick TrombleyCollections of articles, links, and other material from around the web, relevant to software design and engineering.
“Design” is now “Product”
An Article by Dorian TaylorDesign has very little to do with what tools or methodologies you use, or what your job title is, or what you have a degree in, or even anything like “creativity”; design is about your relationship to constraints. Rather: to what extent are you defining constraints rather than just obeying them? Design is about taking a universe of possibilities and converging onto exactly one outcome. Being handed a set of constraints which you treat like immutable laws of physics (because many of them are) and solving within that envelope is what engineering is. To wit: what most designers are doing most of the time is actually a form of engineering, and engineers are always doing at least some design.
This is because genuine design—the power to define constraints—is a privileged political position within an organization, and not everybody can occupy it. In other words, the “seat at the table” comes first. Design is Steve Jobs infamously dropping an iPod prototype into his fish tank, pointing at the bubbles coming out and yelling at his staff to make it thinner. It doesn’t matter what your title is; Jobs is the designer in that scenario.
Are We Really Engineers?
An Essay by Hillel WayneInnovation in Structural Art
A Book by Eladio DiesteDieste's unique and innovative method of design, a melding of architecture and engineering, elevated these often humble buildings to masterworks of art.
Beyond Artboards
The Pursuit of Lossless Design-Development Handoffs.
Can't developers just see?
We designers love artboards. From rough UI sketches to high fidelity mockups, we see ourselves as visual artists expressing ideas on artboards that have a pre-defined width and height. To start a new project, we declare the size of the artboard in the first step.
What about responsive design? Not a problem! We diligently design on three artboards — one for mobile, one for tablet, and one for desktop — with content elegantly adapting, scaling, reflowing, reordering, and reprioritizing. We proudly hand off the artboards to developers while patting ourselves on the back: this is how responsive design should be done.
After weeks of arduous engineering, the product finally comes out. We find, to our great dismay, that some copy is hanging off the grid, the focal point of the hero image has been cropped out, the font sizes don’t even come close to the type ramp. What went wrong? Can’t the developers just see everything on all those artboards?
Nope.
We are the ones who paved the path
No matter how many screen sizes our artboards account for, some user’s browser will break loose from our prescription. With users resizing, rotating, and zooming the screen, new devices stretching, squashing, curving, and cutting (e.g. the speaker area in iPhone X) the screen, the sizes become infinite. Good luck making an artboard for each one of them.
Artboards are a lossy format. Using artboards in a handoff is a lossy process. When we pitch a finite number of plans against an infinite number of situations. We inevitably get in-betweens. Once there are in-betweens, there are unknowns. Once there are unknowns there is guesswork. Once there is guesswork, there are surprises. Engineers take the path of least resistance. We are ones who paved the path.
Until we get there
- 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.