Bear Bibeault wrote:Sounds to me like it's time to up periscope for your next position. It sounds like you have had some good experience previously in your current job, but if there's no chance to continue development, doing continuing manual testing isn't going to do anything for your skill set or career.
Prasanna Raman wrote:Thanks, Jeanne
I am thinking of having an accountID field to uniquely identify an account and an SSN field for uniquely identifying a customer, but I am confused as to why I have to think about these at this point. Could you please help me understand?
Social Security Numbers do not make good primary keys for a table of people for many reasons. First, most people consider their SSN private and don’t want it used in databases in the first place. Second, some people don’t have SSNs – especially those who have never set foot in the United States! Third, SSNs may be reused after an individual’s death. Finally, an individual may have more than one SSN over a lifetime – the Social Security Administration will issue a new number in cases of fraud or identity theft.
Saikrishnan Srivatsan wrote:
Campbell Ritchie wrote:it should be:-
Map<Name,Entry> entries = new HashMap<Name, Entry>();
I understand the concept of dynamic look-up that Java does but haven't come across a real life example to understand why I really need to declare things the one above as the super type. Is this something that someone can explain or maybe point me to other threads where this has been discussed? I can't understand here whyis bad