People seem to think there is only one answer to this question but companies need to figure out what is best for them depending on their employees, culture etc. Right now I think the core problem of remote work is verifying that people are in fact working efficiently. Also people really need to use better metrics to make judgments; parking lot 'emptiness' or even VPN access logs do not hold meaning if projects are on time, and the deadlines are not lax.
I have the note and i would have to agree with the article. I don't think "scribble some notes on a screenshot" is supposed to be a typical use case, it is just one that will demonstrate the benefit of a stylus quickly.Having used the stylus for a while I definitely prefer it and tend to miss it on other devices.
The stylus does have some lag to it and you have to get used to not seeing your writing show up immediately. When you see your writing hasn't showed up yet you tend to stop or slow down which isn't necessary, just keep writing and trust it will show up. I know that sounds terrible but it's really not.
I found it pretty terrible, but I didn't really commit to using the device, just played with it for awhile in the store.
Which is of course why the iPhone was so brilliant. Current stylus technology still can't create a paper-like, pleasant writing experience, while capacitive touchscreen technology can create a pretty good direct manipulation experience. People aren't going to commit to getting over the learning curve after the unpleasant in store experience just because of the theoretical advantages of the stylus.
Its not just the stylus technology: the screen themselves are glass. How often have you written on a glass? Maybe with a marker...
I'm used to the textured feel of paper and the pleasant friction b/w the pen and paper when writing on it. On glass, it just slips...
However, I guess that's just something of a habit. Maybe for future generations, brought up with touchscreen enabled laptops, it will feel more natural.
It's not just habit, writing is just easier on paper. The texture of the paper does two things while you're writing: provide continuous feedback and provide resistance. Delicate movements are a little bit easier when you have some resistance to work against. That's why steering wheels these days still have a lot of push back, even though they're electronic and could be designed to turn much more easily. Moreover, the feel of the pen moving across the textured paper gives the body an additional source of information about which direction the pen is moving in and how fast. This allows for more precise control versus just depending on sight and proprioception.
Many popular cars have electric power steering (most new Toyotas, many Chevys, even some BMWs). A sensor monitors the position of the wheel and drives an electric motor to turn the wheels. They're not completely fly by wire, because the motor augments a traditional mechanical linkage, but that goes back to wanting to maintain the feel of mechanical steering (and also to provide redundancy).
1. You probably won't get a visa to do devbootcamp (Since its educational it would require an F visa (devbootcamp can't help you).
2. With a BSc and and MSc in CS devbootcamp is not going to be of any use for you, get a book and a mentor and learn Rails yourself.
3. Companies can petition for your H1 for a future date no worries as long as the cap has not been exhausted, it is a regular occurrence. The problem will most certainly be how companies can accurately judge your abilities remotely. (People have cheated often on technical video conference interviews before)
Thanks for your comments. I agree that I can learn Rails myself, but I assume the dev bootcamp would be a good proof that I actually know it and I assume I could learn more in less time. Besides, if I learn it myself, I could come up with an idea and build a web app, but would that be enough for a company to consider me (specially when there are probably many developers already with professional experience trying to move to the Bay Area)?
About the H1 visa, the problem is that, according to what I read on the internet, it's estimated that it will be exhausted by July this year. In the meanwhile, I was also told that J1 visa is a possible alternative, but I haven't investigated that possibility yet.
If a company decides to hire me, but is afraid I might be cheating on a technical video conference, I wouldn't have any problems to go to the US for a face-to-face interview, even if I would have to pay the costs myself, simply because I don't cheat. If they are happy with me on a video conference, I'm sure they would be happy after a face-to-face interview.
I think if you learn Rails, build an app in it, and open-source it on GitHub or similar, that would be fairly strong evidence that you know what you're doing.
If I were in your position, I would go to the source ( http://www.uscis.gov/ ) and examine the visa categories that are available to you. Immigration law is complicated, but not as complicated as, say, the tax code. If you've completed a Masters in CS, you can probably navigate it yourself. Protip: Do not lie or mislead USCIS or USCBP (i.e. customs) as you can be banned from the country easily.
Unfortunately it may be very difficult for you to get a visa to DevBootcamp as it's almost certainly not a SEVP-certified school, so ICE / USCIS won't grant visas to people to attend, and you can't just get a tourist visa if you're intending to study. I would instead learn Rails yourself, start / open source a project, and try to get a job offer here with a company that will help with your visa situation (once you have a job offer, immigration becomes much easier as long as the company is game). I guess my main question becomes, is DevBootcamp the only reason you want to move to the US?
I'm an immigrant from Canada but I'm more familiar with family-based immigration as that's how I came across (fiance visa).
Dev Bootcamp is not the only reason I want to move to the US and that's why I posted this question. My main goal is to have an interesting job in the US, but I was in doubt between applying for an iOS developer job from London or go for the dev bootcamp first and then look for a job where I could eventually use my knowledge on iOS and Rails, as I think it would be a good combination. I'm starting to be convinced that I should go for the first option and I'll continue learning Rails on my free time.
Yes unfortunately the option to learn on your own and apply for a job in the US is your best bet. Immigration law in the US is very strict and confusing. Focus on getting a good job offer and once you are inside the US, you can try and get your employer to file for your permanent residency.
Its not as simple as that. No company would let you pay for your own flights because it reflect badly on them and how they treat their talent, at the same time they most definitely will be reluctant to fly you from abroad to interview. Hiring is not so cut and dry, although you may have the best technical abilities they may reject you simply because of bad cultural fit.
devbootcamp is clearly not an option for you, i suggest you take spoom's advice and open source a project you can be proud of in Rails. Then maybe attend some conferences in the US, and try and network to seek jobs. I believe you can get a B1 visa to attend conferences and you should be legally allowed to interview, although IANAL so double check.
This is one way of looking at it, a dissenting view: Because Google is so integrated gmail,google docs, etc -> You are sitting in a restaurant that serves Italian and Mexican food, across the street is another Italian restaurant, where would you go to eat?
Quite a few unshipped. I think there ought to be a difference between unfinished and unshipped. My projects are unshipped by which i mean I finished them but couldn't commit the time to market/sell them.
Eventually you learn: If you build it they will come; If you are lucky.
I feel like this is not so hard to do with NodeJS and Web sockets.
Small NodeJS app that serves the client connection webpage and acts as a proxy. Set the proxy locally, When you get requests instead of fetching them ask the socket for the data and headers.
On the client just do an XMLHttpRequest for whatever and shove it back down the web socket to the proxy server. Done, Right? I'll do a little experiment when i have time...
