Client's legacy code

Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

eek replied

25 August 2011, 09:52
Originally posted by zeitghost

Not forgetting the infamous "MustDoSomethingHere".

my favourite was the comment "must document this" scattered throughout the code.
Leave a comment:
Mich the Tester replied

25 August 2011, 09:13
Originally posted by TimberWolf View Post

Written by the highly paid programmer himself?

No, written by some contractor who was called in to repair it.
Leave a comment:
TimberWolf replied

25 August 2011, 09:12
Originally posted by Mich the Tester View Post

I once came across the following comment;

' Nobody around here knows that this bit does

Written by the highly paid programmer himself?
Leave a comment:
Mich the Tester replied

25 August 2011, 09:09
I once came across the following comment;

' Nobody around here knows what this bit does

Last edited by Mich the Tester; 25 August 2011, 09:13.
Leave a comment:
xoggoth replied

25 August 2011, 09:02
I left a legacy of rude words in my client's code. For some reason code always worked after you rudified it.
Leave a comment:
Peoplesoft bloke replied

25 August 2011, 07:45
I seen some great stuff in comments over the years - including some spectacularly sweary ones in one product - I also saw a function commented as "sort out stupid American date format" (written by an Aussie)

The Americans ruined all our fun with their straight-laced puritanism again - remember all those Easter Eggs? Killed by US govt.
Leave a comment:
Churchill replied

25 August 2011, 06:15
Some of the error conditions in my early code ~20years ago had something like...

; Houston, we have a problem.

or if it was particularly complicated...

; Here be Dragons...

Nobody ever complained in the code reviews
Leave a comment:
TimberWolf replied

25 August 2011, 00:36
Originally posted by thunderlizard View Post

Disappointingly, it was "future" in the financial sense (so should technically have been "futures") and just did a database lookup.

Oh, okay, but now that you've deleted the method to ascertain the existence of the future, is the default for it to exist or not exist? Or is the question without meaning now?
Leave a comment:
thunderlizard replied

25 August 2011, 00:28
Disappointingly, it was "future" in the financial sense (so should technically have been "futures") and just did a database lookup.
Leave a comment:
TimberWolf replied

25 August 2011, 00:25
Originally posted by thunderlizard View Post

...contained the following method, before I deleted it:

Code:

bool DoesFutureExist()

I wish legacy code contained philosophical quandaries more often.

What was in the method?
Leave a comment:
thunderlizard started a topic Client's legacy code

25 August 2011, 00:22
Client's legacy code
...contained the following method, before I deleted it:

Code:

bool DoesFutureExist()

I wish legacy code contained philosophical quandaries more often.
Tags: None