Re:How Super Mario Bros. 3 was made
by tpatke on Friday December 16, 2011 @09:34AM
(#3360787)
I love the picture of the programmers at the bottom of the page. Clearly not the best working conditions even though the office has nice desk space available (see background). Just shows how much more developers are respected now. ...thanks in part to these guys.
Re:How Super Mario Bros. 3 was made
by kabdib on Friday December 16, 2011 @10:11AM
(#3360895)
It's interesting to compare this to what we had at Atari. Typically the game would center around the engineers (for consoles, the software guys), and they'd be supported by artists and sound folks who were a shared resource amongst several programmers. There was usually no game designer per se, just a bunch of management.
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.
Re:How Super Mario Bros. 3 was made
by city41 on Friday December 16, 2011 @12:27PM
(#3361315)
Are you talking about the 2600 days or the 7800 days? From what I understand of Atari, the 7800 era was pretty lousy? But Atari sure put out some really great games for the 2600 considering the level of tech available.
Re:How Super Mario Bros. 3 was made
by InclinedPlane on Friday December 16, 2011 @06:21PM
(#3362774)
2600 games are easy enough to build with a small team and simple enough to have the game mechanics and story completely specified on, say, a single piece of paper. There isn't much room to have a complex story, and there isn't much ability to drift away from the proper story line (since there isn't much of one). By the time of the NES that had definitely changed.
Re:How Super Mario Bros. 3 was made
by enneff on Friday December 16, 2011 @08:05PM
(#3363004)
I love the picture also, but for a different reason. I spent some time writing games for the NES in 6502 assembly, and even with modern tools I couldn't fathom programming something as sophisticated as SMB3 for that platform. Many times I have ruminated on, and been inspired by, the very existence of these people and their remarkable accomplishments. To see a photo of the SMB3 programming team in their office _while they were writing the game_ gives me a thrill I can't really describe.
Re:How Super Mario Bros. 3 was made
by patio11 on Friday December 16, 2011 @10:35AM
(#3360964)
Without specific regards to Nintendo, you could visit a lot of offices here which have the "N programmers at N computers on one table" office layout, and they're frequently a wee bit underpowered. (In 2010 I was rocking XP and fighting to upgrade from 512MB to 1GB of RAM for Java development.)
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.)
Re:How Super Mario Bros. 3 was made
by jrockway on Friday December 16, 2011 @11:20AM
(#3361091)
Interesting. Is the job market different from the US, where there is a core group of actual programmers that want real money, and then a group of people that could theoretically pretend to be programmers, and will work for free?
(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.)
Re:How Super Mario Bros. 3 was made
by code_duck on Friday December 16, 2011 @12:47PM
(#3361396)
I was excited to read this, and the main site is still down... but I'm at a coffee shop and OpenDNS says "Sorry, but www.chrismcovell.com.nyud.net is blocked on this network."
Re:How Super Mario Bros. 3 was made
by iqster on Friday December 16, 2011 @01:32PM
(#3361651)
Like many of you (I suspect), I got into CS because of video games (had an Atari 2600, a C64 and an Amiga 500). Sometimes I get really nostalgic for the good old days. I came across a hilarious series called "Code Monkeys" a few years ago that seems appropriate to point out here ...
Re:How Super Mario Bros. 3 was made
by pjbeardsley on Friday December 16, 2011 @12:59PM
(#3361464)
It's crazy—I taught English in Japan circa 2002-2004, and those pages are laid out exactly the way our school newsletters were (and I'm guessing still are to this day). Right down to the oval portrait shot.
Re:How Super Mario Bros. 3 was made
by code_duck on Friday December 16, 2011 @12:47PM
(#3361399)
I can't read the article at the moment, but I was thrilled when I found out that the programmers, musicians and artists who made most of my favorite Sega Genesis and Master System games were using Amigas.
Re:How Super Mario Bros. 3 was made
by patio11 on Friday December 16, 2011 @10:52AM
(#3361013)
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.)
Re:How Super Mario Bros. 3 was made
by byoung2 on Friday December 16, 2011 @09:33AM
(#3360786)
What would be the best way for an indie guy with a budget hosting to share an interesting article?
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.
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.
Amazing.
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.)
http://en.wikipedia.org/wiki/Code_Monkeys http://www.g4tv.com/codemonkeys/index.html
They aren't kidding. I think I remember this being a problem...
http://webcache.googleusercontent.com/search?q=cache:YvdCxzu...
http://www.reddit.com/r/gaming/comments/nf659/how_super_mari...
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.