|
I thought it is the other way around: the older you get, the less sleep you need. I used to be able to sleep 10 hours everyday, now it is down to 6. 
My articles and software tools
|
|
|
|
|
The thing you do after yawning and before scratching your butt.
--
Talk to the hand!
|
|
|
|
|
Asleep = !Awake;
Awake = !Asleep;
When I can talk about 64 bit processors and attract girls with my computer not my car, I'll come out of the closet. Until that time...I'm like "What's the ENTER key?"
-Hockey on being a geek
|
|
|
|
|
Asleep ~= Awake
!Asleep ~= !Awake
Which I think adequately describes me on the train to and from work each day.
I once programmed in a language where there existed a third possibility. You could have true, false or maybe. [Enable Sarcasm] That was fun! [Disable Sarcasm]
--Colin Mackay--
"In the confrontation between the stream and the rock, the stream always wins - not through strength but perseverance." (H. Jackson Brown)
|
|
|
|
|
Sounds like a more accurate abstraction of life to me. Yes, No, Maybe.
regards,
Paul Watson
Bluegrass
South Africa
Brian Welsch wrote:
"blah blah blah, maybe a potato?" while translating my Afrikaans.
Crikey! ain't life grand?
|
|
|
|
|
I just remembered that it also had a fourth (rarely used) option which was "NoWay". The truth tables were interesting also.
true and false interacted as normal.
NoWay was interesting because, as you know, true = not false, and false = not true. NoWay = not NoWay, false = NoWay, noWay = not true. Not NoWay = NoWay.
In other words NoWay is so false that it would take an infinite amount of time to make it true.
That was a really strange language.
--Colin Mackay--
"In the confrontation between the stream and the rock, the stream always wins - not through strength but perseverance." (H. Jackson Brown)
|
|
|
|
|
Think of the last time you went to a long, boring meeting (or class or lecture) that you felt you had to go to, but didn't really care about one way or the other.
No single raindrop believes that it is responsible for the flood.
|
|
|
|
|
This question implies that LackOfSleep == QualityProgrammer. While I put in a couple of 40 hour days back during school, and have occasionally pulled all-nighters on the job since then, it comes down to this:
If I'm not getting enough sleep because of how I do my job, I'm not doing it right. I've made some sort of mistake, either in the design or more probably in how I've managed the project (or how I've managed the people managing me).
After over twenty years of making a living at writing software, I've found that losing sleep is counterproductive. If you're not getting enough sleep, you're going to write crappy code and make stupid mistakes while debugging.
On the other hand, if you're one of those for whom coding eight hours a day isn't enough, you may think the boss will be impressed with everything you did. Wrong. In fact, he may think you're in all that extra time because you can't do your normal job in the allotted eight hours. At best he's grateful for the free software he's getting from you. The overtime won't make a bit of difference in how you advance through the ranks or your salary.
In short,  == .
Software Zen: delete this;
|
|
|
|
|
You're so correct. The only problem is that I'm too damn stupid to sleep. There's always this "something" I have to do, and all of a sudden it's 3 am. Argh!
I'm thinking about hooking up high voltage electrodes to my alarm and connect them to various parts of my body.
--
Talk to the hand!
|
|
|
|
|
Jörgen Sigvardsson wrote:
I'm thinking about hooking up high voltage electrodes to my alarm and connect them to various parts of my body.
You've been talking to my Dad haven't you?  He's threatening the same thing...
When I can talk about 64 bit processors and attract girls with my computer not my car, I'll come out of the closet. Until that time...I'm like "What's the ENTER key?"
-Hockey on being a geek
|
|
|
|
|
Sounds like your dad is a smart guy!
--
Talk to the hand!
|
|
|
|
|
Jörgen Sigvardsson wrote:
hooking up high voltage electrodes to my alarm and connect them to various parts of my body
Ok, if you're in to that sort of thing  ...
Software Zen: delete this;
|
|
|
|
|
I agree with you, if you are talking about chronic over-working. You're right that a lot of times, if you come to work unrefreshed, or stay up all night, you start writing crappy code. So many times I've been stuck, and have the choice of staying up until I fix whatever is irking me, or saying, "Ah screw it, I'll figure it out in the morning." And more often than not, the latter is the better choice. I hit the problem fresh in the morning, and often figure it out quickly.
That being said, there's definitely something to be said for timely overtime, when it is really needed. Sometimes it's because of unrealistic schedules, sometimes it's because something unexpected came up at the last minute... but I always find it more productive to suck it up, work some extra hours for a few weeks, then whine about it later and try to make sure it doesn't happen again.
No single raindrop believes that it is responsible for the flood.
|
|
|
|
|
Navin wrote:
Sometimes it's because of unrealistic schedules, sometimes it's because something unexpected came up at the last minute...
Unfortunately, that always proves to be the exception to my rule. In my case, the major offender is an old product (it runs under OS/2 for cryin' out loud). Every special thing a customer wants seems to hit the piece I'm responsible for, and nobody schedules that kind of stuff in with everything else I'm doing. Also, the people who quote the schedule for these kinds of things assume I'm say 70% available for their project, when my actual availability is more like 20%. The good news is this old product is going to be 'end-of-life'd during 2004.
Software Zen: delete this;
|
|
|
|
|
Gary Wheeler wrote:
Every special thing a customer wants
Customers. They mess everything up.
No single raindrop believes that it is responsible for the flood.
|
|
|
|
|
|
I totally agree with u!
What would life be without programmers and salesmen?
|
|
|
|
|
I don't sleep much at night, but it's definitly not my computer that's keeping me awake...
A student knows little about a lot.
A professor knows a lot about little.
I know everything about nothing.
|
|
|
|
|
Is that in a Monty Python "Nudge! Nudge! Wink! Wink! A nod's as good as a wink to a blind man? Know what I mean?" kind of way?
--Colin Mackay--
"In the confrontation between the stream and the rock, the stream always wins - not through strength but perseverance." (H. Jackson Brown)
"Does she like photography?" - Eric Idle
|
|
|
|
|
Yep 
A student knows little about a lot.
A professor knows a lot about little.
I know everything about nothing.
|
|
|
|
|
Bob Stanneveld wrote:
Yep
Is that to the question about your original comment being Monty-Python-esque, or to the question I deviously placed after my signature in my previous post?
--Colin Mackay--
"In the confrontation between the stream and the rock, the stream always wins - not through strength but perseverance." (H. Jackson Brown)
|
|
|
|
|
Wish it was to the question after your signature! 
A student knows little about a lot.
A professor knows a lot about little.
I know everything about nothing.
|
|
|
|
|
Bob Stanneveld wrote:
it's definitly not my computer that's keeping me awake...
Yeah Yeah ... stop bragging
|
|
|
|
|
A student knows little about a lot.
A professor knows a lot about little.
I know everything about nothing.
|
|
|
|
|
who tell me sleeping reason
·çäìäìÙâÒ×Ë®º®£¬
׳ʿһȥÙâ²»¸´»¹¡£
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
