This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Some may dismiss it as superstition but I would like to know others experiences. If I have the next 2 or 3 assignments ready while the current one is being nitpicked , I've to go through more than 6 revisions of the same assignment. But if I keep the next assignment untouched, I seem to get by the current assignment in, at the most, 2 tries. This was the case in every single assignment. I'm going to have a look at the servlets today for the first time and hope that things change and I'm able to complete them in a heap.
As I dont have the time to really work ahead, I normally only start work after Marilyn gives the OK to move on. I had high hopes to do the servlets before I even finished OOP but too many things got in the way. As for the # attempts. Who is counting. The main aim should to learn something from each attempt ie. nitpick.
As you may recognise, I am at Servlets Assigment 2 but already working on 4b (3 and 4a work). The nitpicking, behalve of reminding me (too, my fault) often with respect to layout ( int thisvariable; 'forgotton space') are mostly only indirect relevant for the next ones. Most important things are: -1- readability comes first. -2- if something is done more then once, think about a (helper)method. -3- ... And I try to apply my 'learned lessons' Peter
To work ahead or not, that's a good question. Your "superstition" has been true for me too. Lately, I haven't been able to, since there's more new material to deal with. But when I do jump ahead, my thoughts in between submissions usually jump ahead too, so the submission being nitpicked doesn't get as much of my "attention". While doing Say I didn't work ahead on future assignments, and I think that helped me stay focussed on it. When I try to submit a new attempt as quickly as possible, just fixing the nits without stepping back and looking at the big picture, usually I miss something else. It's hard, though, to stay away from the other assignments! cheers, Pauline
I don't really know if it pays to work ahead or not but I can't seem to help myself. I do agree with Pauline in that when I receive my nitpicks I just mainly fix whatever for the nitpicks and send it back. I have tried to look over my programs as a whole but I many times don't see what else I can do until I have been nitpicked on it. It would be hard for me not to work ahead, but I do make sure I comb my assignments right before I send them in to make sure I don't have any mistakes learned from a previous assignments. Ofcourse I don't catch all the mistakes but I try.
"Happiness is a way to Travel, <b>Not</b> a Destination" -- Unknown
At my point in the Cattle Drive (Elementary School), getting the programs to do what they're supposed to do seems to be the easy part. (Putting aside Say, which for my money is the hardest one to get to run properly.) So I don't think in that way it matters whether one works ahead or not. Speaking for myself, to stay busy Java-wise while waiting for nitpicks, I'd work ahead. That way, I figured, when I got the OK to submit them, I would already have a good idea of what the basic structure of the program should be, and I could then spend my time applying what I've learned from nitpicks of previous assignments, instead of spending time figuring out how to get the program to do what it's supposed to do. So, for me the issue has been how to keep myself busy when I've got time to work on Java, and working ahead on the Cattle Drive seems to me at least as good a way to teach oneself as any other.