Comments on: The art of debugging

By: Emanuele Feronato’s Art of Debugging « The Asylum

Emanuele Feronato’s Art of Debugging « The Asylum — Fri, 05 Mar 2010 06:24:19 +0000

[...] via The art of debugging : Emanuele Feronato – italian geek and PROgrammer [...]

By: Thomas (I'm finally back!)

Thomas (I'm finally back!) — Mon, 29 Jun 2009 09:04:14 +0000

@ Matt

You closed flash and your new code wasn’t saved, so it worked perfectly. :D

By: header

header — Mon, 29 Jun 2009 02:42:18 +0000

This is a great help thanks for the tips, i am really interested in debugging so i view this and i am happy to be here to learn. You can visit this squeeze page i hope this helps.

By: pault107

pault107 — Sun, 28 Jun 2009 16:56:58 +0000

@Matt

I’ve been a Flash developer for almost ten years and I can honestly say that the same thing has happened to me around twenty times.

Very frustrating. Especially as you start to lose faith in the Flash IDE and restart when it is in fact a real bug.

By: Link Dump Sunday (June 28th, 2009) - Porter’s World

Link Dump Sunday (June 28th, 2009) - Porter’s World — Sun, 28 Jun 2009 15:49:02 +0000

[...] Manipulating Mp3’s: Learn how to reverse mp3’s with AS3, pretty neat. 2.) The Art of Debugging: Learn the ins and outs of debugging with this expansive explanation. 3.) Improve Your Game Over [...]

By: Matt

Matt — Sat, 27 Jun 2009 18:38:02 +0000

I had a bug a couple days ago that appeared for the sake of appearing. It spent hours rewriting code trying to find the problem and fix it. I finally got frusterated and closed flash. The next time I opened flash, my code worked perfectly. It was a bug with flash, not my code.

By: Wackiegames

Wackiegames — Sat, 27 Jun 2009 12:24:34 +0000

Good post, really enjoyed reading it :D

By: Joel

Joel — Sat, 27 Jun 2009 10:59:04 +0000

I can usually tell where it went wrong (usually where I added new code). So I just tinker, repair, replace or scrap.

Optimization however is where my abilities are lacking, a guide on that could be very useful AS2/AS3 please :)

By: Xodus

Xodus — Sat, 27 Jun 2009 08:34:27 +0000

I liked this post because it is used for every programmer, regardless of how they are making their game. I look forwad for more posts like this, maybe one on optimization?

Anyway, really nice and simple post!

By: Vlad

Vlad — Fri, 26 Jun 2009 21:20:40 +0000

Although I appreciate the irony, I have to say that if you iron the irony off (no pun intended) a lot of good advice is written here.

As an example, in your point 1, if what I’m experiencing or being reported is that a bug happens sometimes and I’m clueless about it, I don’t attack it immediately, I leave it there, open a ticket on our system (sounds fancy but it’s just a shared google document) so I don’t forget it and let it happen time and time again. Sooner or later I’ll have an Eureka moment “Ah! I know what’s going on!” and fix it, usually quickly.

I admit I don’t have a strategy apart from having a bug tracking document and a load of TODO lines commented everywhere inside my code and not actively chasing bugs. That’s how I organize myself and coding keeps flowing without hickups. The whole process is painless even when there are a lot of bugs around. Then I take a day off, refactor the code and debug it and it’s nice clean for the next cycle.