Re: Change management systems

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

Technically, PDM and SEU are not the same thing.  But, PDM calls SEU 
when it needs to edit code.

They both come together as part of a package named ADTS. (Application 
Development Tool Set) along with a few other things.

Personally, I think the advantages of WDSC/RDi/RDP over PDM/SEU are 
being constantly overstated in these forums.  There are certainly some 
things that RDi does better, like copy/paste, outline view, syntax 
highlighting.

But these things aren't the ultra-awesome, revolutionary things that 
folks in these forums make them out to be.  Yes, copy/paste is better in 
RDi, but I could still do it in SEU, and I could do it pretty well. 
Yes, outline view is useful, but searching out what I'm looking for also 
works.  Yes, syntax highlighting/coloring can be nice, but I can read my 
code okay when it's all one color.

Personally, I think the user interface seen by the USER is far more 
important than the interface seen by the DEVELOPER.


On 3/12/2010 7:18 AM, Bryce Martin wrote:
> I think there has been some criss cross of terms going on here.
>
> PDM is not SEU, SEU is a part of PDM.... correct?  I didn't not grow up
> with this system so please forgive me.  When I talk about advantages of
> WDSC it is for development purposes over the use of SEU.  I do not know
> what all PDM uses, but I often do system stuff from the command line
> instead of IBM's snail pased windows alternatives (might be a slight
> exageration, but I believe only slight).  Developing in WDSC/RD(insert
> letter) is significantly faster than SEU and you can recoup the learning
> curve with productivity gains in a month if you are in code all day
> everyday.