A happy programmer
-
when after hours and hours of debugging you find the root of the bug in your code.
-
Clear requirements, sane deadlines, reliable hardware and software, a reasonably free hand to admin his own machine, and time-and-a-half for overtime.
When posting here, I do not represent anybody but myself.
-
when after hours and hours of debugging you find the root of the bug in your code.
-
when after hours and hours of debugging you find the root of the bug in your code.
-
For myself?
- Stable requirements;
- A clean development environment;
- Absolutely no interference from management!
(This message is programming you in ways you cannot detect. Be afraid.)
-
Why did you post this in the "Hall of Shame"?
-
It think when my code runs as intended
-
A happy program. :laugh: But I guess, the very best stable program. ;)
Sir.Dre
-
It makes me happy to see what I consider to be a simple elegant snippet of code. For example, I wanted to generate morse code for a microcontroller and found a simple 26 byte array indexed by character with each byte describing the dots and dashes of morse for that character.
73
-
...when I get in at least 2 hours without hearing: "I don't mean to disturb you, but...."
-
The tools to do a job and the authority to do what needs to be done. A job that is challenging and when done makes them better at their craft. Clear goals and a job that matters. I highly recommend "Drive" by Daniel Pink. Or, if you're in a hurry check out the video from RSA Animate. http://www.youtube.com/watch?v=u6XAPnuFjJc[^]http://www.danpink.com/drive[^] -JimR
-
A happy programmer is the one that does not need to program anymore. The happy programmer programs for fun on his own pace.
"To alcohol! The cause of, and solution to, all of life's problems" - Homer Simpson