My Personal Hell
-
Okay, let me start by stating that while I consider myself "proficient" within the programming and scripting technologies I am familiar with, I would in all likelihood be at the lower end of the food chain at any given programmers conference. Nonetheless, consideing the collective brain trust in here I figured I'd raise a question; Have any of you experienced feeling immense joy in accomplishing a feat that is on the very edge of your programming capabilities, only to feel shame and/or irritation when revisiting the same piece of code a short while later - in the realisation that said code could be written to run n times faster, or utilizing r times less resources? Happens to me frequently. So many times have I revisited code I wrote but a few weeks earlier, only to think "what drugs was I on while writing this crap???". Frustrating. //L
-
Okay, let me start by stating that while I consider myself "proficient" within the programming and scripting technologies I am familiar with, I would in all likelihood be at the lower end of the food chain at any given programmers conference. Nonetheless, consideing the collective brain trust in here I figured I'd raise a question; Have any of you experienced feeling immense joy in accomplishing a feat that is on the very edge of your programming capabilities, only to feel shame and/or irritation when revisiting the same piece of code a short while later - in the realisation that said code could be written to run n times faster, or utilizing r times less resources? Happens to me frequently. So many times have I revisited code I wrote but a few weeks earlier, only to think "what drugs was I on while writing this crap???". Frustrating. //L
All the time, but I am starting on a low base line! :)
------------------------------------ No Good Deed Goes Unpunished Clare Boothe Luce
-
Okay, let me start by stating that while I consider myself "proficient" within the programming and scripting technologies I am familiar with, I would in all likelihood be at the lower end of the food chain at any given programmers conference. Nonetheless, consideing the collective brain trust in here I figured I'd raise a question; Have any of you experienced feeling immense joy in accomplishing a feat that is on the very edge of your programming capabilities, only to feel shame and/or irritation when revisiting the same piece of code a short while later - in the realisation that said code could be written to run n times faster, or utilizing r times less resources? Happens to me frequently. So many times have I revisited code I wrote but a few weeks earlier, only to think "what drugs was I on while writing this crap???". Frustrating. //L
-
Okay, let me start by stating that while I consider myself "proficient" within the programming and scripting technologies I am familiar with, I would in all likelihood be at the lower end of the food chain at any given programmers conference. Nonetheless, consideing the collective brain trust in here I figured I'd raise a question; Have any of you experienced feeling immense joy in accomplishing a feat that is on the very edge of your programming capabilities, only to feel shame and/or irritation when revisiting the same piece of code a short while later - in the realisation that said code could be written to run n times faster, or utilizing r times less resources? Happens to me frequently. So many times have I revisited code I wrote but a few weeks earlier, only to think "what drugs was I on while writing this crap???". Frustrating. //L
-
Okay, let me start by stating that while I consider myself "proficient" within the programming and scripting technologies I am familiar with, I would in all likelihood be at the lower end of the food chain at any given programmers conference. Nonetheless, consideing the collective brain trust in here I figured I'd raise a question; Have any of you experienced feeling immense joy in accomplishing a feat that is on the very edge of your programming capabilities, only to feel shame and/or irritation when revisiting the same piece of code a short while later - in the realisation that said code could be written to run n times faster, or utilizing r times less resources? Happens to me frequently. So many times have I revisited code I wrote but a few weeks earlier, only to think "what drugs was I on while writing this crap???". Frustrating. //L
The silver lining to that thought is that you are a good enough programmer now so that it's easier not to make the same mistakes in the future. If you revisit code a year after is was "finished", and think you could do a lot better, then you have the drive and motivation to do so. Whether or not you have the time is a completely different matter altogether.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
Okay, let me start by stating that while I consider myself "proficient" within the programming and scripting technologies I am familiar with, I would in all likelihood be at the lower end of the food chain at any given programmers conference. Nonetheless, consideing the collective brain trust in here I figured I'd raise a question; Have any of you experienced feeling immense joy in accomplishing a feat that is on the very edge of your programming capabilities, only to feel shame and/or irritation when revisiting the same piece of code a short while later - in the realisation that said code could be written to run n times faster, or utilizing r times less resources? Happens to me frequently. So many times have I revisited code I wrote but a few weeks earlier, only to think "what drugs was I on while writing this crap???". Frustrating. //L
Constantly. Though once in a while, I'm also suprised to find that I've written a piece of code of such decent quality that it balances things out!
It definitely isn't definatley
-
The silver lining to that thought is that you are a good enough programmer now so that it's easier not to make the same mistakes in the future. If you revisit code a year after is was "finished", and think you could do a lot better, then you have the drive and motivation to do so. Whether or not you have the time is a completely different matter altogether.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
Okay, let me start by stating that while I consider myself "proficient" within the programming and scripting technologies I am familiar with, I would in all likelihood be at the lower end of the food chain at any given programmers conference. Nonetheless, consideing the collective brain trust in here I figured I'd raise a question; Have any of you experienced feeling immense joy in accomplishing a feat that is on the very edge of your programming capabilities, only to feel shame and/or irritation when revisiting the same piece of code a short while later - in the realisation that said code could be written to run n times faster, or utilizing r times less resources? Happens to me frequently. So many times have I revisited code I wrote but a few weeks earlier, only to think "what drugs was I on while writing this crap???". Frustrating. //L
Yes, all the time... When I'm looking through software I wrote five years ago... The usual thought is something like, "What the #*%$@## was I thinking?"
Proud to have finally moved to the A-Ark. Which one are you in? Author of Guardians of Xen (Sci-Fi/Fantasy novel)
-
Okay, let me start by stating that while I consider myself "proficient" within the programming and scripting technologies I am familiar with, I would in all likelihood be at the lower end of the food chain at any given programmers conference. Nonetheless, consideing the collective brain trust in here I figured I'd raise a question; Have any of you experienced feeling immense joy in accomplishing a feat that is on the very edge of your programming capabilities, only to feel shame and/or irritation when revisiting the same piece of code a short while later - in the realisation that said code could be written to run n times faster, or utilizing r times less resources? Happens to me frequently. So many times have I revisited code I wrote but a few weeks earlier, only to think "what drugs was I on while writing this crap???". Frustrating. //L
It doesn't need to be weeks, just one or two days is sometimes enough. As Michael Jackson told... you are not alone! :-O
Regards. -------- M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpfull answers is nice, but saying thanks can be even nicer.
-
Okay, let me start by stating that while I consider myself "proficient" within the programming and scripting technologies I am familiar with, I would in all likelihood be at the lower end of the food chain at any given programmers conference. Nonetheless, consideing the collective brain trust in here I figured I'd raise a question; Have any of you experienced feeling immense joy in accomplishing a feat that is on the very edge of your programming capabilities, only to feel shame and/or irritation when revisiting the same piece of code a short while later - in the realisation that said code could be written to run n times faster, or utilizing r times less resources? Happens to me frequently. So many times have I revisited code I wrote but a few weeks earlier, only to think "what drugs was I on while writing this crap???". Frustrating. //L
I feel your pain. :)
“Follow your bliss.” – Joseph Campbell
-
Okay, let me start by stating that while I consider myself "proficient" within the programming and scripting technologies I am familiar with, I would in all likelihood be at the lower end of the food chain at any given programmers conference. Nonetheless, consideing the collective brain trust in here I figured I'd raise a question; Have any of you experienced feeling immense joy in accomplishing a feat that is on the very edge of your programming capabilities, only to feel shame and/or irritation when revisiting the same piece of code a short while later - in the realisation that said code could be written to run n times faster, or utilizing r times less resources? Happens to me frequently. So many times have I revisited code I wrote but a few weeks earlier, only to think "what drugs was I on while writing this crap???". Frustrating. //L
Media2r wrote:
feel shame and/or irritation when revisiting the same piece of code a short while later - in the realisation that said code could be written to run n times faster, or utilizing r times less resources?
If you didn't, you're either the absolutely perfect coder (who doesn't exist) or you've stagnated.
I wanna be a eunuchs developer! Pass me a bread knife!
-
Okay, let me start by stating that while I consider myself "proficient" within the programming and scripting technologies I am familiar with, I would in all likelihood be at the lower end of the food chain at any given programmers conference. Nonetheless, consideing the collective brain trust in here I figured I'd raise a question; Have any of you experienced feeling immense joy in accomplishing a feat that is on the very edge of your programming capabilities, only to feel shame and/or irritation when revisiting the same piece of code a short while later - in the realisation that said code could be written to run n times faster, or utilizing r times less resources? Happens to me frequently. So many times have I revisited code I wrote but a few weeks earlier, only to think "what drugs was I on while writing this crap???". Frustrating. //L
Absolutely! With my coding. With my books and columns. With my songwriting. Pretty much anything / everything I've ever created. I think your experience is a positive thing. If you can't look back on stuff you did in the past and cringe a little, it means you're not growing in your art. The day you should start worrying is when you look back and feel comfortable that absolutely no improvements could be made. :)
Christopher Duncan www.PracticalUSA.com Author of The Career Programmer and Unite the Tribes Copywriting Services
-
Okay, let me start by stating that while I consider myself "proficient" within the programming and scripting technologies I am familiar with, I would in all likelihood be at the lower end of the food chain at any given programmers conference. Nonetheless, consideing the collective brain trust in here I figured I'd raise a question; Have any of you experienced feeling immense joy in accomplishing a feat that is on the very edge of your programming capabilities, only to feel shame and/or irritation when revisiting the same piece of code a short while later - in the realisation that said code could be written to run n times faster, or utilizing r times less resources? Happens to me frequently. So many times have I revisited code I wrote but a few weeks earlier, only to think "what drugs was I on while writing this crap???". Frustrating. //L
I do this every time I take on a new platform.
John
-
Okay, let me start by stating that while I consider myself "proficient" within the programming and scripting technologies I am familiar with, I would in all likelihood be at the lower end of the food chain at any given programmers conference. Nonetheless, consideing the collective brain trust in here I figured I'd raise a question; Have any of you experienced feeling immense joy in accomplishing a feat that is on the very edge of your programming capabilities, only to feel shame and/or irritation when revisiting the same piece of code a short while later - in the realisation that said code could be written to run n times faster, or utilizing r times less resources? Happens to me frequently. So many times have I revisited code I wrote but a few weeks earlier, only to think "what drugs was I on while writing this crap???". Frustrating. //L
Realizing that you are not and don’t need to be a “Genius” and you probably aren’t the sharpest pencil in the box is very important for every professional. So yes, it happens to me too, time to time. :)
The narrow specialist in the broad sense of the word is a complete idiot in the narrow sense of the word. Advertise here – minimum three posts per day are guaranteed.
-
Okay, let me start by stating that while I consider myself "proficient" within the programming and scripting technologies I am familiar with, I would in all likelihood be at the lower end of the food chain at any given programmers conference. Nonetheless, consideing the collective brain trust in here I figured I'd raise a question; Have any of you experienced feeling immense joy in accomplishing a feat that is on the very edge of your programming capabilities, only to feel shame and/or irritation when revisiting the same piece of code a short while later - in the realisation that said code could be written to run n times faster, or utilizing r times less resources? Happens to me frequently. So many times have I revisited code I wrote but a few weeks earlier, only to think "what drugs was I on while writing this crap???". Frustrating. //L
That's a very common occurrence. I haven't found any code I couldn't write better the second or third time around.
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
-
Okay, let me start by stating that while I consider myself "proficient" within the programming and scripting technologies I am familiar with, I would in all likelihood be at the lower end of the food chain at any given programmers conference. Nonetheless, consideing the collective brain trust in here I figured I'd raise a question; Have any of you experienced feeling immense joy in accomplishing a feat that is on the very edge of your programming capabilities, only to feel shame and/or irritation when revisiting the same piece of code a short while later - in the realisation that said code could be written to run n times faster, or utilizing r times less resources? Happens to me frequently. So many times have I revisited code I wrote but a few weeks earlier, only to think "what drugs was I on while writing this crap???". Frustrating. //L
I have never had this happen to me. All my code is always optimum. In fact, without fail, my code uses negative processor cycles thus making the machine run faster the harder my applications are run ;-)
-
I have never had this happen to me. All my code is always optimum. In fact, without fail, my code uses negative processor cycles thus making the machine run faster the harder my applications are run ;-)
-
Okay, let me start by stating that while I consider myself "proficient" within the programming and scripting technologies I am familiar with, I would in all likelihood be at the lower end of the food chain at any given programmers conference. Nonetheless, consideing the collective brain trust in here I figured I'd raise a question; Have any of you experienced feeling immense joy in accomplishing a feat that is on the very edge of your programming capabilities, only to feel shame and/or irritation when revisiting the same piece of code a short while later - in the realisation that said code could be written to run n times faster, or utilizing r times less resources? Happens to me frequently. So many times have I revisited code I wrote but a few weeks earlier, only to think "what drugs was I on while writing this crap???". Frustrating. //L
Seriously I think this will always happen as the brain is always working out better ways of doing things even after you have completed the task. So if you go back to something a while after the brain will almost always have dreamt up a better way of achieving the same goal.
-
I feel your pain. :)
“Follow your bliss.” – Joseph Campbell
-
I have never had this happen to me. All my code is always optimum. In fact, without fail, my code uses negative processor cycles thus making the machine run faster the harder my applications are run ;-)
:laugh:
John