A Practical Guide to Leveling Up Your Grasshopper Skills.

The core methodologies every computational designer needs to know: whether you just opened the software today, or you’ve been building scripts for years.

What changed Everything

I never thought I would be sharing my experience like this…

Before I started my career in architecture, I had my doubts. I actually wanted to study computer science. But at the time, architecture felt like the best decision… (😅). While studying, I discovered Grasshopper and learned that I could make design programmable.

I fell in love. ✅

I became obsessed. ✅

I just wanted to learn Grasshopper and get really good at it. ✅

During the first few years of my career, I used Grasshopper constantly: teaching myself, experimenting in my free time, and testing things on real projects.

I kept getting better and better.

Then, something happened.

I joined the Digital Design Team at Arup in Hong Kong. For the first time, I had a REAL mentor in Computational Design: Ramon. He was a director at Arup and had previously been working at Front, where he was involved in solving the facade for Zaha Hadid’s Morpheus Hotel in Macau.

From him, I learned their methodology: how the true pros use Grasshopper. It took me to a completely different level.

I’m sharing this because it might resonate with you. Because if you are the kind of person obsessed with parametric design, I know we are built from the same DNA.

The 5 Mistakes of the “Pretty Good” Computational Designer

There are a few major mistakes I was completely guilty of: and that I still see in many aspiring computational designers today.

❌ Error 1: The Ego Trap

Assuming you know best, usually because you haven’t yet worked with high-level Grasshopper pros or tested your skills on complex, real-world automation projects.

❌ Error 2: Skipping the Blueprint

Diving straight into problem-solving without analyzing or structuring the workflow first.

❌ Error 3: Building the “God Script.”

I would try to create one massive, overly complex script that was supposed to do everything, instead of logically modularizing the steps.

❌ Error 4: Spaghetti Code

Building chaotic, unreadable definitions filled with invisible wires and zero logical flow.

❌ Error 5: Fragile Workarounds

Building scripts that weren’t truly robust. They relied on quick, dirty patches and would instantly crash if the input deviated from the original plan.

What I Learned (The Turning Point)

✅Lesson 1: Mastering User Attributes (Elefront)

This was the biggest game-changer. Managing data through user attributes isn’t just a trick; it’s a methodology that scales to any parametric system and will instantly take you to the next level.

✅Lesson 2: Dynamic Variables & Naming Conventions.

Use dynamic variables and strict naming conventions for your inputs and outputs. It makes your logic readable for your team, and more importantly, for you. More order = more speed.

✅Lesson 3: Embrace Long Scripts.

Don’t be afraid of long scripts, and stop using invisible wires (that’s cheating!). Keeping your logic visible drastically improves readability.

✅Lesson 4: Think in Modules.

I learned to generate the necessary clusters, whether for reusable, everyday logic or highly specific tasks. Properly using clusters is exactly what allows multiple people to collaborate on the same scripts (which is mandatory for high-complexity workflows).

✅Lesson 5: Standardize Your Colors.

Using named and colored groups and comments changed everything. A consistent, standardized color-coding system helps you stay organized, makes scripts understandable quickly, and improves a lot collaboration within a firm or studio.

Let’s Talk About FOMO

Learning these lessons transformed my career.

I always wished for a space where I could learn the right way from the start, surrounded by people who were just as obsessed with computational design.

Since it didn’t exist, I’m building it.

I’m launching a private community for Computational Designers.

✅ No egos.

✅ No spaghetti code.

✅ No Sketchup.

Right now, the VIP waitlist is our private WhatsApp group. If you stay in the group, you will get early access to the official community.

I want to be totally transparent with you: the community will not be free. But for those of you joining now as founding members, the price will be so low it will literally feel like a joke.