WDSc Survivor
Five Brave RPG Programmers Move from PDM/SEU to WDSc
December 1, 2004
The road trip
Just went through my first road trip after having moved primarily to WDSc. And, as usual, I needed to fix a couple of small things while on the road, from my hotel room. I knew where the code was that had a problem. I went into our application first so I could see the problem that had been reported. Sure enough, I had a small bug. I instinctively went to PDM/SEU as I was on the road and already signed on to the development machine, which is also where I made sure I could duplicate the issue that had been reported. In a matter of seconds, I was in SEU editing the source member. I then stopped, made myself get out and I fired up WDSc. It took over 30 seconds to load and then I had to get a filter added so I could edit the member. I find I'm adding filters to an existing filter more often than browsing an entire source file and all members. It was easy to find my problem, edit it and compile in WDSc. It wasn't as fast as PDM/SEU because I had to start the load from scratch. Typically, in the office I start WDSc in the morning and go. I understand the delay in starting WDSc, but what I'd really like to see is a smarter environment where it knows the last source library & file I worked with and would allow a quick open of a source code member instead of browsing a long list or having to add it to a filter.
Posted by at December 1, 2004 7:14 AM
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| 1 | 2 | |||||
| 3 | 4 | 5 | 6 | 7 | 8 | 9 |
| 10 | 11 | 12 | 13 | 14 | 15 | 16 |
| 17 | 18 | 19 | 20 | 21 | 22 | 23 |
| 24 | 25 | 26 | 27 | 28 | 29 | 30 |
| 31 |
Blog Policy
Our blogs are editorial content of System iNetwork. We welcome your comments and opinions and encourage lively debate on the issues, and we reserve the right to edit all postings for clarity, length, civility of tone, and appropriateness to the topic under discussion. Comments consisting of product or job solicitations and other spam, profanity, and extreme rudeness will be deleted. We also reserve the right to publish excerpts from the blogs in our e-mail newsletters and print magazine.