<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;D0YGQn4yeSp7ImA9WxNVGE4.&quot;"><id>tag:blogger.com,1999:blog-7846496</id><updated>2009-10-29T16:52:03.091Z</updated><title>Hugo Rodger-Brown</title><subtitle type="html">Technical stuff, including none or all of the following: mobile applications, integration, enterprise architecture and life.</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://hugorodgerbrown.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://hugorodgerbrown.blogspot.com/" /><link rel="hub" href="http://pubsubhubbub.appspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>Hugo Rodger-Brown</name><uri>http://www.blogger.com/profile/13275682440882706106</uri><email>noreply@blogger.com</email></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>137</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><link rel="self" href="http://feeds.feedburner.com/HugoRodger-brown" type="application/atom+xml" /><feedburner:browserFriendly>This is an XML content feed. It is intended to be viewed in a newsreader or syndicated to another site.</feedburner:browserFriendly><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><entry gd:etag="W/&quot;D0YGQn87eip7ImA9WxNVGE4.&quot;"><id>tag:blogger.com,1999:blog-7846496.post-415714246105081509</id><published>2009-10-29T16:51:00.001Z</published><updated>2009-10-29T16:52:03.102Z</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-29T16:52:03.102Z</app:edited><title>Is Google Evil?</title><content type="html">&lt;p&gt;Hot on the heels of one giant crushing the ambitions of smaller companies (Amazon’s MySQL solution) comes another – Google’s destruction of the sat-nav market with their latest ann&lt;font size="2"&gt;&lt;strong&gt;ouncement (“&lt;/strong&gt;&lt;/font&gt;&lt;font size="2"&gt;&lt;a href="http://news.bbc.co.uk/1/hi/business/8331824.stm"&gt;Free Google sat-nav shakes market&lt;/a&gt; “).&lt;/font&gt;&lt;/p&gt;  &lt;p&gt;&lt;font size="2"&gt;Enthusiastic free-marketeers would probably say that the addition of Google into the market will spur Garmin and TomTom to greater innovation and ultimately a better deal for the consumer, but it can’t be pleasant having the rug pulled from under you like that.&lt;/font&gt;&lt;/p&gt;  &lt;p&gt;&lt;font size="2"&gt;At least in the good ol’ days they had the decency to buy your company first and then &lt;strike&gt;destroy&lt;/strike&gt; integrate it.&lt;/font&gt;&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7846496-415714246105081509?l=hugorodgerbrown.blogspot.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://hugorodgerbrown.blogspot.com/feeds/415714246105081509/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=7846496&amp;postID=415714246105081509" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/415714246105081509?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/415714246105081509?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HugoRodger-brown/~3/EJji4WfkOK8/is-google-evil.html" title="Is Google Evil?" /><author><name>Hugo Rodger-Brown</name><uri>http://www.blogger.com/profile/13275682440882706106</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="15295275910502460312" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://hugorodgerbrown.blogspot.com/2009/10/is-google-evil.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Dk4FQHs4cSp7ImA9WxNVFkg.&quot;"><id>tag:blogger.com,1999:blog-7846496.post-8242825462553426709</id><published>2009-10-27T09:01:00.001Z</published><updated>2009-10-27T14:48:31.539Z</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-27T14:48:31.539Z</app:edited><title>Amazon marches on</title><content type="html">&lt;p&gt;Why would anyone host or manage their own infrastructure these days - &lt;a title="http://aws.amazon.com/about-aws/whats-new/2009/10/27/introducing-amazon-relational-database-service/" href="http://aws.amazon.com/about-aws/whats-new/2009/10/27/introducing-amazon-relational-database-service/"&gt;http://aws.amazon.com/about-aws/whats-new/2009/10/27/introducing-amazon-relational-database-service/&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;So now Amazon offer storage (S3), compute power (EC2), relational databases (RDS), non-relational databases (SimpleDB), queueing (SQS), Hadoop (Elastic MapReduce), people (Mechanical Turk - for when computers just don’t cut it), connectivity into your own infrastructure via VPN – really, if I owned a hosting company I’d be worried, and if I ran a start-up I’d look no further.&lt;/p&gt;  &lt;p&gt;Apparently they sell a bunch of stuff as well - &lt;a title="http://phx.corporate-ir.net/phoenix.zhtml?c=176060&amp;amp;p=irol-newsArticle&amp;amp;ID=1345413&amp;amp;highlight=" href="http://phx.corporate-ir.net/phoenix.zhtml?c=176060&amp;amp;p=irol-newsArticle&amp;amp;ID=1345413&amp;amp;highlight="&gt;http://phx.corporate-ir.net/phoenix.zhtml?c=176060&amp;amp;p=irol-newsArticle&amp;amp;ID=1345413&amp;amp;highlight=&lt;/a&gt;&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7846496-8242825462553426709?l=hugorodgerbrown.blogspot.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://hugorodgerbrown.blogspot.com/feeds/8242825462553426709/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=7846496&amp;postID=8242825462553426709" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/8242825462553426709?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/8242825462553426709?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HugoRodger-brown/~3/GTBiYUv99eQ/amazon-marches-on.html" title="Amazon marches on" /><author><name>Hugo Rodger-Brown</name><uri>http://www.blogger.com/profile/13275682440882706106</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="15295275910502460312" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://hugorodgerbrown.blogspot.com/2009/10/amazon-marches-on.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEMEQHw_fCp7ImA9WxNVE0w.&quot;"><id>tag:blogger.com,1999:blog-7846496.post-7216334375032242184</id><published>2009-10-22T23:16:00.001+01:00</published><updated>2009-10-23T17:46:41.244+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-23T17:46:41.244+01:00</app:edited><title>Raindrop</title><content type="html">&lt;p&gt;Mozilla’s labs group have released some information on a messaging solution codenamed &lt;a href="http://labs.mozilla.com/raindrop/2009/10/22/introducing-raindrop/"&gt;Raindrop&lt;/a&gt;. It runs on CouchDb, and seems vaguely related to the whole &lt;a href="http://apml.areyoupayingattention.com/"&gt;APML&lt;/a&gt; (attention profiling markup language) movement – allowing users to sift through the daily dump of information by applying qualitative filters to info. (e.g. emails from my family are more important to me than Tweets from some celebrity I happen to follow – that sort of thing).&lt;/p&gt;  &lt;p&gt;I don’t really have an opinion on it as yet, but given how much I dislike &lt;a href="http://hugorodgerbrown.blogspot.com/2009/06/google-wave.html"&gt;email&lt;/a&gt;, and how disappointed I am with Wave, it’s good to see life in this area.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7846496-7216334375032242184?l=hugorodgerbrown.blogspot.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://hugorodgerbrown.blogspot.com/feeds/7216334375032242184/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=7846496&amp;postID=7216334375032242184" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/7216334375032242184?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/7216334375032242184?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HugoRodger-brown/~3/jSHU9gx-fe8/raindrop.html" title="Raindrop" /><author><name>Hugo Rodger-Brown</name><uri>http://www.blogger.com/profile/13275682440882706106</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="15295275910502460312" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://hugorodgerbrown.blogspot.com/2009/10/raindrop.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0QCQ30_cSp7ImA9WxNWGUU.&quot;"><id>tag:blogger.com,1999:blog-7846496.post-2999639483100064120</id><published>2009-10-19T20:42:00.001+01:00</published><updated>2009-10-19T20:42:42.349+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-19T20:42:42.349+01:00</app:edited><title>“Polyglot Persistence”</title><content type="html">&lt;p&gt;As I cycled home this evening I was thinking to myself that perhaps a mixed-database environment might be the best approach. I was trying to work out how I would re-engineer our platform given the opportunity, and it’s clear that whilst some areas are ripe for the NoSQL upgrade, others, notably transaction tables, audit logs etc., are much better suited to strongly-typed relational databases.&lt;/p&gt;  &lt;p&gt;As with everything I seem to do at the moment, I’m definitely a follower, as no sooner had I fired up my browser than I came across the following: &lt;a title="http://johnpwood.net/2009/09/29/using-multiple-database-models-in-a-single-application/" href="http://johnpwood.net/2009/09/29/using-multiple-database-models-in-a-single-application/"&gt;http://johnpwood.net/2009/09/29/using-multiple-database-models-in-a-single-application/&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;It’s a great article, articulate and intelligent, so go read it…&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7846496-2999639483100064120?l=hugorodgerbrown.blogspot.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://hugorodgerbrown.blogspot.com/feeds/2999639483100064120/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=7846496&amp;postID=2999639483100064120" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/2999639483100064120?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/2999639483100064120?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HugoRodger-brown/~3/0nLNgJBpdL8/polyglot-persistence.html" title="“Polyglot Persistence”" /><author><name>Hugo Rodger-Brown</name><uri>http://www.blogger.com/profile/13275682440882706106</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="15295275910502460312" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://hugorodgerbrown.blogspot.com/2009/10/polyglot-persistence.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DU4HQHc9eyp7ImA9WxNWFkk.&quot;"><id>tag:blogger.com,1999:blog-7846496.post-9032205961949699350</id><published>2009-10-15T21:22:00.001+01:00</published><updated>2009-10-16T00:05:31.963+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-16T00:05:31.963+01:00</app:edited><title>Map/Reduce &amp; the Mechanical Turk</title><content type="html">&lt;p&gt;So, I have a project that I have wanted to get off the ground for a long, long time, which involves people solving a problem that computers seems incapable of – making sense of the entertainment industry’s metadata mess. It’s a disaster, no one can match anything to anything with any degree of confidence, and even companies whose raison d'être is value-added metadata don’t seem capable of getting it right. I don’t entirely blame them, as having worked at the sharp end for a number of years I know how difficult it is. &lt;/p&gt;  &lt;p&gt;Except that it isn’t really – at least not for humans. Computers can’t do it because IDs don’t match and there’s very little fixed structure. It’s a schema-less nightmare. The only significant effort I’ve seen at creating a universal schema was hopeless. (Unfortunately I was supposed to be managing it at the time!) And yet it’s quite easy to match assets to metadata across formats (digital, physical etc.) as a human. We can match images and sounds, we can do loose / fuzzy text matches, and above all we have common sense.&lt;/p&gt;  &lt;p&gt;The problem for us people is the scale of the problem – tens of millions of assets need matching – which superficially appears best-suited for tackling programmatically. So how can we reconcile the requirement for human intervention with a problem of vast scale?&lt;/p&gt;  &lt;p&gt;This is a map/reduce problem at its heart – we need to spread the work across as many people as we can, and then aggregate the results. Is the Amazon &lt;a href="https://www.mturk.com/mturk/welcome"&gt;Mechanical Turk&lt;/a&gt; the solution?&lt;/p&gt;  &lt;p&gt;Adding in the spice of having no fixed schema (what happens to your precious database when the music industry decide to create a new product type that looks a bit like an album, but different) and it’s a problem for the NoSQL generation.&lt;/p&gt;  &lt;p&gt;So here’s my solution – stick all the available data into a non-relational document store, index with a search engine, and then present a simple user interface to allow people to validate the metadata and to perform the all-important matching process. Finally, motivate people to do the work by paying them, and use the Mechanical Turk to manage the human map/reduce function.&lt;/p&gt;  &lt;p&gt;Some kind of validation is required to maintain the data quality (only accept matches provided by multiple people?) – who knows, perhaps if enough people join the labels / studios themselves might get involved to officially endorse the work (think Twitter &lt;a href="http://twitter.com/help/verified"&gt;verified&lt;/a&gt; accounts.)&lt;/p&gt;  &lt;p&gt;All I need now is someone pay to have it done… &lt;/p&gt;  &lt;p&gt;[UPDATE]&lt;/p&gt;  &lt;p&gt;I’ve just done my first couple of HITs (Human Intelligence Task) – looking up iTunes AudioBook prices for someone – hopefully I now have $0.04 winging it’s across to me. Here’s a screencast of me in action! &lt;a title="http://screencast.com/t/GazhIehoEW" href="http://screencast.com/t/GazhIehoEW"&gt;http://screencast.com/t/GazhIehoEW&lt;/a&gt;&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7846496-9032205961949699350?l=hugorodgerbrown.blogspot.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://hugorodgerbrown.blogspot.com/feeds/9032205961949699350/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=7846496&amp;postID=9032205961949699350" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/9032205961949699350?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/9032205961949699350?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HugoRodger-brown/~3/a-FpEbii6RI/mapreduce-mechanical-turk.html" title="Map/Reduce &amp;amp; the Mechanical Turk" /><author><name>Hugo Rodger-Brown</name><uri>http://www.blogger.com/profile/13275682440882706106</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="15295275910502460312" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://hugorodgerbrown.blogspot.com/2009/10/mapreduce-mechanical-turk.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C08DSHc4cCp7ImA9WxNWEUU.&quot;"><id>tag:blogger.com,1999:blog-7846496.post-625835737389635588</id><published>2009-10-10T14:37:00.001+01:00</published><updated>2009-10-10T14:37:59.938+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-10T14:37:59.938+01:00</app:edited><title>Riak – another No-SQL option</title><content type="html">&lt;p&gt;Just reading about Riak – another non-RDBMS solution, which pushes all of the right buttons:&lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;Key-value store&lt;/li&gt;    &lt;li&gt;Document-based&lt;/li&gt;    &lt;li&gt;Extensible (in runtime) schema&lt;/li&gt;    &lt;li&gt;Flexible inter-object links (i.e. relationships)&lt;/li&gt;    &lt;li&gt;Includes Map/Reduce functions for data queries&lt;/li&gt;    &lt;li&gt;Natively accessible over HTTP&lt;/li&gt;    &lt;li&gt;Syntactically Get-Put-Delete, not CRUD&lt;/li&gt;    &lt;li&gt;Deterministic &amp;amp; repeatable ID generation&lt;/li&gt;    &lt;li&gt;Shares some concepts with Amazon’s Dynamo&lt;/li&gt; &lt;/ul&gt;  &lt;p&gt;&lt;a href="http://lh5.ggpht.com/_hdVlSl52S18/StCOMkESi2I/AAAAAAAAANw/wfVPtfKPNys/s1600-h/slide02%5B3%5D.png"&gt;&lt;img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="slide02" border="0" alt="slide02" src="http://lh5.ggpht.com/_hdVlSl52S18/StCONLCkJUI/AAAAAAAAAN0/GFy7S85LBSE/slide02_thumb%5B1%5D.png?imgmax=800" width="374" height="284" /&gt;&lt;/a&gt; &lt;/p&gt;  &lt;p&gt;All-in-all it seems on the face of it to be a data persistence solution built for the internet. Details can be found here - &lt;a title="http://riak.basho.com/nyc-nosql/" href="http://riak.basho.com/nyc-nosql/"&gt;http://riak.basho.com/nyc-nosql/&lt;/a&gt; – though be warned, this presentation includes lots of diagrams like this:&lt;/p&gt;  &lt;p&gt;&lt;a href="http://lh3.ggpht.com/_hdVlSl52S18/StCOBKseZ4I/AAAAAAAAAN4/tZfa8KkCx4I/s1600-h/slide08%5B5%5D.png"&gt;&lt;img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="slide08" border="0" alt="slide08" src="http://lh5.ggpht.com/_hdVlSl52S18/StCOBqnumGI/AAAAAAAAAN8/Xme2bB-ioas/slide08_thumb%5B3%5D.png?imgmax=800" width="386" height="299" /&gt;&lt;/a&gt;&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7846496-625835737389635588?l=hugorodgerbrown.blogspot.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://hugorodgerbrown.blogspot.com/feeds/625835737389635588/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=7846496&amp;postID=625835737389635588" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/625835737389635588?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/625835737389635588?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HugoRodger-brown/~3/TaMmszzbOp0/riak-another-no-sql-option.html" title="Riak – another No-SQL option" /><author><name>Hugo Rodger-Brown</name><uri>http://www.blogger.com/profile/13275682440882706106</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="15295275910502460312" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://hugorodgerbrown.blogspot.com/2009/10/riak-another-no-sql-option.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEcBQno8cSp7ImA9WxNXGUg.&quot;"><id>tag:blogger.com,1999:blog-7846496.post-7967921513228569407</id><published>2009-10-07T20:49:00.001+01:00</published><updated>2009-10-07T23:54:13.479+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-07T23:54:13.479+01:00</app:edited><title>Measurable quality</title><content type="html">&lt;p&gt;Whilst boring a (City-based) friend with my thoughts he pointed out that in the City the highest paid people are often not the bosses, but the star traders. So now we have another models to investigate – the bonus culture, where workers are openly rewarded according their contribution. Either way, it’s possible to earn a (very) decent living by continuing to practice the very thing that made you successful in the first place, with the business “management” being taken care of by people trained in their own way to do just that. (And having no greater status than those doing the work.)&lt;/p&gt;  &lt;p&gt;The most successful lawyers continue to practice the law, and the most successful traders continue to trade. One could argue that this is because what they do generates enough money to make this an attractive proposition, whereas software development does not. And yet… software is surely the biggest growth industry in the last 25 years – it has literally appeared out of thin air, and yet it’s created some of the largest personal fortunes every seen. An article I read a couple of years ago (wish I could find it) had some statistics about billionaires that included a summary of those who could “program a computer”; let’s just say that there were more computer programmers in the list than lawyers or accountants. So what gives?&lt;/p&gt;  &lt;p&gt;Back in the real world, most software programmers are neither billionaires, nor working for billionaires, but the question of how to make a &lt;strong&gt;&lt;em&gt;respectable&lt;/em&gt; &lt;/strong&gt;living still exists. Of course, the great advantage that City traders have is that their contribution is measured in numbers* – which can be ranked and rated. Which begs the question, how do you evaluate a developer’s contribution to a company’s success? &lt;/p&gt;  &lt;p&gt;If you started a company that became SAP (as did one of the programmers in the list), and therefore had both money to spend, and the ability to recognise technical talent, how would you measure it? Do you even bother – is one person’s line of code the same as another’s?&lt;/p&gt;  &lt;p&gt;Everyone is not equal, we all know that, but how do you prove it; if it’s not possible to prove it objectively, does that make software development art and not science?&lt;/p&gt;  &lt;p&gt;* &lt;em&gt;They also have the huge advantage of having “make more money” as the sole focus of their job.&lt;/em&gt;&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7846496-7967921513228569407?l=hugorodgerbrown.blogspot.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://hugorodgerbrown.blogspot.com/feeds/7967921513228569407/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=7846496&amp;postID=7967921513228569407" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/7967921513228569407?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/7967921513228569407?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HugoRodger-brown/~3/sGZ8wh9e7iU/measurable-quality.html" title="Measurable quality" /><author><name>Hugo Rodger-Brown</name><uri>http://www.blogger.com/profile/13275682440882706106</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="15295275910502460312" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://hugorodgerbrown.blogspot.com/2009/10/measurable-quality.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUQMQ3c4fip7ImA9WxNXGUk.&quot;"><id>tag:blogger.com,1999:blog-7846496.post-3828860679875129773</id><published>2009-09-14T19:10:00.012+01:00</published><updated>2009-10-07T20:23:02.936+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-07T20:23:02.936+01:00</app:edited><title>Rise up and take control</title><content type="html">I overheard someone on the radio this morning (I think he was Chief Economist @ Google) talking about the skills required for success in the future. He made a case for geeks taking over the world, that an ability to understand information, to analyse and manipulate it, would be more powerful in the new economy than the traditional skills of being able to control language and emotion (hence the reason so many politicians trained as lawyers.)   &lt;br /&gt;  &lt;br /&gt;It struck a chord as I have been thinking along similar lines for a while - why is that most other professional services organisations work as partnerships (lawyers, accountants, doctors, bankers even) where those who do the work own and run the company, with IT services being the exception (with, of course, a few exceptions). Why does the IT and software development community have such a low self-esteem, that they are happy to work for sales and marketing teams who have little real understanding of what they are capable?   &lt;br /&gt;  &lt;br /&gt;Of course there are companies where the techies do run the company, bringing in the business expertise from outside as and when necessary - Google being the most obvious example - but I'm thinking more of the new wave of small companies like those behind Fogbugz, Basecamp etc., where tech-savvy (and I mean really savvy, not just that they read Wired) entrepreneurs have shown that a working knowledge of the HTTP protocol doesn't preclude you from being successful in business.   &lt;br /&gt;  &lt;br /&gt;So why is it so rare - a company where the accountants are brought in for the boilerplate business management issues, with product management and company strategy managed by those who really understand the product from the bottom up.    &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7846496-3828860679875129773?l=hugorodgerbrown.blogspot.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://hugorodgerbrown.blogspot.com/feeds/3828860679875129773/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=7846496&amp;postID=3828860679875129773" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/3828860679875129773?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/3828860679875129773?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HugoRodger-brown/~3/RuHz2Nhj3vA/i-overheard-someone-on-radio-this.html" title="Rise up and take control" /><author><name>Hugo Rodger-Brown</name><uri>http://www.blogger.com/profile/13275682440882706106</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="15295275910502460312" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://hugorodgerbrown.blogspot.com/2009/09/i-overheard-someone-on-radio-this.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkcCR3k9fSp7ImA9WxNRFUo.&quot;"><id>tag:blogger.com,1999:blog-7846496.post-4756821525218074744</id><published>2009-09-10T09:03:00.004+01:00</published><updated>2009-09-10T09:07:46.765+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-10T09:07:46.765+01:00</app:edited><title>Google-ising</title><content type="html">Just to demonstrate how far we have evolved from our tree-dwelling ancestors, who only had to think about how to find food and shelter, there's a lot of online noise this morning about the fact that Google has increased the size (width) of the search box on their homepage.&lt;br /&gt;&lt;br /&gt;Since I'm no better than any other fatuous twit I may as well join in. I think that this is related to the type-ahead dropdown, which is the width of the search box. Wider dropdown means more real estate for displaying richer 'live' content. Possibly. &lt;br /&gt;&lt;br /&gt;Honestly, who gives a ...?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7846496-4756821525218074744?l=hugorodgerbrown.blogspot.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://hugorodgerbrown.blogspot.com/feeds/4756821525218074744/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=7846496&amp;postID=4756821525218074744" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/4756821525218074744?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/4756821525218074744?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HugoRodger-brown/~3/kPfNbBx-MUU/google-ising.html" title="Google-ising" /><author><name>Hugo Rodger-Brown</name><uri>http://www.blogger.com/profile/13275682440882706106</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="15295275910502460312" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://hugorodgerbrown.blogspot.com/2009/09/google-ising.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUECSHoyfCp7ImA9WxJaE08.&quot;"><id>tag:blogger.com,1999:blog-7846496.post-3694084753234120502</id><published>2009-08-03T19:21:00.001+01:00</published><updated>2009-08-03T19:21:09.494+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-08-03T19:21:09.494+01:00</app:edited><title>It’s a car, but what kind?</title><content type="html">&lt;p&gt;In my current role all analogies must be related to cars, so I thought I’d pile in with one of my own (and offload some my current frustrations whilst I’m about it.)&lt;/p&gt;  &lt;p&gt;Imagine for a moment that I work for a large car company. I have been contracted to build a small team to develop a racing car, outside of the factory production process. We can do it quicker than they could normally, use different materials, and have been allowed to operate outside of the normal operational processes.&lt;/p&gt;  &lt;p&gt;For our next project the same team have been asked to develop a rally car. It’s a bit different, and a bit more complicated, but that’s OK, we can handle it, and we’re confident of hitting the date.&lt;/p&gt;  &lt;p&gt;And then, half way through the project, they announce that the rally car we’re building is going to be used as the model on which they intend to base their new family hatchback, and that they have already decided on a date by which they intend to retire their existing top-selling model. Only it’s the same date as we are expected to deliver the rally version. And we’re not getting any more money.&lt;/p&gt;  &lt;p&gt;Several weeks later, having roped in the corporation’s finance, legal, marketing, sales &amp;amp; advertising teams, and gotten buy-in to the date from the executive board they are all asking why we’re struggling to meet the deadline.&lt;/p&gt;  &lt;p&gt;B*stds.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7846496-3694084753234120502?l=hugorodgerbrown.blogspot.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://hugorodgerbrown.blogspot.com/feeds/3694084753234120502/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=7846496&amp;postID=3694084753234120502" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/3694084753234120502?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/3694084753234120502?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HugoRodger-brown/~3/1fMdLliXcYQ/its-car-but-what-kind.html" title="It’s a car, but what kind?" /><author><name>Hugo Rodger-Brown</name><uri>http://www.blogger.com/profile/13275682440882706106</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="15295275910502460312" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://hugorodgerbrown.blogspot.com/2009/08/its-car-but-what-kind.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CU4DRHs7cCp7ImA9WxJUFk0.&quot;"><id>tag:blogger.com,1999:blog-7846496.post-6566509735955328318</id><published>2009-07-14T21:25:00.001+01:00</published><updated>2009-07-14T21:39:35.508+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-14T21:39:35.508+01:00</app:edited><title>Spot the bottleneck</title><content type="html">&lt;p&gt;This article (&lt;a title="http://www.internetretailing.net/news/waitrose-picks-precise-to-manage-website-performance-and-availability" href="http://www.internetretailing.net/news/waitrose-picks-precise-to-manage-website-performance-and-availability"&gt;http://www.internetretailing.net/news/waitrose-picks-precise-to-manage-website-performance-and-availability&lt;/a&gt;) is quite interesting for a couple of reasons:&lt;/p&gt;  &lt;ol&gt;   &lt;li&gt;Did they really need a contract with a third party to work out that some SQL statement were causing performance issues?&lt;/li&gt;    &lt;li&gt;The fact that improving SQL performance is their primary mechanism for performance gains.&lt;/li&gt;    &lt;li&gt;IBM provided the platform.&lt;/li&gt; &lt;/ol&gt;  &lt;p&gt;It would be very interesting to get a view into their existing architecture – to see how much tuning they have done so far.&lt;/p&gt;  &lt;p&gt;(PS – I know performance is difficult – you only need to look at the website I currently work with/for/on to see that I don’t have all the answers; my argument is that if they have the money to employ someone specifically for the task that suggests they have exhausted all possible internal solutions. There is surely nothing more dispiriting for a development team than to be held to account for a performance issue and then denied the resources to solve it, only to see a third party parachuted in and given all the assistance they require.)&lt;/p&gt;  &lt;p&gt;&lt;strong&gt;Update:&lt;/strong&gt;&lt;/p&gt;  &lt;p&gt;The other thing that I wanted to mention was the issue of scalability – we’re being asked to scale 1,000% in three months – should I be scared? An increase of 35% seems trivial – why can’t they scale out to cover that increase?&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7846496-6566509735955328318?l=hugorodgerbrown.blogspot.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://hugorodgerbrown.blogspot.com/feeds/6566509735955328318/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=7846496&amp;postID=6566509735955328318" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/6566509735955328318?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/6566509735955328318?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HugoRodger-brown/~3/wrc-9lrKc8w/spot-bottleneck.html" title="Spot the bottleneck" /><author><name>Hugo Rodger-Brown</name><uri>http://www.blogger.com/profile/13275682440882706106</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="15295275910502460312" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://hugorodgerbrown.blogspot.com/2009/07/spot-bottleneck.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUcMQXw4fSp7ImA9WxJVFUo.&quot;"><id>tag:blogger.com,1999:blog-7846496.post-3484412821931628861</id><published>2009-07-03T00:00:00.005+01:00</published><updated>2009-07-03T00:24:40.235+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-03T00:24:40.235+01:00</app:edited><title>Tipping Point?</title><content type="html">The mercury has now popped out of the top - when Computerworld starts picking up on these things we can now assume they have gone mainstream: &lt;a href="http://www.computerworld.com/action/article.do?command=viewArticleBasic&amp;articleId=9135086"&gt;http://www.computerworld.com/action/article.do?command=viewArticleBasic&amp;articleId=9135086&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;To paraphrase ((c) Computerworld.com)&lt;br /&gt;&lt;i&gt;The movement's chief champions [...] learned to get by at their cash-strapped startups without Oracle by building their own data storage solutions, emulating those being built by Google and Amazon.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;&lt;i&gt;Now that their open source data stores manage hundreds of terabytes or even petabytes of data for thriving Web 2.0 and cloud computing vendors, switching back is neither technically, economically or even ideologically feasible.&lt;/i&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7846496-3484412821931628861?l=hugorodgerbrown.blogspot.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://hugorodgerbrown.blogspot.com/feeds/3484412821931628861/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=7846496&amp;postID=3484412821931628861" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/3484412821931628861?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/3484412821931628861?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HugoRodger-brown/~3/FwUAx-FiJts/tipping-point.html" title="Tipping Point?" /><author><name>Hugo Rodger-Brown</name><uri>http://www.blogger.com/profile/13275682440882706106</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="15295275910502460312" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://hugorodgerbrown.blogspot.com/2009/07/tipping-point.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEMGRXw_eCp7ImA9WxJVFUo.&quot;"><id>tag:blogger.com,1999:blog-7846496.post-5229104837184407346</id><published>2009-06-30T23:41:00.004+01:00</published><updated>2009-07-03T00:13:44.240+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-03T00:13:44.240+01:00</app:edited><title>Yet more bad news for RDBMS enthusiasts</title><content type="html">The temperature's rising, and it's surely only a matter of time before normalisation is wiped from the developer's best-practice lexicon. Another well written article killing the myth here - &lt;a href="http://www.roadtofailure.com/2009/06/19/social-media-kills-the-rdbms/"&gt;http://www.roadtofailure.com/2009/06/19/social-media-kills-the-rdbms/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;As previously stated here - the sheer scale of internet applications has exposed the short-comings of traditional databases in all but the most severe environments (banks?)&lt;br /&gt;&lt;br /&gt;My favourite section of the article is the list of things that the author will not be missing with his new solution:&lt;br /&gt;&lt;br /&gt;[Quote (c) Bradford Stephens, Road To Failure blog]&lt;br /&gt;WHAT WE’RE SCRAPPING:&lt;br /&gt;&lt;br /&gt;* Transactions. Our data is written in from a Hadoop cluster in large batches. If something fails, we’ll just grab the HDFS block and try again.&lt;br /&gt;* Joins. Nothing is more evil than normalization when you need to shard data across multiple servers. If we need to search on 15 primary fields, we’re fine with copying our data set 15 times, with each field a primary key for its table.&lt;br /&gt;* Backup and Complex Replication. All of our data is imported from HDFS. If high-availability is a must, we can simply use Zookeeper to keep track of what nodes die, and then bring up a new one and feed it the data needed in ~ 60 seconds. With scales of hundreds of millions of documents, no one will miss a few hundred thousand for that brief period of time.&lt;br /&gt;* Consistency. If our users are analyzing millions of documents, they’re not going to care if there’s 15,000 unique Authors, or 15,001.&lt;br /&gt;&lt;br /&gt;Agreed - if you're a financial institution, the difference between 15,000,000,000 and 15,000,000,001 is important, but for the rest of us, it just isn't.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7846496-5229104837184407346?l=hugorodgerbrown.blogspot.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://hugorodgerbrown.blogspot.com/feeds/5229104837184407346/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=7846496&amp;postID=5229104837184407346" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/5229104837184407346?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/5229104837184407346?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HugoRodger-brown/~3/RvpstQGTBBk/yet-more-bad-news-for-rdbms-enthusiasts.html" title="Yet more bad news for RDBMS enthusiasts" /><author><name>Hugo Rodger-Brown</name><uri>http://www.blogger.com/profile/13275682440882706106</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="15295275910502460312" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><feedburner:origLink>http://hugorodgerbrown.blogspot.com/2009/06/yet-more-bad-news-for-rdbms-enthusiasts.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D04HSH84fCp7ImA9WxJWF0Q.&quot;"><id>tag:blogger.com,1999:blog-7846496.post-824755205562224482</id><published>2009-06-23T23:25:00.001+01:00</published><updated>2009-06-23T23:25:39.134+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-23T23:25:39.134+01:00</app:edited><title>Graph Databases</title><content type="html">&lt;p&gt;Something that has really resonated with me over recent weeks is the concept of the graph database. I’ve spent most of my professional career railing against RDBMS software and the frustration of database cost/scale/performance, and although graph databases (or key-value databases) won’t solve the database dilemma, it’s very encouraging to find such a vibrant community of experts trying to tackle these issues.&lt;/p&gt;  &lt;p&gt;Here is a great presentation which introduces the concepts - &lt;a title="http://markorodriguez.com/Lectures_files/risk-symposium2009.pdf" href="http://markorodriguez.com/Lectures_files/risk-symposium2009.pdf"&gt;http://markorodriguez.com/Lectures_files/risk-symposium2009.pdf&lt;/a&gt;&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7846496-824755205562224482?l=hugorodgerbrown.blogspot.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://hugorodgerbrown.blogspot.com/feeds/824755205562224482/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=7846496&amp;postID=824755205562224482" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/824755205562224482?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/824755205562224482?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HugoRodger-brown/~3/eqOZGOo7AIQ/graph-databases.html" title="Graph Databases" /><author><name>Hugo Rodger-Brown</name><uri>http://www.blogger.com/profile/13275682440882706106</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="15295275910502460312" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://hugorodgerbrown.blogspot.com/2009/06/graph-databases.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CE8ESHo8cSp7ImA9WxJVFE0.&quot;"><id>tag:blogger.com,1999:blog-7846496.post-4668281386159809018</id><published>2009-06-08T22:49:00.003+01:00</published><updated>2009-07-01T00:00:09.479+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-01T00:00:09.479+01:00</app:edited><title>RDBMS, RIP?</title><content type="html">Many years ago I wrote about the death of the ACID transaction and the rise of the compensating transaction in loosely-coupled systems (&lt;a href="http://hugorodgerbrown.blogspot.com/2005/01/acid-transaction-is-dead-long-live.html"&gt;here&lt;/a&gt;). I've never liked databases, and their sensitive, delicate, demeanour, so I'm particularly pleased to read more and more about the rise of massively scalable (and robust) "databases" based on denormalised key-value pairs - Cassandra (Facebook), BigTable (Google) &amp; Dynamo (Amazon) to name but three.&lt;br /&gt;&lt;br /&gt;I know none of these is exactly new, but I think the ideas behind them are being shared within the broader community these days, and that can only be a good thing.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7846496-4668281386159809018?l=hugorodgerbrown.blogspot.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://hugorodgerbrown.blogspot.com/feeds/4668281386159809018/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=7846496&amp;postID=4668281386159809018" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/4668281386159809018?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/4668281386159809018?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HugoRodger-brown/~3/FCAmjyi05O4/rdbms-rip.html" title="RDBMS, RIP?" /><author><name>Hugo Rodger-Brown</name><uri>http://www.blogger.com/profile/13275682440882706106</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="15295275910502460312" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://hugorodgerbrown.blogspot.com/2009/06/rdbms-rip.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0EBRH0yfCp7ImA9WxJQGUk.&quot;"><id>tag:blogger.com,1999:blog-7846496.post-5913779276581008037</id><published>2009-06-02T12:20:00.001+01:00</published><updated>2009-06-02T12:20:55.394+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-02T12:20:55.394+01:00</app:edited><title>Google Wave</title><content type="html">&lt;p&gt;We’ve been using Basecamp to collaborate on our team for the past year, and one of the things that it highlights is how incredibly poor an experience email provides. A typical email thread (say 10 replies) can encompass a number of people who are cc’d in (or dropped) from any single message, making retrospective auditing of a decision very, very complex. (In fact it’s impossible if you weren’t on the critical email in the chain.)&lt;/p&gt;  &lt;p&gt;Having got used to Basecamp, we now use its Messages function in preference to email precisely because it provides a single conversational thread where anyone can see the decisions being made in chronological order, irrespective of when they joined.&lt;/p&gt;  &lt;p&gt;One of the features of Basecamp we haven’t really got comfortable with is the Chat feature, which is functionally equivalent to the Messages, but in ‘real’ time – i.e. it’s a better IM, where Messages are a better email.&lt;/p&gt;  &lt;p&gt;Google Wave seems like a better Chat and a better Messages function, combined in one. I have no idea if it’s a ‘killer app’, and some of the initial press has suggested it’s just too ambitious, too complicated for non-technical users, but I for one applaud Google’s ambition in at least addressing the problem. Email is well past it’s sell-by-date, I think that for tech-savvy power users Wave (or an equivalent) could become a de facto communication medium.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7846496-5913779276581008037?l=hugorodgerbrown.blogspot.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://hugorodgerbrown.blogspot.com/feeds/5913779276581008037/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=7846496&amp;postID=5913779276581008037" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/5913779276581008037?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/5913779276581008037?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HugoRodger-brown/~3/kTU_rpYDSQQ/google-wave.html" title="Google Wave" /><author><name>Hugo Rodger-Brown</name><uri>http://www.blogger.com/profile/13275682440882706106</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="15295275910502460312" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://hugorodgerbrown.blogspot.com/2009/06/google-wave.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEAERnY7eCp7ImA9WxJQFEk.&quot;"><id>tag:blogger.com,1999:blog-7846496.post-6290076501257541805</id><published>2009-05-27T18:51:00.001+01:00</published><updated>2009-05-27T18:51:47.800+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-05-27T18:51:47.800+01:00</app:edited><title>Where does innovation come from?</title><content type="html">&lt;p&gt;Somewhere in my previous post I stated that in the online economy innovation comes from the bottom not the top, something that I thought at the time was fairly uncontroversial.&lt;/p&gt;  &lt;p&gt;Last week I attended and IT seminar, and two things struck me. First, I really don't work in IT - although I don't know what the alternative is; does the VP product development at Google put &amp;quot;IT Consultant&amp;quot; on their passport? Probably not, but what else is there? Anything else seems a little pretentious.&lt;/p&gt;  &lt;p&gt;Second, my comment about innovation was quite controversial. The assembled crowd (mostly CIOs / IT Directors) nodded in agreement when the panel suggested that innovation was a luxury in the current climate, and that all that really mattered today was business value as measured by cost reductions and efficiency gains.&lt;/p&gt;  &lt;p&gt;But if your business &lt;em&gt;is&lt;/em&gt; technology, how can you not innovate? I was astounded at the assumption that innovation was something could be turned off. I may be very fortunate in my current job but my role is essentially controlling the unstoppable flood of innovation from our development team, and directing it towards some appropriate business objective. Turning it off would be unthinkable, if even possible without losing the team itself.&lt;/p&gt;  &lt;p&gt;Someone at the seminar gleefully announced that the fabled Google 20% time was all but gone now, and even the mighty search giant had succumbed to market forces. Well, possibly, according to the HR team, but I'll bet a lot of money that the innovation continues unabated, 20% time or not. Google's scheme was more about encouraging what goes on anyway, with or without formal recognition.&lt;/p&gt;  &lt;p&gt;So. I hereby declare that I no longer work in IT, and furthermore that I will never work in IT again (given the choice of course). Where I work innovation is endemic, and comes from the youngest, keenest, coolest people in the room and not the oldies in the comfortable chairs. The Internet (capital 'I') has matured to the point where it now represents an industry sector in its own right, and that's where I intend to stay...&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7846496-6290076501257541805?l=hugorodgerbrown.blogspot.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://hugorodgerbrown.blogspot.com/feeds/6290076501257541805/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=7846496&amp;postID=6290076501257541805" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/6290076501257541805?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/6290076501257541805?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HugoRodger-brown/~3/sIYg-iByur4/where-does-innovation-come-from.html" title="Where does innovation come from?" /><author><name>Hugo Rodger-Brown</name><uri>http://www.blogger.com/profile/13275682440882706106</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="15295275910502460312" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://hugorodgerbrown.blogspot.com/2009/05/where-does-innovation-come-from.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUYMRHs8eCp7ImA9WxJSFUg.&quot;"><id>tag:blogger.com,1999:blog-7846496.post-3059943125086988442</id><published>2009-05-05T20:34:00.001+01:00</published><updated>2009-05-05T20:53:05.570+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-05-05T20:53:05.570+01:00</app:edited><title>Old v. New</title><content type="html">&lt;p&gt;Some quick thoughts about the comparison between old Enterprise projects and the new style of web projects:&lt;/p&gt;  &lt;table border="1" cellspacing="0" cellpadding="0"&gt;&lt;tbody&gt;     &lt;tr&gt;       &lt;th width="411"&gt;&lt;strong&gt;Category&lt;/strong&gt;&lt;/th&gt;        &lt;td width="360"&gt;&lt;strong&gt;Enterprise&lt;/strong&gt;&lt;/td&gt;        &lt;td width="427"&gt;&lt;strong&gt;Web&lt;/strong&gt;&lt;/td&gt;     &lt;/tr&gt;      &lt;tr&gt;       &lt;td width="411"&gt;Project style&lt;/td&gt;        &lt;td width="360"&gt;Waterfall - Design, Develop, Test, Deploy, RUP&lt;/td&gt;        &lt;td width="427"&gt;Agile - rapid iterations&lt;/td&gt;     &lt;/tr&gt;      &lt;tr&gt;       &lt;td width="411"&gt;Innovation&lt;/td&gt;        &lt;td width="360"&gt;Top-down (Business Requirements)&lt;/td&gt;        &lt;td width="427"&gt;Bottom-up (Google 20% time, Communities)&lt;/td&gt;     &lt;/tr&gt;      &lt;tr&gt;       &lt;td width="411"&gt;Team structure&lt;/td&gt;        &lt;td width="360"&gt;Vertical - developers code complete spikes from web to database&lt;/td&gt;        &lt;td width="427"&gt;Horizontal - front-end team is split from (and a client of) back-end team&lt;/td&gt;     &lt;/tr&gt;      &lt;tr&gt;       &lt;td width="411"&gt;Software&lt;/td&gt;        &lt;td width="360"&gt;COTS Products - expensive, well-supported commercial products (ATG, IBM, MSFT)&lt;/td&gt;        &lt;td width="427"&gt;OSS Frameworks &amp;amp; Patterns, Community-led initiatives, Bespoke 'glue', products for specific functionality&lt;/td&gt;     &lt;/tr&gt;      &lt;tr&gt;       &lt;td width="411"&gt;Development Environment&lt;/td&gt;        &lt;td width="360"&gt;Restricted software tools, homogenous environment, complex approval process&lt;/td&gt;        &lt;td width="427"&gt;Heterogeneous, open, embracing new technologies (best tool for the job)&lt;/td&gt;     &lt;/tr&gt;      &lt;tr&gt;       &lt;td width="411"&gt;Development Languages&lt;/td&gt;        &lt;td width="360"&gt;Java, .NET, C++&lt;/td&gt;        &lt;td width="427"&gt;PHP, Perl, RoR, Python, JavaScript, …&lt;/td&gt;     &lt;/tr&gt;      &lt;tr&gt;       &lt;td width="411"&gt;Buzzwords&lt;/td&gt;        &lt;td width="360"&gt;SOA, SaaS, Compliance&lt;/td&gt;        &lt;td width="427"&gt;jQuery, Memcache, LAMP, JSON, API, OAuth, Mashup&lt;/td&gt;     &lt;/tr&gt;      &lt;tr&gt;       &lt;td width="411"&gt;Web Services&lt;/td&gt;        &lt;td width="360"&gt;SOAP,WS-*&lt;/td&gt;        &lt;td width="427"&gt;REST, JSON, POX&lt;/td&gt;     &lt;/tr&gt;      &lt;tr&gt;       &lt;td width="411"&gt;Documentation&lt;/td&gt;        &lt;td width="360"&gt;Offline - licensed developer accounts; formal training courses&lt;/td&gt;        &lt;td width="427"&gt;Online - updated on the fly, available to everyone&lt;/td&gt;     &lt;/tr&gt;      &lt;tr&gt;       &lt;td width="411"&gt;Architecture&lt;/td&gt;        &lt;td width="360"&gt;N-Tier&lt;/td&gt;        &lt;td width="427"&gt;Distributed&lt;/td&gt;     &lt;/tr&gt;      &lt;tr&gt;       &lt;td width="411"&gt;Infrastructure&lt;/td&gt;        &lt;td width="360"&gt;Best-of-breed hardware, design against failure&lt;/td&gt;        &lt;td width="427"&gt;Low-end hardware, expect failure and design accordingly&lt;/td&gt;     &lt;/tr&gt;      &lt;tr&gt;       &lt;td width="411"&gt;Database&lt;/td&gt;        &lt;td width="360"&gt;Normalised, strict schema, referential integrity&lt;/td&gt;        &lt;td width="427"&gt;Denormalised, dirty data, lazy-loaded&lt;/td&gt;     &lt;/tr&gt;      &lt;tr&gt;       &lt;td width="411"&gt;Data access&lt;/td&gt;        &lt;td width="360"&gt;Direct – ODBC, JDBC, ADO.NET&lt;/td&gt;        &lt;td width="427"&gt;ORM Framework, Cache, Services&lt;/td&gt;     &lt;/tr&gt;      &lt;tr&gt;       &lt;td width="411"&gt;Requirements&lt;/td&gt;        &lt;td width="360"&gt;Secure, Scalable&lt;/td&gt;        &lt;td width="427"&gt;Flexible, Fast&lt;/td&gt;     &lt;/tr&gt;      &lt;tr&gt;       &lt;td width="411"&gt;Hero clients / employers&lt;/td&gt;        &lt;td width="360"&gt;Government,          &lt;br /&gt;Banks,           &lt;br /&gt;Corporates&lt;/td&gt;        &lt;td width="427"&gt;Google, Yahoo!, Amazon, eBay, Facebook, BBC, Twitter, Next Big Thing&lt;/td&gt;     &lt;/tr&gt;      &lt;tr&gt;       &lt;td width="411"&gt;Success Criteria&lt;/td&gt;        &lt;td width="360"&gt;How big can we grow, how secure is our data?&lt;/td&gt;        &lt;td width="427"&gt;How fast can we react to change, how far can we scale?&lt;/td&gt;     &lt;/tr&gt;   &lt;/tbody&gt;&lt;/table&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7846496-3059943125086988442?l=hugorodgerbrown.blogspot.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://hugorodgerbrown.blogspot.com/feeds/3059943125086988442/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=7846496&amp;postID=3059943125086988442" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/3059943125086988442?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/3059943125086988442?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HugoRodger-brown/~3/I8x45Jgzoe8/old-v-new.html" title="Old v. New" /><author><name>Hugo Rodger-Brown</name><uri>http://www.blogger.com/profile/13275682440882706106</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="15295275910502460312" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://hugorodgerbrown.blogspot.com/2009/05/old-v-new.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0IBQ30zeip7ImA9WxJTGEs.&quot;"><id>tag:blogger.com,1999:blog-7846496.post-6957603069616047836</id><published>2009-04-27T21:00:00.003+01:00</published><updated>2009-04-27T22:59:12.382+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-04-27T22:59:12.382+01:00</app:edited><title>Internet-scale application development</title><content type="html">I have a posting in me somewhere about the significance of internet-scale applications and their impact on software development but for some reason I can't get it all out. So I thought I'd post a placeholder anyway, just to prove that I was thinking about it.&lt;br /&gt;&lt;br /&gt;Summary is that Internet has now exceeded Enterprise as the gold standard in software - platforms like Amazon, Facebook, Google, Yahoo etc. have pioneered ways of working and architectural patterns that make traditional "n-tier" enterprise applications look like toys.&lt;br /&gt;&lt;br /&gt;Expect more soon, once I've worked my thoughts into some logical order.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7846496-6957603069616047836?l=hugorodgerbrown.blogspot.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://hugorodgerbrown.blogspot.com/feeds/6957603069616047836/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=7846496&amp;postID=6957603069616047836" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/6957603069616047836?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/6957603069616047836?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HugoRodger-brown/~3/UpH8i7hxyC4/internet-scale-application-development.html" title="Internet-scale application development" /><author><name>Hugo Rodger-Brown</name><uri>http://www.blogger.com/profile/13275682440882706106</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="15295275910502460312" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://hugorodgerbrown.blogspot.com/2009/04/internet-scale-application-development.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0ENRHg5fip7ImA9WBJWF0w.&quot;"><id>tag:blogger.com,1999:blog-7846496.post-114571569562709545</id><published>2006-04-22T15:15:00.000+01:00</published><updated>2006-04-22T15:21:35.626+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2006-04-22T15:21:35.626+01:00</app:edited><title>Which tool for the job?</title><content type="html">BizTalk, Windows Workflow Foundation, Windows Communication Foundation (Indigo), Connected Services Framework... enough already. We've got the message that software systems are now all about knitting together web services and managing workflow, but how many different frameworks and tools do we need to do all this stuff?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7846496-114571569562709545?l=hugorodgerbrown.blogspot.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://hugorodgerbrown.blogspot.com/feeds/114571569562709545/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=7846496&amp;postID=114571569562709545" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/114571569562709545?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/114571569562709545?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HugoRodger-brown/~3/uaM2lWziSq4/which-tool-for-job.html" title="Which tool for the job?" /><author><name>Hugo Rodger-Brown</name><uri>http://www.blogger.com/profile/13275682440882706106</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="15295275910502460312" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><feedburner:origLink>http://hugorodgerbrown.blogspot.com/2006/04/which-tool-for-job.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0UCSX09fip7ImA9WBJWF0w.&quot;"><id>tag:blogger.com,1999:blog-7846496.post-114571526542687035</id><published>2006-04-22T14:58:00.000+01:00</published><updated>2006-04-22T15:14:28.366+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2006-04-22T15:14:28.366+01:00</app:edited><title>Confusing Stuff Framework</title><content type="html">What is the Connected Services Framework? I've been spending some time recently with those in the know (MCS Reading principally), and the good news is that I'm beginning to understand it. The bad news is that I still couldn't explain it to anyone else with any great confidence. I'm going to try and get there over the next few weeks, so if you're interested keep in touch whilst I attempt to unravel the very subtle concept that is CSF.&lt;br /&gt;&lt;br /&gt;First off, a couple of facts about what it is not:&lt;br /&gt;1. It is not (entirely) salesware. It exists. There is downloadable software, an API, and deployable code. It is currently at v2.5, with v3.0 ("Washington") coming soon.&lt;br /&gt;2. It is not BizTalk, or a replacement for BizTalk.&lt;br /&gt;&lt;br /&gt;As to what it &lt;span style="font-weight:bold;"&gt;is&lt;/span&gt;... that's for another time.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7846496-114571526542687035?l=hugorodgerbrown.blogspot.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://hugorodgerbrown.blogspot.com/feeds/114571526542687035/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=7846496&amp;postID=114571526542687035" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/114571526542687035?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/114571526542687035?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HugoRodger-brown/~3/hTgrw-CU1TU/confusing-stuff-framework.html" title="Confusing Stuff Framework" /><author><name>Hugo Rodger-Brown</name><uri>http://www.blogger.com/profile/13275682440882706106</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="15295275910502460312" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">3</thr:total><feedburner:origLink>http://hugorodgerbrown.blogspot.com/2006/04/confusing-stuff-framework.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CU8ERX44fip7ImA9WBJXFkw.&quot;"><id>tag:blogger.com,1999:blog-7846496.post-114461377945184465</id><published>2006-04-09T20:53:00.000+01:00</published><updated>2006-04-09T21:16:44.036+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2006-04-09T21:16:44.036+01:00</app:edited><title>Welcome back</title><content type="html">First post in nine months, and very little to report. BizTalk has gone from 2004 to 2006, Windows Workflow Foundation is nearly upon us, and everyone's talking about Web 2.0, whatever that may be. &lt;br /&gt;&lt;br /&gt;All of which has passed me by, as I've spent most of the last nine months in meetings, fighting fires, and generally trying to keep on top of my undiminishing workload.&lt;br /&gt;&lt;br /&gt;I'm hoping to restart posting over the next few weeks so hopefully something more useful will be appearing here soon.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7846496-114461377945184465?l=hugorodgerbrown.blogspot.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://hugorodgerbrown.blogspot.com/feeds/114461377945184465/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=7846496&amp;postID=114461377945184465" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/114461377945184465?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/114461377945184465?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HugoRodger-brown/~3/9IohSAb5bAc/welcome-back.html" title="Welcome back" /><author><name>Hugo Rodger-Brown</name><uri>http://www.blogger.com/profile/13275682440882706106</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="15295275910502460312" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><feedburner:origLink>http://hugorodgerbrown.blogspot.com/2006/04/welcome-back.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0ACRHs7eyp7ImA9WBdbFE0.&quot;"><id>tag:blogger.com,1999:blog-7846496.post-111840970526904071</id><published>2005-06-10T13:09:00.000+01:00</published><updated>2005-06-10T14:22:45.503+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2005-06-10T14:22:45.503+01:00</app:edited><title>BizTalk... it ain't easy.</title><content type="html">I had to interview someone yesterday for a developer role, and the discussion inevitably got round to BizTalk. He was rather argumentative, which made the BizTalk discussion particularly frustrating, as he kept insisting that BizTalk was a very easy product to understand. I think precisely the opposite, since the impact of a BizTalk implementation within an organisation can be extremely complex, and the move to a message-based architecture is significant, to say the least.&lt;br /&gt;&lt;br /&gt;I think the confusion lies in Microsoft's classic 'easy-to-use' philosophy, which serves the developer community so well, but which can often lead to people overestimating their own abilities. Yes, creating an XSD in the schema designer is easy. So is creating a map, or even an orchestration. Developing and deploying artefacts into the environment is just drag'n'drop. How hard can it be?&lt;br /&gt;&lt;br /&gt;Understanding the underlying architecture and being able to use it to its best advantage and in the most appropriate manner is anything but easy, and to my mind, if you meet someone who thinks implementing BizTalk is simple, they probably don't understand what they're doing.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7846496-111840970526904071?l=hugorodgerbrown.blogspot.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://hugorodgerbrown.blogspot.com/feeds/111840970526904071/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=7846496&amp;postID=111840970526904071" title="6 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/111840970526904071?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/111840970526904071?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HugoRodger-brown/~3/dD8qMamaEck/biztalk-it-aint-easy.html" title="BizTalk... it ain't easy." /><author><name>Hugo Rodger-Brown</name><uri>http://www.blogger.com/profile/13275682440882706106</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="15295275910502460312" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">6</thr:total><feedburner:origLink>http://hugorodgerbrown.blogspot.com/2005/06/biztalk-it-aint-easy.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEMHR34yeyp7ImA9WBdUF0U.&quot;"><id>tag:blogger.com,1999:blog-7846496.post-111778643608864386</id><published>2005-06-03T09:04:00.000+01:00</published><updated>2005-06-03T09:13:56.093+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2005-06-03T09:13:56.093+01:00</app:edited><title>Connected Systems Competition</title><content type="html">I would be tempted to enter &lt;a href="http://www.csdevcompetition.com/default.aspx"&gt;this&lt;/a&gt; contest, but my day-job seems to be taking up too much time :-S. I think that a SOAP receive adapter, for polling web services, would be a good bet for &lt;a href="http://www.csdevcompetition.com/rules.aspx#Categories"&gt;category&lt;/a&gt; #14?&lt;br /&gt;&lt;br /&gt;On the subject of the day-job, I obviously haven't posted for a while, and that's largely 'cos I'm so busy. I've spent the last month working at the commercial end of the business, spending 8 hours a day in meetings, and very little time at the sharp-end. I will, however, endeavour to resume posting when (/if) things calm down, as we're working with some pretty cool stuff, and the &lt;a href="http://www.microsoft.com/serviceproviders/solutions/csf.mspx"&gt;CSF&lt;/a&gt; is part of our roadmap.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7846496-111778643608864386?l=hugorodgerbrown.blogspot.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://hugorodgerbrown.blogspot.com/feeds/111778643608864386/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=7846496&amp;postID=111778643608864386" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/111778643608864386?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/111778643608864386?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HugoRodger-brown/~3/3SylfCMcSSU/connected-systems-competition.html" title="Connected Systems Competition" /><author><name>Hugo Rodger-Brown</name><uri>http://www.blogger.com/profile/13275682440882706106</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="15295275910502460312" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><feedburner:origLink>http://hugorodgerbrown.blogspot.com/2005/06/connected-systems-competition.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUEAQnc7eyp7ImA9WBdWE0Q.&quot;"><id>tag:blogger.com,1999:blog-7846496.post-111539364375993554</id><published>2005-05-06T16:28:00.000+01:00</published><updated>2005-05-06T16:34:03.903+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2005-05-06T16:34:03.903+01:00</app:edited><title>Visual disk space manager</title><content type="html">Just installed &lt;a href="http://www.diskview.com/diskview.htm"&gt;DiskView&lt;/a&gt; from Vyooh - which looks like a great visual explorer tool that shows where all that HDD space has gone. It plugs-in to explorer itself, which makes it much more accessible that separate space manager apps.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7846496-111539364375993554?l=hugorodgerbrown.blogspot.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://hugorodgerbrown.blogspot.com/feeds/111539364375993554/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=7846496&amp;postID=111539364375993554" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/111539364375993554?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7846496/posts/default/111539364375993554?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HugoRodger-brown/~3/oUqRNoRoUXg/visual-disk-space-manager.html" title="Visual disk space manager" /><author><name>Hugo Rodger-Brown</name><uri>http://www.blogger.com/profile/13275682440882706106</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="15295275910502460312" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://hugorodgerbrown.blogspot.com/2005/05/visual-disk-space-manager.html</feedburner:origLink></entry></feed>
