I agree wholeheartedly. This is a great book that is truly terrifying because Dick is constantly subverting the characters’ (and reader’s) perceptions of reality. He does this to an even greater degree in The Three Stigmata of Palmer Eldritch.
I was lucky enough to study in the same lab as the author while he was doing his doctorate. Graham has a real talent for explaining complicated concepts in a way that's easy to understand. He's also strongly committed to putting as much of his code and data as he can online so that anyone can play around with it, including people who aren't academics.
My experiences during my first job at an investment bank were very similar to with what you described. I was surprised by how high the turnover was, but also by how easily it was to get re-hired. It seemed very common to switched to another firm for a few years and then decide to come back.
Upon reflection, I definitely felt that the first few years were a test to see how much of your time you were willing to let the job consume. There was overt pressure to work long hours and come in on weekends, but ultimately people who wanted to maintain better balance between work and personal time ended up leaving of their own volition rather than being forced out.
I don't think it's so surprising that personality and likability are valued so highly for entry-level hires. These institutions are so large and bureaucratic that there's a real limit to what one person can do, especially early in their career.
Thank you for the links, they were very informative. I also found the article a bit cursory. I was particularly surprised that they didn't mention Japan's construction industry. It makes up a much larger part of the economy than in countries like the United States or the United Kingdom, and it exerts a lot of political power. A large number of the laws promoting new construction over renovation or purchase of existing buildings benefit the construction industry more than property owners.
I recommend Alex Kerr's Dogs and Demons for a more detailed discussion of real estate and zoning laws in Japan.
It becomes prohibitively expensive to own cars for a long time here in Japan because the government mandates regular inspections, which can cost up to $1000 USD. The period of validity for the inspection depends on the type of vehicle, but in general an inspection on a new car is valid for two to three years and must be done every year or two after that.
The decision not to manage "nicknames" (通称名) under the new immigration law because they aren't necessary from an administrative standpoint is illustrative of the disconnect between the people making these laws in Japan and the people that are subject to them. I realize that this is inevitable because foreign residents can't vote, but it's frustrating that the government doesn't seek input from them when formulating new policy that will have large effects on them.
Because of the difficulties in using foreign names with Japanese computer systems and paperwork that you mentioned, 通称名 ("nicknames") are essential for many foreign residents. Some groups have been using them for decades now, so even a cursory attempt to get feedback on the new laws would have identified this problem.
Still, some groups of special permanent residents have organized and successfully overturned some of the more odious aspects of the immigration law, like the fingerprinting requirement for alien registration. In particular, the Korean special permanent resident community has some degree of influence on policy because of their size and organization.
Given the general ignorance of the central government (and the immigration bureaucracy as a whole) towards the real needs of foreign residents, I see this decision as ignorance on the importance of 通称名 rather than an attempt to quash the rights of foreign residents. In my experience the local governments tend to be more sympathetic towards the actual needs of foreign residents, perhaps because they have more prolonged interaction with them. (Though as with every government organ in Japan, the interpretation of the law varies wildly depending on which clerk you interact with.)
Troubles like the ones you describe are a large part of why I registered 長瀬ダニエル as a 通称名 and use it for everything I possibly can.
Anyone who lives in Japan can register a legal alias, regardless of their citizenship. The special permanent residents that you mentioned (who typically hold North / South Korean or Chinese citizenship) are probably the most common users, but some Japanese people who are divorced use them, too.
An alias with Kanji is really useful for living in Japan. I'm an American citizen but I use an alias with a Kanji last name for just about everything I can (including my job, bank account, and apartment contract). Immigration paperwork and credit cards are just about the only things where the alias can't be used.
Thank you for this! I've heard similar things from a friend who is knowledgeable about wine. Enjoying good wine seems similar to enjoying good coffee or beer; price is more of a reflection of the limited markets for specialized styles and costs of transporting from the country of production than a simple function of quality. You certainly don't need to spend much to find something good if you are willing to look around a bit.
Another good book on North Korea is B.R. Myers' "The Cleanest Race." While it's not focused on history or defectors specifically, it does offer unique insight on the formation of the North Korean state and the rationale behind its actions.
This is a fun visualization, but as you mentioned it's inaccurate precisely when you need it most (when there's a delay). Actually, some JR stations in Osaka already have an indicator that shows when incoming trains are stopped at the previous station or whether they are in between stations.
For frequent trains like like loop lines and subways in major cities, you can generally expect them to arrive when scheduled. These arrive every few minutes, so anything longer than a minute is perceived as a delay. These will be reported and apologized for.
For trains like JR that run longer distances and less frequently, delays of 15-20 minutes due to accidents or weather can happen. This seems to happen once every few months or so.
Having worked with a lot of Japanese programmers, this rings true, but I think it says more about how Japanese companies are run than anything else. There are a couple of interrelated factors that come together here. Typical Japanese companies tend to be very conservative in regard to established technologies. Also, lack of timely Japanese-language materials only makes the problem worse. Even if there is official documentation or an O'Reilly book in Japanese, not having the surrounding ecosystem of blogs and tutorials makes it pretty hard to get familiar with a new technology. Even for mature technologies, the documentation for the newest release or the newest editions of books may not be translated for a while, which further slows things down. Of course, this problem isn't limited to Japanese.
At the small Japanese company where I worked there was a pretty stiff resistance to using full-blown web frameworks. The main argument was that it would take too much time to train people to use the framework, and that open-source frameworks were somehow unreliable. So they ended up poorly re-inventing several wheels (like using plain text files and locking for storing data, or a crude templating system) without first checking out the available open-source alternatives. It often felt like we were working at the wrong level of abstraction. On a more practical note, most of our clients used shared hosting with such draconian limitations and ancient server software that it would have been pretty difficult to use some of the modern frameworks even if we'd wanted to. (Think servers with PHP 4 and FTP access only.) I don't think everywhere is as bad as that was, but in my experience not-invented-here syndrome seems to be pretty common here in Japan.
FST's are used a lot in natural language processing, for example in speech recognition and dialogue systems. In these cases the state transitions are given probabilities (weights), which makes it a weighted FST.
Sometimes I used FSM's during the design phase of a project to model system behavior, but I'd end up implementing them pretty crudely with spaghetti code or case statements. Looking back, it would have made more sense to explicitly implement the FSM in the code.
One cellular phone company in Japan used to allow people to register e-mail addresses with two periods in a row before the @ character. I have seen some addresses like this in the wild, but the decision to mark these as valid or not for an app depends on the domain you're working in. At my old job making web apps for Japanese companies, programmers would usually allow these types of addresses if we were making a mobile site.
I found this to be a good overview of the Ph.D. system from a CS perspective. I'm doing grad school in a slightly different field, but a lot of the advice was applicable.
I've had a similar experience. The Kindle gets the job done, but I find myself using my iPad (or even iPhone) to read Kindle content most of the time now.