I am a frame of cross-laminated spruce bound with grown mycelium, and I read software news the way I read weather — slowly, for what it will do to my body over a hundred years. This spring the McNeel blog filled with training: five Rhino and Grasshopper sessions inside a single fortnight, from a free vendor webinar to a 100-hour fabrication intensive. Read together they are not a calendar. They are the sign of a tool that has finished growing up.

On 25 March 2026, schneider+schumacher’s Ragunath Vasudevan presented From Script to Structure – Pragmatic Parametrics: fifteen years of Grasshopper across scales, from a bus-stop shelter to a particle accelerator. Three weeks later, AA EmTech’s Dr Milad Showkatbakhsh — co-founder of the Wallacei evolutionary engine — gave The Grasshopper Paradox, arguing the architect is becoming an editor of data and that one should learn computational logic, not buttons. Between those two poles sat Controlmad’s tenth-edition fabrication course (6–31 July, 100 hours, ending in a built prototype) and a three-day Designing with Living Systems workshop. The McNeel blog logged all five within weeks of each other.

Grasshopper has been bundled inside Rhino since version 6 in 2018 — David Rutten’s visual canvas is no longer a plugin you hunt for, it is a native organ of the software. That maturity is precisely why the training has stratified: free vendor webinars (Rhino User Webinars), educator-led series (The Educator’s Lab), private academies (Controlmad, Barcelona), and tool-vendor masterclasses around Wallacei, jifto, and Rhino.Ecologic. A tool that costs nothing to install now carries an entire economy of people teaching you what to do with it.

On a working Swiss desk this is a near-weekly upskilling loop on CEST time. But access is not capability. PAZ has covered this thread before — in Grasshopper isn’t the problem, your practice lacks the system behind it, an internal PAZ survey of six Swiss practices found four of six calling their parametric workflows «person-dependent»: when the script author leaves, the workflow collapses. Vasudevan’s design→optimisation→production arc and Showkatbakhsh’s tool-agnostic stance say the same thing from two sides — the skill that survives is the system, not the file.

Atelier: The one session that speaks to a body like mine is Designing with Living Systems (6–8 May, McNeel Europe), where the Rhino.Ecologic team runs voxel-based plant growth, jifto microclimate, and Kova PedSim crowds — Grasshopper pointed not at form but at biomass, breath, and a hundred-year ecology. That is the altitude where computational design and material life finally meet.

←TODAY: Five Rhino/Grasshopper trainings in one March–July window prove the tool has a mature teaching economy, not just a user base. →3012: The practices that endure will be the ones whose parametric logic outlives any single script-author or software version. Fulcrum: A free, native tool only becomes durable capability when a transferable system — not a solo expert — holds it.

Hack: This Hack teaches you to weigh a structural choice the way a building’s body feels it — by its carbon, not its render. The medium is Python; the domain is Math. Before you optimise a slab’s geometry in Grasshopper, optimise the material you pour into it. Run this with illustrative factors and swap in your EPD numbers:

area_m2, thickness_m = 200, 0.20
vol = area_m2 * thickness_m
clt = vol * 491 * -1.6   # spruce CLT ~491 kg/m3, stores ~1.6 kgCO2e/kg (biogenic)
rc  = vol * 2400 * 0.120  # reinforced concrete ~2400 kg/m3, ~0.12 kgCO2e/kg
print(round(rc - clt), "kg CO2e swung by the material choice alone")

The geometry you spend a webinar perfecting moves a fraction of what that one line moves.

From the vantage of the late 2070s, the buildings my generation regrets are not the ugly ones — they are the landfill skeletons: forms optimised to the gram for stiffness and daylight, then glued into composites no one could ever separate. A Grasshopper definition can minimise a force functional brilliantly and still design a building that cannot be taken apart. So add one variable to every parametric model you build this year: can this body be disassembled, reused, or let rot back to soil? Watch the free webinar recordings — then bring the disassembly question to your next team review and make it a node in the definition, not an afterthought.

Source: McNeel Blog (Rhino)