|
I went there, I couldn't find the "Upvote" button, I went away again. 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I had it once for one of my articles (not top but 5th or so as far as I remember) while I did some research to update that article (so it was not what I was looking for; or better: It did not contained what I was looking for).
Just tried it with the article title (which contains only three very general terms):
710,000 hits, position 4, positions 1 to 3 from the MSDN. Wow 
|
|
|
|
|
 It's a good feeling, isn't it? I'm really not sure why it feels good though.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I often have to google/bing "technical words" + "my name" and get a direct link to my blog or article when I am trying to do something I had done in the past, had written an article about, but had then completely forgotten. 
|
|
|
|
|
Yeah, a couple of years ago I googled how to do something in linux, and the article that solved the problem was one that I wrote the previous year.
I'm retired. There's a nap for that...
- Harvey
|
|
|
|
|
if I google my name exactly yep I am the first hit. Of course there is only one person with my exact name in the entire world so that helps. Slightly unusual last name with a slightly uncommon first name gets you that
To err is human to really mess up you need a computer
|
|
|
|
|
Nope, not an anti-Apple rant but a general moan about all things starting with a gratuitous "i".
I'm writing some helpers for a third party API which is one of those annoying products called IWhatever - now I can't call a class IWhateverHelpers because it will look like it should be an interface and if I call it something more descriptive like ThirdRateThirdPartyHorseDroppingsHelpers, it will probably get frowned upon for being too honest.
Whoever wrote the actual API neatly sidestepped the problem by not using any interface naming conventions at all - having seen this in action (Intellisense looks like an explosion in a custard factory), I'm not convinced that this was the greatest of ideas.
98.4% of statistics are made up on the spot.
|
|
|
|
|
PeejayAdams wrote: Whoever wrote the actual API neatly sidestepped the problem by not using any interface naming conventions at all
Such people should be defenestrated!
There is no excuse whatsoever for not following well-known coding conventions, the Ixxx convention for interfaces being one of the oldest in the field.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
I have trouble starting a sentence with It, I keep looking for the t intefacce 
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Defenestration certainly sounds like a good idea.
It wouldn't tidy up their abysmal code in any way but it would leave those of us who have to use it feeling a whole lot better.
I wonder where there office is (I'm rather hoping that it's several stories off the ground).
98.4% of statistics are made up on the spot.
|
|
|
|
|
Daniel Pfeffer wrote: There is no excuse whatsoever for not following well-known coding conventions
Said the StyleCop to the code monkey. So we finally meet.
If I had the choice, I would not lose a word about code that may not adhere to all rules and conventions, but does an excellent job at what it was written for. The exact opposite, all style but no substance, would be far less useful. Last, there are also those that fail at both, like probably this one here.
Anyway, I don't need excuses to think more about what I'm doing and less to blind adherence to some conventions. I even know some cases where sticking to the conventions would have introduced very tricky problems.
I am endeavoring, ma'am, to construct a mnemonic memory circuit using stone knives and bearskins.
|
|
|
|
|
I am not referring to minutia such as 1TBS vs K&R or some such. I am referring to a useful convention that helps a lot when reading code. The 'I' at the beginning of the name indicates that we are dealing with an interface, i.e. it declares a "contract", rather than an implementation.
Yes, there are many stupid conventions out there (tabs vs spaces, etc. ad nauseum), but this is not one of them.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Nor did I. It was something that would make the class names, variable names or method names mostly unreadable for the majority of the people here. Such things were never really taken into account by the heroes who made up the conventions. After all, all the world speaks English, right?
Our customer doesn't. He doesn't even see a value in using terms consistently. He thinks that such things are merely guidelines. Translating his requirements to object and method names would require a glossary with exact definitions of what this term means, which would have to be carefully maintained over more than 20 years now.
Besides that, the customer's representatives up to now have resisted writing such a glossary and even if it existed they are against using it when they look at the code. This tiny little company is a real star among the car manufacturers.
I am endeavoring, ma'am, to construct a mnemonic memory circuit using stone knives and bearskins.
|
|
|
|
|
I remember when i was an integer before it became an interface,
seems like only yesterday ...sigh, how fast they grow these days.
Format Success.
Welcome to your new signa&*(gD@@@ ![Beer | [beer]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/beer.gif) @@@@@@*@x@@
|
|
|
|
|
Lopatir wrote: I remember when i was an integer before it became an interface,
If you name your interfaces 'I1', 'I2', etc., you should be thrown out of the window after the programmer mentioned by the OP. 
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
It also used to be lpstr and now it's Lopatir.
I am endeavoring, ma'am, to construct a mnemonic memory circuit using stone knives and bearskins.
|
|
|
|
|
Lopatir wrote: sigh, how fast they grow these days
I remember when int's were only 16 bits. 
Software Zen: delete this;
|
|
|
|
|
I call you, you call me - sounds like we are straining the dog again! (9)
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Recursive.
Dog -> cur
Straining -> sieve -> sounds like sive.
again -> re
Andy B
|
|
|
|
|
Close enough:
I call you, you call me
sounds like ---
we are straining SIEVE
the dog CUR
again! RE
RE-CUR-SIVE
You are up tomorrow!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Telephone
Cockney slang, dog and bone.
|
|
|
|
|
I did.
You didn't pick up. 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Sorry, I was on the Khazi.
|
|
|
|
|
In case that is not clear I HATE EXCEL
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I like it - it's a good spreadsheet from a user POV.
Now take a deep breath and explain why it's a pile of ![Elephant | [mastadon]](https://www.codeproject.com/script/Forums/Images/elephant.gif) cr@p for you...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
