Validate my method is fine please (programmers differ in opinion)

It seems like a divisive matter. I have worked with a very knowledgeable person that insists that you must Level - Rotate - Translate in that exact order. They said they have had problems with feature nominals in the past when they translated before rotating. I have not observed any such issues myself. However, I have only worked with the software since 2006, so maybe those sorts of problems had been fixed before my time.

Personally, I don't think the order matters. For years I would typically select my alignment features, click the Auto-align button, quickly check that everything looks right, then go with whatever order was auto generated. Then offset if necessary. A plane with two holes would mean that the rotation is done last. I always program with displayprecision set to 6 so I can check for any wonky positions/vectors out to the millionths place and have not seen anything funky happen that I could trace back to the order of operations in my alignment.

Then, I worked for a boss that gave me a long lecture every time I did not Level- Rotate - then Translate (the afore mentioned "knowledgeable person"). Now I still use the Auto-align button, but I have the habit of cutting and pasting the rotation line of the alignment and placing it right after the level line. It only takes me a few seconds to do that and who knows, maybe it has prevented a problem from happening. Or maybe it has future proofed my programs against some new obscure bugs that won't get discovered because the testers assumed everyone does their rotating before translating.

It seems like a divisive matter. I have worked with a very knowledgeable person that insists that you must Level - Rotate - Translate in that exact order. They said they have had problems with feature nominals in the past when they translated before rotating. I have not observed any such issues myself. However, I have only worked with the software since 2006, so maybe those sorts of problems had been fixed before my time.

Personally, I don't think the order matters. For years I would typically select my alignment features, click the Auto-align button, quickly check that everything looks right, then go with whatever order was auto generated. Then offset if necessary. A plane with two holes would mean that the rotation is done last. I always program with displayprecision set to 6 so I can check for any wonky positions/vectors out to the millionths place and have not seen anything funky happen that I could trace back to the order of operations in my alignment.

Then, I worked for a boss that gave me a long lecture every time I did not Level- Rotate - then Translate (the afore mentioned "knowledgeable person"). Now I still use the Auto-align button, but I have the habit of cutting and pasting the rotation line of the alignment and placing it right after the level line. It only takes me a few seconds to do that and who knows, maybe it has prevented a problem from happening. Or maybe it has future proofed my programs against some new obscure bugs that won't get discovered because the testers assumed everyone does their rotating before translating.