Being a career software developer who has recently learned to use parametric CAD (specifically, Geomagic Design, formerly known as Alibre Design), this is just not true. On the software side, I'm one of those who generally prefers code vs. GUI config. But that's an utterly terrible analogy to parametric CAD, which is really a touch closer to a kind of end-user programming language.
Parametric CAD is far better about keeping relevant dimension values, formulas, and model constraints right where they're relevant and trivial to visually comprehend in terms of their function in the model.
A better analogy for the uninitiated would be the frustration of a spreadsheet where the cell values and formulas had to be edited on some entirely separate text code UI sheet, requiring flipping back and forth and holding stuff in short-term memory to do anything to the model.
That said, I'm actually quite interested to play with Antimony. At first blush, it looks far more appealing than OpenSCAD for practical applications. Over time, it's UI might be able to converge functionally to the mature CAD packages, but allow for greater insight into how the engine is really building up the model, especially in complex projects. Constraint debugging in parametric CAD can occasionally be a frustrating kind of hell. Antimony and/or its descendents may be able to help out with that.