Join our MCAD Central community forums, the largest resource for MCAD (Mechanical Computer-Aided Design) professionals, including files, forums, jobs, articles, calendar, and more.
Better question could be - How much is Pro\E in this BUG program it is supposed to be
anyway, I am sure it starts some long thread with many jokes, just because your post touches some basic and obvious part of Pro\E in genral.
So, considering bugs - it is software term describing problem which comes from bad coding - guy who asked you about that was curoius if you are aware of strange, not expected behaviour of Pro\E.
Avoiding the obvious, I think this guy was trying to see if you have a fair amount of experience with Pro/E, because anyone that has spent a decent amount of time on Pro/Ecan spit out a laundry list, scratch that, a SCROLL of bugs in Pro/E!
No bugs, only Un-intended functionality. Of course, there are SPR's, TAN's and TPI's ...
There are also no crashes, only unplanned exits.
Seriously, there is a tool on PTC.com called the update advisor that will tell you the number of 'open issues' ina particular builr compared to another, as well as the total number for the newer build. According to that, there are 133 in WF3, M100 (newest WF3), 794in WF2, M280 (last build of WF2).
That's straight from PTC tech support. Call them and say that something works unexpectedly, they'll tell you (nearly without fail) that it is 'intended functionality'. Tell them that Pro|E crashed, they will stop you and correct you - it wasn't a crash, it was an unplanned exit.
Like the pretty words make it any easier to deal with.
That's straight from PTC tech support. Call them and say that something works unexpectedly, they'll tell you (nearly without fail) that it is 'intended functionality'. Tell them that Pro|E crashed, they will stop you and correct you - it wasn't a crash, it was an unplanned exit.
Reminds me of a cartoon I saw many years ago. A bunch of guys in suits sitting aroung a conference table, and one of them saying "I propose that, rather than fix the bugs, we change the documentation and call them features."
I thought it was humor - I guess PTC tech support took it seriously.
Interviewers frequently ask questions that are intended simply to judge your response: the question itself has little relevance. The interviewer may have been trying to judge your comfort level with Pro/E. I suspect that employers are concerned about hiring users who are overly frustrated by Pro/E, even though they may be experienced users.It's important for any interviewee to impress his potential employer with his ability to roll with the punches, and to pursue solutions to problems, not simply bitch and moan.
I think a good response would be: "Sure, there are some bugs in Pro/E, but I can deal them. I'd rather not go into detail on the ones I'm familiar with: besides, the bugs get fixed and rarely prevent me from getting my work done. But I do make an effort to report them to PTC, as I see this as part of my responsibility as a user".
P.S. Please do not ask me about my frustration level with Pro/E.
"I propose that, rather than fix the bugs, we change the documentation and call them features."
Unfortunately this is exactly what PTC sometimes does. Just one example:
When changing the number of decimals for a dimension in a Drawing, the value of the tolerance is set to some default value. E.g 6,678
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
