BTW make sure you can apply H1b visa in England; maybe your first H1b visa (from F1) must be applied in China.
j*o
20 楼
这一干就得至少两年,555~~
【在 M***l 的大作中提到】 : 人没有选择的余地就只有接受。先干着呗,骑驴找马什么都不耽误。
S*8
21 楼
看来中印捆绑是以后的既定方针了
S*e
22 楼
GAE is indeed pretty bad -- I tried to move a small application onto it and it seems it is very slow and erroneous (due to slow processing). I use the free version http://elookinto.com.
从某个网站上面copy的,格式得你自己调一下;最后找个中国人帮你签字 THE PEOPLE’S REPUBLIC OF CHINA MARRIAGE CERTIFICATE (English Translation) XXX and XXX applied for marriage registration. After being examined, their application conforms to the Marriage Law of the People’s Republic of China. We give them the permission to register and hereby issue this marriage certificate. Ministry of Civil Affair of the People’s Repepublic of China ( seal) Special Seal for Marriage Register of Haidian District, Beijing Civil Affairs Bureau Marriage Register: (signature) XXX Certificate Holder: XXX Registration Date: xx/xx/xxxx Marriage Certificate No. XXXXXXXXX Name: XXX Sex: XX Nationality: Chinese Date of Birth: xx/xx/xxxx ID Card: xxxxxxxxxxxxxxxxxxx Name: XXX Sex: XX Nationality: Chinese Date of Birth: xx/xx/xxxx ID Card: xxxxxxxxxxxxxxxxxxx
you don't have to stick with this company for 2 years if you don't care about losing $3k-4k attorney fee. there is no contract and the employment is at will. as long as you can find a better pay job just leave. so if you are desperate and this is your only choice, then it's better than nothing. otherwise, try to negotiate a better deal. if negotiation fails, move on and continue job search.
just saw your post, sorry for the late. below is my 2 cents: It had to do with: Local development emulation was very slow -- their local server could only perform at a fraction of the speed as being deployed. Deploying an application to the google cluster was very slow -- it may take 5-10 minutes per deployment. I felt that application execution was unreliable -- actions such as reading and writing to the datastore would fail intermittently for no reason ( nothing related to the developers code), this applied to the google caching services as well. This made it very difficult to benchmark your application . It made it very difficult to find exceptions in logs available. Googles own uptime charts often lacked short term outage -- that led to bug reports from investors and users -- that developers were not able to address. In general it would work “95% of the time” for huge numbers of users -- but I felt like it was difficult to have consistent, reliable, reproducible performance. In any 24 hour period there would almost always be some number of “random failures” I hope that helps. This is just my opinion -- it does serve well for “ mostly” dealing with huge amounts of traffic. BUT -- you are charged by how much traffic you have -- so it can be very easy to have a very large monthly bill. One time I did something that accrued about $80 in charges in about 4 hours.
【在 b***i 的大作中提到】 : 请问你在哪方面遇到困难了吗?我正在用gae做项目。
g*g
82 楼
a3 is not that stupid to kill a winning platform. what to gain here?