I used to work at a small architectural office. 9 to 6, boring drawings, overtime on weekends. It sucked because I questioned every day whether this was really what I wanted to do. I didn't have a strong portfolio. The gap between what I imagined architecture would be and what it actually was felt massive. I wanted freedom over my time and a stronger purpose in my work. But then I quit, built a stronger portfolio, applied for better opportunities, and started teaching computational design to other architects. (I also lost my hair somewhere in that transition, so not everything improved, but my career definitely did😅) Which led me to switching between academia and industry on my own terms, helping 500+ architects learn Grasshopper 3D, and doing work I actually care about. Want to know how I did it? Comment YES and I'll send you the details.

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?

I used to work in a small architecture office doing boring drafting work every day. It sucked because I didn’t have a strong portfolio, I felt stuck, and I kept asking myself if this was really the career I wanted. But then computational design and a stronger portfolio changed my path. That shift led me to better opportunities, teaching, freelance work, and a PhD in the U.S. I couldn’t be more grateful.

Before watching the video, answer this: What should come first in Grasshopper? Then: - Watch the video below - Try the attached exercise - Compare the result before and after changing floor count or floor height - Come back and share what was actually driving the form In this video, I talk about: - Why I do not chase the final shape too early - How I use plots, floor count, and floor height as a system - Why the form should emerge from the relationship - How does this make Grasshopper feel less random 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?