|
If you would be so kind to publish your address here I would gladly help ... as would millions of others ... that said, (sub)empty inbox would bother you no more
modified 19-Nov-18 21:01pm.
|
|
|
|
|
...you look at the commit log, see a couple of messages saying "addressed a few bugs", check what they are and find out that the 'solution' was to comment some lines out!!!!
|
|
|
|
|
Or when I look at my log and it says addressed a few bugs but there is no body text at all! - Because I hate myself I guess.
|
|
|
|
|
The YAGNI Strikes Back
Code Trek 2: The Wrath of YAGNI
Code Trek 3: The Search for YAGNI
Code Trek 4: ....whales...really...?
Sorry, derailed a minute there. I was just going to say that YAGNI usually the cause of bugs that can be fixed with comments. Just saying.
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
Quite possibly. But if the code itself is unneeded then the commented version is even more unneeded...
|
|
|
|
|
On production version: absolutely.
On source version it can give a good idea of plans and thought process. Or it can be a horrible mess, which will still give the next people who look at it a hint as to the thought process of the author. By and large I tend to find commented code more useful than actual code comments
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
WiganLatics wrote: But if the code itself is unneeded then the commented version is even more unneeded... Ah, you're one of those who can't stand leaving commented code in place.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Yep, that's what source control history is for (with an appropriate comment).
#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
I just created a module called "FileEventStreamProviderFactory"
|
|
|
|
|
You might be insane , but it is descriptive; however, I don't think I've ever read a class name with 30 characters before.
When you are dead, you won't even know that you are dead. It's a pain only felt by others.
Same thing when you are stupid.
modified 19-Nov-21 21:01pm.
|
|
|
|
|
|
|
"I don't think I've ever read a class name with 30 characters before."
I find that hard to believe. They seem a common occurrence to me.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
Did you at least bury it way down deep in a long namespace?
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
It is in Namespace Azure.File
It's not even close to being the longest named class - I think that is "InMemoryIdentifierGroupSnapshotReaderFactory"
|
|
|
|
|
We have one called "EstimatedYearlyCreditOpportunityImportDataSaver"
djj55: Nice but may have a permission problem
Pete O'Hanlon: He has my permission to run it.
|
|
|
|
|
personally I don't see what's wrong with that - too short, its not descriptive enough, at least that says what the class is/does - even if you said "FESStreamProviderFactory", would you remember what acronym FES stood for, 2 years from now, without re-examining the source ?
..as a friend oft quotes "naming things is one of the hardest things in programming"
|
|
|
|
|
It is pointless to question the nonexistent...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Duncan Edwards Jones wrote: I just created a module ...
If you're creating a module[^], then there's no question of you having any sanity left.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
It's just syntactic sugar over
public static class ...
|
|
|
|
|
Not quite. It's more like a combination of public static class and using static - the members of a Module don't need to be qualified with the module name.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Was wondering why one of my unit tests was passing even when nonsense values were passed in...found:-
if (row != null)
{
if (!row.IsNull(fieldName))
{
double fieldValue = (double)row[fieldName];
}
}
What indeed....
|
|
|
|
|
Be fair: we've all had days like that. Granted, one usually fixes it the next day...
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
Yeah - it's probably existential despair at what the code has to do - it is a filter function run on the client side that would be much more healthy if implemented as an SQL WHERE clause.
|
|
|
|
|
Not always. I've had the following in one of mine for years:
else
{
}
|
|
|
|