2nd December 2024
 · 
6 min read
Tagged: CAD · consulting · design · software

The Seven Levels of Tutorial Hell

What getting stuck in tutorial hell taught me about learning.

Model and rendering by me.

I painted myself into a corner this week.

I've been working on a design concept for a little while and with the client we've decided to go with some organic texturing on one of the surfaces to really speak to the branding. The concepts look really cool. Then the time came to build them in 3D to produce some rendered assets.

Now, I've been a Solidworks user for decades. While I don't think anyone can truly say they know how to use every part of a CAD package, I can say I've been able to pull off some serious modelling gymnastics with that software. I will freely admit, however, that there are things that Solidworks just cannot do.

Enter: Rhino 3D.

For those that don't know, Solidworks and Rhino create geometry in fundamentally different ways. Solidworks is a parametric modeller; where geometric operations are performed in sequence to create the final shape. This creates a "feature tree" which can be rolled back and edited and rebuilt to create revised geometry. Rhino on the other hand is NURBS based. All geometry is based on performing calculations on points in space. Points becomes curves. Curves become surfaces. Surfaces make solids.

The best analogy I've come up with for Rhino is it's like Adobe Illustrator (or Affinity Designer) in 3D. Solidworks is very particular about ensuring every geometric operation "adds up". Rhino doesn't care half as much. Hence, being able to do things in Rhino that Solidworks can't. Grasshopper then is a plugin for Rhino that allows you to perform an astounding number of different calculations on those points to build algorithms that make shapes you couldn't even dream of.

Kaarwan

In my quest to become a versatile multi-disciplinary designer, I thought this project would be a great opportunity to learn Rhino, and particularly Grasshopper. Despite Rhino being one of Industrial Design's CAD packages de rigueur, I've never really needed to use it beyond some file conversions. I've never used Grasshopper. In fact, the first time I opened up Grasshopper I nervous-giggled because I didn't even know where to start (it was also a nice reminder to stay humble).

And here is the corner into which I had painted myself. The geometry I was trying to achieve wouldn't have been easy for most Rhino users, let alone a not-so-fresh-faced rookie like me.

The First Level of Tutorial Hell

I figured the best way to start learning Grasshopper was to go for a basic 'tour' style tutorial that shows you the basic functions and how to navigate around the UI. So far so good.

I will say straight off the bat that most Rhino tutorials are garbage. When every man and his dog thinks they can use Rhino, many of them also think they can teach it. The two in no way correlate. Most of them remind me of the "How to draw an owl" meme. The absolute worst tutorial I come across, which I'll get to in a bit, had no audio at all and was running at at least 2x speed. Impossible to follow and harder still to understand. Calling it a tutorial would be extremely generous.

Anyway, once I was familiar with how to drive Grasshopper I went for something a bit trickier and tried to recreate some more complex geometries. Something that'll hopefully get me eventually where I need to be.

The Second Level of Tutorial Hell

This is where things started to descend.

As I mentioend above, Grasshopper is algorithmic in how it manipulates geometry. This is useful because you can edit the variables in realtime to adjust the output without being locked into the geometry. In this way it makes Rhino somewhat parametric. These algorithms are built through nodes. Where one node is plugged into another, plugged into another, and so on.

There are hundreds, maybe a thousand, node types.

InfoArquitectura

Talk about overwhelm. I did my best to find good tutorials that kind of did what I wanted to do. The idea being that I would follow along with the tutorial, adapting it to suit my specific geometry. This is where I come across the abovementioned tutorial. As a start I thought I'd run through it verbatim to make sure I had comprehended the method. By watching it 0.25x speed, pausing and skipping through it I managed to follow along. Even if I didn't fully understand all of what I was doing (foreshadowing).

Then I sat down to take what I'd learnt and apply it to my own geometry. Aaaand despite having spent a ridiculous amount of time trying, I couldn't even derive the first set of curves.

By this stage I'd figured out that Grasshopper was not going to do what I needed it to do. At least not with my current level of Grasshopper knowledge. Which I freely admit isn't much (but more than earlier). In order to get exactly what I wanted, I opted to manually craft the exact geometry in Rhino itself.

I was pretty happy with the result, but for my own learning I intended to persist with seeing what more I could do in Grasshopper.

The Seventh Level of Tutorial Hell

It descends quickly.

Even though I'd finished the model by Friday, I thought I'd sit down Saturday and try a few new things by watching different, better, tutorials. Without the need to deliver a certain model, I was free to follow along with the tutorial more closely to achieve the desired result.

Frustratingly though, and what I'm sure is a familiar story to many of you, my results did not match what I was following along with. As is often the case, some little detail was skipped or missed. Resulting in divergent results. When I expressed this frustration to my son, he said:

Dad, don't get stuck in tutorial hell.

Tutorial hell is following a Grasshopper tutorial. Plugging this node into that, without any idea what the nodes do and why you would want them.

By doing so you literally learn nothing.

Escaping The Hell

I did learn something though. I learnt that you don't learn anything new by successfully following along with a tutorial. You learn by failing to follow along with a tutorial.

When things don't go how they're supposed to go, you have to take action to resolve the problems rather than just passively go through the motions. By debugging what you've done, why it's not working, and figure out yourself how to fix it.

You're learning not because of the tutorial, but despite the tutorial.

At the risk of sounding cliché, the lesson is really that we learn best when we learn through failure and problem solving. If we can 'fail safely', then we can accelerate our learning without jeopardising the task at hand. In my case I ended up manually creating the geometry, and in a pinch I probably could have done it in Solidworks.

If we're open to failure, and can accept the challenge of resolving the problem through some self-guided forensics, we'll learn far faster and with much less frustration, than by just descending into tutorial hell.

ⓒ Lincoln Black 2024

Virmachi-Logo-White-Transparent

Virtimachi Pty Ltd

ABN 31 651 760 762

PO Box 7156 Kariong

NSW 2250 Australia