poetry
The past of his image upon me
Poetic drugs
The haiku
Japanese Death Poems
Silent Conversation
A few things that could be poetry
An Article by Wesley Aptekar-Cassels- The right combination of street signs, viewed from a artful vantage point
- Words on bit of packaging, torn to reveal and conceal as needed
- The output of a command line tool, perhaps unexpectedly
- Overheard words, drifting along, liberated from their initial context
- A form, at first appearing bureaucratic, revealing humanity on deeper reflection
- An idea, if you consider it divine enough
155-217-155
A Website by Nick TrombleyThe Gifted Listener: Composer Aaron Copland on Honing Your Talent for Listening to Music
An Article by Maria PopovaThe poetry of music, Copland intimates, is composed both by the musician, in the creation of music and its interpretation in performance, and by the listener, in the act of listening that is itself the work of reflective interpretation. This makes listening as much a creative act as composition and performance — not a passive receptivity to the object that is music, but an active practice that confers upon the object its meaning: an art to be mastered, a talent to be honed.
The way an oyster does
A Fragment by Kay RyanHer poems, [Kay Ryan] says, don't begin with a simple image or sound, but instead start "the way an oyster does, with an aggravation." An old saw may nudge her repeatedly, such as "It's always darkest before the dawn" or "Why did the chicken cross the road?"
"I think, 'What about those chickens?' " she says, "and I start an investigation of what that means. Poets rehabilitate clichés."
If we were allowed to visit
A Poetry CollectionIf We Were Allowed To Visit is an anthology of poems by Gemma Mahadeo rendered by Ian MacLarty.
As you move through the game's environment, the poems are rearranged into the shapes of the objects they're about, each frame becoming a new generative poem.
Haiku 2018–2019
A Poetry Collection by Katy DeCorahI found an old note that contained a project to write a haiku every day. My project started in December 2018 and ended promptly in January 2019. The themes included work, baking, and difficulty finding nice fabric.
Some Other Sign that People Do Not Totally Regret Life
An Episode from 99% Invisible by Roman Mars & Kurt Kohlstedt
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.