For years people (user people and PTC people) have mentioned there are\npersonal names and comments embedded in the Pro\/E code. But that fact\napparently has never been documented. At the user conference in\nOrlando, I submitted a question to the PTC management track on these\nnames and comments, with some examples, but didn’t get a reply.\n<\/p>\n\n\n\n
Pro\/E may be unique among major software applications because of all\nthe personal observations distributed in the compiled code. These\ncomments could be a contribution to the history of software\nprogramming—at times you feel as if you’re looking right over the\nindividual programmers’ shoulders, as they express themself on the\nkeyboard. You get an insight into the people, their work, their common\nculture and their personal differences.\n<\/p>\n\n\n\n
To list out the plain text in any compiled code, you can use the Unix\n‘strings’ command. That’s often useful to check a version, or to\ncollect and compare error messages, normally very dull reading. But\nwith Pro\/E you get a lot more, not dull at all. Everything indented\nbelow is taken directly from the plain text in the R18 code, with\ncomments added.\n<\/p>\n\n\n\n
Customers don’t often talk directly to programmers. However here you can\nlisten to the programmers talking among themselves. Often they are\npolite, courteous even:\n<\/p>\n\n\n\n
Although there can also be a trace of stress:\n<\/p>\n\n\n\n
Mike and Jatin seem to share responsibility for part size:\n<\/p>\n\n\n\n
But it’s Anton who gets the calls with steadily increasing urgency:\n<\/p>\n\n\n\n
Most of the personal names embedded in the code are Russian, not a big\nsurprise, since for years many Russian technical immigrants relied on\njobs with one of the Boston area MCAD vendors. And these Russian names\nusually appear with courteous and polite statements (like, “Please\ntell…”). There’s also at least one Scot in the crowd:\n<\/p>\n\n\n\n
However other programmers are not quite so polite, here are some\nexamples of a more abrupt native born American style:\n<\/p>\n\n\n\n
Here’s a common observation, but surely not intended for the paying\ncustomer:\n<\/p>\n\n\n\n
And us native born Americans can get pretty rude, even:\n<\/p>\n\n\n\n
Sad to say, Konstantin’s children growing up in the US are more likely\nto talk that way than in the polite manner of their father.\n<\/p>\n\n\n\n
NC programming often depends on using a quilt of surfaces to guide\nthe tool, and if you lose the quilt that’s important:\n<\/p>\n\n\n\n
Another NC programming problem is gouges, caused when the cutting tool\ncuts into the part surface. Here the story is one of steady progress:\n<\/p>\n\n\n\n
Data can have problems:\n<\/p>\n\n\n\n
But an explanation might be close to hand:\n<\/p>\n\n\n\n
We all probably know someone like that, the kind of person who forgets\nto clean up after themselves, making problems for others.\n<\/p>\n\n\n\n
In MCAD programming, geometry can be difficult to deal with:\n<\/p>\n\n\n\n
Sometimes the whole outlook isn’t good:\n<\/p>\n\n\n\n
Something can happen in different ways:\n<\/p>\n\n\n\n
Sometimes we get a few more details about something:\n<\/p>\n\n\n\n
Sometimes something wrong doesn’t mean much:\n<\/p>\n\n\n\n
Goofs happen in programming, that’s normal:\n<\/p>\n\n\n\n
And mistakes too, sometimes big mistakes:\n<\/p>\n\n\n\n
Imagine you’re on a plane, and you happen to hear this exclamation from\nthe cockpit:\n<\/p>\n\n\n\n
You might be concerned. But we’re not on a plane, this is just a\nsoftware application, and it doesn’t seem to apply to any particular\narea of the software.\n<\/p>\n\n\n\n
However here’s a warning message that might have any user worried:\n<\/p>\n\n\n\n
I tried to find out from the context, which button it is, that you’d\nbetter not push, but that isn’t clear. Hopefully you get the message\nbefore you push the button.\n<\/p>\n\n\n\n
Of course, in any programming task, weird things happen:\n<\/p>\n\n\n\n
Weird slots can jump on you almost any time, you’d better be alert—\nlook out, be ready to duck down right under your desk!\n<\/p>\n\n\n\n
You hear some pretty candid admissions:\n<\/p>\n\n\n\n
Sometimes the statement is the simplest possible fact:\n<\/p>\n\n\n\n
(good at least someone is on the job there).\n<\/p>\n\n\n\n
Sometimes questions appear just as they might have been asked\nright out in the hallway, or at the soda machine:\n<\/p>\n\n\n\n
And sometimes the tone is more discursive:\n<\/p>\n\n\n\n
Sometimes comments are tied to particular routines:\n<\/p>\n\n\n\n
Yes, I’d hope you would say sorry, if you called crash_on_exit on me.\nSorry is refreshing, would be nice to see more computer error messages\nthat say sorry. Most of these were probably intended for fellow\nprogrammers, and not for users:\n<\/p>\n\n
Anyone who’s done any programming should recognize these states of\nmind, when words just fail:\n<\/p>\n\n
And the monotony and routine of programming work can get you down:\n<\/p>\n\n
Language becomes pretty colloquial at times:\n<\/p>\n\n
Perhaps by now you might agree with this statement:\n<\/p>\n\n
To conclude, anyone who has ever worked on a major software development\nproject has probably felt this way:\n<\/p>\n\n
However from the heart of the code comes this affirmative answer:\n<\/p>\n\n
<\/p>\n For years people (user people and PTC people) have mentioned there are personal names and comments embedded in the Pro\/E code. But that fact apparently has never been documented. At the user conference in Orlando, I submitted a question to the PTC management track on these names and comments, with some examples, but didn’t get … Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"parent":46,"menu_order":1,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-78","page","type-page","status-publish"],"_links":{"self":[{"href":"https:\/\/creosite.com\/index.php\/wp-json\/wp\/v2\/pages\/78","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/creosite.com\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/creosite.com\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/creosite.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/creosite.com\/index.php\/wp-json\/wp\/v2\/comments?post=78"}],"version-history":[{"count":5,"href":"https:\/\/creosite.com\/index.php\/wp-json\/wp\/v2\/pages\/78\/revisions"}],"predecessor-version":[{"id":829,"href":"https:\/\/creosite.com\/index.php\/wp-json\/wp\/v2\/pages\/78\/revisions\/829"}],"up":[{"embeddable":true,"href":"https:\/\/creosite.com\/index.php\/wp-json\/wp\/v2\/pages\/46"}],"wp:attachment":[{"href":"https:\/\/creosite.com\/index.php\/wp-json\/wp\/v2\/media?parent=78"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nSun Microsystems
\n<\/addres><\/li>\n","protected":false},"excerpt":{"rendered":"