3,569 karma · joined September 4, 2008
Mid-way through that three year visa, I quit, and created a consulting company. After consulting with an immigration lawyer, I was told it was "probably ok" to be the director of a company on an Engineering visa, so long as the primary thing I was doing was Engineering related. When my three year visa expired, I successfully had my own company sponsor it, and got another three year one, followed by a five year one. Last year, I successfully got PR here.
Its hard to say why you're continually getting one year visa renewals. If you're not already doing it, it could be worth having an immigration lawyer submit the application on your behalf. Because it was a cheap business expense (~80,000 JPY) compared to the cost of screwing something minor up, that's what I did for every renewal I did under my own company (for PR, I did it myself though).
I'd argue that Japan has a relatively friendly policy for skilled immigrants. To get a job as a developer here, all you need is a company that's willing to sponsor your visa and a university degree in a related field. As far as I'm aware, there's no onus on the company to prove they couldn't get a Japanese to fill the position, or quotas on the number of visas like there are in other countries (US for instance).
Furthermore, a great thing about Japanese working visas are that they aren't tied to a specific company, only the field of work (which they've made broader by combining several statuses into the Engineer/Specialist in Humanities/International Services visa category). This means once you have a visa here, you can easily switch jobs, and even if your company was to lay you off or you were to quit, you don't immediately need to return to your country.
What's more, Japan's introduced a points based system to give preferential treatment to highly skilled professionals. While the points they give create a bias towards someone coming from academia or working at a large well paying job, it makes it theoretically possible to get PR here without being married to a Japanese citizen after one year.
There are a lot of problems with Japan. I agree with you that the trainee visa is one big one. The lack of being able to get a clear answer about immigration status issues also makes it challenging, and encourages you to take a certain amount of risk in stepping into a grey area legally, which I understand will hold some people back. But for me personally, and other foreign entrepreneurs around me, it has made it possible to transition from being an employee to entrepreneur with relatively little investment compared to what is required in other countries.
If anyone is interested in more detail about transitioning from an engineer to entrepreneur here, I've written more about my experience here: http://www.tokyodev.com/2014/04/17/creating-company-japan/.
Japanese society classifies people as insiders or outsiders. The key I’ve found is to become active in some community where you can become an insider. For instance, I’ve been active in the Japanese Ruby community where I’ve found acceptance.
By this time they’ve maybe picked up up some basic Japanese but aren’t fluent. Becoming fluent in a language is quite challenging, especially if you’re working full time in an English language environment. Even without fluency, it’s possible to enjoy life here.
> I should mention that almost all of my open source projects have 100% code coverage. This is because most of my open source projects are smaller libraries and tools that are reusable in many different situations (a breakage could lead to a serious problem in a lot of consuming projects) and they’re relatively easy to get 100% code coverage on anyway.
Maybe you've never experienced any problems with the open source community. Personally, I know I never had. Even if most of us have positive experiences, there are some people who don't. These guidelines are trying to make it so less people have a bad experience in the future.
Having community guidelines doesn't kill a community. Hacker News itself has guidelines (https://news.ycombinator.com/newsguidelines.html), and I don't think we've suffered because of it. While the language of GitHub's guidelines is different, the goals seem very much the same.
Let's assume that GitHub is acting in good faith here, and trying to make things better for the community.
2) Integration with development tools like http://pow.cx/ or https://github.com/puma/puma-dev allow you to automatically startup and shutdown apps. This is useful when you're juggling multiple apps.
3) Security. Using a standard domain/port for local development opens you up to exploits like http://benmmurphy.github.io/blog/2016/07/11/rails-webconsole...
However, since then, I have found there is research that indicates diverse groups can be more advantageous than homogenous groups of highly talented people [1], [2]. So from this perspective, striving for diversity makes economic sense.
[1] http://www.pnas.org/content/101/46/16385.full
[2] http://www.scientificamerican.com/article/how-diversity-make...
Software developers in Japan have traditionally been undervalued, as it has been seen as a job as anyone can do with a little training. This has meant while there have been some really great Japanese software developers, there have been many more totally incompetent ones, bringing down the average level of software developers here.
In recent years though, there's been a mini-boom of startups here. These startups realise the value of talented developers, and are trying to attract them through hirer salary and better working conditions. While the pay isn't as good as the US (the weak yen makes them look even lower) and the working conditions aren't as good as Europe, things are defiantly heading in the right direction.
If you are someone who's been wanting to work as a developer in Japan, I've put together some resources here: http://www.tokyodev.com/jobs/
Part of the problem of any trade deal is that you'll end up pissing off one group at home to make another one more happy. Trade negotiators argue they need to have the deals be negotiated in secret or special interest groups will cause too much noise and trade deals will never get done.
Going from have a unilingual website to a multilingual one slows everything down. Now whenever you make a change to one of the strings in your app, you need to wait to have it translated before you can deploy a new version.
Furthermore, merely translating your service isn't enough, you need to localise it. To do this, you (or someone else) needs to understand your target market. This isn't something you can outsource (cheaply at least).
Finally, adding another language to your application means you need to do customer support in that language. This means the founders can no longer do support themselves, and you'll need to rely on a third party instead.
Think carefully before going down the multilingual path.
If you find a large percentage of accounts are shared, then maybe you should take a look at revising your pricing and segmenting on something else. Alternatively, you could look at adding functionality that makes having multiple user accounts more useful than just sharing one.
If it is just a few accounts, it's probably not worth your time worrying about it.
I add a hidden "spam" field to the form. When the form is submitted, I use Javascript to remove it. If the field is still present when sending to the server, flag the entry as spam. This has blocked all spam bots for us.
One thing you might be clear is whether the positions are for English speakers living in Japan, or if they are open to developers worldwide.
In my experience, most companies where Japanese isn't necessary still prefer people to already be in Japan, as bringing someone from abroad is seeing as more risky, as even if the candidate ends up liking the company, they still might not like life in Japan.
Sharing interests might be a nice secondary thing, but I would start with the kind of person you're looking for first.
For web applications where you don't care about content being indexed, I wouldn't worry about it being a javascript only application (and this is the direction lots of apps are heading with frameworks like Ember.js, Angular.js, and Meteor).
The organizers of that event probably know of companies in Vancouver who are looking for Python developers. You could also comb the attendee list and try to figure out what companies they are working for, as they'll probably be using Python.