|
When it is easy, or will end up causing too much confusion later on. Sorry, my answer is as vague as your question.
|
|
|
|
|
Jörgen Andersson wrote: when is it ok to rename it
a) Wednesday
b) The last day of your employment
c) Never
d) All of the above
PooperPig - Coming Soon
|
|
|
|
|
[Obsolete("This method is older than Yoda. We have new shiny one with lightsaber")]
public void OneThousnadYerOldMethod()
{
NewShinyOne();
}
public void NewShinyOne()
{
}
Zen and the art of software maintenance : rm -rf *
Maths is like love : a simple idea but it can get complicated.
|
|
|
|
|
Jörgen Andersson wrote: If your application/library/class/function has developed out of scope and can no longer be considered having the right name, when is it ok to rename it?
a. As soon as it's out of scope and can no longer be considered having the right name, and
b. You can find a poor slob to do the code renaming, refactoring, updating of tables, updating of docs, rerouting of any old URLs that point to that name, corrections and redistribution of written material, changes to DNS, server naming, jobs and schedules, Unit tests and test data, and all those coffee cups with the old name on them.
cheers
Chris Maunder
|
|
|
|
|
That poor slob would be me, and we don't get special coffee cups over here. Can I have a CodeProject one? I promise to not touch your code.
|
|
|
|
|
Jörgen Andersson wrote: I promise to not touch fix your code.
So close, but you blew it.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
If I promised that, I'd probably blow it anyway.
Wrong is evil and must be defeated. - Jeff Ello
Any organization is like a tree full of monkeys. The monkeys on top look down and see a tree full of smiling faces. The monkeys on the bottom look up and see nothing but assholes.
|
|
|
|
|
Chris Maunder wrote: You can find a poor slob to do the code renaming, refactoring, updating of tables, updating of docs, rerouting of any old URLs that point to that name, corrections and redistribution of written material, changes to DNS, server naming, jobs and schedules, Unit tests and test data, and all those coffee cups with the old name on them to blame when problems caused by the renaming appear
FTFY
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 helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
I don't know about library, but if it's a class, never, you simply shouldn't if it used across several systems.
You can extend it by sub-classsing and giving the child class an appropriate name.
modified 20-Oct-19 21:02pm.
|
|
|
|
|
Kamen Nik wrote: I don't know about library, but if it's a class, never, you simply shouldn't if it used across several systems.
Hence the ghost of NextStep that lingers on in every Mac and iDevice...
|
|
|
|
|
Anytime, and if a name already in use that is suitable, just append a number to the end. e.g. SomeClass2, 3, 4
|
|
|
|
|
Hey, it wasn't passwords I were asking about.
|
|
|
|
|
SimpleClass201410101456 would be more elegant, wouldn't it? 
Your time will come, if you let it be right.
|
|
|
|
|
Wait until it's in the header of at least twenty other programs.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I'm going with April 1st, or a Friday 13th. Conveniently, 2015 has three of those.
If it's C++, go ahead and rename it and let the compiler puke all over everyone. Then accuse them of not following standards if they complain.
... or #define it to a MessageBoxA() call.
|
|
|
|
|
For functions, create a new one (like "overload") so that the code calling the "old" function does not break.
TOMZ_KV
|
|
|
|
|
That's not one question - it's four. Methods and classes can be renamed safely as long as you continue to support the old names (be sure to deprecate them using [Obsolete]) for n releases per your SLA.
Renaming assembly and file names can wreak havoc. Do this only if absolutely necessary.
Renaming an app requires sales, marketing and end-user support to get involved and is the most expensive option. Do this only if your bottom line depends on it.
/ravi
|
|
|
|
|
gesh people, don't you know. You always start all programs with Project1 and all variables are var1, var2 etc...
text boxes
txt1
txt2
txt3 etc..
Got to save keystrokes here. Short people short.
Seriously though. Worked with a programmer many many years ago that named everything that way. Oh my goodness her code was horrible.
Anyway. Rename as soon as possible but try to keep it as general as possible. Hard balancing act to follow. I actually have a reporting project that I wasn't 'allowed' to know the name of when I started coding it. I named it DrillInSpecialReports. Unfortunately it was too general and everyone on the team has put all their special reports in that project and hung them all off each other. It is a beast now.
But we know where to look for anything that is a special report.
<grin>
To err is human to really mess up you need a computer
|
|
|
|
|
I've also worked with one of those people, he also didn't know there existed such a thing as repeaters.
So we had a report with 72 (SeventyTwo) fields named Label1 through Label72.
Wrong is evil and must be defeated. - Jeff Ello
Any organization is like a tree full of monkeys. The monkeys on top look down and see a tree full of smiling faces. The monkeys on the bottom look up and see nothing but assholes.
|
|
|
|
|
I can relate. At my last job I had to debug a function that the parameters were (a, b, c, d, e, f, g, h, i) and not one comment in the entire function.
We were also taught names mean nothing when it came to function names.
The consultants who wrote the initial program would commonly call functions that did ten different things when they were only interested in two of them and they assumed the other eight would not adversely affect the rest of the program.
A coworker and I traced a subroutine down twenty-five levels like that and did not hit bottom. We quit because by that time we had no idea what the intent of the original function call was.
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|
|
I worked at a place where one developer named all his functions after Disney characters.
He would have fit in at my last job where the first thing we were taught was that "Names mean nothing, just because a function is named 'PRINT', it may not get around to doing any."
Of course the initial software had been written by consultants who had no interest in communicating how the software worked.
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|
|
How nice it would be if webinars get started on Code project, Apart from posting writings we can come live to the world.
This is just an idea.
Sorry if this is inappropriate here..
|
|
|
|
|
You could always post a Video Article.
You could always host a Hangout with Google+ CodeProject Group.
You could, I'm not saying you must.....
|
|
|
|
|
Yes that is true, but I was saying if experts on code project set up some thing like webinars..we would have gained much through a live and direct interaction ...
Thank you
|
|
|
|
|
Maybe the experts don't want to set up sessions to have direct interactions. You remember CodeProject.tv?
You can almost guarantee that the muppets would spoil it for everyone else.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
