|
... for whom flipping burgers is too difficult.
|
|
|
|
|
I won't argue with that!
"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
|
|
|
|
|
It's all in the wrists.
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
glennPattonContracting2 wrote: I think that a lot of Q&A is caused by people not taking a break and looking at what is going wrong Well, I'd say you are an optimist !
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
|
|
|
|
|
No break until a working solution is obtained from someone else.
|
|
|
|
|
Last Tuesday, I was hacking away at some project I'm working on.
Apparently, I just typed if (Task.StartsOn) when I got a phone call and had to do other stuff (I didn't even finish the sentence as StartOn is not a bool and so that line of code doesn't compile)...
Today, I found some time to work on that project again.
I can't remember what the if (Task.StartsOn) was all about though.
Deleted it, finished the page, and never needed that if-statement again.
Can't wait to find out what it was supposed to do when this breaks in production
|
|
|
|
|
I don't always test my code, but when I do, I do it in Production.
|
|
|
|
|
You make it sound as if there are alternatives
|
|
|
|
|
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
But it works on my machine.
|
|
|
|
|
either you didn't need it and your subconscious brain figured out a better way. OR you most certainly need it and you had a nightmare about it going horribly wrong in production. So bad in fact that you blocked that memory and how to fix it. So now you will live the nightmare.
I bet it is option #1.
To err is human to really elephant it up you need a computer
|
|
|
|
|
This is why you should write comments first. Or at least that is how the fairy tales tell it...
|
|
|
|
|
I find it helpful to write comments first, sometimes. It helps me think through the algorithm, and then it helps me complete it if I become distracted or have to leave the project for any reason and come back to it later.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
But before you try it, read to the end ...
Accidentally used WINKEY + NUM+ and discovered it zooms in on the active object on your screen - the browser, say, or VS. And WINKEY + NUM- moves teh zoomed bit around.
But ... it doesn't work at all usefully on multiple monitors since it counts it as one huge screen with gaps in ...
So you're going to need this bit: WINKEY + ESC to exit.
If you read this far, that is ...
"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!
modified 28-May-21 11:07am.
|
|
|
|
|
So glad I use a keyboard with no WINKEY.
|
|
|
|
|
PIEBALDconsult wrote: WINKEY
|
|
|
|
|
I've always wondered why they put the WINKEY next to the CTRL and ALT keys. Why not just place it up with the function keys. I always end up hitting the WINKEY by accident when playing games causing the game to minimize screwing up the frame rate of the game when I bring the game back into focus.
"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."
Ignorant - An individual without knowledge, but is willing to learn.
Stupid - An individual without knowledge and is incapable of learning.
Idiot - An individual without knowledge and allows social media to do the thinking for them.
modified 19-Nov-21 21:01pm.
|
|
|
|
|
Because WinKey is used as a modifier, just like Shift, Ctrl, and Alt. Historically those keys have been located near the bottom left and bottom right corners of the keyboard.
Software Zen: delete this;
|
|
|
|
|
One of my gaming keyboards, a Logi g510s, has this nice winkey enable/disable slider. It didn't take long to find out how useful it is, but I do miss out on inadvertently discovering new winkey hotkeys.
|
|
|
|
|
OriginalGriff wrote: you're gong int need Oh yes, I can see that.
|
|
|
|
|
Gawd, my typing is getting worse and worse ...
"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 tried it on one of my Win7 machines and it just brings up a zoom tool window. WINKEY + NUM- shrinks it, WINKY + ESC closes it. Quite handy that way - why did they change it for WIN10? Odd!
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
As far as I can tell, it's just a shortcut to launching the magnifier utility that's existed since...well, I'm too lazy to look it up...I never use it.
|
|
|
|
|
Me too!
I read your post and it was an OMG!
|
|
|
|
|
I hope they realize that they are then responsible for following HIPAA regulations as to all patient data, and can be severely fined (see below) for each record if any of that data is released. Greed knows no bounds.
'HIPAA violations are expensive. The penalties for noncompliance are based on the level of negligence and can range from $100 to $50,000 per violation (or per record), with a maximum penalty of $1.5 million per year for violations of an identical provision.'
|
|
|
|