|
Peter_in_2780 wrote: She mentions an upcoming engagement Is this a picles-cartoon?
Peter_in_2780 wrote: In my defence, I'm still on my first cup of coffee. In your defense, a bullet proof vest is a better idea.
Bastard Programmer from Hell
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Quote: In my defence, I'm still on my first cup of coffee
NEVER EVER do anything on such a low level of caffeine. That's asking for trouble!
Get me coffee and no one gets hurt!
|
|
|
|
|
|
That looks like what I was after a couple of months ago! to prevent the screen save kicking in while doing a colorimetry test on the screen.
|
|
|
|
|
Autocomplete for passwords, awesome time-saver ! 13 days ago, I would have proposed it as a company internal improvement - maybe also just to see how far it goes before someone says "Nah".
|
|
|
|
|
"Having login problems? Chat with us!"
[Log in to your account to start a chat]
I won't name names.
cheers
Chris Maunder
|
|
|
|
|
I use a number of websites like that - my mobile phone company site for example is so poor I changed my username to "IHateThisCr*p".
My bank (otherwise excellent) whose fraud detection department ring you up and refuse to prove they are my bank, but do want me to prove I am who they called.
Oh, and a large company I won't name whose "forgotten password" system ... needed you to log in to reset it ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: Oh, and a large company I won't name whose "forgotten password" system ... needed you to log in to reset it
I'm not afraid to name names. Bell Canada. Had to help a relative solve some problem with his Bell account. In order to do anything, you first have to log into your account.
Guess what sort of problem I was trying to resolve.
|
|
|
|
|
Is it a bank?
Hints! We need hints!
TTFN - Kent
|
|
|
|
|
Bingo
cheers
Chris Maunder
|
|
|
|
|
It would have been a sucker bet.
TTFN - Kent
|
|
|
|
|
B.I.N.G.O. = Bank Internationalé Now Goon Operators?
Software Zen: delete this;
|
|
|
|
|
Never heard of 'em; you sure you awake and not dreaming?
Happens to the best of us
Bastard Programmer from Hell
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
so frequently I find myself doing a proof of concept very short code that I am going to flush out later. Sometimes I even flush it. Pun intended.
Anyway I frequently use variables like the following.
astr - it is A String
Temp table
#ewww - because the data in the table is stinky at best.
and so forth. I always promise myself to clean it up before I actually use it anywhere. Sometimes I even do.
Does anyone else do this?
To err is human to really elephant it up you need a computer
|
|
|
|
|
rnbergren wrote: Does anyone else do this?
Nope.
rnbergren wrote: Sometimes I even do.
Because "sometimes" is "usually never."
|
|
|
|
|
Well said!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I'm with Marc: never.
Why not? Because you will not find the time to go back and correct it - it will be permanent. That's why I "do it right" even for throwaway apps: parameterized queries, proper names, no default control names from Visual Studio, and so forth.
Do it right all the time, and you don't get into bad habits which enter production cycle.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
This. And, don't use names like 'astr'. Hovering in VS will tell you it's a string. Don't waste time and space giving redundant information.
I've said it for decades. It's usually not that much harder to be right than close to right. Be right.
|
|
|
|
|
Nope - I write all code as if it is "production" code with proper naming, etc.
One reason is to not have two styles of coding or naming conventions; it's just easier!
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Never. Either write code properly, or don't write it at all.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
"We are what we repeatedly do. Excellence, then, is not an act, but a habit." - Aristotle
So no, I've made doing it "right" a habit and would not even think about naming something "astr" or "ewww"
|
|
|
|
|
I learned a long time ago that the temp code I'm planning on ditch often becomes the bedrock on which my applications teeter.
cheers
Chris Maunder
|
|
|
|
|
rnbergren wrote: Does anyone else do this?
I have been known to use slightly 'inappropriate' abbreviations for variable names. By inappropriate, I mean in human terms 'cause the compiler doesn't care. A common abbreviation in my line of business is ASS. It appears frequently in my code, and I've never been asked to change it.
Another example is when we used crystal reports. The application object was crAp!
The worst I've done is leave some salty comments for myself as they were well deserved.
TBH, for utility variables I always use the same ones, usually 2 or 3 letters, kind of a signature I suppose. For others, I've gotten a lot more descriptive over the last decade or so.
"Go forth into the source" - Neal Morse
"Hope is contagious"
|
|
|
|
|
If I'm writing "one-off" code I do this sometimes (e.g. a QA answer). Any code I might actually end up using for something I generally don't for three reasons: 1) harder to read for me, 2) you may never get back around to renaming everything, and 3) naming practice. Good naming is a skill just like any other.
|
|
|
|
|
Never ever do this in what you think is prototype code, it will and should come back and bite you when it goes into production.
Doing it right MUST become a habit, an automatic action that you don't even think about it. Name it correctly, format it correctly and use the most efficient and elegant structure you can think of, even in a throw away piece of code you don't ever expect to use.
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP
|
|
|
|