Many of you are considering developing staggered grid systems for stacking your modules. I’ve put together a quick Grasshopper definition that does this — it’s posted under Workshop 6 files.
A must read –brief– article from the NYTimes that raises many of the questions we’ve approached in our class:
And a link to some design responses to the need to engage user thought, Experience Design:
And a –brief– paper on the Caterpillar cord and The Forget Me Not reading light:
From Marc Swackhamer:
1. Start with something concrete.
2. Overlay diagrammatic information.
3. Focus on the things we cannot see: cycles, time, movement, change over time, spatial characteristics/descriptors (fast, slow, thick, thin)
4. Pull out information you do not need (important to use layers). Use just enough contextual information so that the viewer can orient him/herself.
5. Minimize text / Minimize arrows.
6. White space is your friend.
7. Use color sparingly.
8. Don’t be afraid to invent notational systems or new ways to depict information.
9. Don’t confuse clarity and simplicity for simplistic — a good diagram can be rich, complex, and deep.
10. Do it again… and again…
Going in for DA help this evening made me realize that having been down the Grasshopper rabbit hole for three weeks it would be good to pull out a map and reconnoiter.
I had varyingly read and skimmed through the primer by Lift Architects before ever even opening Rhino/GH. Gotta say that going back to it now…well…now it makes a helluva-lot more sense.
Thought I’d post the link just as a little nudge (you’re probably not as lost as you think): http://www.liftarchitects.com/storage/research/Grasshopper%20Primer_Second%20Edition_090323.pdf