Amen. After a grad degree nobody looks at your undergrad gpa. But, the dirty truth is, if you're applying to a mid/large company, the key is to get an in. Know/meet/talk to/email someone in the company. The HR filters can be quite ridiculous - getting an in allows you to bypass all that carp and get your resume directly into the hiring manager's hands. After that, you better have the skills for your position. As an example, 6 years ago we hired a Flash developer. We shut assorted college applicants in a room with a standalone computer (no google!), and asked them to perform a simple task. The guy we hired showed some hot skills way above and beyond the reqs, in fith the alotted time. Good thing too, because his gpa was dreadful. The manager has declined to reveal how such a resume got into the right pile. Bottom line - get an in, show your skill, and when asked where you see yourself in 5 years, say "with a masters degree".
In addition to the topics already discussed, my parents and other pre-computer adults I've taught have trouble figuring out how to intearct with software, conceptually. How do you know when to single-click or double click? It may be helpful to include the history of standard GUI interactions, such as how the mousing UI was developed/evolved - and in doing so explain why users have to click and drag to highlight or double-click to run. But, as with all other concepts you'll consider discussing, it would be very difficult to keep this chapter simple and manageable.
Slashdot Mirror
Amen. After a grad degree nobody looks at your undergrad gpa.
But, the dirty truth is, if you're applying to a mid/large company, the key is to get an in. Know/meet/talk to/email someone in the company. The HR filters can be quite ridiculous - getting an in allows you to bypass all that carp and get your resume directly into the hiring manager's hands.
After that, you better have the skills for your position. As an example, 6 years ago we hired a Flash developer. We shut assorted college applicants in a room with a standalone computer (no google!), and asked them to perform a simple task. The guy we hired showed some hot skills way above and beyond the reqs, in fith the alotted time. Good thing too, because his gpa was dreadful. The manager has declined to reveal how such a resume got into the right pile.
Bottom line - get an in, show your skill, and when asked where you see yourself in 5 years, say "with a masters degree".
--.dude, you're getting a hysteriaectomy.--
In addition to the topics already discussed, my parents and other pre-computer adults I've taught have trouble figuring out how to intearct with software, conceptually. How do you know when to single-click or double click? It may be helpful to include the history of standard GUI interactions, such as how the mousing UI was developed/evolved - and in doing so explain why users have to click and drag to highlight or double-click to run. But, as with all other concepts you'll consider discussing, it would be very difficult to keep this chapter simple and manageable.