Re: RdI vs SEU was: RE: Change management systems

Vern Hamberg wrote:

Kurt

Scott didn't say, as you misquoted him, "...SEU is no different in RDi in regard to productivity..." - he said something more like "...the advantages...are being constantly overstated in these forums..."

Those are completely different. I agree with the latter. Do I use WDSC+? Of course. Do I find it super-productive? Naw. Does it help me do things it'd be less simple to do in PDM or SEU? Sometimes. But there is still nothing as good for merging changes as option 55 in PDM. That just isn't available in WDSC+.

If you are as productive in SEU as you are in RDi, then you simply aren't taking advantage of the tool, or you're writing old style code. I don't ever merge changes, so I don't care about that (we use pessimistic locking so we don't have that issue), but even if I did, that would be a single issue that has nothing to do with the overall writing of code. I suppose if you spend 50% of your time doing source merges, it might make a difference, but if you're spending half your time doing merges, you have other problems <grin>.

I am on average twice as productive in RDi, whether it's the outline or the content assist or the colored syntax or the task view or the ease of copying source from one machine to another or the powerful search capabilities or the user-defined commands or ...

And that's working on a mix of RPG II through ILE.

So you use the tool for the job that best fits it. Both green-screen apps and graphical/browser/thick client apps have their place.

I'm just sayin'!
Vern

SEU has no place as the primary development tool for a programmer, in ANY language. It works, but it's the wrong tool for the job.

How often do you use SEU to write Java code, Vern?

Just askin'

Joe