|
I read that a week ago. I still stand by my comment. My hat is made of hemp. 
|
|
|
|
|
Hats and Caps [^]
You better start saving... of course it won't violate the laws of physics as we currently understand them.
BTW: don't you think it a real shame that there is a whole universe out there that we'll never get to explore unless we do find a way to traverse interstellar space at more than the snail's pace we do now?
|
|
|
|
|
Our (current) inability of not being able to explore universe without being able to do FTL travel (or at least without Earth aging really significantly in the process), doesn't change the fact that we should accept these wild concepts. NASA doesn't mean "cannot make a mistake in an experiment". Either the laws of physics are broken or they made a mistake. What's more likely? 
|
|
|
|
|
Smart K8 wrote: doesn't change the fact that we should accept these wild concepts
Luddite.
Smart K8 wrote: Either the laws of physics are broken or they made a mistake
Neither need be true.
|
|
|
|
|
Seems much more likely that mankind will weaponize this technology before it gets a chance to provide our salvation.
I'm sorry was that too honest pessimistic?
Contrary to popular belief, nobody owes you anything.
|
|
|
|
|
Now here's a man who knows how things are done! +5
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
|
The surest way for us to acquire a useful interstellar travel capability would be to declare war on all of the habitable planets within a 100 light year radius, and then kill whoever shows up to figure out who the annoying twerps are.
Software Zen: delete this;
|
|
|
|
|
I'm getting out of the office for a few days, going to man the booth at a local (300 mile drive) trade show...hooray  At least it's in Daytona Beach. I could think of worse places to go. Have a good weekend coders!
"Go forth into the source" - Neal Morse
|
|
|
|
|
I feel really, really sorry for you!
A couple of tips I have picked up over the years:
1) Don't wear new shoes. Old, comfortable (but still smart) is much, much better - you are going to be on your feet for 9 or ten hours - and new, stiff and painful shoes do not help at all...
2) Eat a good, big breakfast. You don't know how busy the stand is going to be around lunch time, and if you don't get time for food it can affect your thinking.
3) if you smoke - wear a patch instead.
4) Stuff a bunch of pens in a pocket - visitors will nick them all.
5) Make notes on the back of the visitors business card - good as you can, but anything is better than nothing - it's pointless having his card if you don't know what he is interested in a week later.
6) If at all possible, get contact names and address back to the office the same day - and get them to send info with a "thanks for visiting" cover and a promise to get back to them when you are in the office again. Keeping your company at the top of their mind is important here, and they will get confused as to who said what just like you will.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Quote: Don't wear new shoes
You have more than one pair of shoes? You - you - capitalist pig! 
|
|
|
|
|
Not so, they are like any tool - you need the right tool for the right job!
So...
Trainers - normal footwear for me (1 pair)
Dress shoes - for when I have to wear a suit (1 pair)
Worn out shoes - for mowing and other dirty jobs round the garden (1 pair)
Steel toe cap boots - for heavy duty or dangerous jobs (1 pair)
Bike boots - for motorcycling (1 pair)
And that's me lot!
The only thing I do insist on is buying quality: buy "fashionable", or "cheap" and they don't last. Buy decent quality - which does cost more - and they last a lot, lot longer and that means they are comfortable for longer, and end up cheaper as well!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Thanks OG! All really good advice. I almost started the previous post with 'My feet already hurt'! 
OriginalGriff wrote: Eat a good, big breakfast
Lucky I work in nutrition...only a handful of software companies, but a ton of food vendors...I will be surrounded by sample sized food for two days! As much as I hate doing these shows, it does give me a chance to show off all the hard work.
"Go forth into the source" - Neal Morse
|
|
|
|
|
|
Just a natural extension of the Bass-O-Matic[^].
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
There's been a niggle with VS for me for a while: I use CTRL+C and CTRL+V to copy and paste, but they are close together and occasionally I get a Copy when I wanted a Paste. Normally I just sigh, and go back to copy it again - but it annoys me a little when I'm on a blank line with nothing selected, and the Paste operation copies the blank line to the clipboard. Why? Why do that?
Well, it's deliberate: there's an option to specifically do that.
Tools -> Options -> Text Editor -> All Languages -> General ... "Apply Cut or Copy commands to blank lines when there is no selection"
And for whatever reason the default state is "Yes, copy a damn blank line to the clipboard when there is no selection".
Why, Microsoft? Why? 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: Why, Microsoft? Why?
I can't answer that, but if you google that phrase (with quotes) you get over 11k hits!
In the meantime a heartfelt "Thank You"  It's always bugged me too.
|
|
|
|
|
I guess you should start leaning "How to keep focus on which button I am going to click".
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
Don't you know WordStar?[^]
Ctrl-Insert for copy
Shift-Insert for paste
Works everywhere. Visual Studio messes it up. 
Solves that empty-line-copy problem too, from what I can tell.
* EDIT *
Oh, interesting, Ctrl-Insert and Shift-Insert are from the IBM Common User Acess (CUA)[^]
modified 14-May-15 8:56am.
|
|
|
|
|
That's the old school way of doing it. I can remember it from the DOS / Word Perfect / Quatro Pro days. Funny thing is, nobody ever considered copy/pasting an empty line back then. We did things more efficiently by using the huge [Enter] key on the keyboard.
My plan is to live forever ... so far so good
|
|
|
|
|
DJ van Wyk wrote: old school way of doing it
best way...
|
|
|
|
|
They were the ones shown on the menus in Win 3.1
|
|
|
|
|
greldak wrote: They were the ones shown on the menus in Win 3.1
You're right. That's how I learned them and I've never forgotten them. They work in places the other hotkeys don't.
|
|
|
|
|
Even more bizarre is that someone had the foresight to make that behavior configurable.
Marc
|
|
|
|
|
I'm gonna guess that in the early days copy just copied whatever was there even if it was nothing, people kept complaining, eventually they added in the option to make it behave more sensibly but didn't want to make the default different to accustomed behaviour.
Which is a sensible general policy.
True sense comes, however, from not blindly applying your policy, no matter how sensible it may be.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
