rafa3rafa

Good points by ChuckMcM.

I second the need to bring warm clothes, be prepared to dress in layers. If you're in Palo Alto most of the time it'll be 10-15+ degrees warmer (Fahrenheit) than SF so bring a mix of cool & warm clothes but again yes be prepared for cold evenings in SF.

Regarding transport between SF to Palo Alto, while it is easily accessible there are two things you need to consider. 1) Commute time: the commute between SF to Palo Alto is at least 35-45 minutes by car, commuting via CalTrain will be slightly longer 50-60 minutes. 2) Where you will live and work: 50-70 minutes assumes you live near the Caltrain station in SF and work near the Caltrain stop in Palo Alto, otherwise your commute can easily be 60-90 minutes one way. If you plan to be working 10-14hours days in Palo Alto you may reconsidering living in SF during this short stint.

Regarding managing money, not sure how long you will be here if it's just two months or so. Something I usually do when traveling, is use a credit card for most purchases. Then I withdraw cash from my bank account one or however many times needed but max the daily withdrawal limit each time to minimize fees as much as possible. You should quickly research which credit cards in the UK do not charge international transaction fees. Capital One does not charge international transaction fees.

I think this is a great idea. I've come up with this problem in the past not being a technical person myself. Especially when vetting out new hires early on. In the past I've worked in organizations that have their own internal testing but those are often baselined against the person who originally wrote them. The great thing with your service is that you could also, once you've gained traction, normalize the data and create "the" benchmark to score testers. You can even splice by geographic region, etc. You could go further once you establish your service as the "industry" standard allow programmers themselves self-test and post (show off) their scores on resumes, linkedin, github, etc. in effect quantifying their qualifications. Could even explore a partnership with CodeAcademy downstream. What you need to do now is get some validation, a way to say your tests are sufficient and/or above average. Then you need to go to market and drive awareness, lots of outlets to seed this. I'd be happy to bounce some ideas with you. Would you mind checking out my app too? www.whisper.me thanks

nice work, like the simplicity. I agree with some of the users that the messaging can be massaged further but overall like where you're going. I've sent a link to your to a few folks including my little sister. Good luck!