“Hey Roop, Arnosite Asbestos is not a thing.”
I had just come back from a week-long vacation. It was 8:00 am…and I was in my first Monday morning meeting. My post-vacation haze immediately dissipated.
Before leaving for vacation, I had recorded the latest iTwin Platform course. It took weeks of programming, scripting, recording, and re-recording to get the course content down. And I distinctly remember saying the words “Arnosite Asbestos”…at least a million times.
Which apparently was not a thing.
“It’s called AMOSITE Asbestos.”
“No, it’s not!” I shouted into the muted microphone. “I am pretty sure it’s Arnosite Asbestos.” I scurried open the design application involved in the course recordings. I rubbed and re-rubbed my eyes to make sure my vision was intact.
How could this be? Was there a bug in the application? I called the person (who called the person, who called the person) who wrote the application, and found out — much to my chagrin — this indeed was a bug. A bug caused by a quirk in the English language.
The rn = m conundrum.
You see the characters “r” and “n” when placed next to each other, give the appearance of an “m.” Somebody (a while back) accidentally typed “Arnosite Asbestos” instead of “Amosite Asbestos.”
Which were the words my entire course was based on.
Say hello to:
The iTwin Property Validation API Course
The imperfect course about perfecting digital twin data. Check out the sneak peek below:
“But what the heck IS Amosite Asbestos?”
Glad you asked!
AMOSITE Asbestos is a popular design material used for thermal insulation in infrastructure assets. And turns out my Google search has some serious gripes against it:
Exactly — it’s actually quite hazardrous. It’s known to cause lung disease in people who are exposed to it. In this course, we will take the example of an asbestos-ridden digital twin…and use the validation API to make it asbestos-free.
If you would like to learn how to detect (and correct) issues like these, please head on over to the course page / YouTube. After all, If there’s anything I have learned from recording this course — it’s best to catch your s̶p̶e̶l̶l̶i̶n̶g data issues as early as possible.
-Roop, reporting live frorn the basernent.
<- previous post | home | next post ->