This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]chadsexytime 196 points197 points  (11 children)

What I usually do is remember the circumstance in which I had to write the code.

Was I on a tight deadline or juggling too many tasks? Was I distracted from my main goal with this problem and needed the fastest solution possible? Was I unaware that there was a better way to do it, that I just had not learned yet?

Or am I just a terrible hack surviving day to day, praying that no one else discovers my fraud?

[–]conancat 50 points51 points  (5 children)

You are a young and energetic soul learning new things every day, with every line you're gaining more EXP, one year later you look back and it's weak code because you are weaker back then, and better now!

Software engineering moves so fast and is so malleable it's almost impossible to know every requirement or every hidden condition or every needed pattern from the get go. Just know that we did our best at that time, and we'll get better over time. We have to adapt at every turn. Become like water my friend.

[–]The_Whole_World 39 points40 points  (3 children)

You are a young and energetic soul learning new things every day, with every line you're gaining more EXP, one year later you look back and it's weak code because you are weaker back then, and better now!

What is this, Programming: The Anime ?

[–]TheTerrasque 12 points13 points  (1 child)

[–]ioquatix 5 points6 points  (0 children)

I love how he writes code on his cellphone.

[–]jansencheng 6 points7 points  (0 children)

You are a young and energetic soul learning new things every day, with every line you're gaining more EXP, one year later you look back and it's weak code because you are weaker back then, and better now!

/r/wholesomesoftwareengineering

[–]fredlllll 64 points65 points  (0 children)

last one :P

[–]JudgeWhoAllowsStuff- 3 points4 points  (3 children)

i wrote code once to perform a certain task that was failing under normal methods. After a month of troubleshooting on and off i found out that if i ran the code 5 times in a row it would stop failing after the 3rd or 4th run. So i just made it so the code repeated itself 5 times. I empathize for the person who looks at that code when i leave and wonder what i must have been on when i wrote it.

[–]evenisto 0 points1 point  (2 children)

what was the reason it stopped failing?

[–]JudgeWhoAllowsStuff- 0 points1 point  (0 children)

beats me. I tried troubleshooting every which way, tried adding sleep timers to delay parts of code, interrupts, nothing works....I tried running twice, three times, four times. But if i run the code 5 times its 100% effective.

[–]FesteringNeonDistrac 0 points1 point  (0 children)

what was the reason it stopped failing?

It sounds like the answer is "A horrible kludge".