Grasshopper: Designing Rules, Not Shapes

A different way of thinking than ordinary modelling

In ordinary modelling you draw the final shape directly. In Grasshopper you compose a sequence of steps, take this curve, divide it into ten points, draw a line at each, rotate by some angle, and the shape emerges as the result. Change one number at the start and the whole form updates automatically.

That power shows clearly in repeating patterns with variation: hundreds of façade panels each slightly different in size, or a structure whose form needs testing across dozens of options before one is chosen. A definition built once can be reused on the next project with different parameters.

When direct modelling is better

If the shape is made once and will never be revised, drawing directly in Rhino is far faster than building a Grasshopper definition for a single output. If the form is organic and guided by feel rather than a rule you can formalise, digital sculpting works more freely. And if your team needs to hand-edit the final result in fine detail, Grasshopper's output sometimes needs baking into ordinary geometry first.

The workflow for building a definition

A tidy definition from the start is far easier to change later, and it almost always will change, since that is the point of using Grasshopper.

1. 1Decide which parameters you want to vary first. If nothing needs varying, you do not need Grasshopper for this job.
2. 2Sketch the logic on paper before building nodes. Definitions built by trial and error tend to end up tangled and untraceable.
3. 3Build incrementally and check results at each step, rather than wiring many nodes and only checking at the end.
4. 4Name important parameters and node groups. An unnamed definition becomes hard to follow even for you, a month later.
5. 5Test extreme values for each parameter, the smallest and largest sensible numbers. Definitions usually break at the edges, not in the middle.
6. 6Tidy up before handing off: group related nodes, annotate unclear parts, and remove components no longer in use.

What makes a definition hard to change

These four most often turn a Grasshopper definition into a burden rather than a tool:

• Numbers typed directly into nodes instead of through parameters. Once something needs changing, each number must be hunted down individually.
• Relying on computation order without clear data structure. A misunderstood data tree is the most common source of confusion.
• No performance plan for complex models. A definition that runs smoothly with five elements can freeze a computer with five thousand.
• Leaving the definition messy for "tidying up later". Later rarely comes, and a messy definition is hard to hand to anyone else.