In this video, I explain how Evaluate Curve works and why it gives you more control than simply dividing a curve. Divide Curve is useful when you want equal points. But when you want to control where points land, create uneven spacing, or use logic like Graph Mapper or Fibonacci sequences, Evaluate Curve becomes much more flexible. The main idea is simple: - Curves can be read through parameters - Reparameterize helps remap the curve between 0 and 1 - Evaluate Curve lets you place points with more control - Graph Mapper can create uneven point spacing - Fibonacci values can create gradual spacing changes Watch here Book a strategy call

In this video, I show how one curve and one basic rule can help you explore different design options quickly. The example starts with a product-like form, then shifts into an architectural pavilion idea. The main idea is simple: - Grasshopper can support quick design exploration - A simple curve can generate many options - The revolution axis changes the result - The domain controls how much of the form is created Watch here Book a strategy call

Before Watching The Video, Answer This in the Poll: What Makes Facade Panels Harder In Grasshopper? Then: - Watch The Video - Try The Attached Exercise - Build One Panel With More Architectural Detail - Come Back And Share What Made The Biggest Difference In this video, I Talk About: - Why Panel Workflows Get Heavy Very Fast - Why Facade Detailing Is Harder Than Simple Paneling - How I Use SkinDesigner To Simplify That Step - How One Panel Can Become A More Usable Facade Component - Watch Here Book A Strategy Call

Most architects trying to learn computational design are watching video tutorials on repeat. The problem with this is you follow along, finish the video, and then forget everything the next day. You never actually learn how to think in Grasshopper. You just know how to copy what someone else did. This leads to feeling behind, losing confidence in your technical skills, and watching less experienced architects get the jobs and promotions you wanted. After selling 500+ courses and helping architects build real portfolio projects with computational design, here's what I'd do instead: Learn by solving, not watching. Build real projects from scratch, get feedback on your work, and tie every lesson to something you can actually put in your portfolio. This is because when you build something yourself and get it reviewed, it sticks. You understand the logic, not just the steps. Which leads to having portfolio work that makes employers notice you, the confidence to say you actually know Grasshopper, and a real shot at a better job or promotion. You can think about it like this: Do you want to keep watching tutorials and forgetting everything the next day? Or would you prefer to build real projects and use them to land a better job?

Working on an exciting project that will help so many architects land a better job or get a promotion by learning computational design. Anyone excited?