This is my dumping ground for quotes and other stuff relating to the wonderful world of digital & communications.
Rule 1: “The war room and the meetings are for solving problems. There are plenty of other venues where people devote their creative energies to shifting blame.”
Rule 2: “The ones who should be doing the talking are the people who know the most about an issue, not the ones with the highest rank. If anyone finds themselves sitting passively while managers and executives talk over them with less accurate information, we have gone off the rails, and I would like to know about it.” (Explained Dickerson later: “If you can get the managers out of the way, the engineers will want to solve things.”)
Rule 3: “We need to stay focused on the most urgent issues, like things that will hurt us in the next 24—48 hours.”
The stand-up culture—identify problem, solve problem, try again—was typical of the rescue squad’s ethic.
This is the story of a team of unknown—except in elite technology circles—coders and troubleshooters who dropped what they were doing in various enterprises across the country and came together in mid-October to save the website. In about a tenth of the time that a crew of usual-suspect, Washington contractors had spent over $300 million building a site that didn’t work, this ad hoc team rescued it and, arguably, Obama’s chance at a health-reform legacy.
Apple needs to answer some serious questions.
Why wasn’t this broken code spotted by some sort of review process before it ended up in a software build? After all, this sort of mistake can even be picked up by various automated code analysis tools, let alone by human reviewers.
Why wasn’t the failure picked up in the testing phase, before the software was published? After all, testing that each step in a security authentication process still works is kind of important.
Why was a patch for iOS released, thereby revealing the existence of the problem and giving security researchers good and evil the opportunity to reverse engineer it and see whether the problem also existed in OS X — which it did — before that operating system was also patched? After all, both operating systems are produced by the same company. Don’t these people talk to each other?
I think we have some cultural problems here, folks
DeepMind has been building “learning algorithms — ones that automatically learn how to do things from raw data, rather than being programmed to do things”. … The only public demonstration so far of what his company has achieved was getting his AI to learn how to play Space Invaders on an old Atari computer just by showing it the information on screen
…that slow and steady migration is one of the reasons the project has largely managed to stay within its budget with minimal disruption. The project finished within budget in October 2013, with more than 14,800 staff migrated to using Limux and more than 15,000 to OpenOffice
the way that tech often does disrupt industries - by affecting parts of the industry that no-one paid attention to but which were actually key leverage points. Not many magazine people thought of themselves as being in the trucking and light-manufacturing business, for example, but they were, and that was why the internet had such an impact on them. But the opposite can also be true - there are industries where tech doesn’t look important but is actually crucial, but there are also industries where tech looks crucial but doesn’t actually matter very much at all
(In the 1930’s) Long-playing record technology was still in its infancy, and didn’t sound very good for recorded music. But the LP was perfectly fine for the spoken word… given the strange intellectual property agreements hammered out at the time, it was essentially illegal for anyone but blind people to use an LP record player in the 1930s.