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.
I'm working on my choices.txt as I develop my SCJD assignment and I was wondering how elaborate I should explain my choices. As an example, I use the room record index as recNo. Which could be described in choices.txt as :
- I use the room record index in the database file as recNo.
- I use the room record index in the database file as recNo. This will obviously be a unique identifier for room records. I dont consider the fact that rooms that are created by reusing disk space of previously deleted records will end up with the same recNo of previously deleted records a problem.
If I go for the latter option my choices.txt will end up being multiple pages, and I have the feeling when people will mark assignments they prefer a less is more approach.