|
|
At risk of sounding too political for the lounge can Mrs Reagan be regarded as the first female president of the United States??
|
|
|
|
|
In our family she was regarded as a real lady. Something that cannot be said of all our past First Ladies. She may have had significant influence over Reagan. Who can really tell? And President Reagan had an open mind when it came to considering the advice of other people. He knew and accepted his own limitations! This is one trait sadly lacking in some of the other Presidents.
Get me coffee and no one gets hurt!
modified 6-Mar-16 13:03pm.
|
|
|
|
|
Hmmm, yes but if I remember correctly Ronnie Regan was starting to show the signs of Altzimers and some Parkinsons and refered to Nacy as Mummy once in public...Show for certanly later bits she was definitly driving but as you said 
|
|
|
|
|
Probably not, James A. Garfield and Woodrow Wilson were both medically incapacitated for extended periods of time; the latter also had persistent rumors of his wife running the show behind the scenes while he was in bed.
Which two Presidents were incapacitated for long periods while still in office[^]
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Being a Brit, I was not aware of James A Garfield being medically incapacitated, I heard about Woodrow Wilson via the History channel
|
|
|
|
|
Classy lady! R.I.P.
New version: WinHeist Version 2.2.2 Beta tomorrow (noun): a mystical land where 99% of all human productivity, motivation and achievement is stored.
|
|
|
|
|
Get me coffee and no one gets hurt!
|
|
|
|
|
Any experience with?
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
I think there aren't that many Japanese CP-Members 
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
Well, there were - but the last time Clonezilla attacked Tokyo, most of them perished... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: but the last time Clonezilla attacked Tokyo, most of them perished disassembled.
ftfy 
|
|
|
|
|
Yes, but the last time I used it was a few years ago. It worked well, but it wasn't the most user friendly. Other options are EaseUS Todo Backup or Aomei Backupper.
|
|
|
|
|
I can second AOMEI - I use it and it's damn good! 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: What are your methods?
Well, I take several approaches, often multiple ones:
- Determine test fixture -- what do I need to set up to actually debug / test? How do I isolate the test fixture? How can it be automated so I'm not clicking through the UI?
- Write the test first. I actually do this very rarely because I find it hard to express the test results ahead of time. It's only when I write the actual code that I think, ok, this needs to be tested, that needs to be tested. Also, when dealing with new technologies, I often don't know what the format of the data is until I get the hardware or API working -- what does the card scanner actually give me, what does the JSON actually look like?
- Step through the code. I do this almost all the time to make sure that I'm understanding correctly the tech with which I'm interfacing.
- Write the test after writing the code. For certain things, I definitely do this. Once the baseline code is working, I can then throw different scenarios at it. Useful scenarios that represent anticipated use cases, not just mindless contract testing or the like.
- Debug the tests.
- Try out the code via the UI. Funny thing is, that often reveals things I didn't consider.
- Put the app in front of someone else. Not so funny is seeing how other people go about using the app, and the bugs that are revealed in that process. Not just algorithmic bugs, but also UX bugs -- if the user experience sucks, I consider that a bug.
- Put the app in front of select customers. Very revealing and is the best way to discover that the spec itself is buggy.
So debugging is not just about code. It's about the user experience, whether the spec accurately captured the user's needs, and understanding how stuff is used in the wild.
Marc
|
|
|
|
|
Oh, Marc!
That was far too serious for Sunday...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: That was far too serious for Sunday...
I know.  But it got me thinking!
Marc
|
|
|
|
|
Debugging? Testing? Pah! That's what customers are for.  
|
|
|
|
|
You don't work for HP do you?
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: What are your methods?
No need to debug if you get it right the first time! Of course, this rarely happens!
"Go forth into the source" - Neal Morse
|
|
|
|
|
I used to check in insect repellent with my code in TFS. I had to stop because of that awful code smell.
"You'd have to be a floating database guru clad in a white toga and ghandi level of sereneness to fix this goddamn clusterfuck.", BruceN[ ^]
|
|
|
|
|
I test as I go. I'd rather debug 10-50 lines than get 100's of lines in to find I must have been smoking the wacky taccy with code that had no hope of ever working.
When people bring me code they want help debugging, I usually gut the code to something smaller and gives proof of concept instead of dealing with all the bells and whistles they coded before finding if the core code was going to work in the first place.
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|
|
'Prince of Tides' author Pat Conroy dies at 70[^]
Cancer is a [REDACTED].
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
![Rose | [Rose]](https://www.codeproject.com/script/Forums/Images/rose.gif)
![Rose | [Rose]](https://codeproject.freetls.fastly.net/script/Forums/Images/rose.gif)