 |
| Click the windows menu button, then click the Excel Options (shown below with a red arrow) |
 |
| Click Customize (1), then Click All Commands (1a), then Document Location (2), then Add (3) and finally OK |
 |
| And that’s it. It should look like the above picture when you're done. |
Mitch,
Thank you for taking the time to speak with me today; I look forward to receiving your availability for the technical phone interview as well as your resume at your earliest convenience.
(*Keep in mind interviewers conduct phone screens between 11am and 4pm daily (EST) except for Thursdays; you will want to be in front of a computer and it will take roughly 45 minutes; a few days/times for me to schedule from would be greatly appreciated.
As I mentioned, here are the areas of expertise that you can select from. Also, a list of projects in some of our offices for your reference at the bottom. I should have more information to you in regards to the next steps as soon as I get all of your information back.
Technical Strengths (Please select no more than 3 to 5):
Mobile/Wireless
Networking
Advanced Algorithms
Artificial Intelligence
Machine Learning
Natural Language Processing
Data Mining
Information Retrieval
Windows
Databases/SQL
Operating Systems/Kernel
Audio/Video/Multimedia
UI design and implementation
Links:
Focus Areas/Projects at Google: http://www.google.com/intl/en/jobs/profiles/swe.htmlNew York office: http://www.google.com/support/jobs/bin/static.py?page=why-ny-ny.html&dep_id=1054&loc_id=1122&topic=1054
Hi Mitchell,
I work with <name removed> and have scheduled your phone interview for the following:DATE: Thursday, <date removed>TIME: <time removed>PHONE: <phone removed>Google Doc: <google doc removed>
So now I confirmed with the recruiter and all I had to do was wait for the call at the specified time. I was at Cosi 15 minutes early so I got my computer setup. At the alloted time, there was no call. I waited 6 minutes and fired off an email to the recruiter then 10 minutes late, the interviewer called me.Should your availability change due to personal emergencies, please notify your Recruiter immediately. We are more than happy to reschedule your interview. Please keep in mind that this may result in a scheduling delay, as well as a delay in the interview process.IMPORTANT NOTE: Your interviewer may opt to use the Google Doc linked above. You will need a computer with internet access for this interview in order to use Google Docs, a web-based word processor which lets you share and collaborate your work online. Please ensure that you are able to log into this at least a day prior to your interview and be logged in and ready to go at least 5 minutes prior to your scheduled call. Additionally, to make hands free coding a little easier, we recommend that you have a headset or a phone with speaker option available for the interview.A member of our engineering team will call you at the phone number above. Please note this will be a technical interview that will last for approximately 45 minutes. Google takes an academic approach to the interviewing process. This means that we are interested in your thought process, your approach to problem solving as well as your coding abilities. You may be asked questions that relate to technical facts and knowledge, algorithms, code, performance, how to test solutions, and perhaps your interest in Google products. During the interview, please feel free to ask the interviewer if you are not clear with any of the questions. Also, feel free to talk through a problem so that your interviewer can better understand your thought process. We ask that you keep our interview questions confidential as we do use them with other candidates and having them published would jeopardize the integrity of the process.For more information, we invite you to take a look at the following:* Life at Google: http://www.youtube.com/lifeatgoogle* Interviewing at Google: http://www.youtube.com/watch?v=w887NIa_V9w* Preparing for your interview: http://www.google.com/intl/en/jobs/joininggoogle/interview/index.htmlPlease CONFIRM the time and phone number listed above, so we can add it to our company calendar.If you have any questions or concerns related to scheduling, please reply directly to me. Otherwise, your recruiter <name removed> will happily assist you with any other interview-related queries you may have.Thank you,<name removed>
I started some iOS development from scratch starting in 2010 in May. I wanted to create a talking weather alarm clock and had not done *any* iOS development previously. Yes, I worked with C but primarily, I've been doing java development for the past 14 years. I was surprised that development was "required" to be done (this has since been laxed) in Objective C.
The time I allotted to this project is my daily 2.5 hour (round drip) comute. This doesn't allow me nearly enough time to focus as I'd like but still was enough time to get "something" done.
Things I needed to learn for this project:
1. Objective C. Objective C isn't a difficult language to learn. The syntax is similar enough to other languages BUT memory management is something that has to be taken seriously.
2. Objective C has also adopted many patterns and unenforced rules. I.e. the word alloc means you're responsible for releasing an object but if an object is created without a special keyword, then it is autoreleased.
2. The *vast* iOS api's. Along the way I needed to understand Audio, Animations, NS Core Data Structures, Table Window semantics and threading concepts.
3. Creating images using Adobe Illustrator.
4. Creating sounds using Garage Band.
While all of these things are not hard by themselves, doing them all yourself is very time consuming and I wished a many times for a partner to help out but that didn't work out as I had expected.
So the app is now in the app store review after much frustrations. Once it's available, give it a shot. You can download the app "snooZe" (it's free :) in the iTunes app store.
If I had to do it again, I would probably use a 3rd party library. I've been researching Cocos2d (free), Corona (free to develop, $200 to deploy), and Unity ($$$). I'll write about them in other posts.
#c::
Send ^c
ClipWait ; Wait for the clipboard to contain text.
SetTitleMatchMode, 2
IfWinExist Excel
{
WinActivate ; Activate Excel
}
else
{
Run Excel
WinWait Excel
WinActivate
}
Send ^v{enter} ; paste and hit enter to go to the next line
Send !{tab} ; switch back to original window
return
