My Grasshopper Diary

I recommend you to do the same

Hello, I´m Isma 👋 

When I started learning Grasshopper, more than 10 years ago, I began with something I called my “Grasshopper Diary.”

It was just a regular notebook where I used to print and paste my Grasshopper scripts.

Every time I learned something new, I’d print out the script, glue it into the notebook, and write a short explanation of what each component did.

Little blocks. Simple snippets of code.

Then, whenever I needed to do something, instead of searching online and wasting time, I’d just flip through my notebook and follow the logic I had already documented.

These days, I don’t need it as much—I can do most things by heart.

But if you're just starting out, or at an intermediate level in Grasshopper: you should definitely do this.

Eventually, my Grasshopper Diary evolved.

As I got better at coding, I started using GitHub.

I created a GitHub repository to upload my sample Grasshopper scripts, each with a short description, instead of printing and pasting them in a notebook.

I also began adding Python and C# code, so a digital repository made much more sense.

(Quick sidenote: GitHub is a free, cloud-based platform for managing code projects.)

Even now, I keep adding code snippets to it.

I no longer use the physical Grasshopper Diary, but I still use the GitHub repository.

Now, with the rise of AI, my old Grasshopper Diary, which has evolved into a GitHub repository, has started to evolve once again.

Want to know what’s next?

Reply

or to participate.