Would it be OK to ask a question about code review on something that strictly-speaking is not code as such, as far as most users are concerned? But the underpinnings are such that the problem is in fact code and could be constructed as such?
To be a bit more concrete in this case, the "code" is a parametric 3D CAD model, which has all the attributes of code. Things are referenced from elsewhere and you need to think about maintenance of such things. It would be relatively easy to express the drawing as abstract code.
The thing is I'm trying to come up with a list of things that programmers know intuitively and through experience that does not filter well to most mechanical engineers. The challenges of maintaining the models are still strictly-speaking the same as writing code. So I would know what is good encapsulation when DRY is violated etc.
What I am trying to get eventually is a way evaluate the CAD drawing practices in a context of what is known by programmers about code layout. This way I can construct better guidelines for making and maintaining CAD models in the first place.
Obviously this would be a lot of work on my part but still possibly an interesting and fruitful review.