|
..in the case of humor the salt would be randomly pulled from a pre-seeded table, also containing Bacon and CListCtrl.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
No comment needed...
If (InputBox("Access is highly restricted. Please enter the password: ") = "nooneneedstoseethisscreensokeepoutyoumonkey.") Then
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
On a positive note, they've got enough characters and included punctuation
How do you know so much about swallows? Well, you have to know these things when you're a king, you know.
modified 31-Aug-21 21:01pm.
|
|
|
|
|
|
erm. the password to 'something in our network' (I wn't say what just in case!!!) is actually "correcthorsebatterystaple"
PooperPig - Coming Soon
|
|
|
|
|
Like.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Ha! A few of our screens are protected with a password of WMTSU and some numbers. Easy to remember: we're making this stuff up!
"Go forth into the source" - Neal Morse
|
|
|
|
|
At my former employer we had a small config app with such a password baked into the code.
It ran with all our clients on many computers.
The regular user couldn't change the configs and we, and admins at the customers, always knew the password.
A bit more secure than a regular config file or a non-password protected config app.
It did the job!
I wouldn't use it on a website or anything though
My blog[ ^]
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
|
Even in those circumstances, the password should at the very least be encrypted.
Further, should it become necessary to change the password, your app will have to be rebuilt. There are many, many better alternatives.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
Rob Grainger wrote: the password should at the very least be encrypted. Why? It wasn't a big secret. Just some local configuration...
Rob Grainger wrote: should it become necessary to change the password That was the beauty of it, the password was always the same!
Rob Grainger wrote: There are many, many better alternatives I know, I'd actually never use such a solution. I'm just saying it did the job of keeping users out and letting admins in
My blog[ ^]
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
|
In the following chunk of code:
service.SetClosingResultOfAtePolicy(this, terminationType);
The suggestion was "Add argument name 'terminationType' (Alt+Enter)", yielding:
service.SetClosingResultOfAtePolicy(this, terminationType: terminationType);
Because that really helps improve clarity, right?
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
But of course! Not it is twice as clear as was before!
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
What's the full signature of SetClosingResultOfAtePolicy(...) though?
How do you know so much about swallows? Well, you have to know these things when you're a king, you know.
modified 31-Aug-21 21:01pm.
|
|
|
|
|
Er, not sure how that is relevant, but...
public void SetClosingResultOfAtePolicy(AtePolicy policy, TerminationType terminationType)
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
It's relevant if you have optional parameters
In this case though, it looks like overkill.
How do you know so much about swallows? Well, you have to know these things when you're a king, you know.
modified 31-Aug-21 21:01pm.
|
|
|
|
|
Was that a suggestion, or just a context action?
If you hit Alt+Enter, R# will usually list everything you might want to do with the code under the cursor. That doesn't necessarily mean it thinks you should do it.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
I wouldn't mind, but it consistently puts up a squiggly line under the code, and I've conditioned myself to treat those as warnings - i.e. something to be eliminated.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
In an Excel spreadsheet, enter the following two dates:
01-Feb-1900
01-Mar-1900
In another cell, subtract the first from the second and set the formatting to general,
Look at the result.
In VBA (just because you're in Excel anyway), from the immediate window enter:
? datediff("d","01-Feb-1900","01-Mar-1900")
Check the result.
The VBA result is correct...
This goes back to my college days.
|
|
|
|
|
I think it's down to the problem mentioned here[^] - for compatibility's sake they replicated a bug in Lotus 123, which thought that 1900 was a leap year.
=========================================================
I'm an optoholic - my glass is always half full of vodka.
=========================================================
|
|
|
|
|
Backward compatibility is the cause of numerous problems in computing, I believe.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
It's even documented here[^].
|
|
|
|
|
The sad thing is I immediately knew when I saw the subject and the dates.
|
|
|
|
|
Excel is horrible at a number of things. What causes me much trouble is that there are some string values, e.g. 1DEC , that I am supposed to get from a database, but because along the way from their point of origin to my source they pass through Excel, they come in as 12/1/2013 (whatever the current year is). So then my ETL process has to detect these and correct them.
|
|
|
|
|
|
Ian Shlasko wrote: it won't be wrong again for 85 more years...
Only if your computer's clock gets reset:
NOTE: Microsoft Excel correctly handles all other leap years, including century years that are not leap years (for example, 2100). Only the year 1900 is incorrectly handled.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|