how do u know when 2 stop spending time on one code?

This is a discussion on how do u know when 2 stop spending time on one code? within the A Brief History of Cprogramming.com forums, part of the Community Boards category; expanding on the title, how do u know when 2 stop spending time on a code that is not working? ...

"What are you after - the vague post of the week award?" - SalemIPv6 Ready.Travel the world, meet interesting people...kill them.Trying to fix or change something, only guaruntees and perpetuates its existence.
I don't know about angels, but it is fear that gives men wings.
The problem with wanting something is the fear of losing it, or never having it. The thought makes you weak.E-Mail Xei

"Owners of dogs will have noticed that, if you provide them with food and water and shelter and affection, they will think you are god. Whereas owners of cats are compelled to realize that, if you provide them with food and water and shelter and affection, they draw the conclusion that they are gods."
-Christopher Hitchens

Well, lets get back on topic guys. I personally think that if you are having trouble with code, you shouldnt stop till you figure it out. If you want, put it on back burner for a while, and try to think about and learn the stuff you need to figure out a problem.

Originally posted by Salem Clearly, these are the last incoherent words of the recently deceased hussein brothers. No doubt more careful analysis of the rest of the message will reveal the last hiding place of the ace-of-spades himself

the length of time I work before I give up keeps increasing each year... I used to think 3 or 4 non-productive hours on an assignment was ridiculous, but here at work I just scrapped 2 weeks worth of code to go back to an earlier version. (Luckily, after a few changes the earlier version worked great!)