Submission + - How to Tell Your Client That His "Expert" is an Idiot
Submission + - The Standards Wars and the Sausage Factory 1
As just one example, Steven Vaughan-Nichols details the steps it took to approve a networking standard that everyone, everyone knew was needed: "Take, for example, the long hard road for the now-universal IEEE 802.11n Wi-Fi standard. There was nothing new about the multiple-in, multiple-out (MIMO) and channel-bonding techniques when companies start moving from 802.11g to 802.11n in 2003. Yet it wasn’t until 2009 that the standard became official."
Submission + - A Short History of Computers in the Movies
For a long time, the "product placement" of big iron was limited to a few brands, primarily Burroughs. For instance:
Batman: The Movie and Fantastic Voyage (both 1966) revert to the archaic Burroughs B205, though Fantastic Voyage also shows an IBM AN/FSQ-7 Combat Direction Central. At 250 tons for each installation (there were about two dozen) the AN/FSQ-7 was the largest computer ever built, with 60,000 vacuum tubes and a requirement of 3 megawatts of power to perform 75,000 ips for regional radar centers. The last IBM AN/FSQ-7, at Luke Air Force Base in Arizona, was demolished in February 1984.
Fun reading, I think.
Submission + - Stop listening to your users (citeworld.com)
Submission + - Computers and Doctor Who: The First 20 Years (smartbear.com)
Actually, for a show so closely associated with the slashdot-techie lifestyle, Doctor Who didn't have much to do with computers early on. This article by Peter Salus traces the formative years, e.g. "In January 1970, Jon Pertwee (Doctor #3) acquired a Cambridge scientist (Caroline John as Liz Shaw) as his companion, which might lead the unsuspecting viewer to think that a firmer computer science basis might ensue. But only in April did Liz exhibit her technical knowledge (by recognizing a Geiger counter reading)." And then we get to K-9.....
Submission + - Fighting the number-one killer in the U.S. with data (citeworld.com) 1
Submission + - The RFP and IT Logistics for Washington's "Pot Czar" (citeworld.com)
But this is an IT and business process story, not a marijuana legalization story. Ron Miller writes about the cloud workflow required to solve the task:
He chose these particular tools because they all had open APIs, which allowed him to mash them together easily into the solution. They were easy to use, so reviewers could learn the system with little or no training, and they were mobile, so users could access the system from any device. In particular he wanted reviewers to be able to use the system on a tablet.
I suppose this could have been written about more mundane RFPs, but I bet you'll find this more interesting than most.
Submission + - Wolfram Alpha Updates Facebook Analytics Features (slashdot.org)
Submission + - Sony fined in UK for PlayStation Network hack (bbc.co.uk)
Submission + - Microsoft Co-founder Dings Windows 8 as 'Puzzling, Confusing' (computerworld.com)
Submission + - Will the Next Web Platform Please Hold Still? (softwarequalityconnection.com)
Fulton doesn't just write a general rant: He gets input from several of the people who are creating browsers and standards. And they don't just spout a company line. My favorite quote is from Bruce Lawson, a Web evangelist for Opera Software as well as a long-time contributor to the Accessibility Task Force of the Web Standards Project: “You wouldn’t believe how many e-mails I get saying, ‘Bruce, would you give me some feedback on my HTML5 page,’ and I look at it, and it’s no more HTML5 than my vacuum cleaner. Because it looks snazzy and it’s got a rounded corner and a drop-shadow, people are calling it HTML5.”"
Submission + - Linux-Friendly Alternatives To MS-Skype? (itworld.com)
Submission + - Is Process Killing the Software Industry? (oreilly.com)
A piece on O'Reilly Radar is arguing that excessive process in software development is sucking the life out of passionate developers, all in the name of making sure that 'good code' gets written. TFA:"The underlying feedback loop making this progressively worse is that passionate programmers write great code, but process kills passion. Disaffected programmers write poor code, and poor code makes management add more process in an attempt to 'make' their programmers write good code. That just makes morale worse, and so on."