"This type of development actually works quite well in some cases."
Wow, that's right bold; gonna call up Standard Deviation to fudge that wedge just a little more?
*Holy sheep shit BatMan, no sentient life here!*
"Quick, incremental updates, along with heavy user involvement, are key characteristics of the emerging software development methods"
Are you merely contemptuous of your readers? What part of that is anything like news?
"A survey conducted for Computerworld showed that an overwhelming majority of the respondents said that traditional corporate development teams could benefit from Web 2.0 techniques, specifically the incremental feature releases, quick user feedback loops and quality assurance programs that include users."
Oh, so you're pimping ComputerWord? (For the record, when I wanna go to my local to get drunk, I take a copy of InformationWeek... shit's so fine, I keep reading even when I'm drunk. Introduces an fascinating non-artistic irony into what follows.)
Why have I not introduced my discourse-based document portal? Cuz you yuppies' kidz are/just plain/stuhpud//.
Folk who earn their salt by sophistry, like other kinds of whores, are not interested in discourse.
Point: I never left. I come back. I was here. I ain't leaving.
*fuckwads*
Like I'm gonna explain myself. Not f'n likely.
Find a thread.
Login.
Find yourself on/. homepage.
Incompetence is the thin edge of a wedge called corruption.
I've been on the "web" since '72.
Dealing with you has silenced me.
Which doesn't mean I went elsewhere...... that's what yuppies do.
bla-yada, kiddos... yada-blah.
An arguably credible place to make plausibly legitimate arguments...... all the while knowing you're in no danger of entailments.
Kidz, it's cliche that the smart are stuhpuhd.
*Don't know how I am? Follow a link... google... I've only been online for 2 or 3 decades. fuckwads*
I never ever ever ever write run-on paragraphs like that.
WTF do you think you are to ignore my having hit NL?
I know precisely who you are: passive agressive geeks who very precisely hide your true nature. Want proof? Your interface has been pathetic since day.1 and remains so.
lamerz
W^B
p.s. read the.sig asshole. I no longer include geek-code... I/know/ you're way too ADD to consult. "FOAF" pfffffffffffffffffffffffft!
In '72 I was toggling bits/bytes in manually to crack the "evuhl empire"... tracking subs and suchlike; after I gagged on tumbling Chile's democratically elected gov't I shifted to supporting SAC/NORAD by single-handedly maintaining the arctic tropo site. *shrug* So what... withdrawing from all that to run MCR/CBC and repair kits at Heathkit was proper.
My point: snake oil, gentlemen and gentlewomen. Before TimBL (in a resource rich environment, note) invented WWW some of us had been toying with and using SGML/hyper-text for years... in my case developing MILSPEC tech_docs for navaids in an R&D environement... to land passenger planes in snow storms.
*shrug*
I've been on welfare since '92. I got grossed out. Uber-grossed. Snake-oil... smoke and mirrors... Gates, M$, Win95... not QuatroPro, or JWZ and NS1.02 (Mosaic 0.72a for that matter.)
It ain't just forward fire support that suffers... or e-commerce... or S&R... right down to the roots, kidz... check out http://thedailywtf.com/
Point? Saddam Hussein is a brave mofo... massively hypocritical mofos (i.e. "plausible deniability") screw up the education system or rob old folk of their retirement funds.
*shrug*
To you, from failing hands, we throw the torch.
stay well
"The authors acknowledge that the book isn't meant for the MySQL beginner. Even so, the book does spend a little time going over a refresher of MySQL. If the reader is looking for a book on the basics of MySQL, though..."
Speaks well for the authors... as though they're pro (assuming that section isn't just fluff).
I'd take that as an indication of quality.
Now, if a person proceeds on the assumption that the NASA is witholding and engaged in a massive deceipt, then everything becomes a mug's game. But listening to the daily briefings has been a real insight... the impression I got was that the NASA was easily as good as the best group I've ever worked with/for, and better than most.
But here's my point... Dittemore laid a lot of things out on the table, and in the course of that displayed the priorities: 1) get the crew back, 2) get the shuttle back in a way that minimizes turnaround time.
Worst case scenario (short of catastrophic failure, of course) is to get the thing groaning and thumping down to an altitude where crew could bail out... ya gotta admit that's really ugly.
Slightly better is to adjust attitude to minimize stresses on a damaged area; this means beating the crap out of the rest of the craft, but pondering the foam impact lead to a possibility of localized structural damage, i.e. the bird gets bruised but lands in one piece, so there's some heavy lifting to be done before it flies again.
But actually, the scenario that developed included this fact: Columbia was flying just fine... word is that there were no out of nominal indications. Roll trim became active at some point, which indicates that left side drag. Jets fired, which indicates that trim wasn't quite keeping up. The interest expressed was in the way things were developing, where the system was losing ground against increasing drag./But/ Columbia was acceptably oriented when there was loss of signal.
Even if it's the case that mistaken conclusions were acted on, things weren't just overlooked.
Columbia's flight characteristics did not hint at the doom that was to unfold. Now,/there's/ a basis for real humility.
Skill sets have priorities and criteria built in as assumptions. Managers usually have the final say because, normally, bottom-line dictates ("We don't want to screw up cuz we might get sued" is the thinking of a "rational agent".) If I remember correctly, those who knew the O-rings' thermal characteristics and their track record for blow-by were asked, in the course of one of those conference calls, to "take off their engineer's hats and put on their manager's hats"... and the decision was made... ready to go. Human, all too human, ehh whot?
Oh man, the hours I worked with GeoProgrammer... I even had the 64K RAM pack...//64K//!!!! haaahaha It was a totally wonderful assembler IDE.
I used it for creating optimized fractal programs, calling BIOS for the math. And I wrote a double-res print driver, and even got the 64C to run at 2400BPS instead of 2396.5 or whatever it was by default.
*Hey, if some C64 geek out there remembers "Thinking Cap", give me a call wudya?*
The only machine I enjoyed programming more was NEC Trek... Z80 at 1.2 MHz! Whoohooo! 8-)
What I find sadest is that there's a real chance the failure might never be tracked down or traced back. I followed it all day, and the closest thing to fault indication was garbled radio, but since the vehicle is travelling in a bubble of plasma, that's not unusual.
Telemetry failed "out of range low", as if the instrumentation had just died... and whatever was failing was failing from the trailing edge forward, as though some circuitry was giving up... certainly no obvious connection to had insulation contact the leading edge on take-off. But this is off topic...
Concerning probabilies of survival, keep in mind that the vehicle was travelling 12,500 MPH... unimaginable forces. Weather radar showing the debris path gives some idea of the energy that needed to be dissipated.
Here's something that really chokes me up... I had a comm link go quiet on me once upon a time, a long time ago. My thoughts are with crew's family, of course, but this really hits the support staff. "Columbia, Houston... UHF comm check." [no reply]
(Note: My.sig may seem cruel, but it was my motto at work in avionics... sometimes failure is not an option.)
Apparently coaches have been getting athletes to wear high tight socks (I suppose somewhat like "executive stockings") on long plane trips, with good results. So now high socks will become standard geek ware, instead of pocket protectors?
It's easy to be cool when all you have to do is put in your 35 hours and collect a cheque, but gawd forbid if you should have to actually get something done!/That/ puts a tiger in your tank. *does that date me somewhat?*
In another place (is it PC to mention LiveJournal?) a friend mentionned how her mic stopped working; she had upgraded to OS-X 10.1... the advice was *drumroll* upgrade to 10.2... but 10.2 has the same problem... sooooo &tc &tc &tc. My comments there:
"... gawd, isn't this lame? I remember dreading upgrades because 1) the printer might stop working, 2) the backup disks might be unreadable, 3) it might scramble the passwords, 4) the batch files would no longer work, 5) bla-bla-blah... but that was in the mid 80s!!
As a side-note, Linux geeks spend a lot of time beating up on themselves and each other cuz of SNAFUs like this... I'm sorry to hear that OS-X is just as stuhned, but in a perverse way it leaves me feeling better."
When little things are a royal pain, is it any surprise sysadmin types are loathe to do bigger jobs, like install SPs in M$ $QL $erver?
FWIW, this is my favorite part of JwZ's rant... and I defy anyone to say the points are trivial:
"Resizing the window changes the aspect ratio of the video! Yeah, I'm sure someone has ever wanted that.
It moves the mouse to the upper left corner of every dialog box it creates! Which is great, because that means that when it gets into this cute little state of popping up a blank dialog that says "Error" five times a second, you can't even move the mouse over to another window to kill the program, you have to log in from another machine."
Actually, I think it is just a matter of basics. For a thorough treatment, this is as good as any I've found and far better than most: MSSQL-UDP Analysis
I hope Earl wasn't just indulging in M$/Enron type sophistry... I mean, heck, nobody deserves to be found out to be both unprincipled and incompetent.
As Bucky Fuller put it, tell the truth, tell all of it, and tell it right away.
*The part that blows me away is how officialdom acknowledges that admin-types are uncomfortable with M$ service packs *DUHH* because they sometimes call for editing critical system files. huh... I mean, well, I made a good living cleaning up after engineers, but still... there's something sad about that, doncha think?*
... just thinking about the "sabotage" report that filtered up from the backrooms... gawd, that's such M$ FUD/spam/mind-ph*k... like callling the outage on the XP registration service "maintenance" [see my blog]... "Oh, we wouldn't call that a bug"... it's Enron-think, and it sux.
You in TO?
Okay, since we're here in/. and I'm me and you're you... and in the spirit of *damn, I'm gonna get it wrong too!* "in order to achieve what we never have before, we have to do what we never have before": I was hacking the Evil Empire back when that meant the USSR. And we shurr as fuck didn't fool around.
Ok, so they used M$... ok, so they didn't do the patches ("SPs may take as long as half an hour to install, and may involve editing critical files, and a lot of staff don't feel comfortable with that degree of bla-bla-blah"... but WTF?! They didn't know the friggin' web was in spasm? (ISC shows a peak of something like 8K packets / targets per minute... I think that's low). I mean, who's doing IT for something that frangible and doesn't have their heads up?!
Geezus, when we did IMC with CMAQ for FTAA/QC-A20... but that's another story, yaa? *grin*
stay in touch
regards to everyone there from the Far East of North America (i.e. Alexa's consituency)
and my best to Ducasse [mark my works: he's going to be the first NDP prime minister @ hfx_ben 2247AST 25JAN03]
cya
In my blog (I got a little pissed and vented some) I wrote, "Like democracy itself, the 'net is vulnerable to stupidly self-indulgent ineptitude. Because SQL Server needs to be tucked in, otherwise it's a train wreck waiting for someone to act nasty, global web reachability dived below 75% around midnight EST."
In the "gruesome details" category, Matrix NetSystems' report includes this gem: "ISS MSS (Managed Security Services) has recorded 2.5 million attacks from 12 a.m. to 3 a.m. EST (GMT-5) on January 25, 2003." What's that, approx 850K / hour... approx 15K / minute... approx 250 / second.
I happened to be listening to the New Democratic Party's leadership convention live: yes, they did use Web voting; and yes, they did encounter problems consistent with this worm, problems which gave rise to rumours of sabotage since it seemed that someone was denying access to login. [Were they using M$ $erver $000?.] Happily, things worked out just fine. I don't know what the full story is yet.
During the dot-bomb "adjustment" some of us recalled how we had been saying that the 90s was like a slow-motion version of the 30s. I don't think Dubya has what it takes to jerk that sort of mass around. Now, some of the slugs who hang just out of sight, though...
Slashdot Mirror
"This type of development actually works quite well in some cases." Wow, that's right bold; gonna call up Standard Deviation to fudge that wedge just a little more? *Holy sheep shit BatMan, no sentient life here!*
"Quick, incremental updates, along with heavy user involvement, are key characteristics of the emerging software development methods" Are you merely contemptuous of your readers? What part of that is anything like news? "A survey conducted for Computerworld showed that an overwhelming majority of the respondents said that traditional corporate development teams could benefit from Web 2.0 techniques, specifically the incremental feature releases, quick user feedback loops and quality assurance programs that include users." Oh, so you're pimping ComputerWord? (For the record, when I wanna go to my local to get drunk, I take a copy of InformationWeek ... shit's so fine, I keep reading even when I'm drunk. Introduces an fascinating non-artistic irony into what follows.)
Why have I not introduced my discourse-based document portal? Cuz you yuppies' kidz are /just plain /stuhpud//.
Folk who earn their salt by sophistry, like other kinds of whores, are not interested in discourse.
Point: I never left. I come back. I was here. I ain't leaving.
*fuckwads*
Like I'm gonna explain myself. Not f'n likely. Find a thread. Login. Find yourself on /. homepage.
Incompetence is the thin edge of a wedge called corruption.
I've been on the "web" since '72.
Dealing with you has silenced me.
Which doesn't mean I went elsewhere ... ... that's what yuppies do.
bla-yada, kiddos ... yada-blah.
An arguably credible place to make plausibly legitimate arguments ... ... all the while knowing you're in no danger of entailments.
Kidz, it's cliche that the smart are stuhpuhd.
*Don't know how I am? Follow a link ... google ... I've only been online for 2 or 3 decades. fuckwads*
Dogs lick themselves cuz they can; the human equivalent program the interface to /.
bid: pfffffffffffft
I never ever ever ever write run-on paragraphs like that. WTF do you think you are to ignore my having hit NL? I know precisely who you are: passive agressive geeks who very precisely hide your true nature. Want proof? Your interface has been pathetic since day.1 and remains so. lamerz W^B p.s. read the .sig asshole. I no longer include geek-code ... I /know/ you're way too ADD to consult. "FOAF" pfffffffffffffffffffffffft!
In '72 I was toggling bits/bytes in manually to crack the "evuhl empire" ... tracking subs and suchlike; after I gagged on tumbling Chile's democratically elected gov't I shifted to supporting SAC/NORAD by single-handedly maintaining the arctic tropo site. *shrug* So what ... withdrawing from all that to run MCR/CBC and repair kits at Heathkit was proper.
My point: snake oil, gentlemen and gentlewomen. Before TimBL (in a resource rich environment, note) invented WWW some of us had been toying with and using SGML/hyper-text for years ... in my case developing MILSPEC tech_docs for navaids in an R&D environement ... to land passenger planes in snow storms.
*shrug*
I've been on welfare since '92. I got grossed out. Uber-grossed. Snake-oil ... smoke and mirrors ... Gates, M$, Win95 ... not QuatroPro, or JWZ and NS1.02 (Mosaic 0.72a for that matter.)
It ain't just forward fire support that suffers ... or e-commerce ... or S&R ... right down to the roots, kidz ... check out http://thedailywtf.com/
Point? Saddam Hussein is a brave mofo ... massively hypocritical mofos (i.e. "plausible deniability") screw up the education system or rob old folk of their retirement funds.
*shrug*
To you, from failing hands, we throw the torch.
stay well
tightwad
"The authors acknowledge that the book isn't meant for the MySQL beginner. Even so, the book does spend a little time going over a refresher of MySQL. If the reader is looking for a book on the basics of MySQL, though ..."
Speaks well for the authors ... as though they're pro (assuming that section isn't just fluff).
I'd take that as an indication of quality.
I think you got it: I found it painfully un-funny ... likely it'd key right in with first year students' sense of humour.
--
If you look to see how the system works
likely you'll find that it doesn't.
Hogwash ... you must have mis-spoken yourself. It's elementary that the sample must be random ... not simple, not easy, but elementary and requisite.
But here's my point ... Dittemore laid a lot of things out on the table, and in the course of that displayed the priorities: 1) get the crew back, 2) get the shuttle back in a way that minimizes turnaround time. ... ya gotta admit that's really ugly.
Slightly better is to adjust attitude to minimize stresses on a damaged area; this means beating the crap out of the rest of the craft, but pondering the foam impact lead to a possibility of localized structural damage, i.e. the bird gets bruised but lands in one piece, so there's some heavy lifting to be done before it flies again.
Worst case scenario (short of catastrophic failure, of course) is to get the thing groaning and thumping down to an altitude where crew could bail out
But actually, the scenario that developed included this fact: Columbia was flying just fine ... word is that there were no out of nominal indications. Roll trim became active at some point, which indicates that left side drag. Jets fired, which indicates that trim wasn't quite keeping up. The interest expressed was in the way things were developing, where the system was losing ground against increasing drag. /But/ Columbia was acceptably oriented when there was loss of signal.
Even if it's the case that mistaken conclusions were acted on, things weren't just overlooked.
Columbia's flight characteristics did not hint at the doom that was to unfold. Now, /there's/ a basis for real humility.
Full size photo, which was linked to the Sensors and timeline There's also a page of general Columbia information.
FWIW I've created an intereactive presentation of sensor readings.
Skill sets have priorities and criteria built in as assumptions. Managers usually have the final say because, normally, bottom-line dictates ("We don't want to screw up cuz we might get sued" is the thinking of a "rational agent".) ... and the decision was made ... ready to go.
If I remember correctly, those who knew the O-rings' thermal characteristics and their track record for blow-by were asked, in the course of one of those conference calls, to "take off their engineer's hats and put on their manager's hats"
Human, all too human, ehh whot?
I used it for creating optimized fractal programs, calling BIOS for the math. And I wrote a double-res print driver, and even got the 64C to run at 2400BPS instead of 2396.5 or whatever it was by default.
*Hey, if some C64 geek out there remembers "Thinking Cap", give me a call wudya?*
The only machine I enjoyed programming more was NEC Trek ... Z80 at 1.2 MHz! Whoohooo! 8-)
Telemetry failed "out of range low", as if the instrumentation had just died
Concerning probabilies of survival, keep in mind that the vehicle was travelling 12,500 MPH ... unimaginable forces. Weather radar showing the debris path gives some idea of the energy that needed to be dissipated.
Here's something that really chokes me up ... I had a comm link go quiet on me once upon a time, a long time ago. My thoughts are with crew's family, of course, but this really hits the support staff. "Columbia, Houston ... UHF comm check." [no reply]
(Note: My .sig may seem cruel, but it was my motto at work in avionics ... sometimes failure is not an option.)
Apparently coaches have been getting athletes to wear high tight socks (I suppose somewhat like "executive stockings") on long plane trips, with good results. So now high socks will become standard geek ware, instead of pocket protectors?
In another place (is it PC to mention LiveJournal?) a friend mentionned how her mic stopped working; she had upgraded to OS-X 10.1
FWIW, this is my favorite part of JwZ's rant ... and I defy anyone to say the points are trivial:
Actually, I think it is just a matter of basics.
For a thorough treatment, this is as good as any I've found and far better than most: MSSQL-UDP Analysis
As Bucky Fuller put it, tell the truth, tell all of it, and tell it right away.
*The part that blows me away is how officialdom acknowledges that admin-types are uncomfortable with M$ service packs *DUHH* because they sometimes call for editing critical system files. huh ... I mean, well, I made a good living cleaning up after engineers, but still ... there's something sad about that, doncha think?*
This Research Advisary reads real well ... lays it right out there. Any admin-type that ignores this should really find another line of work.
... just thinking about the "sabotage" report that filtered up from the backrooms ... gawd, that's such M$ FUD/spam/mind-ph*k ... like callling the outage on the XP registration service "maintenance" [see my blog] ... "Oh, we wouldn't call that a bug" ... it's Enron-think, and it sux.
Geezus, when we did IMC with CMAQ for FTAA/QC-A20
stay in touch
regards to everyone there from the Far East of North America (i.e. Alexa's consituency)
and my best to Ducasse [mark my works: he's going to be the first NDP prime minister @ hfx_ben 2247AST 25JAN03]
cya
In the "gruesome details" category, Matrix NetSystems' report includes this gem: "ISS MSS (Managed Security Services) has recorded 2.5 million attacks from 12 a.m. to 3 a.m. EST (GMT-5) on January 25, 2003." What's that, approx 850K / hour ... approx 15K / minute ... approx 250 / second.
I happened to be listening to the New Democratic Party's leadership convention live: yes, they did use Web voting; and yes, they did encounter problems consistent with this worm, problems which gave rise to rumours of sabotage since it seemed that someone was denying access to login. [Were they using M$ $erver $000?.] Happily, things worked out just fine. I don't know what the full story is yet.
During the dot-bomb "adjustment" some of us recalled how we had been saying that the 90s was like a slow-motion version of the 30s. I don't think Dubya has what it takes to jerk that sort of mass around. Now, some of the slugs who hang just out of sight, though ...