|
I ask myself that every year. Yet I keep finding myself here.
"If we don't change direction, we'll end up where we're going"
|
|
|
|
|
It's such a ridiculous question, so maybe the answer should be, "If I could foretell the future I would not be applying for this crummy job".
|
|
|
|
|
Better then your cell mate saying; "Hey you're kinda cute"
|
|
|
|
|
They asked me that at my last job interview. I gave my usual response:
“I would say my biggest weakness is that I don’t listen when others are talking.”
If you can't laugh at yourself - ask me and I will do it for you.
|
|
|
|
|
|
UnoriginalGriff?!?!?!
If you can't laugh at yourself - ask me and I will do it for you.
|
|
|
|
|
I was asked this at a time travel convention.
|
|
|
|
|
Hi All,
I was having a fight with Word I was about to post a please help message. I then sat back and looked at the margin settings and realised there were three columns on the page. I deleted them and all is right with Word, my document looks a bit better. I think that a lot of Q&A is caused by people not taking a break and looking at what is going wrong. Also I think most if not all of us have had the "Oh My Gord, it's gone wrong" what happens next is the interesting, some have the 'why has that happen, lets poke it and find out' others 'well I did what I was told and it didn't work therefore you are a fool for asking me, make it work' this makes this assumes what you did and what you were told are the same thing. I made mistakes while under pressure of assuming what I was doing was correct and then getting 'shirty' with people who say 'do you understand it'. So to all it's Friday afternoon (in the UK) Have a nice weekend!
|
|
|
|
|
I think that a lot of Q&A is caused by people taking too many breaks.
"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
|
|
|
|
|
... 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
|
|
|
|