Tutorials Taught You Everything Except How to Use Grasshopper

Experience > Tutorials

There’s this satisfying feeling that happens after you finish a tutorial or a lesson in a course.

You know what I mean. You’ve watched the whole thing, maybe you’ve followed along, maybe you even took some notes. After that, you’ve definitely mastered “data-trees for Grasshopper”.

So, why is it that when you open up Grasshopper on your own, the only thing you can do is stare? You should have mastered this, you watched the tutorial. You even took notes. But all you have are more questions.

What components do you use ?
How do you even start, a point ? a curve ?
Where’s the list to graft ?

If any of that sounds familiar, it’s because it’s the classic “I don’t know how to apply what I’ve just learnt to the real world” problem. That’s why even after 4 years of going to Unviersity, most people will still treat graduates as “starry eyed fledglings”.

I have written about this a couple of times now. One piece was about why I would learn Grasshopper differently if I started over. Another, was about the moment the tool finally made sense to me. And this one was about why learning through tutorials only won’t get you very far. I even made a LinkedIn post about it.

The TLDR of all of them is that tutorials and online courses teach you what the components do and where they are. But they don’t teach you how to use them to solve real world problems. That part only comes from getting more experience.

The responses I got from those pieces told me that a lot of people understand this. They have done the tutorials. Understand the material in the moment. And then nothing transfers to their jobs. They can take every “masterclass” under the sun and still feel like they are starting from scratch every time they open Grasshopper.

Context is key when learning

I got lucky because my job at the time gave me context while I was learning Grasshopper for the first time. I had a real task with real deadlines and a real manager to hold me accountable. He was also a manager that would occasionally pull up a chair when I was completely lost and say, here, think about it like this.

He gave me direction, so that I wasn’t completely lost. He gave me some breadcrumbs to follow. But I still had to find my way there. It was still up to me to learn the right techniques to solve the problem.

I did end up learning the fundamentals of Grasshopper though. But not because a course told me to, because it was the only way I was going to solve my problem. I had to learn about data-trees because my situation demanded it. I wanted my scripts to work well and for that, the fundamentals are important. But doing it for the sake of doing it is how you get so bored that you rather run into a wall.

Learning in context is different to your regular online course or tutorial. Because it means you have to intentionally get lost and find your way back on your own. Which can be an extremely uncomfortable feeling, especially if you’re paying for a course to be reassured you’re on the “right” path. It’s weird to say “I am buying this course to feel lost and find my way back”. It’s much easier to buy a course that spoon feeds you problems and answers.

But all you’re doing is accumulating carnival cash. It feels great in the moment but means nothing in the real world.

The part that is hard to replicate

The problem is that most people learning Grasshopper today don’t have access to their own problems. They have jobs, but Grasshopper is not central to them yet. Or they are students, or they are trying to upskill before a role that needs it. They can’t find their own context to make the learning stick.

Telling you to find your own problems doesn’t help if you don’t know what can be done. It also doesn’t help if it’s too overwhelming to go through it on your own. I even made a course on how to find your own problems but it still doesn’t help if you are very new at this.

So, I have been trying to figure out how to give someone that project experience if they don’t have one? How do I structure a problem in a way that is not too overwhelming, that challenges you and still gives you enough direction?

The inspiration of modelling challenges

That is what I am trying to build here. A series of modelling challenges that give you that context for learning and forces you to come up with your own workflows.

Okay, why modelling?

For starters, I think it’s the most common use case for Grasshopper. I also think it teaches you the most about how the tool works. From there on, if you wanted to branch off to urban analysis or optimization, it’s not a huge leap anymore.

I know how overwhelming that all sounds. But the point here is to challenge yourself to come up with your own way of solving problems. That’s how you build that instinct.

So, if you’re interested in getting some reps in for Grasshopper or you want hone your skills, I encourage you to join me.

We are going to start with a model brief which is basically summary of what you are going to start modelling. In the brief, you’ll have reference images, how I would model it and also what to look out for. Then, you just have to start.

But I did say that to learn effectively, you also need direction. Which is why after you’ve tried or if you’re feeling extra stuck, I’ll be publishing a modelling guide too. It’s basically my “answer” to the brief.

It’s not like I am giving you a problem and then leaving you alone. I am going to solve it too and show you how I did it. Mostly for you to reference and compare against your method. The key here though is that you have to try and solve it on your own first.

P.S. if you’ve never opened Grasshopper before, I’d suggest going through my primer in Grasshopper first to get up to speed on the basics. It’s only six lessons and it gets you to the point where you can read a script and know what you are looking at. Start there and come back.

What we are working through

Starting tomorrow, I am introducing the first building we are going to look at: Frank Gehry’s Winton Guest House, completed in 1987. It’s six distinct structures, each with its own geometry.

I chose it deliberately because it is complex enough to be challenging. But it also has a quality that I think makes it a good teaching vehicle, there is a clear logic to the order of things. Each part of the building follows what came before it.

The brief will walk through what the building is, how I see the building in terms of “plan of attack” and how to approach modelling it. Think of it like a mentor giving you a task and some direction and your job is to use Grasshopper to solve it.

From then on, there will be four parts to the guide, published every Tuesday for next few weeks. Each guide also comes with a script, so you can see how the solution progresses along with my thinking. And they are all available for paid members of CodedShapes.

If you are on the fence about subscribing, this might be a good chance. You can always subscribe to learn from it and then quit after you got what you needed, no hard feelings at all. The pool of resources will always be here.

Closing thoughts

Learning in context is one of the most effective ways I’ve found to learn. After going through it, it’s hard to imagine ever sitting in a classroom or a tutorial learning for no reason. With anything that I am trying to learn (Grasshopper or not), I always anchor it to a problem/project.

This though, is a much harder way of learning and the effort you need is a lot higher than just kicking back and watching tutorials. Just be mindful of that. But that is the point of all of this. I don’t want you to memorize things for the sake of it, I want to give you a reason and some meaning to it.

Thanks for reading
Subscribe to CodedShapes and I’ll send you my free guide on how to actually apply computational design to your projects.