Not so much Esperanto, which matches Model Based Documentation. In looking at the video, it's more like a style guide for users. Overall not that bad a modeling strategy and in keeping with my own typical habits of model creation, though I don't go to the extreme of suppressing features to make sure they don't reference each other; experience lets me avoid that. https://www.youtube.com/watch?t=691&v=YU_lTS1vIx4 As suggested, I do go to the trouble of renaming features for what they do, rather than what they are and grouping them according to function. Not touched on in the video is what to do about assemblies.
17:45 is the funniest bit, and so true - Holy Grail Best Practices, based on former experiences with unqualified Admins skipping critical areas and pushing fools errands. For example, on CADDS IV, one Admin (former school teacher) insisted that text be on one layer and all other drawing entities be on another, so the drafters would be able to get the plots made with the correct pens. The 'problem?' A single mapkey (tablet pick, really) could put all the text onto one layer and everything else on the other as prep for plotting, so why make all the engineers, many low time users, responsible for a nitpicking detail that a single mapkey could sort out 100% just before plotting, a job done by high time drafters?
O/T Same thing happened with the rechargeable mice in the big conference room - main secretary emailed all 300 people in the building about people not putting the mice back on the chargers. However only a few people would ever use the mice, so maybe 270 people had to put in time to read the message (30 seconds each = 2 man hours lost, ~$200 based on overhead rate) and of the 30 likely targets, 15 would forget (8 man minutes lost) and it does not reach those who join the company later or are outside presenters, and so would be entirely ineffective for them. They could buy new mice for about $50 that would use regular AAs that last for ~ 1 year under the typical conference room use and can be immediately remediated if the battery dies, unlike the rechargeable ones, or she could stop in the conference room on her way out at the end of each day and make sure. Instead the 'answer' was to misplace responsibility and minimize compliance while wasting the company $200. A lot of Holy Grail rules end up like that, while ignoring the important things.
