|
The Texas Chain Saw Massacre
|
|
|
|
|
Oso Oluwafemi Ebenezer wrote: Home Alone 1-5
Wait, what??? There are 5 Home Alones??
Jeremy Falcon
|
|
|
|
|
Yes, there are 5 too many.
|
|
|
|
|
I stopped at two. Never saw the third one. Four and five seem like milking the cow.
Jeremy Falcon
|
|
|
|
|
Never saw any of them. The ads were bad enough.
|
|
|
|
|
|
"We're No Angels", 1955 -- Bogart and Ustinov
"The Box of Delights", 1984
|
|
|
|
|
Best movie ever ELF!
.'\ /`.
.'.-.`-'.-.`.
..._: .-. .-. :_...
.' '-.(o ) (o ).-' `.
: _ _ _`~(_)~`_ _ _ :
: /: ' .-=_ _=-. ` ;\ :
: :|-.._ ' ` _..-|: :
: `:| |`:-:-.-:-:'| |:' :
`. `.| | | | | | |.' .'
`. `-:_| | |_:-' .'
`-._ ```` _.-'
``-------'/xml>
|
|
|
|
|
How many of the guys know about Reliability engineering? Do you or your company follows this to showcase your product/services?
I just wanted to know if it would be helpful if I write an article on this wrt to software?
I was into software developement (Good old VC++ with MFC) and thats how I got introduced to Codeproject. But 5 years ago, I had to change my direction in to core enginnering to protect my job from overseas developers. It was the difficult initial years to keep my head above the water and grasp the whole concept.
So just wanted to know if these kind of articles ( mostly consisting of abstract concept, formulas and statistics) will be welcomed or not?
cheers,
Super
------------------------------------------
Too much of good is bad,mix some evil in it
|
|
|
|
|
Yes - if you can write an article around the concepts, formulae and statistics I'd definitely like to read it. It is something we should look to apply in software development.
(A good quote I heard: "We have fault tolerant hardware and we have fault intolerant software running on it")
|
|
|
|
|
Write it, but maybe it should be a Reference? And try not to rely heavily on graphics and charts.
|
|
|
|
|
Movie Quote Of The Day
'A ludicrous parcel of driveling galoots,' ma'am.
Which movie?
|
|
|
|
|
|
The French
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
Grease: the pre-teen years
|
|
|
|
|
Rambo: First blood
Every day, thousands of innocent plants are killed by vegetarians.
Help end the violence EAT BACON
|
|
|
|
|
But..but.. I was going to write that
|
|
|
|
|
Jar Jar Binks of the Marvel Universe
Your time will come, if you let it be right.
|
|
|
|
|
Every single iPhone launch event
|
|
|
|
|
On the Spot: Average Social Media User
|
|
|
|
|
|
The Lounge in a Box.
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
|
|
|
|
|
OK, so we had a messy, messy day here with a deploy that went pear-shaped, so I was wondering if anyone has any true horror stories of deploys that went terribly, horrifyingly bad. The sorts of thing where you no longer even visit that town because the Wanted posters are still flying from the street posts.
cheers
Chris Maunder
|
|
|
|
|
Chris Maunder wrote: I was wondering if anyone has any true horror stories of deploys that went
terribly, horrifyingly bad.
I have cleaned up after plenty of people who have had deployments go sideways. So far, knock on wood I have always had a good back out plan.
Common sense is admitting there is cause and effect and that you can exert some control over what you understand.
|
|
|
|
|
The worst deployment I remember involved an act of nature in the middle of a software upgrade on a client's site. The installation required a copy of the client's data on tape for reformatting of certain data files. As luck would have it, the building was struck by lightning, causing damage to the tape in the middle of reloading a critcal index. For reasons as yet unknown, we discovered that the client had not backed up their data for three months prior to the incident. Since I was on duty during the holiday weekend, I was stuck with the task of salvaging the damaged index file from the raw data that survived... a seventeen hour marathon.
|
|
|
|