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

Thorbjoern Ravn Andersen wrote:

Vern Hamberg skrev:

This is just me, but I find WDSC+ too big a hammer for doing a
quick 10-line test in CL. For that I almost always use SEU. If
there were a shop rule not to use SEU, I could live with that,
though.

Sounds like "notepad is enough for me for this task" under
Windows.

I could code Java in Notepad (with javac) but I'd rather use an
IDE:

That "notepad is enough for me for this task" sounds like a legitimate rationalization to me; i.e. at least given the /correct/ circumstances. Both EDTF & Notepad would function fine for me in some scenarios.

If the IDE is already started, then surely I would rather use the /better/ tool for the job. However if I have to wait a period of time to even begin to do something that would have been both started & completed within just a portion of that same time, by having used an alternate & quicker method, and if that is the only reason I would have to start the IDE, then why choose the slower means to accomplish the same task? Perhaps there are some who [not me] might rationalize instead, using the /better/ tool, if they were being paid by the hour? ;-)

That scenario mimics my typical situation with some GUI versus a command line alternative. If I know already how to perform something quickly in a command line, and the command line is quickly available [as compared to starting a GUI], then... Why would I spend time to start or even just navigate the GUI to accomplish a task, when I can easily just keyboard the entire request with keyboard characters and press the Enter key? Given a /command/ scripting interface were available, I may have even been able to just run an existing script that had been created specifically to replace those numerous interactive GUI manipulations; i.e. clicking, tabbing, scrolling, etc..

Regards, Chuck