I think questions about: 1) Field Ids 2) Workflow naming 3) How do you document what you have done (and this is a biggy, the WHY stuff was done is usually left out)
The responses to those 3 open ended questions tell you alot. I had one senior person tell me recently that he didn't think there was any reason to choose your own field ids for a custom module (on a system with the ITSM6 suite). Didn't get a chance to show him how much workflow I had been able to borrow from ITSM6 for the custom module by using the same field ids for the standard fields and then just copying the workflow with new naming (so changes for the ITSM module, or BMC patches would not affect the workflow that I borrowed). ... Daniel -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Tim Widowfield Sent: February 21, 2008 3:48 PM To: arslist@ARSLIST.ORG Subject: Re: Interview questions Well, I can only speak for myself, but I normally use the TR. prefix, just so you can look at the qualification at a glance and understand what it means. It reminds me of C and Java programmers who omit braces when they aren't necessary. Sure, it's legal, but is it more readable? Too often we forget that code may be written once, but read hundreds of times (e.g., by beleaguered maintenance programmers at 3:00 AM). I'd much rather argue over whether you should ever let the admin tool pick your field IDs and whether workflow names should be meaningful rather than over syntactic sugar. --Tim _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
