<?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:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;DEEERX07fyp7ImA9WhRUFko.&quot;"><id>tag:blogger.com,1999:blog-11168006</id><updated>2012-01-27T15:03:24.307Z</updated><category term="quota" /><category term="tools" /><category term="package" /><category term="heatmap" /><category term="phones" /><category term="strategy" /><category term="UI" /><category term="interfaces" /><category term="Apple" /><category term="DR" /><category term="mobility" /><category term="safety" /><category term="geo-ripping" /><category term="Sky+" /><category term="practice" /><category term="SAP" /><category term="airports" /><category term="divide" /><category term="reliability" /><category term="resource" /><category term="video" /><category term="Flex" /><category term="stateless" /><category term="iOS" /><category term="Globalisation" /><category term="Legacy" /><category term="anti-patterns" /><category term="rant" /><category term="next" /><category term="IBM" /><category term="Google+" /><category term="semantic" /><category term="MSN" /><category term="clint eastwood" /><category term="engineering" /><category term="Javascript" /><category term="JBI" /><category term="information" /><category term="holiday" /><category term="humour" /><category term="definition" /><category term="policy" /><category term="delivery" /><category term="Rules" /><category term="legal" /><category term="patents" /><category term="iPhone" /><category term="scope creep" /><category term="Mashups" /><category term="vendors" /><category term="business SOA" /><category term="marketing" /><category term="design" /><category term="governance" /><category term="Prior Art" /><category term="specifications" /><category term="project" /><category term="conferences" /><category term="formalism" /><category term="analysts" /><category term="Vista" /><category term="technology" /><category term="yahoo pipes" /><category term="Microsoft" /><category term="PaaS" /><category term="FUD" /><category term="ESB" /><category term="Tivo" /><category term="BTL" /><category term="advertising" /><category term="Oracle" /><category term="SOA" /><category term="us border" /><category term="canonical form" /><category term="Scala" /><category term="Wikipedia" /><category term="VM" /><category term="dumb" /><category term="systems" /><category term="learning" /><category term="Facebook" /><category term="WS-*" /><category term="adoption" /><category term="recovery" /><category term="scale" /><category term="BSA" /><category term="BSB" /><category term="SCA" /><category term="Blueprints" /><category term="principles" /><category term="TCO" /><category term="issue" /><category term="Google" /><category term="Open Source" /><category term="VME" /><category term="pop" /><category term="private" /><category term="App Engine" /><category term="infrastructure" /><category term="Ruby" /><category term="standards" /><category term="caching" /><category term="debt" /><category term="virtualisation" /><category term="mobile" /><category term="DOA" /><category term="finance" /><category term="documentation" /><category term="comedy" /><category term="zombies" /><category term="predictions" /><category term="methodology" /><category term="time machine" /><category term="Enterprise Architecture" /><category term="big data" /><category term="product" /><category term="BEA" /><category term="Orange" /><category term="apple TV" /><category term="iPod" /><category term="rightscale" /><category term="Paris" /><category term="Java SE 7" /><category term="EDA" /><category term=".net" /><category term="performance" /><category term="consultancy" /><category term="eclipse" /><category term="tin" /><category term="future" /><category term="Adobe" /><category term="open cloud" /><category term="business" /><category term="security" /><category term="maths" /><category term="UML" /><category term="XML" /><category term="cloud" /><category term="BPEL" /><category term="decisions" /><category term="people" /><category term="integration" /><category term="AM" /><category term="software" /><category term="gerald" /><category term="coding" /><category term="requirements" /><category term="redundancy" /><category term="scam" /><category term="BeJUG" /><category term="Google Maps" /><category term="pricing" /><category term="value" /><category term="contract" /><category term="public" /><category term="social business" /><category term="NFC" /><category term="IT" /><category term="snakeoil" /><category term="CBP" /><category term="change" /><category term="socbiz" /><category term="RPC" /><category term="complexity" /><category term="JavaOne" /><category term="WS" /><category term="geo-social" /><category term="SaaS" /><category term="metrics" /><category term="python" /><category term="simple IT" /><category term="requirements landfill" /><category term="POA" /><category term="modelling" /><category term="EAI" /><category term="hype" /><category term="HTML5" /><category term="database" /><category term="language design" /><category term="XaaS" /><category term="platforms" /><category term="recession" /><category term="vision" /><category term="budget" /><category term="vacation" /><category term="REST" /><category term="GDA" /><category term="MDM" /><category term="HCI" /><category term="culture" /><category term="streaming" /><category term="ERP" /><category term="games" /><category term="OASIS" /><category term="BPM" /><category term="Java" /><category term="Web 2.0" /><category term="Air" /><category term="SLA" /><category term="TSOA" /><category term="SOAP" /><category term="dead" /><category term="JCP" /><category term="economics" /><category term="Sun" /><category term="jobs" /><category term="QoS" /><category term="iPhone 4" /><category term="selling" /><category term="religion" /><category term="joke" /><category term="fail" /><category term="iPad" /><category term="failure" /><category term="JDO" /><category term="data" /><category term="estimation" /><category term="kick-off" /><title>Business SOA</title><subtitle type="html">A Simple blog about Business SOA and generally about how to drive IT from a business perspective. All opinions are mine and should be taken with a pinch of salt etc etc</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://service-architecture.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://service-architecture.blogspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>Steve Jones</name><uri>https://profiles.google.com/101953459252929322687</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-vprBOVtrPKI/AAAAAAAAAAI/AAAAAAAAFIE/BFr93W72njw/s512-c/photo.jpg" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>490</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><feedburner:info uri="servicearchitecture" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://service-architecture.blogspot.com" /><entry gd:etag="W/&quot;DEEERX05fCp7ImA9WhRUFko.&quot;"><id>tag:blogger.com,1999:blog-11168006.post-846054962198146585</id><published>2012-01-27T15:03:00.002Z</published><updated>2012-01-27T15:03:24.324Z</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-27T15:03:24.324Z</app:edited><title>Controlling what kids access - VPN to the Home - the next big thing in Mobile security</title><summary type="html">
I've got kids, currently they are under the age where they get Smartphones and unfettered internet access but such a day is coming.  Now at home I can set it up so on the WiFi there is a proxy and all content has to be routed via that proxy or it doesn't go out and I can lock down the proxy so they can't go where I don't want.


However on a Smartphone they get good internet access without me &lt;img src="http://feeds.feedburner.com/~r/ServiceArchitecture/~4/ByL17_05590" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://service-architecture.blogspot.com/feeds/846054962198146585/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=11168006&amp;postID=846054962198146585" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/846054962198146585?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/846054962198146585?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ServiceArchitecture/~3/ByL17_05590/controlling-what-kids-access-vpn-to.html" title="Controlling what kids access - VPN to the Home - the next big thing in Mobile security" /><author><name>Steve Jones</name><uri>https://profiles.google.com/101953459252929322687</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-vprBOVtrPKI/AAAAAAAAAAI/AAAAAAAAFIE/BFr93W72njw/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://service-architecture.blogspot.com/2012/01/controlling-what-kids-access-vpn-to.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0UFQHs_cCp7ImA9WhRVGEQ.&quot;"><id>tag:blogger.com,1999:blog-11168006.post-7613581220461488577</id><published>2012-01-18T14:00:00.000Z</published><updated>2012-01-18T14:00:11.548Z</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-18T14:00:11.548Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="iPhone" /><category scheme="http://www.blogger.com/atom/ns#" term="learning" /><category scheme="http://www.blogger.com/atom/ns#" term="iOS" /><category scheme="http://www.blogger.com/atom/ns#" term="language design" /><category scheme="http://www.blogger.com/atom/ns#" term="coding" /><title>IT going backwards - Objective C is 90s retro</title><summary type="html">
I've ranted quite regularly on how Enterprise IT just hasn't really developed in the last 5 years and my personal task for 2012... learning Objective C and programming for iOS has taken my disbelief to another level.  Back in 2008 I learnt Python and for me it sucked.  Its 'advantage' over scripting languages of the 80s and 90s was minimal and it had the most hated (for me) of things... indent &lt;img src="http://feeds.feedburner.com/~r/ServiceArchitecture/~4/80ONpii3eQA" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://service-architecture.blogspot.com/feeds/7613581220461488577/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=11168006&amp;postID=7613581220461488577" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/7613581220461488577?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/7613581220461488577?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ServiceArchitecture/~3/80ONpii3eQA/it-going-backwards-objective-c-is-90s.html" title="IT going backwards - Objective C is 90s retro" /><author><name>Steve Jones</name><uri>https://profiles.google.com/101953459252929322687</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-vprBOVtrPKI/AAAAAAAAAAI/AAAAAAAAFIE/BFr93W72njw/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://service-architecture.blogspot.com/2012/01/it-going-backwards-objective-c-is-90s.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUUEQHk7cCp7ImA9WhRVF04.&quot;"><id>tag:blogger.com,1999:blog-11168006.post-8177377275214400188</id><published>2012-01-16T17:00:00.000Z</published><updated>2012-01-16T17:00:01.708Z</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-16T17:00:01.708Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="rant" /><category scheme="http://www.blogger.com/atom/ns#" term="CBP" /><category scheme="http://www.blogger.com/atom/ns#" term="mobile" /><category scheme="http://www.blogger.com/atom/ns#" term="us border" /><title>iPads on planes during takeoff?  Hell I'd like to use it in the airport!</title><summary type="html">
People have been asking for iPads, and Kindles, to be used during takeoff and landing (like Pilots can) but for me that isn't a massive deal, yes I'd like to read my online Economist from the iPad when I'm travelling and sure it can be a bit of a pain to have to use old style paper... but I've got a bigger gripe.

The CBP (Customers and Border Protection) and their mental policies at immigration&lt;img src="http://feeds.feedburner.com/~r/ServiceArchitecture/~4/jQMEf3xrjow" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://service-architecture.blogspot.com/feeds/8177377275214400188/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=11168006&amp;postID=8177377275214400188" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/8177377275214400188?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/8177377275214400188?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ServiceArchitecture/~3/jQMEf3xrjow/ipads-on-planes-during-takeoff-hell-id.html" title="iPads on planes during takeoff?  Hell I'd like to use it in the airport!" /><author><name>Steve Jones</name><uri>https://profiles.google.com/101953459252929322687</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-vprBOVtrPKI/AAAAAAAAAAI/AAAAAAAAFIE/BFr93W72njw/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://service-architecture.blogspot.com/2012/01/ipads-on-planes-during-takeoff-hell-id.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Dk8CR3c9fip7ImA9WhRXFUs.&quot;"><id>tag:blogger.com,1999:blog-11168006.post-5369749063161297892</id><published>2011-12-22T14:41:00.000Z</published><updated>2011-12-22T14:41:06.966Z</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-22T14:41:06.966Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Facebook" /><category scheme="http://www.blogger.com/atom/ns#" term="REST" /><category scheme="http://www.blogger.com/atom/ns#" term="information" /><title>RESTs marketing problem and how Facebook solved it</title><summary type="html">
Earlier in the year I commented on REST being still born in the enterprise and now Facebook have now deprecated the REST API in favour of a Graph API now I could choose to say this is 'proof' that REST doesn't work for the Web either.  That would be silly for a couple of reasons



The new API appears to be RESTful anyway
REST clearly can work on the web


No, what this really shows is that you &lt;img src="http://feeds.feedburner.com/~r/ServiceArchitecture/~4/6XU-w0lPntE" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://service-architecture.blogspot.com/feeds/5369749063161297892/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=11168006&amp;postID=5369749063161297892" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/5369749063161297892?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/5369749063161297892?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ServiceArchitecture/~3/6XU-w0lPntE/rests-marketing-problem-and-how.html" title="RESTs marketing problem and how Facebook solved it" /><author><name>Steve Jones</name><uri>https://profiles.google.com/101953459252929322687</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-vprBOVtrPKI/AAAAAAAAAAI/AAAAAAAAFIE/BFr93W72njw/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://service-architecture.blogspot.com/2011/12/rests-marketing-problem-and-how.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEUMRnw_eCp7ImA9WhRXEUg.&quot;"><id>tag:blogger.com,1999:blog-11168006.post-3943372818727602327</id><published>2011-12-17T21:04:00.001Z</published><updated>2011-12-17T21:11:27.240Z</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-17T21:11:27.240Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="humour" /><category scheme="http://www.blogger.com/atom/ns#" term="scam" /><title>Wasting the time of a PPI scammer</title><summary type="html">
There are a number of scams going around today which really demonstrate how mainstream outsourcing has become.  There is the current one around the 'unique' number that proves the scammer is from Microsoft and today I got a new one.  This time it was someone claiming to be from 'iClaims' (another Steve Jobs legacy, 'i' is the new 'e') telling me that I was entitled to a PPI or bank charges &lt;img src="http://feeds.feedburner.com/~r/ServiceArchitecture/~4/E0ilSaRkfBs" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://service-architecture.blogspot.com/feeds/3943372818727602327/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=11168006&amp;postID=3943372818727602327" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/3943372818727602327?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/3943372818727602327?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ServiceArchitecture/~3/E0ilSaRkfBs/wasting-time-of-ppi-scammer.html" title="Wasting the time of a PPI scammer" /><author><name>Steve Jones</name><uri>https://profiles.google.com/101953459252929322687</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-vprBOVtrPKI/AAAAAAAAAAI/AAAAAAAAFIE/BFr93W72njw/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://service-architecture.blogspot.com/2011/12/wasting-time-of-ppi-scammer.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D04GSHw5fip7ImA9WhRXEUg.&quot;"><id>tag:blogger.com,1999:blog-11168006.post-6951530207178065347</id><published>2011-12-13T16:22:00.002Z</published><updated>2011-12-17T21:05:29.226Z</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-17T21:05:29.226Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="snakeoil" /><category scheme="http://www.blogger.com/atom/ns#" term="cloud" /><title>Cloud in a box: Life on Mars in Hardware or an empty glass of water?</title><summary type="html">
There are some phrases that are just plain funny and for me 'Cloud in a Box' which is available from multiple vendors is probably just about the best.  The idea here is that you can buy a box - a box that looks and acts like a 1970s Mainframe: virtualisation, big power consumption, vendor lock in - and joy of joys you've now got a 'cloud'.
 So:


Do you pay for this cloud on demand? 

Nope

Do &lt;img src="http://feeds.feedburner.com/~r/ServiceArchitecture/~4/9aQMVdC3rhQ" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://service-architecture.blogspot.com/feeds/6951530207178065347/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=11168006&amp;postID=6951530207178065347" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/6951530207178065347?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/6951530207178065347?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ServiceArchitecture/~3/9aQMVdC3rhQ/cloud-in-box-life-on-mars-in-hardware.html" title="Cloud in a box: Life on Mars in Hardware or an empty glass of water?" /><author><name>Steve Jones</name><uri>https://profiles.google.com/101953459252929322687</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-vprBOVtrPKI/AAAAAAAAAAI/AAAAAAAAFIE/BFr93W72njw/s512-c/photo.jpg" /></author><thr:total>2</thr:total><feedburner:origLink>http://service-architecture.blogspot.com/2011/12/cloud-in-box-life-on-mars-in-hardware.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEcFQ3g8eyp7ImA9WhRQEU8.&quot;"><id>tag:blogger.com,1999:blog-11168006.post-2698105312302852862</id><published>2011-12-05T21:42:00.001Z</published><updated>2011-12-05T21:53:32.673Z</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-05T21:53:32.673Z</app:edited><title>Why thinking counts and development doesn't</title><summary type="html">
I'm having one of those interviewing streaks at the moment.  The sort of interviews where after 2 minutes the only question is how to politely wrap the interview up but where secretly you want to scream 'DO YOU SERIOUSLY THINK YOU ARE ANY GOOD?'.  You know the sort, where you ask a simple question like

'Explain the difference between EJB and SCA' and you get an explanation of the different &lt;img src="http://feeds.feedburner.com/~r/ServiceArchitecture/~4/smRnCIuXOhg" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://service-architecture.blogspot.com/feeds/2698105312302852862/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=11168006&amp;postID=2698105312302852862" title="4 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/2698105312302852862?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/2698105312302852862?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ServiceArchitecture/~3/smRnCIuXOhg/why-thinking-counts-and-development.html" title="Why thinking counts and development doesn't" /><author><name>Steve Jones</name><uri>https://profiles.google.com/101953459252929322687</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-vprBOVtrPKI/AAAAAAAAAAI/AAAAAAAAFIE/BFr93W72njw/s512-c/photo.jpg" /></author><thr:total>4</thr:total><feedburner:origLink>http://service-architecture.blogspot.com/2011/12/why-thinking-counts-and-development.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUUGSXwzfip7ImA9WhRRF0g.&quot;"><id>tag:blogger.com,1999:blog-11168006.post-8916927154133545210</id><published>2011-12-01T15:14:00.001Z</published><updated>2011-12-01T15:27:08.286Z</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-01T15:27:08.286Z</app:edited><title>Five reasons why Facebook is dying and Email is king</title><summary type="html">Mark Zuckerberg tried to pull a Steve Jobs the other day by announcing that a new product of his was going to kill off a competitor.  Now there have been articles on the fact that email use is still rising and I'll give five reasons why Facebook is dying and five reasons why email will remain king

Why Facebook is dying
Facebook is at near saturation point, this makes it valuable through the &lt;img src="http://feeds.feedburner.com/~r/ServiceArchitecture/~4/qfZKiQ2hllk" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://service-architecture.blogspot.com/feeds/8916927154133545210/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=11168006&amp;postID=8916927154133545210" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/8916927154133545210?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/8916927154133545210?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ServiceArchitecture/~3/qfZKiQ2hllk/five-reasons-why-facebook-is-dying-and.html" title="Five reasons why Facebook is dying and Email is king" /><author><name>Steve Jones</name><uri>https://profiles.google.com/101953459252929322687</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-vprBOVtrPKI/AAAAAAAAAAI/AAAAAAAAFIE/BFr93W72njw/s512-c/photo.jpg" /></author><thr:total>2</thr:total><feedburner:origLink>http://service-architecture.blogspot.com/2011/12/five-reasons-why-facebook-is-dying-and.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEMHQXYycCp7ImA9WhRSEks.&quot;"><id>tag:blogger.com,1999:blog-11168006.post-7338324230645494268</id><published>2011-11-14T09:33:00.001Z</published><updated>2011-11-14T10:27:10.898Z</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-11-14T10:27:10.898Z</app:edited><title>SOA Anti-Pattern: Sharing data like Candy</title><summary type="html">
Back in 2006 I wrote a bunch of SOA Anti-patterns, with some additional help,  and these are pretty much as valid then as now.  I'd like to add a new one though that I've seen over and over again its related to the canonical model problem and its pretty easy to solve.

Name: Sharing Data like candy
Description
This anti-pattern comes from a desire to 'share' all the information between areas but&lt;img src="http://feeds.feedburner.com/~r/ServiceArchitecture/~4/bhcg41U08iA" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://service-architecture.blogspot.com/feeds/7338324230645494268/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=11168006&amp;postID=7338324230645494268" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/7338324230645494268?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/7338324230645494268?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ServiceArchitecture/~3/bhcg41U08iA/soa-anti-pattern-sharing-data-like.html" title="SOA Anti-Pattern: Sharing data like Candy" /><author><name>Steve Jones</name><uri>https://profiles.google.com/101953459252929322687</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-vprBOVtrPKI/AAAAAAAAAAI/AAAAAAAAFIE/BFr93W72njw/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://service-architecture.blogspot.com/2011/11/soa-anti-pattern-sharing-data-like.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUYBQH09eyp7ImA9WhRSEks.&quot;"><id>tag:blogger.com,1999:blog-11168006.post-9121916485597868654</id><published>2011-11-09T19:11:00.001Z</published><updated>2011-11-14T09:32:31.363Z</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-11-14T09:32:31.363Z</app:edited><title>How Microsoft missed the cloud....</title><summary type="html">
Back in 2007 I posted about a research leader (who retired this year) at Microsoft who made some predictions on the future which could be summarised as the following

Single processing is an old school idea - this was pointing out the obvious in 2007 and indeed obvious in 1990 and before if you know anything about decent scale systems.  This was a prediction of the future being the same as the &lt;img src="http://feeds.feedburner.com/~r/ServiceArchitecture/~4/f6HccvLihN0" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://service-architecture.blogspot.com/feeds/9121916485597868654/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=11168006&amp;postID=9121916485597868654" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/9121916485597868654?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/9121916485597868654?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ServiceArchitecture/~3/f6HccvLihN0/how-microsoft-missed-cloud.html" title="How Microsoft missed the cloud...." /><author><name>Steve Jones</name><uri>https://profiles.google.com/101953459252929322687</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-vprBOVtrPKI/AAAAAAAAAAI/AAAAAAAAFIE/BFr93W72njw/s512-c/photo.jpg" /></author><thr:total>1</thr:total><feedburner:origLink>http://service-architecture.blogspot.com/2011/11/how-microsoft-missed-cloud.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D08BQ3o7fip7ImA9WhRTGEs.&quot;"><id>tag:blogger.com,1999:blog-11168006.post-3717104830364818116</id><published>2011-11-09T19:10:00.003Z</published><updated>2011-11-09T19:10:52.406Z</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-11-09T19:10:52.406Z</app:edited><title>When Big Data is a Big Con</title><summary type="html">
I'm seeing a lot of 'Big Data' washing going on in the market.  Some companies are looking at this volume explosion as part of a continuation of history, new technologies, new approaches but evolution not revolution.  Yes Map Reduce is cool but its technically much harder than SQL and database design this means that it is far from a business panacea.  Yes the link between structured and &lt;img src="http://feeds.feedburner.com/~r/ServiceArchitecture/~4/IlhtWw6IPEc" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://service-architecture.blogspot.com/feeds/3717104830364818116/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=11168006&amp;postID=3717104830364818116" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/3717104830364818116?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/3717104830364818116?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ServiceArchitecture/~3/IlhtWw6IPEc/when-big-data-is-big-con.html" title="When Big Data is a Big Con" /><author><name>Steve Jones</name><uri>https://profiles.google.com/101953459252929322687</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-vprBOVtrPKI/AAAAAAAAAAI/AAAAAAAAFIE/BFr93W72njw/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://service-architecture.blogspot.com/2011/11/when-big-data-is-big-con.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DU4BSXc8fyp7ImA9WhRTF04.&quot;"><id>tag:blogger.com,1999:blog-11168006.post-3846729090153446395</id><published>2011-11-08T07:39:00.000Z</published><updated>2011-11-08T07:39:18.977Z</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-11-08T07:39:18.977Z</app:edited><title>Soylent Green is Facebook - People as a Product</title><summary type="html">

As everyone knows 'Soylent Green is People' and indeed its taken nearly 30 years for people to really make a product whose only ability is to sell the value of people, people cut into cross sections, relationships and information.  This is what all social media companies are really selling, they aren't selling TO people they are selling people TO companies.  This is the only way they make money&lt;img src="http://feeds.feedburner.com/~r/ServiceArchitecture/~4/-KFwUHH-0Q4" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://service-architecture.blogspot.com/feeds/3846729090153446395/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=11168006&amp;postID=3846729090153446395" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/3846729090153446395?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/3846729090153446395?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ServiceArchitecture/~3/-KFwUHH-0Q4/soylent-green-is-facebook-people-as.html" title="Soylent Green is Facebook - People as a Product" /><author><name>Steve Jones</name><uri>https://profiles.google.com/101953459252929322687</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-vprBOVtrPKI/AAAAAAAAAAI/AAAAAAAAFIE/BFr93W72njw/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://service-architecture.blogspot.com/2011/11/soylent-green-is-facebook-people-as.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEEGQn87fyp7ImA9WhdaFEo.&quot;"><id>tag:blogger.com,1999:blog-11168006.post-1751375136345659172</id><published>2011-10-24T18:17:00.000+01:00</published><updated>2011-10-24T18:17:03.107+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-10-24T18:17:03.107+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="tin" /><category scheme="http://www.blogger.com/atom/ns#" term="people" /><category scheme="http://www.blogger.com/atom/ns#" term="software" /><category scheme="http://www.blogger.com/atom/ns#" term="infrastructure" /><title>The 'Natural Platform' - Why people matter more than performance in picking hardware</title><summary type="html">One of the things that I get asked is 'what hardware should we run this on?'.  I've said for years that I don't care about the tin and the tin is irrelevant from a differentiation perspective.  Now before people leap up and say 'but X is 2x faster than Y' let me make a couple of points

Software tuning and performance will have miles more than a 2x impact
The software licenses will probably cost &lt;img src="http://feeds.feedburner.com/~r/ServiceArchitecture/~4/3JNts28ris8" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://service-architecture.blogspot.com/feeds/1751375136345659172/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=11168006&amp;postID=1751375136345659172" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/1751375136345659172?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/1751375136345659172?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ServiceArchitecture/~3/3JNts28ris8/natural-platform-why-people-matter-more.html" title="The 'Natural Platform' - Why people matter more than performance in picking hardware" /><author><name>Steve Jones</name><uri>https://profiles.google.com/101953459252929322687</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-vprBOVtrPKI/AAAAAAAAAAI/AAAAAAAAFIE/BFr93W72njw/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://service-architecture.blogspot.com/2011/10/natural-platform-why-people-matter-more.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkcASXo-cCp7ImA9WhdbGEk.&quot;"><id>tag:blogger.com,1999:blog-11168006.post-8990604359267803285</id><published>2011-10-17T10:34:00.000+01:00</published><updated>2011-10-17T10:34:08.458+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-10-17T10:34:08.458+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="consultancy" /><title>Improvised Explosive Consultants - neutralising a bad consultant</title><summary type="html">One of the challenges I often have is where a company employs a consultant to give 'independent' advice and the individual employed is a total snake-oil salesperson.  They've read a couple of books and websites and see their only job to lob in a 'bomb' in a meeting and sit back.  I categorise a bomb as a piece of input that is
Completely and utterly wrong
Contains a grain of truth that has been &lt;img src="http://feeds.feedburner.com/~r/ServiceArchitecture/~4/9TwSCrnR55Q" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://service-architecture.blogspot.com/feeds/8990604359267803285/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=11168006&amp;postID=8990604359267803285" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/8990604359267803285?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/8990604359267803285?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ServiceArchitecture/~3/9TwSCrnR55Q/improvised-explosive-consultants.html" title="Improvised Explosive Consultants - neutralising a bad consultant" /><author><name>Steve Jones</name><uri>https://profiles.google.com/101953459252929322687</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-vprBOVtrPKI/AAAAAAAAAAI/AAAAAAAAFIE/BFr93W72njw/s512-c/photo.jpg" /></author><thr:total>1</thr:total><feedburner:origLink>http://service-architecture.blogspot.com/2011/10/improvised-explosive-consultants.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0MER3ozcCp7ImA9WhdVFE8.&quot;"><id>tag:blogger.com,1999:blog-11168006.post-5207380755596236503</id><published>2011-09-19T11:50:00.000+01:00</published><updated>2011-09-19T11:50:06.488+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-09-19T11:50:06.488+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="iPhone" /><category scheme="http://www.blogger.com/atom/ns#" term="Apple" /><category scheme="http://www.blogger.com/atom/ns#" term="NFC" /><title>NFC - What Apple does next? Buy Amex?</title><summary type="html">Chatting around on the iPhone 5 I have to say its all rather dull, yes they'll fix the antenna, yes the camera might get better and the processor faster.   But really is that a big deal?  So what could Apple announce either now or next year that would really blow people away.

I travel a lot, and one thing I see around Europe is the rise of NFC, so the use of 'smart'cards on the Underground, &lt;img src="http://feeds.feedburner.com/~r/ServiceArchitecture/~4/judOPMAeKeI" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://service-architecture.blogspot.com/feeds/5207380755596236503/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=11168006&amp;postID=5207380755596236503" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/5207380755596236503?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/5207380755596236503?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ServiceArchitecture/~3/judOPMAeKeI/nfc-what-apple-does-next-buy-amex.html" title="NFC - What Apple does next? Buy Amex?" /><author><name>Steve Jones</name><uri>https://profiles.google.com/101953459252929322687</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-vprBOVtrPKI/AAAAAAAAAAI/AAAAAAAAFIE/BFr93W72njw/s512-c/photo.jpg" /></author><thr:total>1</thr:total><feedburner:origLink>http://service-architecture.blogspot.com/2011/09/nfc-what-apple-does-next-buy-amex.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Dk8DSH89fCp7ImA9WhdSEU0.&quot;"><id>tag:blogger.com,1999:blog-11168006.post-8973733249080533898</id><published>2011-07-19T20:47:00.000+01:00</published><updated>2011-07-19T20:47:59.164+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-19T20:47:59.164+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Java" /><category scheme="http://www.blogger.com/atom/ns#" term="Java SE 7" /><title>Java 7 SE approved... Meh</title><summary type="html">Hey Java SE 7 has been approved... now that is spectacularly quickly.  You'd almost think that the normal Java Community Process had been ignored and instead the spec lead had taken an externally created spec straight to approval...

What is most depressing in reading the various Oracle (mainly ex-Sun employee) releases on this is that not a single one actually commented on the fact that of the &lt;img src="http://feeds.feedburner.com/~r/ServiceArchitecture/~4/sk22YlUfN0g" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://service-architecture.blogspot.com/feeds/8973733249080533898/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=11168006&amp;postID=8973733249080533898" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/8973733249080533898?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/8973733249080533898?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ServiceArchitecture/~3/sk22YlUfN0g/java-7-se-approved-meh.html" title="Java 7 SE approved... Meh" /><author><name>Steve Jones</name><uri>https://profiles.google.com/101953459252929322687</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-vprBOVtrPKI/AAAAAAAAAAI/AAAAAAAAFIE/BFr93W72njw/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://service-architecture.blogspot.com/2011/07/java-7-se-approved-meh.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0YFSHg9cSp7ImA9WhdSEU0.&quot;"><id>tag:blogger.com,1999:blog-11168006.post-6359156639054896982</id><published>2011-07-19T19:45:00.000+01:00</published><updated>2011-07-19T19:45:19.669+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-19T19:45:19.669+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="technology" /><category scheme="http://www.blogger.com/atom/ns#" term="decisions" /><category scheme="http://www.blogger.com/atom/ns#" term="dumb" /><category scheme="http://www.blogger.com/atom/ns#" term="vendors" /><title>Dumb IT: We've already got some licenses for this</title><summary type="html">There are certain phrases that fill me with dread.  'We are using Agile so we don't need to have a vision, we'll just iterate', 'there are no data quality issues', 'We're the first people to use this' and 'The vendors roadmap says they'll do X in 2 years so it will be fine by the time we need that'.  One however is completely variable in the fear it introduces because it comes in three clear &lt;img src="http://feeds.feedburner.com/~r/ServiceArchitecture/~4/oUAv_GnjT1U" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://service-architecture.blogspot.com/feeds/6359156639054896982/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=11168006&amp;postID=6359156639054896982" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/6359156639054896982?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/6359156639054896982?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ServiceArchitecture/~3/oUAv_GnjT1U/dumb-it-weve-already-got-some-licenses.html" title="Dumb IT: We've already got some licenses for this" /><author><name>Steve Jones</name><uri>https://profiles.google.com/101953459252929322687</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-vprBOVtrPKI/AAAAAAAAAAI/AAAAAAAAFIE/BFr93W72njw/s512-c/photo.jpg" /></author><thr:total>2</thr:total><feedburner:origLink>http://service-architecture.blogspot.com/2011/07/dumb-it-weve-already-got-some-licenses.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkYAQ3k-fyp7ImA9WhdTGUo.&quot;"><id>tag:blogger.com,1999:blog-11168006.post-1862148960160641166</id><published>2011-07-18T09:00:00.001+01:00</published><updated>2011-07-18T09:35:42.757+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-18T09:35:42.757+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="fail" /><category scheme="http://www.blogger.com/atom/ns#" term="recovery" /><category scheme="http://www.blogger.com/atom/ns#" term="project" /><category scheme="http://www.blogger.com/atom/ns#" term="business" /><title>Hackgate and what it teaches us about responsibility</title><summary type="html">The ongoing Hackgate scandal, we can call it that as people in the US are now interested rather than just the dull old 'phone hacking scandal', teaches us some very interesting lessons about corporate politics and the meaning of the term responsibility.

I see quite a few projects where the issue is that someone somewhere hasn't taken control or responsibility and therefore things have gone off &lt;img src="http://feeds.feedburner.com/~r/ServiceArchitecture/~4/5hwM_fPaY6s" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://service-architecture.blogspot.com/feeds/1862148960160641166/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=11168006&amp;postID=1862148960160641166" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/1862148960160641166?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/1862148960160641166?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ServiceArchitecture/~3/5hwM_fPaY6s/hackgate-and-what-it-teaches-us-about.html" title="Hackgate and what it teaches us about responsibility" /><author><name>Steve Jones</name><uri>https://profiles.google.com/101953459252929322687</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-vprBOVtrPKI/AAAAAAAAAAI/AAAAAAAAFIE/BFr93W72njw/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://service-architecture.blogspot.com/2011/07/hackgate-and-what-it-teaches-us-about.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0UEQ3szfSp7ImA9WhdTF04.&quot;"><id>tag:blogger.com,1999:blog-11168006.post-7701703993954239186</id><published>2011-07-15T13:00:00.000+01:00</published><updated>2011-07-15T13:00:02.585+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-15T13:00:02.585+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="rant" /><category scheme="http://www.blogger.com/atom/ns#" term="people" /><category scheme="http://www.blogger.com/atom/ns#" term="fail" /><category scheme="http://www.blogger.com/atom/ns#" term="IT" /><title>Preaching to the Choir: the bane of IT</title><summary type="html">Sometimes I get asked why I bother debating with people who clearly have a different opinion with me and are unlikely to change their mind.  The reason is that sometimes, rarely I'll admit, that sometimes I will change my mind and occasionally I will change theirs.

The other reason is what is the point of debating with someone who agrees with you?  Unfortunately in a lot of IT we have two types &lt;img src="http://feeds.feedburner.com/~r/ServiceArchitecture/~4/UyInRjRNnms" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://service-architecture.blogspot.com/feeds/7701703993954239186/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=11168006&amp;postID=7701703993954239186" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/7701703993954239186?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/7701703993954239186?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ServiceArchitecture/~3/UyInRjRNnms/preaching-to-choir-bane-of-it.html" title="Preaching to the Choir: the bane of IT" /><author><name>Steve Jones</name><uri>https://profiles.google.com/101953459252929322687</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-vprBOVtrPKI/AAAAAAAAAAI/AAAAAAAAFIE/BFr93W72njw/s512-c/photo.jpg" /></author><thr:total>2</thr:total><feedburner:origLink>http://service-architecture.blogspot.com/2011/07/preaching-to-choir-bane-of-it.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0IHRH08fSp7ImA9WhdTE0Q.&quot;"><id>tag:blogger.com,1999:blog-11168006.post-9155363006671305535</id><published>2011-07-11T15:45:00.000+01:00</published><updated>2011-07-11T15:45:35.375+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-11T15:45:35.375+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="integration" /><category scheme="http://www.blogger.com/atom/ns#" term="SaaS" /><category scheme="http://www.blogger.com/atom/ns#" term="MDM" /><title>SaaS integration - making the ERP mistakes on a bigger scale</title><summary type="html">One of the most frustrating things in IT is the totally amazing ability of people not to learn from past experiences.  The following are all the sorts of things I've recently heard at conferences, vendor presentations, business presentations and in company architecture practices.
"We don't need an MDM solution as Salesforce is going to be our only customer repository"
"Integration is simple, its &lt;img src="http://feeds.feedburner.com/~r/ServiceArchitecture/~4/q-jISsE89d0" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://service-architecture.blogspot.com/feeds/9155363006671305535/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=11168006&amp;postID=9155363006671305535" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/9155363006671305535?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/9155363006671305535?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ServiceArchitecture/~3/q-jISsE89d0/saas-integration-making-erp-mistakes-on.html" title="SaaS integration - making the ERP mistakes on a bigger scale" /><author><name>Steve Jones</name><uri>https://profiles.google.com/101953459252929322687</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-vprBOVtrPKI/AAAAAAAAAAI/AAAAAAAAFIE/BFr93W72njw/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://service-architecture.blogspot.com/2011/07/saas-integration-making-erp-mistakes-on.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkcERXY9fip7ImA9WhZaF0o.&quot;"><id>tag:blogger.com,1999:blog-11168006.post-8780198391239680956</id><published>2011-07-04T11:06:00.000+01:00</published><updated>2011-07-04T11:06:44.866+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-04T11:06:44.866+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Google" /><category scheme="http://www.blogger.com/atom/ns#" term="mobility" /><category scheme="http://www.blogger.com/atom/ns#" term="Microsoft" /><category scheme="http://www.blogger.com/atom/ns#" term="business" /><title>Microsoft's Eastern Front: the iPad and mobility</title><summary type="html">For those who study European Wars the decision to invade Russia consistently stands as one of the dumbest that any individual can attempt.  Not because Russia as an army was consistently brilliant or strong but because the Russian country is just too big and the winters too harsh to defeat via an invasion.

For years this has been the challenge of those taking on Microsoft, they've attacked the &lt;img src="http://feeds.feedburner.com/~r/ServiceArchitecture/~4/E6cJz-Xmb1Y" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://service-architecture.blogspot.com/feeds/8780198391239680956/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=11168006&amp;postID=8780198391239680956" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/8780198391239680956?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/8780198391239680956?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ServiceArchitecture/~3/E6cJz-Xmb1Y/microsofts-eastern-front-ipad-and.html" title="Microsoft's Eastern Front: the iPad and mobility" /><author><name>Steve Jones</name><uri>https://profiles.google.com/101953459252929322687</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-vprBOVtrPKI/AAAAAAAAAAI/AAAAAAAAFIE/BFr93W72njw/s512-c/photo.jpg" /></author><thr:total>0</thr:total><georss:featurename>Reading, UK</georss:featurename><georss:point>51.45504099999999 -0.9690884000000324</georss:point><georss:box>51.41336549999999 -1.0314244000000323 51.496716499999984 -0.9067524000000324</georss:box><feedburner:origLink>http://service-architecture.blogspot.com/2011/07/microsofts-eastern-front-ipad-and.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkQESXg5cSp7ImA9WhZaF0o.&quot;"><id>tag:blogger.com,1999:blog-11168006.post-6707619599553462423</id><published>2011-07-04T10:05:00.000+01:00</published><updated>2011-07-04T10:05:08.629+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-04T10:05:08.629+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Google+" /><category scheme="http://www.blogger.com/atom/ns#" term="Google" /><category scheme="http://www.blogger.com/atom/ns#" term="social business" /><title>Why Google Apps plus Google+ would change the market</title><summary type="html">Okay I managed to get into Google+... so what did I find?  Well first off I found something with an unusual view on privacy and security.  I can send a message to a specific Circle and then anyone in that Circle can then share that information with anyone they want.  So the ability for private information to go viral is absolutely straight there... this is something that needs to be changed for &lt;img src="http://feeds.feedburner.com/~r/ServiceArchitecture/~4/zL_kLsMFL18" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://service-architecture.blogspot.com/feeds/6707619599553462423/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=11168006&amp;postID=6707619599553462423" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/6707619599553462423?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/6707619599553462423?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ServiceArchitecture/~3/zL_kLsMFL18/why-google-apps-plus-google-would.html" title="Why Google Apps plus Google+ would change the market" /><author><name>Steve Jones</name><uri>https://profiles.google.com/101953459252929322687</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-vprBOVtrPKI/AAAAAAAAAAI/AAAAAAAAFIE/BFr93W72njw/s512-c/photo.jpg" /></author><thr:total>2</thr:total><feedburner:origLink>http://service-architecture.blogspot.com/2011/07/why-google-apps-plus-google-would.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEQFSHs-cSp7ImA9WhZaF0s.&quot;"><id>tag:blogger.com,1999:blog-11168006.post-8403739263019030721</id><published>2011-07-04T07:47:00.001+01:00</published><updated>2011-07-04T07:51:59.559+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-04T07:51:59.559+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Prior Art" /><category scheme="http://www.blogger.com/atom/ns#" term="geo-social" /><title>Geo-Privacy bubbles: controlling smart phone features based on location</title><summary type="html">The new iOS 5 integration with Twitter is great and the ability to geo-tag posts is fine and dandy.  But there is a problem, when I get home and tweet I don't want to send the location, nor do I want to send the location when I pick the kids up from school or do any number of stalker/burglar friendly things.  These elements are almost always related to specific physical locations that I don't &lt;img src="http://feeds.feedburner.com/~r/ServiceArchitecture/~4/i8-8OY4afyo" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://service-architecture.blogspot.com/feeds/8403739263019030721/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=11168006&amp;postID=8403739263019030721" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/8403739263019030721?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/8403739263019030721?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ServiceArchitecture/~3/i8-8OY4afyo/geo-privacy-bubbles-controlling-smart.html" title="Geo-Privacy bubbles: controlling smart phone features based on location" /><author><name>Steve Jones</name><uri>https://profiles.google.com/101953459252929322687</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-vprBOVtrPKI/AAAAAAAAAAI/AAAAAAAAFIE/BFr93W72njw/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/-WfkcEAlplxM/ThFgev2YqKI/AAAAAAAAFIU/qLppLbw1UIk/s72-c/Map%2Bcopy.png" height="72" width="72" /><thr:total>0</thr:total><georss:featurename>Plymouth Station, Plymouth, Devon PL4 6AA, UK</georss:featurename><georss:point>50.3777152 -4.142963699999996</georss:point><georss:box>22.074571699999996 -63.908588699999996 78.6808587 55.622661300000004</georss:box><feedburner:origLink>http://service-architecture.blogspot.com/2011/07/geo-privacy-bubbles-controlling-smart.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkQGQnczfCp7ImA9WhZaF0s.&quot;"><id>tag:blogger.com,1999:blog-11168006.post-7250930069950220865</id><published>2011-07-04T07:18:00.000+01:00</published><updated>2011-07-04T07:18:43.984+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-04T07:18:43.984+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Prior Art" /><category scheme="http://www.blogger.com/atom/ns#" term="geo-social" /><category scheme="http://www.blogger.com/atom/ns#" term="social business" /><title>The problem of mobile places in a geo-social world</title><summary type="html">I'm sitting writing this on a train, a specific train, the 06:37(ish) leaving St Austell Station and heading to London Paddington.  Later in the week I'm going to take a specific train to Paris from London and then probably another to get back to the UK.  A few weeks ago I took a specific flight to get to the US.

When considering the current state of the Geo-Social world its clear that movement &lt;img src="http://feeds.feedburner.com/~r/ServiceArchitecture/~4/WvKlGng0qRc" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://service-architecture.blogspot.com/feeds/7250930069950220865/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=11168006&amp;postID=7250930069950220865" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/7250930069950220865?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/7250930069950220865?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ServiceArchitecture/~3/WvKlGng0qRc/problem-of-mobile-places-in-geo-social.html" title="The problem of mobile places in a geo-social world" /><author><name>Steve Jones</name><uri>https://profiles.google.com/101953459252929322687</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-vprBOVtrPKI/AAAAAAAAAAI/AAAAAAAAFIE/BFr93W72njw/s512-c/photo.jpg" /></author><thr:total>2</thr:total><georss:featurename>St Austell Rail Station, Saint Austell, Cornwall PL26, UK</georss:featurename><georss:point>50.33951 -4.789409999999975</georss:point><georss:box>22.0171115 -64.55503499999998 78.6619085 54.976215000000025</georss:box><feedburner:origLink>http://service-architecture.blogspot.com/2011/07/problem-of-mobile-places-in-geo-social.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkcBSXczeCp7ImA9WhZaFU8.&quot;"><id>tag:blogger.com,1999:blog-11168006.post-5075031392763712400</id><published>2011-07-01T14:47:00.000+01:00</published><updated>2011-07-01T14:47:38.980+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-01T14:47:38.980+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="performance" /><category scheme="http://www.blogger.com/atom/ns#" term="big data" /><category scheme="http://www.blogger.com/atom/ns#" term="database" /><title>Has de-normalisation had its day?</title><summary type="html">Ever since the relational database became king there has been a mantra in IT and information design.  De-normalisation is critical to the effective use of information in both transactional and, particularly, analytical systems.  The reason for de-normalisation is to do with the issues around read performance in relational models.  De-normalisation is always an increase in complexity over the &lt;img src="http://feeds.feedburner.com/~r/ServiceArchitecture/~4/1BZBudhsH8w" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://service-architecture.blogspot.com/feeds/5075031392763712400/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=11168006&amp;postID=5075031392763712400" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/5075031392763712400?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/11168006/posts/default/5075031392763712400?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ServiceArchitecture/~3/1BZBudhsH8w/has-de-normalisation-had-its-day.html" title="Has de-normalisation had its day?" /><author><name>Steve Jones</name><uri>https://profiles.google.com/101953459252929322687</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-vprBOVtrPKI/AAAAAAAAAAI/AAAAAAAAFIE/BFr93W72njw/s512-c/photo.jpg" /></author><thr:total>3</thr:total><feedburner:origLink>http://service-architecture.blogspot.com/2011/07/has-de-normalisation-had-its-day.html</feedburner:origLink></entry></feed>

