Aadhar Joshi (6/22/2013)
Jeff sounds interesting, u should do instead.
I've already done it. Wouldn't have recommended it unless I tried it and it worked. That's why I currently have my dream job so close to home that I could ride a unicycle to work without the need of chaffing powder. :-P
The key is going to be the resume. I'm here to tell you that you really only do have 15 seconds to be put in the "let's talk" pile by most prospective employers. For starters, you'd better have a good, job oriented "Objective" instead of the touchy-feely stuff I see on a lot of resumes (if one was included at all and you better have one). If the Objective looks like a sentence, then you've done it wrong. Having a brief or even extended job history is nice but tells me nothing of what you really did. When I interview people, I want to know if they made a difference or not in their previous jobs and, if they did, how they made a difference. I wrote my resume with that same thought in mind.
Of course, you'd better be able to back up what you have on the resume during the interview.
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is usually not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs