What the hell were you doing coding for 7 hours in the first place straight?
Printable View
What the hell were you doing coding for 7 hours in the first place straight?
Hey, there's nothing wrong with 7 hours of coding! Last year there were days where I put in 8 or more hours on my senior project, with the only breaks being for food and going to class... besides the deadlines, once I got started coding, I couldn't stop til I got the function or module to work! :D
So maybe I'm just a geek....
Thats an entire day though! if you're rushing school maybe thats an acceptable answer. But 7 hours.... Thats a long damn time!
I do about 8 straight hours of coding 5 days a week. What's so strange about that?:eek:
For real-world projects, professionals spend a lot more time than a full day coding.Quote:
Originally posted by ZakkWylde969
Thats an entire day though! if you're rushing school maybe thats an acceptable answer. But 7 hours.... Thats a long damn time!
It's different if you're doing it for a job other than a hobby though.
Hey, when you're taking 14 hrs with half of them being upper-level CS classes, and have to log at least 20 hrs/week on senior project, and trying to get A's in all your classes... well you just can't get around it. Believe me, any spare time I have is NOT spent coding! :)Quote:
Thats an entire day though! if you're rushing school maybe thats an acceptable answer. But 7 hours.... Thats a long damn time!
At least during the summer I *only* work 40 hrs/week, and actually have evenings and weekends free...
As for getting a life... maybe when I get out of school :D Besides, if we were all extroverts, who would have the patience to sit in front of a computer all day and write the programs the rest of the world uses every day?
hmmm... I think I remember saying something like this a while back..... eh whatever.Quote:
Originally posted by ZakkWylde969
It's different if you're doing it for a job other than a hobby though.
If it's compiler errors, or you can't get the code to run- then don't quit until you can get it to compile and run.Quote:
Originally posted by Commander
expanding on the title, how do u know when 2 stop spending time on a code that is not working? or how long does it take 4 u 2 'give up'.
it just took me 7 hours of straight worthless coding (+ the other countless hours b4) to realize it was time to stop and be happy with what i have.
stupid java :mad: this just refreshed my memories about why i hated java in the first place. :/
If it's not working because there's too many bugs, then chances are you should start over(that's if you've already put a good amount of time and effort into actually debugging the program), or quit if you're not concerned with finishing the program.
Java is much easier to debug than c++, so you shouldn't complain that it's the languages fault.
Currently I only do it as a hobby. I am currently creating my own sockets library to handle stream connections online, and hope to make it IPv6 compatible under MS specification. I've logged about 6 to 9 hours on memory managment & SEH (Structured Exception Handling) alone. To me, there is nothing unusual about spending great sums of time coding on one thing.Quote:
Originally posted by ZakkWylde969
It's different if you're doing it for a job other than a hobby though.
Usually if I spend long periods of time coding, the result needs to be debugged endlessly for about that same length of time. It's much easier to just do it in small increments.