Slashdot Mirror
Donkey Kong and Me
MBCook sends us to the blog of one Landon Dyer, who posted an entry the other day entitled Donkey Kong and Me. It describes how he was offered at job at Atari after writing a Centipede clone and ended up programming Donkey Kong for the Atari 800. It's full of detail that will be fascinating to anyone who ever programmed assembly language that had to fit into 16K, as well as portents of what was to come at Atari. "My first officemate didn't know how to set up his computer. He didn't know anything, it appeared. He'd been hired to work on Dig Dug, and he was completely at sea. I had to teach him a lot, including how to program in assembly, how the Atari hardware worked, how to download stuff, how to debug. It was pretty bad."
My first officemate didn't know how to set up his computer. He didn't know anything, it appeared. He'd been hired to work on Dig Dug, and he was completely at sea. I had to teach him a lot, including how to program in assembly
Without RTFA, I bet its a relative of an Atari bigwig.
Table-ized A.I.
Frankly, I enjoyed reading through TFA but I don't see how it's relevant. Sure it can be noted how all technology is doomed to failure, companies enjoy success before getting sloppy, and new, inexperienced, programmers are hired and must be mentored by experienced employees. But honestly, this article doesn't mean anything; it's history and anything that can be learned from it is common sense.
I've conversed with Landon online a couple of times over the years. He seems to be a super nice guy, and his blog is at times hilarious. My favorite two stories are the guy with no degree (who purports to have one) and repeatedly applies for a job, and another entry with an intimidating inscrutable bulging forehead genius who interviewed Landon for a job.
Not that it has direct relevance here, but if you haven't seen it, "The King of Kong" is a fantastic documentary about "Competitive Donkey Kong". It's the tale of a guy who has the gall to challenge the world record holder in Donkey Kong and the corruption in the competitive gaming industry. It's also fantastically funny and a great time to watch.
Highly recommend it if you're at all into gaming, but it's also a great social commentary to watch even with your non-gamer girlfriend/boyfriend.
After RTFA, you can watch some video of the game (here's the Atari 2600 version).
Possible kill screen coming up.
How I wish Atari had got that guy to teach everyone how to program the Atari 800 and 400. I had to teach myself from the most cryptic, sparse and often contadictory documentation. There was an "Internet" in the early 1980s, but practically no one had access (I did), so we depended on the few published books, occasional insights in magazines like COMPUTE!, Creative Computing and Byte.
It wasn't enough. Programming wasn't just hard because it required assembly code skills (or forth, hah!), but because it was completely hidden territory. There was no real way to get source code from the programs that some people managed to write and distribute, and certainly no obligtion for anyone to release it (except the occasional superficial magazine article).
The competing Apple ][+, IBM-PC and TRS-80, all had BBSes full of downloadable code (often including source). Their corporate vendors each published detailed programming guides. The TRS-80 was doomed because of the direction of its corporate parent (which should have stayed in the PC business, porting its OS on Intel HW when they all upgraded from 8 to 16 bits). But IBM and Apple survived, even thrived (as we all know), because it was easy to get in the programming game.
By the time Atari finally published its "De Re Atari", which was a good start (the source code to the OS), the small developer "community" had already chosen either Apple or PC. If Atari had taught us all how to program from the beginning, its superior hardware and attractive game platform would probably have left it a strong competitor to the PC, much as the Mac has. But we were all on our own, and our platformed disappeared.
The same dynamic is still true on new platforms. Make it easy to develop for it, and it will survive, even thrive.
--
make install -not war
Just to think I started programming that was a lot of memory, today code seems so bloated....
Wise men speak because they have something to say, Fools because they have to say something!!!!
definitely appropriate but not new.
I lol'ed when I saw it in TFA.
-- @rjamestaylor on Ello
So, what was it like to work with Bill Gates?
[rim shot]
It's Donkey Kong and I ;-)
Donkey Kong and Me
In the fall of 1981 I was going to college and became addicted to the Atari arcade games Centipede and Tempest. I knew a little bit about the hardware of the Atari 400/800 home computer systems, and decided to make a scary purchase on my student budget and buy an Atari 400 and a black and white TV (which was all I could afford). I messed around in Basic for a while, then bought an Assembler/Editor cartridge and started hacking away on a Centipede clone. I didnt have much to go on in terms of seeing prior designs for games and had to figure everything out myself. Like most of the school problems, you really just have to work things out with a few hints from the textbooks and lectures.
Anyone whos worked with that Asm/Editor cartridge probably bears the same deep emotional scars that I do. It was unbelievably slow, the debugger barely worked, and I had to remove comments and write in overlays of a couple K in order to squeeze in enough code. My game, which I called Myriapede, took about three months to write. I still have the original artwork and designs in my files; graph paper marked up with multi-colored pens, with the hexadecimal for the color assignments painstakingly translated on the side.
[I had to guess at colors. All I had was that cheap black and white TV, and I had visit a friends and his color TV for a couple hours in order to fine tune things].
The Atari Program Exchange (a captive publishing house) was holding a contest. The grand prize for the winning game was $25,000. Id spent a semester of college blowing off most of my courses and doing almost nothing except work on Myriapede. I finished it with a week or two to spare and submitted to the contest.
A few weeks after I mailed Myriapede off to the contest, I got a letter from Atari that said (1) they were very impressed with the work, but (2) it looked to them like a substantial copy of Centipede (well, it was) and that theyd rejected it for that reason. The subtext was they would probably sue me if I tried to sell it anywhere else, too. I was crushed. I wound up going to a local user group and giving a couple copies of it away; I assume that it spread from there. I hear that people liked it (best download of 1982 or something like that).
A few weeks later I got a call from Atari; they wanted to know if I was interested in interviewing for a job. I was practically vibrating with excitement. I flew out and did a loop, and made sure to show Myriapede to each interviewer; it was a conversation stopper every time. Until they saw it they kind of humored me (yeah, okay, you wrote a game), then when the game started up they started playing it, got distracted and (ahem!) had to be reminded that they were doing an interview! One of the guys I talked to was the author of Ataris official Centipede cartridge. He said on the spot that my version was better than his.
A couple weeks later they gave me an offer. Atari moved my single roomful of stuff out to California. I flew out and spent two weeks in a hotel waiting for my things to arrive; Atari wanted me out there real bad.
Now, there were two popular arcade games that I simply could not stand; the first was Zaxxon, a stupid and repetitive scrolling shooter. The second was Donkey Kong it was loud, pointless and annoying. Of course, the reason they wanted me in California was so I could work on a Donkey Kong cartridge. After a few moments of dispair (and faking enthusiasm in front of my bosses) I gritted my teeth, got a roll of quarters and spent a lot of time in the little arcade that my hotel had, playing the DK machine there and getting to know it really, really well.
I should explain how Ataris Arcade conversions group worked. Basically, Ataris marketing folks would negotiate a license to ship GameCorps Foobar Blaster on a cartridge for the Atari Home Computer System. That was it. That was the entirety of the deal. We got ZERO help from the original developers of the games. No listings, no talking to the engineers, no design documents
The ______ Agenda
And he's now hosting his blog on that very same Atari he used oh-so-many years ago.
Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
Interesting insight into the games of that era. Could have used a lot less ego stroking and more details, I wouldn't be all that proud of a port.
This was not funny at all.
Linux is only free if your time has no value. Windows is only free if you threaten to use Linux.
Apparently this blog is running on 16k, too.
-David
No shit, +5 funny? C'mon moderators -- not any completely unclever insult to MS/Gates/Balmer is funny.
"Orthodoxy means not thinking--not needing to think. Orthodoxy is unconsciousness." --Eric Blair
the best computer ever in the whole universe, except for virtually every other computer that has been produced since, was my Atari 600XL. Simple enough for a 5 year old to program in machine code, by copying long lists of poke statements out of the blue pages of antic magazine, this computer changed the way I saw the world. In fact, after only a few short years of sitting in front of a 27" inch TV typing in listings, the way I saw the world had become rather myopic.
Until I got my first Amiga of course. 68000 assembly language reads like a great literary work. Yes, the Amiga 500 with it's unix-like (but not *too* unix like) operating system and it's non-surface mounted giant chips named after *hot chicks*, and later, pregnant chicks, brought a 12 year old and his potentially permanently scarring soldering iron closer together than they had ever been before. Yes.. I got my first virus on an Amiga. It was so cool.. and so scary. Never before had I seen a virus! Don't share floppies kids!
Back then, there were also machines called "macs" which were identifiable by the fact that they used completely different hardware than a PC (stuff made by Motorola.. pfft.. a cellphone manufacturer. leave it up to them and we'll soon be computing on our cellphones!!) and completely different input devices. People said we would never learn to like mice... and they were right.
Well.. it's all gone kids. The mac doesn't exist anymore. Just PC's with unix-like operating systems, and PC's with Microsoft operating systems... and we still rate them on the same system... we fire up mame, and see how well they can duplicate the Donkey Kong experience.
I nearly beat level 2 today.
Barrels and other creatures are XOR'd onto the screen (I had some mask-and-repaint code at one point, but it was way too slow). Mario is a few player objects (three, I think). The "prize" objects (umbrellas, etc.) are the remaining players. The XOR graphics are pretty annoying to me, but most other people didn't seem to mind
Wasn't there a big lawsuit in the late 80's over using XOR for mouse cursors? If so, you had provable prior art right there. Then again, it was your competitor, Commodore that was under the gun, so wouldn't have benefited Atari.
Table-ized A.I.
That's what happens when you over-educate people: they learn all these great abstractions and ideas, and then have to do it the primitive way in the field. My first job out of college was programming in Fortran-66 (1966 standard), which had no IF blocks and WHILE loops, only GOTO's. The company didn't want to pay for a newer compiler. It was hard to accept; I was not ready for the real world and can relate to the poor FORTH dude. I hope he's making big bucks in a FORTH shop with plenty of RAM somewhere.
Table-ized A.I.
"MBCook sends us to the blog of one Landon Dyer, who posted an entry the other day entitled Donkey Kong and Me." Entitle: to furnish with proper grounds for seeking or claiming something titled: to designate or call by a title
Gah. That last post came out formatted differently than I had intended. Here's a correction: "MBCook sends us to the blog of one Landon Dyer, who posted an entry the other day entitled Donkey Kong and Me." Entitle: to furnish with proper grounds for seeking or claiming something. Titled: to designate or call by a title.
You must be new here.
vi +
Bill [G.] looked down on Steve [J.] because he couldn't actually program.
dig dug was the best arcade game of its time -- way more fun than donkey kong.
From the aticle: "After DK shipped, a cow-orker of mine got a copy of the source listing" So how do you ork a cow?
Indeed, had the original poster done some research, Atari employed Jobs who in turn outsourced work to Woz.
You DO know that Bill was a programmer, wrote for the Altair, and had a reputation for writing tight code, right?
Stating on Slashdot that I like cheese since 1997.
Yes, just because Bill became rich selling bloated code doesn't mean he likes bloat.
All his computing needs are covered by his x86_64 PC. The whole OS(MS-BASIC 64, written by himself in long-mode assembly) fits in 16kb, and he has never used more than 640kb of RAM.
He never uses Windows as evidenced in the Windows 98 presentation.
10 little-endian boys went out to dine, a big-endian carp ate one, and then there were -246.
I've done most of the stuff mentioned in that article so it was fun to read, but a bit light on horrific details.
I remember well the hundreds of pages of assembly language with no comments, the overloaded "server" machines which would grind for an hour if everybody hit "assemble" at the same time, RS232 downloads to the target machine, etc.
Crappy license deals, the "need something, anything, by next week" deadlines which meant that most games were much worse than they could have been, all standard fare in those days.
No sig today...
The only code I wrote that got in to the wild was some disk based copy protection. I wrote the loader using an interpreted C compiler (Deep Blue C), and some 6502 code - stored in duplicate sectors on a certain track. For example, track 5 would contain two sectors 7s, one sector 7 with valid 6502 code, the other with bogus code. The only way to read in the correct sector 7 was by reading the track sectors in reverse sequence, something no disk copy program would do, but the Deep Blue C code did (the code took advantage of the order in which sectors on a track were placed so as to optimize read times). The 6502 code was the loader (and de-mangler) for the rest of the program.
Of course, if I knew then what I know now, I'd have written Tetris and retired...
IBM doesn't play chess with the Universe.
Second hit on Google gives me:
Third hit on Google gives me:
Dude, I don't mean to be a dick, but... are you sure about this?