I had a similar experience.  The customer requested a change to an out of the 
box solution and another Remedy Developer thought they would "dazzle" the 
customer with some extremely bloated, overly complicated solution.  The 
customer hated it, it was a nightmare to maintain (and understand) and took 
about 2 months to develop.  They eventually rejected it.  About a week later I 
came back with a very simple solution (1 extra form, and a couple of active 
links) and it's been approved and will be moving over to production.  

So the solution that the other developer was creative and did a lot more than 
the customer requested, but does that make them a better developer if it 
eventually is not what the customer wanted?

Lisa

-----Original Message-----
From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Misi Mladoniczky
Sent: Wednesday, June 04, 2014 8:43 AM
To: [email protected]
Subject: Re: Remedy Developer Performance Metrics

Hi,

I once got the assignment to add some functionality the ITSM notification 
system.

I could probably have hammered away right away, adding a bunch of field and 
loads of FLTR/ACTL/ESCL to do this. Maintaining that solution would have been a 
nightmare.

Instead I sat staring at the existing code for a week, and finally I added one 
FIELD and one FLTR, and then changed one FIELD and one FLTR.

These were 4 very expensive workflow objects!

        Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011)

Ask the Remedy Licensing Experts (Best R.O.I. Award at WWRUG10/11/12/13):
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
Find these products, and many free tools and utilities, at http://rrr.se.

> Dave,
>
> Ok, fair enough.  And I agree there are a lot of 
> qualifications/considerations.
>
> I'm seeing now, though, that I posed too broad (and sensitive) a question.
>  Let me try a different angle on this, which should be sufficient for 
> my
> needs:
>
> On a good day, and if it's all you had to do, about how many workflow 
> objects (AL's, filters, escalations) can you create (minimum, maximum, 
> and average)?
>
> For me, if it's very complex workflow, it might be as low as 15-20 objects.
>
> On the other hand, if it's a highly mechanical operation - e.g. I need 
> to replicate the same On Return active link that perhaps calls a 
> common guide across all the fields of several forms, so I'm only 
> changing the field id and doing a "Save As" - it might get up to a few 
> hundred (say one/minute).
>  But even on my worst day and the most complex workflow it's not going 
> to be just one object on the low end, and it's never going to be a 
> thousand on the high end.
>
> So for me, min to max, my answer would be 15 to, say, 400.  And, on 
> average, I'd say it's probably around 30 or so.
>
> So, anyone willing to answer, I'd appreciate the data points.
>
> Thanks,
> Charlie
>
>
> On Tue, Jun 3, 2014 at 4:44 PM, Shellman, David <[email protected]>
> wrote:
>
>> Charlie,
>>
>> Being an AR System admin is not about how many active links or 
>> filters or fields one can put together in a day.  Do they work as 
>> intended?  Are the permissions right?  If they are not working as 
>> intended how well does the individual do to figure out what is not 
>> right and correct the problem.  Is it entirely new workflow or is the 
>> individual adding to something another person put together?  Or they 
>> finding and correcting issues and with existing workflow.
>>
>> If you count workflow objects one could do coding to meet that criteria.
>> On the other had they could be efficient and combine three actions 
>> into one filter instead of three.
>>
>> Finally there is more than one way to create code within the AR System.
>>  One individual could do something one way and another individual 
>> completely different.  Both ways meet the design requirements.
>>
>> Dave
>>
>> > On Jun 3, 2014, at 5:46 PM, "Charlie Lotridge" 
>> > <[email protected]>
>> wrote:
>> >
>> > **
>> > Hi all,
>> >
>> > I'm curious...what are your opinions about what might be useful 
>> > metrics
>> to use to judge the performance of Remedy developers?  To narrow the 
>> conversation a bit, let's just talk about during the creation of a 
>> new custom application, or custom module to an existing application.  
>> In other words for code generation.
>> >
>> > So for example, you might tell me that a good developer can create 
>> > at
>> least 50 logic objects (active links/filters/escalations) in a day.  
>> Or create & format one form/day.
>> >
>> > What are you opinions?
>> >
>> > Thanks,
>> > Charlie
>> > _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"
>>
>
> ______________________________________________________________________
> _________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org 
> "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"


_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Reply via email to