• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Nothing Beats the Feeling of Working Code!!!

D

Dragnov

Diamond Member
Well almost nothing 😉

I spent all day yesterday and today, pulling an all nighter working on my code. I'm so dead tired, but I finally got one section working!!!!! I'm so happy!!!!! 😀😀😀😀😀😀😀😀😀😀😀😀😀😀😀😀😀😀😀

Now only 2 more sections to go! 😛 I have till midnight.

I'm just so happy and needed to express my happiness. This is like my first time ever getting some fairly difficult code to work! Does everyone usually get excessively happy once they finally finish working code?! 🙂
 


<< I'm just so happy and needed to express my happiness. This is like my first time ever getting some fairly difficult code to work! Does everyone usually get excessively happy once they finally finish working code?! 🙂 >>


Yes! 🙂

I'm glad for ya.

Happy coding!
 


<< cool!

but... i disagree, getting a lot of money is an equal if not better feeling. >>



i agree, a large sum of money can make me cream.
 
When writing code, one spends 1/4th or less on writing the actual code, the rest of the time is spend on debugging.

Exception being an 'hello world!'-type of program, of course.

BTW, yakko: mental pleasure beats any form of physical pleasure 😉
 
I had this feeling yesterday as well... had a program due that we had to split up between three of us and do independantly and then put it all together.

So we put it all together, and it compiles right on the first shot, booyah... a.out... damn, segmentation fault... spent hours looking for the mistake only to realize that we were trying to display something from a null pointer, and we just kept overlooking that it had become null.

When we finally got it though, and realized that our spring break happened when we truned it in, we were all very happy people
 


<< When writing code, one spends 1/4th or less on writing the actual code, the rest of the time is spend on debugging. >>



Hmm, I hope you were being facetious! 75% of coding time spent on debugging sounds extremely high. If you have a solid design, debugging time should be marginal (depending on what you're writing).
 


<< no I would say 75% sounds about right. Maybe even a little low. >>



Then either you two have malformed perceptions of "debugging", or you don't know your language that well. Saying you're spending 75+% on debugging says you're only writing 25% working code. That's pretty poor. Now, if we're talking logic errors, that's a different story, but usually those aren't manifested until later. These could also be entirely eliminated through the use of a solid unit test built against the requirements of the class/module/routine anyway.

What languages are you using? I can't reasonably see spending that much on debugging in any language other than maybe asm.
 


<<

<< When writing code, one spends 1/4th or less on writing the actual code, the rest of the time is spend on debugging. >>



Hmm, I hope you were being facetious! 75% of coding time spent on debugging sounds extremely high. If you have a solid design, debugging time should be marginal (depending on what you're writing). >>



I agree, in most cases debugging should not be that time consuming. There are certain exceptions though, as in when I was translating some complex Hidden Markov Model code from Matlab (something I don't fully understand) to C++. I had to do a LOT of debugging and stepping through the code, making sure my values matched the matlab ones at every step along the way, because minor inconsistencies in the code would result in completely erroneous results in my program. Worse, certain errors would only show up under certain conditions, and so when I finally got my first test working (processing ~150MB of data), it still failed on the second data set.

Worse yet, we were manipulating multidimensional (up to 4 or 5 dimensions) matricies, so nearly each step in the program resulted in millions of numbers to compare. I obviously couldn't look at each number, but you can see why this was such a tedius and time consuming process.

That said, I was very relieved and happy when I was finished, but I'd surely give up that feeling for other carnal pleasures, or a million bucks. 😉
 


<< no I would say 75% sounds about right. Maybe even a little low. >>



Hmm, I spend 15% of my time writing code, 1-5% of my time debugging, and the rest goofing off and neffing. 😉 If I had to spend 75% of my time debugging, my head would pop.
 


<< mental pleasure beats any form of physical pleasure >>



Scary to say this, but I completely agree with Elledan.


Good job! So what's the project?


peace
sean
 


<<

<< When writing code, one spends 1/4th or less on writing the actual code, the rest of the time is spend on debugging. >>



Hmm, I hope you were being facetious! 75% of coding time spent on debugging sounds extremely high. If you have a solid design, debugging time should be marginal (depending on what you're writing). >>


Writing documentation takes the longest, but fixing bugs takes much longer than writing the actual code.

If fixing bugs truly was as easy as you say, then why do software companies spend so much time on it? 😛
 


<< << mental pleasure beats any form of physical pleasure >>



Scary to say this, but I completely agree with Elledan. >>


Scary to see that someone agrees with me 😉
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top