<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for edumbill</title><link>http://disqus.com/by/edumbill/</link><description></description><atom:link href="http://disqus.com/edumbill/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Tue, 25 Jun 2013 00:38:49 -0000</lastBuildDate><item><title>Re: Open to Rackspace</title><link>http://journal.dajobe.org/journal/posts/2013/06/24/open-to-rackspace/#comment-941072638</link><description>&lt;p&gt;Congratulations, old pal. I'm sure it's going to be a great time there for you.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Edd Dumbill</dc:creator><pubDate>Tue, 25 Jun 2013 00:38:49 -0000</pubDate></item><item><title>Re: Let&amp;#8217;s do this the hard way</title><link>http://radar.oreilly.com/2013/03/lets-do-this-the-hard-way.html#comment-1444126702</link><description>&lt;p&gt;More pertinent info in this article&lt;/p&gt;&lt;p&gt;&lt;a href="http://blog.sdelements.com/why-the-latest-rails-exploit-is-indicative-of-a-bigger-problem/" rel="nofollow noopener" target="_blank" title="http://blog.sdelements.com/why-the-latest-rails-exploit-is-indicative-of-a-bigger-problem/"&gt;http://blog.sdelements.com/...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Quote: [[&lt;/p&gt;&lt;p&gt;Security-minded developers can protect themselves by taking the following steps:&lt;/p&gt;&lt;p&gt;Turn off unnecessary extensibility in third party libraries and frameworks&lt;/p&gt;&lt;p&gt;Do not use untrusted input in libraries that provide broad extensibility, such as Apache’s Xalan with extensions enabled&lt;/p&gt;&lt;p&gt;Be vigilant about monitoring for and patching newly discovered vulnerabilities in frameworks and third party libraries. Wherever possible, sign up for security mailing lists or groups likeRuby on Rails Security&lt;/p&gt;&lt;p&gt;]]&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Edd Dumbill</dc:creator><pubDate>Wed, 27 Mar 2013 22:21:00 -0000</pubDate></item><item><title>Re: Let&amp;#8217;s do this the hard way</title><link>http://radar.oreilly.com/2013/03/lets-do-this-the-hard-way.html#comment-844337784</link><description>&lt;p&gt;More pertinent info in this article&lt;/p&gt;&lt;p&gt;&lt;a href="http://blog.sdelements.com/why-the-latest-rails-exploit-is-indicative-of-a-bigger-problem/" rel="nofollow noopener" target="_blank" title="http://blog.sdelements.com/why-the-latest-rails-exploit-is-indicative-of-a-bigger-problem/"&gt;http://blog.sdelements.com/...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Quote: [[&lt;/p&gt;&lt;p&gt;Security-minded developers can protect themselves by taking the following steps:&lt;/p&gt;&lt;p&gt;Turn off unnecessary extensibility in third party libraries and frameworks&lt;/p&gt;&lt;p&gt;Do not use untrusted input in libraries that provide broad extensibility, such as Apache’s Xalan with extensions enabled&lt;/p&gt;&lt;p&gt;Be vigilant about monitoring for and patching newly discovered vulnerabilities in frameworks and third party libraries. Wherever possible, sign up for security mailing lists or groups likeRuby on Rails Security&lt;/p&gt;&lt;p&gt;]]&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Edd Dumbill</dc:creator><pubDate>Wed, 27 Mar 2013 18:21:24 -0000</pubDate></item><item><title>Re: Why I&amp;#8217;m changing my tune on paywalls</title><link>http://radar.oreilly.com/2013/03/why-im-changing-my-tune-on-paywalls.html#comment-1444126433</link><description>&lt;p&gt;My basic uncut reaction is: I'd rather watch HBO programming than the endless dross on network TV that must support advertisers. Makes senses that this translates. Smaller audience, but a model that gives you greater scope for quality and subject.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Edd Dumbill</dc:creator><pubDate>Mon, 18 Mar 2013 15:24:00 -0000</pubDate></item><item><title>Re: Why I&amp;#8217;m changing my tune on paywalls</title><link>http://radar.oreilly.com/2013/03/why-im-changing-my-tune-on-paywalls.html#comment-833663813</link><description>&lt;p&gt;My basic uncut reaction is: I'd rather watch HBO programming than the endless dross on network TV that must support advertisers. Makes senses that this translates. Smaller audience, but a model that gives you greater scope for quality and subject.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Edd Dumbill</dc:creator><pubDate>Mon, 18 Mar 2013 11:24:29 -0000</pubDate></item><item><title>Re: Peeking Into the Trough</title><link>http://strata.oreilly.com/2013/01/peeking-into-the-trough.html#comment-783671258</link><description>&lt;p&gt;I went into a bit more detail about what I think of the hype cycle in this piece, "I Scoff At the Trough" - &lt;a href="http://edd.me/WxDaOU" rel="nofollow noopener" target="_blank" title="http://edd.me/WxDaOU"&gt;http://edd.me/WxDaOU&lt;/a&gt;.&lt;/p&gt;&lt;p&gt;To summarize, the hype cycle is just common sense in a dark suit. If you focus on your goals and business problems, it's a lot harder to become unstuck. Tech for tech's sake has a low chance of doing what you want it to.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Edd Dumbill</dc:creator><pubDate>Wed, 30 Jan 2013 15:40:00 -0000</pubDate></item><item><title>Re: Aaron was one of us</title><link>http://radar.oreilly.com/2013/01/aaron-was-one-of-us.html#comment-1444128341</link><description>&lt;p&gt;I think you are perhaps replying to voices other than mine. I don't agree with everything Aaron did, but I do benefit from much of his work in open standards, Creative Commons and the public domain. Furthermore, I was very struck by his willingness to engage with others and not be an elitist. I acknowledge above, and indeed it's critical to do so, that he was no saint. My injunction to myself and all of us is to be conscious that every day, even in small ways, we can help other people.&lt;/p&gt;&lt;p&gt;For the "meal ticket" issue, with your gracious acceptance, I'm not going to divert this thread into that discussion, because those issues have been played out elsewhere and continue to do so. Not everything that earns people their meal tickets is necessarily right.&lt;/p&gt;&lt;p&gt;In this post, I wanted to note and take inspiration from Aaron's humanity and sharing.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Edd Dumbill</dc:creator><pubDate>Mon, 28 Jan 2013 14:37:00 -0000</pubDate></item><item><title>Re: Aaron was one of us</title><link>http://radar.oreilly.com/2013/01/aaron-was-one-of-us.html#comment-780703793</link><description>&lt;p&gt;I think you are perhaps replying to voices other than mine. I don't agree with everything Aaron did, but I do benefit from much of his work in open standards, Creative Commons and the public domain. Furthermore, I was very struck by his willingness to engage with others and not be an elitist. I acknowledge above, and indeed it's critical to do so, that he was no saint. My injunction to myself and all of us is to be conscious that every day, even in small ways, we can help other people.&lt;/p&gt;&lt;p&gt;For the "meal ticket" issue, with your gracious acceptance, I'm not going to divert this thread into that discussion, because those issues have been played out elsewhere and continue to do so. Not everything that earns people their meal tickets is necessarily right.&lt;/p&gt;&lt;p&gt;In this post, I wanted to note and take inspiration from Aaron's humanity and sharing.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Edd Dumbill</dc:creator><pubDate>Mon, 28 Jan 2013 09:37:19 -0000</pubDate></item><item><title>Re: The future of programming</title><link>http://radar.oreilly.com/2013/01/the-future-of-programming.html#comment-1444125878</link><description>&lt;p&gt;Thanks! I think my underlying sentiment here is that we should be at the age of telling computers what we want, not what to do.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Edd Dumbill</dc:creator><pubDate>Fri, 11 Jan 2013 15:59:00 -0000</pubDate></item><item><title>Re: The future of programming</title><link>http://radar.oreilly.com/2013/01/the-future-of-programming.html#comment-1444125872</link><description>&lt;p&gt;Good question. Here's some initial thoughts. I'd like to build this up into a bookshelf that can accompany this investigation.&lt;/p&gt;&lt;p&gt;LANGUAGES&lt;/p&gt;&lt;p&gt;Clojure Programming&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/0636920013754.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/0636920013754.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;ClojureScript: Up and Running&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/0636920025139.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/0636920025139.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Programming Scala&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/9780596155964.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/9780596155964.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;DEVICES&lt;/p&gt;&lt;p&gt;Arduino Cookbook&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/0636920022244.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/0636920022244.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Programming Android&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/0636920023005.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/0636920023005.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Learning iOS Programming&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/0636920028642.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/0636920028642.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Building Wireless Sensor Networks&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/9780596807740.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/9780596807740.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;DATA&lt;/p&gt;&lt;p&gt;R Graphics Cookbook&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/0636920023135.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/0636920023135.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;R in a Nutshell&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/0636920022008.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/0636920022008.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;R Cookbook&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/9780596809164.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/9780596809164.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Python for Data Analysis&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/0636920023784.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/0636920023784.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Hadoop: The Definitive Guide&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/0636920021773.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/0636920021773.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;DEMOCRATIZED&lt;/p&gt;&lt;p&gt;We have plenty on JavaScript, but these titles help to bring the wild west under control:&lt;/p&gt;&lt;p&gt;JavaScript Enlightenment&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/0636920027713.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/0636920027713.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;JavaScript: The Good Parts&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/9780596517748.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/9780596517748.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Maintainable JavaScript&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/0636920025245.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/0636920025245.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Here's a NoStarch book on Scratch&lt;/p&gt;&lt;p&gt;Super Scratch Programming Adventure!&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/9781593274092.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/9781593274092.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Edd Dumbill</dc:creator><pubDate>Fri, 11 Jan 2013 15:24:00 -0000</pubDate></item><item><title>Re: The future of programming</title><link>http://radar.oreilly.com/2013/01/the-future-of-programming.html#comment-763795114</link><description>&lt;p&gt;Thanks! I think my underlying sentiment here is that we should be at the age of telling computers what we want, not what to do. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Edd Dumbill</dc:creator><pubDate>Fri, 11 Jan 2013 10:59:24 -0000</pubDate></item><item><title>Re: The future of programming</title><link>http://radar.oreilly.com/2013/01/the-future-of-programming.html#comment-763761023</link><description>&lt;p&gt;Good question. Here's some initial thoughts. I'd like to build this up into a bookshelf that can accompany this investigation.&lt;/p&gt;&lt;p&gt;LANGUAGES&lt;/p&gt;&lt;p&gt;Clojure Programming&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/0636920013754.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/0636920013754.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;ClojureScript: Up and Running&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/0636920025139.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/0636920025139.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Programming Scala&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/9780596155964.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/9780596155964.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;DEVICES&lt;/p&gt;&lt;p&gt;Arduino Cookbook&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/0636920022244.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/0636920022244.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Programming Android&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/0636920023005.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/0636920023005.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Learning iOS Programming&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/0636920028642.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/0636920028642.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Building Wireless Sensor Networks&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/9780596807740.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/9780596807740.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;DATA&lt;/p&gt;&lt;p&gt;R Graphics Cookbook&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/0636920023135.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/0636920023135.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;R in a Nutshell&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/0636920022008.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/0636920022008.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;R Cookbook&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/9780596809164.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/9780596809164.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Python for Data Analysis&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/0636920023784.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/0636920023784.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Hadoop: The Definitive Guide&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/0636920021773.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/0636920021773.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;DEMOCRATIZED&lt;/p&gt;&lt;p&gt;We have plenty on JavaScript, but these titles help to bring the wild west under control:&lt;/p&gt;&lt;p&gt;JavaScript Enlightenment&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/0636920027713.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/0636920027713.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;JavaScript: The Good Parts&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/9780596517748.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/9780596517748.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Maintainable JavaScript&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/0636920025245.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/0636920025245.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Here's a NoStarch book on Scratch&lt;/p&gt;&lt;p&gt;Super Scratch Programming Adventure!&lt;br&gt;&lt;a href="http://shop.oreilly.com/product/9781593274092.do" rel="nofollow noopener" target="_blank" title="http://shop.oreilly.com/product/9781593274092.do"&gt;http://shop.oreilly.com/pro...&lt;/a&gt;&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Edd Dumbill</dc:creator><pubDate>Fri, 11 Jan 2013 10:24:57 -0000</pubDate></item><item><title>Re: http://eddology.com/post/9769919337</title><link>http://eddology.com/post/9769919337#comment-753974142</link><description>&lt;p&gt;I've not used it recently, I suggest you try it for yourself. I wouldn't advise a Chromebook as a development platform.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Edd Dumbill</dc:creator><pubDate>Wed, 02 Jan 2013 22:23:53 -0000</pubDate></item><item><title>Re: Follow up on big data and civil rights</title><link>http://radar.oreilly.com/2012/08/follow-up-on-big-data-and-civil-rights.html#comment-1444131136</link><description>&lt;p&gt;The paper referenced here should be of interest: &lt;a href="http://jeffjonas.typepad.com/jeff_jonas/2012/06/privacy-by-design-in-the-era-of-big-data.html" rel="nofollow noopener" target="_blank" title="http://jeffjonas.typepad.com/jeff_jonas/2012/06/privacy-by-design-in-the-era-of-big-data.html"&gt;http://jeffjonas.typepad.co...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;[[ While organizations have practical incentives to make the most of their evergrowing observation space (the data they have access to), they also have a pressing &lt;br&gt;need to embed in these systems enhanced privacy protections. We outline in this &lt;br&gt;paper just such an example — how an advanced Big Data sensemaking technology &lt;br&gt;was, from the ground up, engineered with privacy-enhancing features. Some of &lt;br&gt;these features are so critical to accuracy that the team decided they should be &lt;br&gt;mandatory — so deeply baked-in they cannot be turned off.&lt;br&gt;This paper demonstrates how privacy and responsibility can be advanced in this &lt;br&gt;new age of Big Data analytics.  ]]&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Edd Dumbill</dc:creator><pubDate>Sat, 01 Sep 2012 23:08:00 -0000</pubDate></item><item><title>Re: Follow up on big data and civil rights</title><link>http://strata.oreilly.com/2012/08/follow-up-on-big-data-and-civil-rights.html#comment-642840335</link><description>&lt;p&gt;The paper referenced here should be of interest: &lt;a href="http://jeffjonas.typepad.com/jeff_jonas/2012/06/privacy-by-design-in-the-era-of-big-data.html" rel="nofollow noopener" target="_blank" title="http://jeffjonas.typepad.com/jeff_jonas/2012/06/privacy-by-design-in-the-era-of-big-data.html"&gt;http://jeffjonas.typepad.co...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;[[ While organizations have practical incentives to make the most of their evergrowing observation space (the data they have access to), they also have a pressing &lt;br&gt;need to embed in these systems enhanced privacy protections. We outline in this &lt;br&gt;paper just such an example — how an advanced Big Data sensemaking technology &lt;br&gt;was, from the ground up, engineered with privacy-enhancing features. Some of &lt;br&gt;these features are so critical to accuracy that the team decided they should be &lt;br&gt;mandatory — so deeply baked-in they cannot be turned off.&lt;br&gt;This paper demonstrates how privacy and responsibility can be advanced in this &lt;br&gt;new age of Big Data analytics.  ]]&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Edd Dumbill</dc:creator><pubDate>Sat, 01 Sep 2012 23:08:00 -0000</pubDate></item><item><title>Re: Follow up on big data and civil rights</title><link>http://radar.oreilly.com/2012/08/follow-up-on-big-data-and-civil-rights.html#comment-637301767</link><description>&lt;p&gt;The paper referenced here should be of interest: &lt;a href="http://jeffjonas.typepad.com/jeff_jonas/2012/06/privacy-by-design-in-the-era-of-big-data.html" rel="nofollow noopener" target="_blank" title="http://jeffjonas.typepad.com/jeff_jonas/2012/06/privacy-by-design-in-the-era-of-big-data.html"&gt;http://jeffjonas.typepad.co...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;[[ While organizations have practical incentives to make the most of their evergrowing observation space (the data they have access to), they also have a pressing &lt;br&gt;need to embed in these systems enhanced privacy protections. We outline in this &lt;br&gt;paper just such an example — how an advanced Big Data sensemaking technology &lt;br&gt;was, from the ground up, engineered with privacy-enhancing features. Some of &lt;br&gt;these features are so critical to accuracy that the team decided they should be &lt;br&gt;mandatory — so deeply baked-in they cannot be turned off.&lt;br&gt;This paper demonstrates how privacy and responsibility can be advanced in this &lt;br&gt;new age of Big Data analytics.  ]]&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Edd Dumbill</dc:creator><pubDate>Sat, 01 Sep 2012 19:08:32 -0000</pubDate></item><item><title>Re: Why big data is big: the digital nervous system</title><link>http://radar.oreilly.com/2012/08/digital-nervous-system-big-data.html#comment-1444131122</link><description>&lt;p&gt;Measurement is a key part of big data, and in particular the ability to take every measurement into account, rather than needing to sample. They form the inputs to a system. But the story is also about the algorithms we use to respond, to learn, and to control systems. From my point of view, action is the outcome of the system. The aim of the big data project for business ought to be to shorten that feedback loop between input and action, and to use ever better inputs.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Edd Dumbill</dc:creator><pubDate>Thu, 30 Aug 2012 17:10:00 -0000</pubDate></item><item><title>Re: Why big data is big: the digital nervous system</title><link>http://strata.oreilly.com/2012/08/digital-nervous-system-big-data.html#comment-643793791</link><description>&lt;p&gt;Measurement is a key part of big data, and in particular the ability to take every measurement into account, rather than needing to sample. They form the inputs to a system. But the story is also about the algorithms we use to respond, to learn, and to control systems. From my point of view, action is the outcome of the system. The aim of the big data project for business ought to be to shorten that feedback loop between input and action, and to use ever better inputs.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Edd Dumbill</dc:creator><pubDate>Thu, 30 Aug 2012 17:10:00 -0000</pubDate></item><item><title>Re: Why big data is big: the digital nervous system</title><link>http://radar.oreilly.com/2012/08/digital-nervous-system-big-data.html#comment-634523187</link><description>&lt;p&gt;Measurement is a key part of big data, and in particular the ability to take every measurement into account, rather than needing to sample. They form the inputs to a system. But the story is also about the algorithms we use to respond, to learn, and to control systems. From my point of view, action is the outcome of the system. The aim of the big data project for business ought to be to shorten that feedback loop between input and action, and to use ever better inputs.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Edd Dumbill</dc:creator><pubDate>Thu, 30 Aug 2012 13:10:16 -0000</pubDate></item><item><title>Re: Why big data is big: the digital nervous system</title><link>http://radar.oreilly.com/2012/08/digital-nervous-system-big-data.html#comment-1444132262</link><description>&lt;p&gt;I like David Busch's take. Another thought I had was that it could be smart agents that autonomously regulate subsystems. For instance, the application of machine learning to predict and mitigate failure in data centers. Or look for anomalous results in computations and bring them to the attention of humans.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Edd Dumbill</dc:creator><pubDate>Thu, 30 Aug 2012 02:08:00 -0000</pubDate></item><item><title>Re: Why big data is big: the digital nervous system</title><link>http://strata.oreilly.com/2012/08/digital-nervous-system-big-data.html#comment-642840530</link><description>&lt;p&gt;I like David Busch's take. Another thought I had was that it could be smart agents that autonomously regulate subsystems. For instance, the application of machine learning to predict and mitigate failure in data centers. Or look for anomalous results in computations and bring them to the attention of humans.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Edd Dumbill</dc:creator><pubDate>Thu, 30 Aug 2012 02:08:00 -0000</pubDate></item><item><title>Re: Why big data is big: the digital nervous system</title><link>http://radar.oreilly.com/2012/08/digital-nervous-system-big-data.html#comment-1444131116</link><description>&lt;p&gt;I drew a sketch while writing this piece that didn't make it into the final article, but I did post it up on Google+ here: &lt;a href="https://plus.google.com/u/0/114723964985237592593/posts/QQi1gfouWc9" rel="nofollow noopener" target="_blank" title="https://plus.google.com/u/0/114723964985237592593/posts/QQi1gfouWc9"&gt;https://plus.google.com/u/0...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Edd Dumbill</dc:creator><pubDate>Thu, 30 Aug 2012 02:07:00 -0000</pubDate></item><item><title>Re: Why big data is big: the digital nervous system</title><link>http://strata.oreilly.com/2012/08/digital-nervous-system-big-data.html#comment-642840525</link><description>&lt;p&gt;I drew a sketch while writing this piece that didn't make it into the final article, but I did post it up on Google+ here: &lt;a href="https://plus.google.com/u/0/114723964985237592593/posts/QQi1gfouWc9" rel="nofollow noopener" target="_blank" title="https://plus.google.com/u/0/114723964985237592593/posts/QQi1gfouWc9"&gt;https://plus.google.com/u/0...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Edd Dumbill</dc:creator><pubDate>Thu, 30 Aug 2012 02:07:00 -0000</pubDate></item><item><title>Re: Why big data is big: the digital nervous system</title><link>http://radar.oreilly.com/2012/08/digital-nervous-system-big-data.html#comment-633809293</link><description>&lt;p&gt;I like David Busch's take. Another thought I had was that it could be smart agents that autonomously regulate subsystems. For instance, the application of machine learning to predict and mitigate failure in data centers. Or look for anomalous results in computations and bring them to the attention of humans.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Edd Dumbill</dc:creator><pubDate>Wed, 29 Aug 2012 22:08:42 -0000</pubDate></item><item><title>Re: Why big data is big: the digital nervous system</title><link>http://radar.oreilly.com/2012/08/digital-nervous-system-big-data.html#comment-633807935</link><description>&lt;p&gt;I drew a sketch while writing this piece that didn't make it into the final article, but I did post it up on Google+ here: &lt;a href="https://plus.google.com/u/0/114723964985237592593/posts/QQi1gfouWc9" rel="nofollow noopener" target="_blank" title="https://plus.google.com/u/0/114723964985237592593/posts/QQi1gfouWc9"&gt;https://plus.google.com/u/0...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Edd Dumbill</dc:creator><pubDate>Wed, 29 Aug 2012 22:07:00 -0000</pubDate></item></channel></rss>