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
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
-
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 ;-)
Russell Jones wrote:
my code uses negative processor cycles thus making the machine run faster the harder my applications are run
That reminds me of the april fool prank blog post on an msdn page which described about an "improvement" to the
Sleep()command such that it accepts negative values. :laugh:“Follow your bliss.” – Joseph Campbell
-
Although the sentiment is much appreciated, I doubt it - I've got an inflammation on my jaw the size of Nebraska today. Every heartbeat feels like someone kicking me in the face. :sigh: //L
Probably someone is actually kicking you in the face? You might want to double check if your manager is around. :)
“Follow your bliss.” – Joseph Campbell
-
Although the sentiment is much appreciated, I doubt it - I've got an inflammation on my jaw the size of Nebraska today. Every heartbeat feels like someone kicking me in the face. :sigh: //L
Check your boss' office for voodoo dolls? :-\ Flynn
-
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:
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???"
Of course, but the fact that you can recognize that is wonderful! I wouldn't beat yourself up about it. Anytime you create something, you do the best you can, then as time goes on and you critique your own work, learn new skills and techinques, when you go back, you'll see the flaws of your previous work. It's perfectly normal. Marc
I'm not overthinking the problem, I just felt like I needed a small, unimportant, uninteresting rant! - Martin Hart Turner
-
Although the sentiment is much appreciated, I doubt it - I've got an inflammation on my jaw the size of Nebraska today. Every heartbeat feels like someone kicking me in the face. :sigh: //L
So... what did you do to piss off Chuck Norris?
Software Zen:
delete this; -
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 write business software, trust me, you want the spit. (Will anyone get the reference)
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. A man said to the universe: "Sir I exist!" "However," replied the universe, "The fact has not created in me A sense of obligation." --Stephen Crane
-
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
If you're a good programmer, it happens far too often. ;) It means that you're learning and growing as a developer.
Jamie Nordmeyer
Portland, Oregon, USA
http://www.feralcodemonkies.com -
All the time, but I am starting on a low base line! :)
------------------------------------ No Good Deed Goes Unpunished Clare Boothe Luce
Dalek Dave wrote:
I am starting on a low base line!
Sounds like my last performance review: "Sets low goals, but consistently fails to acheive them."
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
-
Although the sentiment is much appreciated, I doubt it - I've got an inflammation on my jaw the size of Nebraska today. Every heartbeat feels like someone kicking me in the face. :sigh: //L
-
So... what did you do to piss off Chuck Norris?
Software Zen:
delete this; -
Dalek Dave wrote:
I am starting on a low base line!
Sounds like my last performance review: "Sets low goals, but consistently fails to acheive them."
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
Glowing review. Did you and the boss have a beer later on? :D
-- Kein Mitleid Für Die Mehrheit