It actually summarizes the history rather well. The foresight from Gehry was really taking parametrics from the Mechanical-CAD world and applying them to Archit

It actually summarizes the history rather well. The foresight from Gehry was really taking parametrics from the Mechanical-CAD world and applying them to Architectural CAD whilst everyone else was still emulating the drawing board virtually (and unfortunately many still do), the hierarchical nature of the relationships you get from parametric modelers, and having to abstract out your physical objects, surely made the jump to storing structured information a lot more natural. The real power in practice comes from the information interoperability between stakeholders, which it didn't really touch on, but enough to highlight it's biggest roadblock, contracts. For information into how to create a productive contractual environment you can look into Integrated Project Delivery arrangements. "(I don't know a ton about this stuff, as I switched from an architecture degree to CS after a year once I realized tools like Grasshopper existed. I decided I'd rather learn to program and apply it to architecture then learn architecture and try to pick up some programming)" Similar to you I started out in Architecture but spent around 3 years in that program (at three separate universities) before finding a rather unique degree that combines both (Architectural Computing). I did my final project on Parametric Structures that were also "intelligent" in Bentley Generative components.