So if everybody writes a bug tracking app, why are there so few (Remedy-based) available on the Net (BMC Communities?)
On Tue, Nov 11, 2014 at 7:18 AM, John Sundberg < [email protected]> wrote: > ** > Funny - that is pretty much what I started writing as my first ARS some 20 > years ago now. > (After I figured out how to install an XWindows client onto Windows 3.1 or > Windows 95, TCP/IP (WRQ stack) on my machine, and basic Unix navigation) > (That’s right — Windows didn’t come with TCP/IP — you had to buy a product > for that - and then configure Windows to use it) > (ARS 1.02) > > *** I was sort of the WRQ TCP/IP troubleshooter for our company. (I > learned a ton about networking back then) > > > -John > > On Tue, Nov 11, 2014 at 9:08 AM, Rick Cook <[email protected]> wrote: > >> ** >> John is correct about jumping into ITSM code. It contains concepts too >> advanced for beginners, and even has some old timers scratching their heads >> and diving into manuals at times. I used to recommend that new Remedy >> developers start out by writing a bug tracking application. It's easy >> (should be able to do it in a week), everyone knows basically how one is >> supposed to look and work, it teaches basic concepts of how AR System code >> works, and doesn't mess with any existing applications. You might try >> something similar. >> >> Rick Cook >> >> On Tue, Nov 11, 2014 at 7:04 AM, John Sundberg < >> [email protected]> wrote: >> >>> ** >>> I think if you are a smart person … you could write workflow within the >>> first week (even day). >>> >>> However, I don’t think you should write workflow in the first week. >>> >>> I would assume you are not a “from scratch” system … but walking into a >>> “real system”. >>> >>> If that is the case — I think it would be 6+ months before you should be >>> touching the real system. >>> >>> These large systems are like big bowls of Jello… you touch it here - and >>> it wiggles in 100 other places. (And - it is not easy to know where / what >>> you are affecting.) >>> >>> (You have to be a significantly skilled person to understand what is >>> changeable and what is not, and what is the convention for changes, naming, >>> etc… — and sadly - it is not until upgrade time that you find you have >>> been tying a knot that is one m****f*** to figure out) >>> >>> >>> So - yes - you can pick up the hammer and start swinging soon. Problem >>> is - you are in a fine art gallery and it will be a net negative. >>> >>> >>> -John >>> >>> >>> >>> >>> On Tue, Nov 11, 2014 at 8:27 AM, Zee Remshab <[email protected]> wrote: >>> >>>> dear listers, >>>> >>>> say you have +15 years in the IT, many years as DBA/sys admin/web admin >>>> + several years on BMC Remedy but only ARSystem and haven't opened yet the >>>> ITSM objects in the Dev Studio. >>>> How long could that take to get the hand on the ITSM modules and be >>>> capable of writing basic workflow ? I don't need an precise figure, just >>>> some random comments/thought would be very much appreciated. But no jokes >>>> please. >>>> Very best regards >>>> zee remshab >>>> >>>> >>>> _______________________________________________________________________________ >>>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >>>> "Where the Answers Are, and have been for 20 years" >>>> >>> >>> >>> >>> -- >>> >>> *John Sundberg* >>> Kinetic Data, Inc. >>> "Your Business. Your Process." >>> >>> 651-556-0930 I [email protected] >>> www.kineticdata.com I community.kineticdata.com >>> >>> >>> _ARSlist: "Where the Answers Are" and have been for 20 years_ >> >> >> _ARSlist: "Where the Answers Are" and have been for 20 years_ > > > > > -- > > *John Sundberg* > Kinetic Data, Inc. > "Your Business. Your Process." > > 651-556-0930 I [email protected] > www.kineticdata.com I community.kineticdata.com > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
