|
Well you know everything about fixing old legacy code, don't you. 
At least I know that no one else has touched the code I need to fix.
I'm even happy enough to know that it's MS that broke it, not me.
That said, I'm still having a load of forehead slapping moments here. 
|
|
|
|
|
As you get older, you get more legacy.
|
|
|
|
|
I am sitting at my office waiting for a replacement machine..My machine broke down on friday afternoon (which is probably nice way to end a week and start a weekend..). They are yet to replace my machine..half a day gone by...
|
|
|
|
|
Time machine? 
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
|
|
|
|
|
it would have been better than my machine!! 
|
|
|
|
|
Well, I started at a doctor's appointment (not the dentist).. Took more time to drive to the doctor's place than the actual appointment..
The signature is in building process.. Please wait...
|
|
|
|
|
If that can be of a cheer up, I guess you would not want to change jobs with @glennPattonWork lately.
What language are you coding in ?
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus
Entropy isn't what it used to.
|
|
|
|
|
|
That's exactly what i thought when this morning i took the scooter from the box and found the rear tire flat .... so i tried to put it again on the kickstand and it broke 
Monday morning sucks doubly
|
|
|
|
|
I know what you mean, there's someone from our branch in Italy who's been bad mouthing some code I wrote back in '06. All I can say is, if they can do better, they can write their own bad code...
It was broke, so I fixed it.
|
|
|
|
|
Well, I'm not saying the intern's code from 2006 is necessarily worst than mine: I'm just saying that, supposedly, in 2014 I have more instruments than what he/she had back in 2006 and, also, it might be the case that stuff he/she used at the time is not working anymore, got lost, et cetera...
Also, my IDE is going to complain a lot about this 2006 project, before letting me actually edit it.
Software simply gets old (and ugly), it's not the coders' faults.
|
|
|
|
|
Dycz wrote: ...simply gets old (and ugly)
I think you just described about 3/4 of the programmers/developers that I know. 
It was broke, so I fixed it.
|
|
|
|
|
No idea if it's worse but:
I'm trying to wrap my head around mountains of spaghetti code written by a ex-colleague in order to try and fix the mountain off bugs in it, and all of that after getting only 1 hour of sleep last night (for some reason I just couldn't sleep).
(Been trying to get my boss to agree to a full rewrite but no success as of yet)
|
|
|
|
|
I guess he/she left no comments and no readable code, right?
We're in the same boat, more or less
|
|
|
|
|
I wish there where comments.
To give you a idea at how bad this is (you can compare to your own situation then )
- A method to calculate all the days between 2 given dates that would run for 3 hours without actually doing something (hint year switch mend the loop went on until an integer overflow happened,
not sure how to explain it in English correctly but you probably get the idea)
- A class that inherits from another class that inherits from another class that... (about 5 or 6 layers deep).
- A helper class that has only 2 or 3 methods in it but is 5000+ lines code.
- A function called Convert... that actually updates the database (take a guess at how long it took me to find that bug)
- Update = delete + insert (without transactions) (got most of that out of it (I hope))
- A function called Add... that actually doesn't do adds (well not only adds, also updates (see previous) and deletes)
And then I'm not even touching the fact that EF was used in totally wrong way resulting in massive memory usage (8gig+ to get only 50 records) (got most of that out of it as well I think)
So yeah it's been a long 8months cleaning this mess of a code up and the mess it made in the db's. (and still a long way to go I'm afraid)
|
|
|
|
|
...I guess I've never seen an integer overflow really happening...
really sounds like 8 months in hell!!
Good luck
|
|
|
|
|
Dycz wrote: ..I guess I've never seen an integer overflow really happening...
Neither did I until that day.
Dycz wrote: really sounds like 8 months in hell!!
Yep, and still a few more to go, but at least I got it semi-stable and semi-usable (a year after it's initial release)
Dycz wrote: Good luck
Thanks, same to you 
|
|
|
|
|
Looking at HC6811 assembler written in the mid 90's. Actually it's kinda fun, I must be coming down with something.
|
|
|
|
|
Dycz wrote: I've just started my week editing rewriting code written by an intern back in 2006...
FTFY 
/ravi
|
|
|
|
|
yes, it's exactly what I'm doing now... turning winforms into wpf and XMLs into sqlite database records 
|
|
|
|
|
"Split a horny model to change one's aspect."(11)
Best of luck.
---------------------------------
Obscurum per obscurius.
Ad astra per alas porci.
Quidquid latine dictum sit, altum videtur .
|
|
|
|
|
Is it One Night in Paris?
|
|
|
|
|
Rhinoplasty - anag of split a horny
|
|
|
|
|
Movie Quote Of The Day
Find me that piece of paper I had in my hand yesterday morning.
Which movie?
|
|
|
|
|
Finding Memo.
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
