Link Details

The audio has some issues, but it looks pretty decent.

This tutorial is not that good. The guy spends 1/2 of the time debugging the code he's writing. It looks hacked together so it works, rather than actually being coded well. He probably read a book on physics/animation in Flash then spat that out.

Just another tutorial that teaches poor development with Flash. And people wonder why Flash has such a bad name on the net. If you're looking for some decent Flash tutorials, check out gotoAndLearn.com. The author (Lee Brimelow) is a very well respected individual in the Flash community, and he really knows what he's talking about.

Pax: I am not just regurgitating some book. I have been programming for over 15 years, have a B.S. in computer science, and am starting my Ph.D. in AI a couple of months. I have literally reverse engineered parts of the Flash player in PPC assembly, to make use of undocumented features. The code here is not perfect and squeaky clean as it would be if I took my time and re-factored it. However, the point of this series was to do it fast- most of the screencasts are a first take, of me just programming this stuff off the top of my head with little or no design or pre-planning. This is not supposed to be the quake engine here- it is a quick hack. If I took the time necessary to make this code shiny and nice, the videos would have taken much longer and would probably be even more boring than they are now.

All this said, this is NOT A TUTORIAL. It is a series of screencasts showing the complete process of making a game (although in a somewhat hurried fashion). If you want to learn how to write clean AS3, start by reading the Adobe Developer guidelines and other documentation, and take some classes on algorithms and data structures. If you want to learn a few basic concepts that will help you get started writing games in AS3, this series of videos may be more helpful than a tutorial, simply because it is a vide demonstration.

P.S. In the real world, programmers spend most of their time debugging.

Sorry mate, I'm a firm believer that if you're going to showcase something, you should do it right. Even more so when it is in areas like development. The majority of people who are going to check this out will be less skilled developers, who are likely to take bad practice and follow it. The only reason I checked this out is because I am a Flash developer, and I am constantly looking for other quality developers to hire or learn from.

I fully understand that a hefty amount of time will be spent debugging, but planning shouldn't be left out like that. Like it or not, people will use this as a tutorial or example (like you said) of how to make a game.

Rather than have it look like I'm just flaming you (not what I'm trying to do), I'll give you some constructive criticism. Try writing the code beforehand so you can copy it and eliminate the debugging from your screencasts. This will also make them shorter and easier to watch. If the example is about the complete process of making a game, show some of how you would plan the project, as this is arguably the most important part which is usually left out, or minimalized.