Pro/E Programmers Speak: R20A year and a half ago I put together a list of personal comments found within the R18 Pro/E compiled code. Pro/E seems to be the only major software application in the world that includes these comments in the code distributed to customers, apparently other vendors usually remove them. So, seems time to check on R20 and see what's there. All the indented lines below are exact text from the R20 compiled code, extracted with the Unix 'strings' command. I'm also attaching the R18 comments, for anyone who didn't read them at the time. Good to see all the familiar names are still there on R20: Lev, Piotr, Anton, Jatin, Konstantin, and Mike. You might think from this list that PTC programmers must be at least 80% Russian, but probably not, seems the Russians are just more polite than other nationalities, they're always calling each other by name: "Please tell Piotr", "Please tell Konstantin", and so forth. On R20 there is a new person, Maxime:
In a preliminary message I said Maxime was a woman, but since then I've been corrected, no, he's a man. Maxime is just an English version of a Russian male name, Maksim. Although a lot of companies are nervous about publishing the names of technical people, worrying about headhunters, apparently not so PTC. Why, you can even get the internal phone extension of a programmer:
There's a regular flow of polite requests:
But sometimes politeness gets strained, perhaps even among the Russians:
Why bother about all this stuff? Well, take this message in the R20 code:
If it was your Pro/E session which was crashing, wouldn't you like to know? And the cheerful farewell message might just improve your mood. Now the experienced programmer has tricks to avoid a crash:
Although it's not quite clear that this is an total solution for the end user, who may find that his data has suddenly become complete nonsense. And there are other ways to avoid problems, even if you have to regress and be bad:
Or how about this, as a message before you crash:
That might at least leave you time to fasten your seatbelt. Here's another warning message which the end user might find informative:
Would be good to know that, so when your input has no visible effect on what is happening on the screen at least you know why, and you know it's not you who is going crazy. At times there is frank bafflement:
Or small triumphs:
We're all human, you or I might forget to close the door, a programmer has similar problems:
Some of the programming terms have very descriptive names:
In programming as in life, crap happens:
And even worse:
Sounds like a sewer leak, perhaps, seems as if the flow line broke somewhere. Confusion may abound:
But still there's a strong determination to succeed, keep on trying:
Things get crazy at times, just like in any other job:
And you might just have to depend on sheer luck:
Not clear here, whether the 'Good luck' message is for some fellow programmer, or for the end user. If it's for the end user, would be nice to see it printed out on the screen too. These programmers can be pretty hard on each other at times, they can be quite critical of each other's work:
Although there are some more polite comments:
It can be difficult to follow the train of thought:
And things go bad too:
And bad can even be amazing:
It's true, sometimes you might not want to know just exactly everything that can go wrong with the software you are using:
And corruption can get into the computer itself too:
Although sometimes a professional programmer can still keep that positive upbeat attitude:
Why does everything get corrupted like this? Here's one attempt to explain:
That sounds like a typical programmer, just blaming it all on the poor user. You can hear a note of apology in some remarks:
Something can still be a problem on R20, just as on R18:
Although sometimes with a literary allusion:
And the long arm of the law can affect programming too:
Worth concluding with the last two lines from my R18 report, still there in the R20 code. A question from one programmer to another:
And the affirmative answer:
Sun Microsystems peter.nurkse at sun.com |