I think it shows -- the NES games were a lot more fun, more imaginative, more colorful, and (the big test) did much better in the market over time.
If this same book had been written about (say) Star Raiders, it would have been shorter and pretty boring.
This is, at least in part, because of the relative social statuses of people who program things and people who do important work for the company.
One would think that game developers would be exquisitely sensitive to the needs of programmers because, hey, that is their business, but anecdotally they're treated pretty much like they are in the US: chew 'em up, spit 'em out, there will be more stupid boys to take their place next year. (I got a solicitation to work for a game company here by a recruiter who had heard of me from my ex-employers. I kid you not, the pay was $2k a month.)
(My first thought was, "well, the schools are better", but I went to high school for a year in Tokyo, and I did not touch a computer once. I has a scheme interpreter on a PalmOS device that I played with, and that was it.)
They aren't kidding. I think I remember this being a problem...
I always find this sort of DoS attack interesting. What would be the best way for an indie guy with a budget hosting to share an interesting article?
Publish like normal and accept that, if simultaneously on Slashdot and Reddit, you're doomed. If "doomed" is not an acceptable outcome for your online presence or if you have a greater-than-epsilon chance of going viral, don't use budget hosting. (Better options include a VPS or hosting environments which are not bottom-of-the-barrel.)
Or may be, if it's just a blog post, let Google(blogger) handle it.
Amazon Cloudfront with the cheap hosting as a custom origin. Use a CNAME like cached.domain.com and share that link. If the original link gets shared, you could at least change the links to images, css, and js to the cdn copy.