Jump to content
  • Advertisement
Sign in to follow this  
  • entries
    63
  • comments
    56
  • views
    44252

Tip of the day

Sign in to follow this  
rick_appleton

141 views

If you know there's bug in your code but you can't find it, then leave alone to the next day.

I spent the last two hours yesterday trying to fix a but which prevented from text displaying correctly. Couldn't find it. This morning I came in, took one look at the code, and found the problem. And I am not exagerating (sp?).

In other news, the trackeditor I'm making for the Brew contest is coming along quite nicely. I plan on having the first working track at the end of the week.
Sign in to follow this  


1 Comment


Recommended Comments

As a rule of thumb, if I can't solve a bug in less than 30 minutes, I walk away or do something else on the comp for about 30 minutes to an hour. It's kinda like defragging your brain, IMO. If you program long enough, you can start to lose track of stuff - that nice clean picture that was in your head just starts to disintigrate, and you have trouble remembering what this function does or what that class is for. I can always come back after my break and solve the bug like within 10 minutes. It's kinda freaky. I learned this the hard way too [smile]

Share this comment


Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!