
The Good Parts Of Revit API?
A few weeks ago I found an Autodesk forum post where people commented on how IsAlmostEqualTo
method doesn’t work as they expect in some scenarios (I arrived to that post facing unexpected results comparing two XYZ
objects with that method - I ended up creating an extension method for the class that can be used instead of IsAlmostEqualTo
).
That forum post reminded me of a Douglas Crockford presentation I watched a while ago (maybe this one - I didn’t save the link to the exact video) on the “good parts” of JavaScript (there is also a book). The main idea that stuck in my head after the presentation is that not all the features in a language are necessarily there to be used - some are there because they can’t be taken out (it’s too late). So we need to learn to use the good parts only.
Maybe there is a list of methods of the Revit API that is best not to use. If someone has a link to an article listing them please let me know.