<?xml version="1.0" encoding="utf-8" standalone="no"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-GB">
  <generator uri="https://jekyllrb.com/" version="4.3.1">Jekyll</generator>
  <link href="https://feeds.feedburner.com/julianbrownerecent" rel="self" type="application/atom+xml"/>
  <link href="https://www.julianbrowne.com/" hreflang="en-GB" rel="alternate" type="text/html"/>
  <updated>2023-03-27T16:52:00+01:00</updated>
  <id>https://www.julianbrowne.com/rss/posts.xml</id>
  <title>Recent Articles from Julian Browne</title>
  <subtitle>Periodic essays on software architecture, development and technology management in start-ups, scale-ups and the corporate enterprise</subtitle>
  <entry>
    <id>https://www.julianbrowne.com/article/the-95/</id>
    <title>The 95%</title>
    <published>2023-03-27T00:00:00+01:00</published>
    <updated>2023-03-27T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/the-95/" rel="alternate" title="The 95%" type="text/html"/>
    <summary>
      It's easy to get carried away with the notion of productivity. It's important but it's also important not to single out highly productive people and compare them to others. It's the varied differences in teams which are both unavoidable and can be harnessed to do better work. Not talking about 10x developers is good for team diversity and avoiding tech-bro monocultures.
    </summary>
    <category term="business"/>
    <category term="development"/>
    <category term="culture"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/the-95/assets/images/surfers.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/the-95/assets/images/surfers.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/blockchain/</id>
    <title>Blockchain and The Third Web</title>
    <published>2023-03-14T00:00:00+00:00</published>
    <updated>2023-03-14T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/blockchain/" rel="alternate" title="Blockchain and The Third Web" type="text/html"/>
    <summary>
      The second in a two-part series looking at the evolution of the architecture of the web and its future. This article interactively explores blockchain technology  and Web3 (vs Web 3.0) to predict that Web3 will fade away and probably take  blockchain with it.
    </summary>
    <category term="architecture"/>
    <category term="development"/>
    <category term="gadget"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/blockchain/assets/images/prometheus.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/blockchain/assets/images/prometheus.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/100-year-architecture/</id>
    <title>100-Year Architecture</title>
    <published>2023-02-28T00:00:00+00:00</published>
    <updated>2023-02-28T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/100-year-architecture/" rel="alternate" title="100-Year Architecture" type="text/html"/>
    <summary>
      What do we think about when we design software architectures to last? The modern web is a great example of a software architecture that has stood the test of time but it took some crazy thinking and an atomic bomb to get there.
    </summary>
    <category term="architecture"/>
    <category term="development"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/100-year-architecture/assets/images/fireflies.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/100-year-architecture/assets/images/fireflies.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/sacred-cows/</id>
    <title>Killing The Sacred Cows</title>
    <published>2023-02-21T00:00:00+00:00</published>
    <updated>2023-02-21T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/sacred-cows/" rel="alternate" title="Killing The Sacred Cows" type="text/html"/>
    <summary>
      Lots of businesses are striving to be 'digital' and yet when it comes to  making changes to the way they work with tech and product teams they won't do simple things that make a huge difference
    </summary>
    <category term="business"/>
    <category term="delivery"/>
    <category term="development"/>
    <category term="governance"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/sacred-cows/assets/images/cow-2.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/sacred-cows/assets/images/cow-2.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/tech-culture/</id>
    <title>Tech Culture</title>
    <published>2023-02-13T00:00:00+00:00</published>
    <updated>2023-02-13T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/tech-culture/" rel="alternate" title="Tech Culture" type="text/html"/>
    <summary>
      The most important thing to get right in any tech-powered busines is the culture. It may feel like we are making strides in this area but we're not. Mary Parker Follet had it nailed more than a hundred years ago.
    </summary>
    <category term="business"/>
    <category term="culture"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/tech-culture/assets/images/the-last-hours-of-pompei.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/tech-culture/assets/images/the-last-hours-of-pompei.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/moving-to-the-cloud/</id>
    <title>Moving to the Cloud</title>
    <published>2023-02-06T00:00:00+00:00</published>
    <updated>2023-02-06T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/moving-to-the-cloud/" rel="alternate" title="Moving to the Cloud" type="text/html"/>
    <summary>
      A short article on cloud migrations based on having done a few
    </summary>
    <category term="architecture"/>
    <category term="business"/>
    <category term="delivery"/>
    <category term="strategy"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/moving-to-the-cloud/assets/images/cloud.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/moving-to-the-cloud/assets/images/cloud.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/risk-free-development/</id>
    <title>Risk-Free Development</title>
    <published>2023-01-31T00:00:00+00:00</published>
    <updated>2023-01-31T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/risk-free-development/" rel="alternate" title="Risk-Free Development" type="text/html"/>
    <summary>
      This article looks at the concept of risk and asks whether it really exists in the way we perceive it and whether that can be used to operate like it doesn't
    </summary>
    <category term="business"/>
    <category term="delivery"/>
    <category term="development"/>
    <category term="governance"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/risk-free-development/assets/images/the-tightrope-walker.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/risk-free-development/assets/images/the-tightrope-walker.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/creator-myth/</id>
    <title>The Creator Myth</title>
    <published>2023-01-30T00:00:00+00:00</published>
    <updated>2023-01-30T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/creator-myth/" rel="alternate" title="The Creator Myth" type="text/html"/>
    <summary>
      Product Management is an important part of modern software development but it's proving hard to successfully implement in organistions, especially those that have not quite got agile delivery working yet. This article looks at why that is and how you can address some of the main anti-patterns
    </summary>
    <category term="business"/>
    <category term="development"/>
    <category term="requirements"/>
    <category term="strategy"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/creator-myth/assets/images/howff.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/creator-myth/assets/images/howff.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/death-by-customer/</id>
    <title>Death By Customer</title>
    <published>2018-10-13T00:00:00+01:00</published>
    <updated>2018-10-13T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/death-by-customer/" rel="alternate" title="Death By Customer" type="text/html"/>
    <summary>
      If companies want to get better at being agile and digital, whatever that means, they need to stop looking to rules and process for the answer. Most of all they need to stop expecting the appointment of an agile coach to change them. Make the company a happy one and the rest will follow.
    </summary>
    <category term="delivery"/>
    <category term="agile"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/death-by-customer/assets/images/tooth-puller.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/death-by-customer/assets/images/tooth-puller.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/scaling-agility/</id>
    <title>Scaling With Agility</title>
    <published>2016-12-01T00:00:00+00:00</published>
    <updated>2016-12-01T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/scaling-agility/" rel="alternate" title="Scaling With Agility" type="text/html"/>
    <summary>
      
    </summary>
    <category term="development"/>
    <category term="agile"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/scaling-agility/assets/images/tree.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/scaling-agility/assets/images/tree.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/agile-killing-architect/</id>
    <title>Is Agile Killing the Architect?</title>
    <published>2016-07-01T00:00:00+01:00</published>
    <updated>2016-07-01T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/agile-killing-architect/" rel="alternate" title="Is Agile Killing the Architect?" type="text/html"/>
    <summary>
      Has the rise of agile delvery killed off the role of the sofware architect in businesses, or is it still as relevent as it ever was?
    </summary>
    <category term="architecture"/>
    <category term="development"/>
    <category term="agile"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/agile-killing-architect/assets/images/slide.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/agile-killing-architect/assets/images/slide.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/freemarket-freelancer/</id>
    <title>The Freemarket Freelancer</title>
    <published>2015-06-08T00:00:00+01:00</published>
    <updated>2015-06-08T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/freemarket-freelancer/" rel="alternate" title="The Freemarket Freelancer" type="text/html"/>
    <summary>
      The market for contractors is all wrong. It should operate more like the film industry where top talent (not rockstars, or those with the loudest voices, but inidivduals who can make, and have made, a difference to the bottom line) gets recognised to the same degree and those that don't get walk-on parts only.
    </summary>
    <category term="development"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/freemarket-freelancer/assets/images/joachim-beuckelaer-market-woman.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/freemarket-freelancer/assets/images/joachim-beuckelaer-market-woman.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/happy-software/</id>
    <title>Happy Software</title>
    <published>2015-04-26T00:00:00+01:00</published>
    <updated>2015-04-26T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/happy-software/" rel="alternate" title="Happy Software" type="text/html"/>
    <summary>
      
    </summary>
    <category term="development"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/competence-debt/</id>
    <title>The Competence Debt</title>
    <published>2014-05-03T00:00:00+01:00</published>
    <updated>2014-05-03T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/competence-debt/" rel="alternate" title="The Competence Debt" type="text/html"/>
    <summary>
      A summary, and a little extension, to Ben Horowitz's book The Hard Thing About Hard Things
    </summary>
    <category term="business"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/competence-debt/assets/images/competence-debt.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/competence-debt/assets/images/competence-debt.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/software-economics/</id>
    <title>Software Economics</title>
    <published>2013-12-03T00:00:00+00:00</published>
    <updated>2013-12-03T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/software-economics/" rel="alternate" title="Software Economics" type="text/html"/>
    <summary>
      Everything large companies do to fund software projects is wrong. Large capital investments and a misguided attempt to separate 'software' from 'business' leads to poor requirements management, information arbitrage, and a general lack of diligence around budgets.
    </summary>
    <category term="delivery"/>
    <category term="development"/>
    <category term="business"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/software-economics/assets/images/software-economics.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/software-economics/assets/images/software-economics.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/rockstars/</id>
    <title>No More Rock Stars</title>
    <published>2013-10-29T00:00:00+00:00</published>
    <updated>2013-10-29T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/rockstars/" rel="alternate" title="No More Rock Stars" type="text/html"/>
    <summary>
      Real rockstars can be assholes. That may be annoying but we tolerate it because we prioritise their art over their behaviour. This should not be the case with rock star developers. It's time to say goodbye to the notion that they produce good code or help our industry in any way.
    </summary>
    <category term="development"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/rockstars/assets/images/rockstars.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/rockstars/assets/images/rockstars.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/the-lean-architect/</id>
    <title>The Lean Architect</title>
    <published>2013-03-18T00:00:00+00:00</published>
    <updated>2013-03-18T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/the-lean-architect/" rel="alternate" title="The Lean Architect" type="text/html"/>
    <summary>
      Contrary to popular belief, the concepts of lean delivery and architecture are not mutually exclusive. The practices of architecture design are in many senses wasteful, but waste isn't a simple thing to define. Many types of wasteful activity are in fact highly valuable in the longer term.
    </summary>
    <category term="architecture"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/the-lean-architect/assets/images/the-lean-architect.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/the-lean-architect/assets/images/the-lean-architect.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/big-data-deception/</id>
    <title>The Big Data Deception</title>
    <published>2013-02-10T00:00:00+00:00</published>
    <updated>2013-02-10T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/big-data-deception/" rel="alternate" title="The Big Data Deception" type="text/html"/>
    <summary>
      Big data is going to be awesome for the few select industries that have the skills and the need for it. But they are few and far between. Most of the others will just jump on the Big Data bandwagon as the next in a long line of money wasters that introduce more complexity into the enterprise.
    </summary>
    <category term="architecture"/>
    <category term="business"/>
    <category term="strategy"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/big-data-deception/assets/images/ahab.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/big-data-deception/assets/images/ahab.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/inevitability-of-evil/</id>
    <title>The Inevitability of Evil</title>
    <published>2013-02-07T00:00:00+00:00</published>
    <updated>2013-02-07T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/inevitability-of-evil/" rel="alternate" title="The Inevitability of Evil" type="text/html"/>
    <summary>
      Why are big companies so often seen as evil. Is corporate evil inevitable? Small companies don't seem to be tarnished with the evil brush. So is it related to how we view growth and is there a limit at which corporations should just stop growing and leave room for others to step in.
    </summary>
    <category term="business"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/inevitability-of-evil/assets/images/weyden.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/inevitability-of-evil/assets/images/weyden.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/easter-bunny/</id>
    <title>The Grand High Order of the Easter Bunny</title>
    <published>2012-09-01T00:00:00+01:00</published>
    <updated>2012-09-01T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/easter-bunny/" rel="alternate" title="The Grand High Order of the Easter Bunny" type="text/html"/>
    <summary>
      Open source doesn't just work because it's better quality (generally) than closed source software. It works because it's far easier to weave knowledge of it into an organisation. If everybody can use it then anybody can become expert in it. The lack of licenses, training, etc demystifies and democratises software which massively improves it's changes of long term success in the business.
    </summary>
    <category term="business"/>
    <category term="delivery"/>
    <category term="development"/>
    <category term="humour"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/easter-bunny/assets/images/bunny.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/easter-bunny/assets/images/bunny.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/the-new-new-tool/</id>
    <title>The New New Tool</title>
    <published>2011-11-05T00:00:00+00:00</published>
    <updated>2011-11-05T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/the-new-new-tool/" rel="alternate" title="The New New Tool" type="text/html"/>
    <summary>
      A change story for everyday folk. Any similarities to projects ongoing or past are entirely intentional.
    </summary>
    <category term="business"/>
    <category term="humour"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/the-new-new-tool/assets/images/new-new-tool.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/the-new-new-tool/assets/images/new-new-tool.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/nosql-in-the-enterprise/</id>
    <title>NoSQL in the Enterprise</title>
    <published>2011-07-31T00:00:00+01:00</published>
    <updated>2011-07-31T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/nosql-in-the-enterprise/" rel="alternate" title="NoSQL in the Enterprise" type="text/html"/>
    <summary>
      Part two of series on NoSQL in the enterprise. This one specifically looks at MongoDB and all it's nuances and how these were managed in a corporate development setting.
    </summary>
    <category term="architecture"/>
    <category term="development"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/nosql-in-the-enterprise/assets/images/nosql-in-the-enterprise.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/nosql-in-the-enterprise/assets/images/nosql-in-the-enterprise.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/freedom-from-the-tyranny-of-schemas/</id>
    <title>Freedom from the Tyranny of Schemas</title>
    <published>2011-07-30T00:00:00+01:00</published>
    <updated>2011-07-30T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/freedom-from-the-tyranny-of-schemas/" rel="alternate" title="Freedom from the Tyranny of Schemas" type="text/html"/>
    <summary>
      This article, based on commercial experience, takes a pragmatic look at NoSQL and its fit with the conservative world of corporate IT. It covers how NoSQL products sit alongside relational alternatives, some of the issues experienced in breaking resistance to the concept, and how to overcome them.
    </summary>
    <category term="architecture"/>
    <category term="business"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/freedom-from-the-tyranny-of-schemas/assets/images/the-oatmeal-fanboi.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/freedom-from-the-tyranny-of-schemas/assets/images/the-oatmeal-fanboi.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/attraction-of-laws/</id>
    <title>The Attraction of Laws</title>
    <published>2011-06-05T00:00:00+01:00</published>
    <updated>2011-06-05T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/attraction-of-laws/" rel="alternate" title="The Attraction of Laws" type="text/html"/>
    <summary>
      A short treatise on some of the most relevant eponymous laws as they may apply to the field of software engineering.
    </summary>
    <category term="business"/>
    <category term="humour"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/attraction-of-laws/assets/images/wanderer.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/attraction-of-laws/assets/images/wanderer.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/secret-sauce/</id>
    <title>The Secret Sauce</title>
    <published>2011-05-29T00:00:00+01:00</published>
    <updated>2011-05-29T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/secret-sauce/" rel="alternate" title="The Secret Sauce" type="text/html"/>
    <summary>
      Great software requires an understanding of the secret sauce that goes into making it. Enterprises that fall down when it comes to great architectures can also tap into this recipe. It turns out that architecture needs and good agile practices are actually one and the same.
    </summary>
    <category term="architecture"/>
    <category term="delivery"/>
    <category term="development"/>
    <category term="governance"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/secret-sauce/assets/images/sauce.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/secret-sauce/assets/images/sauce.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/crisis-over/</id>
    <title>Crisis Over</title>
    <published>2011-01-30T00:00:00+00:00</published>
    <updated>2011-01-30T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/crisis-over/" rel="alternate" title="Crisis Over" type="text/html"/>
    <summary>
      Software development projects have problems, but software development doesn't.
    </summary>
    <category term="architecture"/>
    <category term="business"/>
    <category term="delivery"/>
    <category term="development"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/crisis-over/assets/images/noodle_tree.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/crisis-over/assets/images/noodle_tree.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/ungoverning-the-business/</id>
    <title>Ungoverning the Business</title>
    <published>2010-11-13T00:00:00+00:00</published>
    <updated>2010-11-13T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/ungoverning-the-business/" rel="alternate" title="Ungoverning the Business" type="text/html"/>
    <summary>
      Standards in enterprise IT aren't just irrelevent, they're devisive, dangerous and they restrict progress. You don't need governance and you don't need standards. You need checkpoints in the process you already have and a community that determines its own accepted practices and keeps them alive.
    </summary>
    <category term="architecture"/>
    <category term="business"/>
    <category term="delivery"/>
    <category term="development"/>
    <category term="governance"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/ungoverning-the-business/assets/images/mckean_still_in_business.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/ungoverning-the-business/assets/images/mckean_still_in_business.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/hammer-time/</id>
    <title>Hammer Time</title>
    <published>2010-05-17T00:00:00+01:00</published>
    <updated>2014-05-13T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/hammer-time/" rel="alternate" title="Hammer Time" type="text/html"/>
    <summary>
      IT in big corporates has become so afraid of making mistakes that hardly anybody will stand up and say following corporate platform standards, or waterfall design, might not be the best approach. This is a post in favour of (some) tool-first thinking.
    </summary>
    <category term="architecture"/>
    <category term="business"/>
    <category term="delivery"/>
    <category term="development"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/hammer-time/assets/images/the_hammer.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/hammer-time/assets/images/the_hammer.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/strained-relationships/</id>
    <title>Strained Relationships</title>
    <published>2009-11-03T00:00:00+00:00</published>
    <updated>2009-11-03T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/strained-relationships/" rel="alternate" title="Strained Relationships" type="text/html"/>
    <summary>
      Just what is all this fuss about NoSQL? Is the relational database dead? Or are we just in need of alternative options to solve a new breed of problem?
    </summary>
    <category term="architecture"/>
    <category term="business"/>
    <category term="development"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/strained-relationships/assets/images/titian-david-and-goliath.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/strained-relationships/assets/images/titian-david-and-goliath.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/law-and-order/</id>
    <title>Law and Order</title>
    <published>2009-08-29T00:00:00+01:00</published>
    <updated>2009-08-29T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/law-and-order/" rel="alternate" title="Law and Order" type="text/html"/>
    <summary>
      Has Enterprise Architecture had its day? All rise. The court is in session.
    </summary>
    <category term="architecture"/>
    <category term="business"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/quixotics-anonymous/</id>
    <title>Quixotics Anonymous </title>
    <published>2009-07-25T00:00:00+01:00</published>
    <updated>2009-07-25T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/quixotics-anonymous/" rel="alternate" title="Quixotics Anonymous " type="text/html"/>
    <summary>
      Quixotics Anonymous a special interest group for the down at heart in corporate IT. Patron Saint: C. Northcote Parkinson.
    </summary>
    <category term="business"/>
    <category term="humour"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/gangsta-scale/</id>
    <title>Gangstas Don't Scale</title>
    <published>2009-06-19T00:00:00+01:00</published>
    <updated>2009-06-19T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/gangsta-scale/" rel="alternate" title="Gangstas Don't Scale" type="text/html"/>
    <summary>
      Enterprise integration had a tendency about ten years ago to be all asynchronous. Enterprise Architects, seduced by talk of cheap limitless scale from vendors, installed message based middeware everywhere. But asynchrony has some important constraints that aren't always obvious. This article illustrates one of these constraints using an example from The Wire TV show.
    </summary>
    <category term="architecture"/>
    <category term="development"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/gangsta-scale/assets/images/gangsta-cop-dog.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/gangsta-scale/assets/images/gangsta-cop-dog.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/walking-the-walk/</id>
    <title>Walking the Walk</title>
    <published>2009-05-05T00:00:00+01:00</published>
    <updated>2009-05-05T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/walking-the-walk/" rel="alternate" title="Walking the Walk" type="text/html"/>
    <summary>
      
    </summary>
    <category term="delivery"/>
    <category term="gadget"/>
    <category term="requirements"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/walking-the-walk/assets/images/walking-the-walk.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/walking-the-walk/assets/images/walking-the-walk.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/estimation-game/</id>
    <title>The Estimation Game</title>
    <published>2009-04-05T00:00:00+01:00</published>
    <updated>2009-04-05T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/estimation-game/" rel="alternate" title="The Estimation Game" type="text/html"/>
    <summary>
      Much of what happens during portfolio planning is just wasting time on a wistful mirage.
    </summary>
    <category term="business"/>
    <category term="delivery"/>
    <category term="strategy"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/tactegic-stractical/</id>
    <title>Was that Tactegic or Stractical?</title>
    <published>2009-03-08T00:00:00+00:00</published>
    <updated>2009-03-08T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/tactegic-stractical/" rel="alternate" title="Was that Tactegic or Stractical?" type="text/html"/>
    <summary>
      When there's a clash of opinion on whether to go strategic or tactical, do not waste time debating how you could do the tactical first then deploy the strategic option later. It. Never. Happens.
    </summary>
    <category term="architecture"/>
    <category term="business"/>
    <category term="delivery"/>
    <category term="development"/>
    <category term="strategy"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/planning-the-plan/</id>
    <title>Planning the Plan</title>
    <published>2009-01-25T00:00:00+00:00</published>
    <updated>2009-01-25T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/planning-the-plan/" rel="alternate" title="Planning the Plan" type="text/html"/>
    <summary>
      Portfolio planning and the McFarlan Matrix in action.
    </summary>
    <category term="business"/>
    <category term="delivery"/>
    <category term="strategy"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/brewers-cap-theorem/</id>
    <title>Brewer's CAP Theorem</title>
    <published>2009-01-11T00:00:00+00:00</published>
    <updated>2009-01-11T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/brewers-cap-theorem/" rel="alternate" title="Brewer's CAP Theorem" type="text/html"/>
    <summary>
      An explanation of Eric Brewer's CAP theorem, which says you cannot have more than two of Consistency, Availability and Partition-tolerance in web-based distributed systems.
    </summary>
    <category term="architecture"/>
    <category term="business"/>
    <category term="strategy"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/brewers-cap-theorem/assets/images/sex_pistols_by_jsaurer.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/brewers-cap-theorem/assets/images/sex_pistols_by_jsaurer.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/super-geek-top-ten/</id>
    <title>The Super-Geek Top Ten</title>
    <published>2008-12-30T00:00:00+00:00</published>
    <updated>2008-12-30T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/super-geek-top-ten/" rel="alternate" title="The Super-Geek Top Ten" type="text/html"/>
    <summary>
      A super-geek top ten, exploring the more human side of some of the greatest computer scientists in history.
    </summary>
    <category term="humour"/>
    <category term="other"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/event-driven-architecture/</id>
    <title>The Event-Driven Architecture</title>
    <published>2008-12-07T00:00:00+00:00</published>
    <updated>2008-12-07T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/event-driven-architecture/" rel="alternate" title="The Event-Driven Architecture" type="text/html"/>
    <summary>
      An introduction to the event-driven architecture and the subject of complex event processing as they apply to business.
    </summary>
    <category term="architecture"/>
    <category term="business"/>
    <category term="strategy"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/wife-swapping-art-conflict/</id>
    <title>Wife Swapping and the Art of Conflict</title>
    <published>2008-11-22T00:00:00+00:00</published>
    <updated>2008-11-22T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/wife-swapping-art-conflict/" rel="alternate" title="Wife Swapping and the Art of Conflict" type="text/html"/>
    <summary>
      Great results requires great leadership, which is less about trying to get people to reach consensus than enabling productive conflict via the gift of the wife swap pattern.
    </summary>
    <category term="business"/>
    <category term="delivery"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/role-models-services/</id>
    <title>Role Models and Services</title>
    <published>2008-11-09T00:00:00+00:00</published>
    <updated>2008-11-09T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/role-models-services/" rel="alternate" title="Role Models and Services" type="text/html"/>
    <summary>
      Successful SOA is about being able to define real services and not confusing them with interfaces. The secret to services is roles.
    </summary>
    <category term="architecture"/>
    <category term="business"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/role-models-services/assets/images/bridgewater_foundary.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/role-models-services/assets/images/bridgewater_foundary.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/systemic-requirements/</id>
    <title>Systemic Requirements</title>
    <published>2008-11-01T00:00:00+00:00</published>
    <updated>2008-11-01T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/systemic-requirements/" rel="alternate" title="Systemic Requirements" type="text/html"/>
    <summary>
      Non-functional requirements, system constraints and qualities, systemic requirements. Whatever you call them, here they are.
    </summary>
    <category term="architecture"/>
    <category term="requirements"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/solution-maturity/</id>
    <title>Solution Maturity</title>
    <published>2008-10-28T00:00:00+00:00</published>
    <updated>2008-10-28T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/solution-maturity/" rel="alternate" title="Solution Maturity" type="text/html"/>
    <summary>
      Design, or Technical, Debt is receiving growing acceptance in the development community as a useful and practical metaphor. This article shows how it can be used as a measure of solution maturity at the enterprise level in corporate environments.
    </summary>
    <category term="architecture"/>
    <category term="business"/>
    <category term="strategy"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/fp-pt2/</id>
    <title>Make room for Functional Programming (2)</title>
    <published>2008-10-12T00:00:00+01:00</published>
    <updated>2008-10-12T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/fp-pt2/" rel="alternate" title="Make room for Functional Programming (2)" type="text/html"/>
    <summary>
      The second of two parts explaining the main concepts of functional programming: this time through a worked example.
    </summary>
    <category term="development"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/fp-pt1/</id>
    <title>Make room for Functional Programming (1)</title>
    <published>2008-08-25T00:00:00+01:00</published>
    <updated>2008-08-25T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/fp-pt1/" rel="alternate" title="Make room for Functional Programming (1)" type="text/html"/>
    <summary>
      The first of a two-part article explaining all the main concepts of functional programming: from lambda functions, to closures, to continuations, to monads.
    </summary>
    <category term="development"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/the-reuse-fairy/</id>
    <title>Dancing with the Reuse Fairy</title>
    <published>2008-08-13T00:00:00+01:00</published>
    <updated>2008-08-13T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/the-reuse-fairy/" rel="alternate" title="Dancing with the Reuse Fairy" type="text/html"/>
    <summary>
      This is the story of the software reuse fairy. She comes and goes, seducing some, and annoying others. She is real, but there are good reasons not to believe.
    </summary>
    <category term="architecture"/>
    <category term="business"/>
    <category term="development"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/third-way/</id>
    <title>Embracing the Third Way</title>
    <published>2008-08-04T00:00:00+01:00</published>
    <updated>2008-08-04T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/third-way/" rel="alternate" title="Embracing the Third Way" type="text/html"/>
    <summary>
      There's still too much fervour around open source vs commercial software. One isn't better than the other, and both are here to stay. Harmony lies not with the communities, but with the users and IT leaders who need to accept their responsibilities to make both prosper.
    </summary>
    <category term="business"/>
    <category term="development"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/change-antipattern/</id>
    <title>10 Reasons Change is an Antipattern</title>
    <published>2008-07-09T00:00:00+01:00</published>
    <updated>2008-07-09T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/change-antipattern/" rel="alternate" title="10 Reasons Change is an Antipattern" type="text/html"/>
    <summary>
      Everybody's talking about change: Change Programmes, Embracing Change, Championing Change. Here are ten reasons you might want to avoid change and just improve instead.
    </summary>
    <category term="business"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/pragmatic-strategy/</id>
    <title>Strategy for the Irretrievably Pragmatic</title>
    <published>2008-07-05T00:00:00+01:00</published>
    <updated>2008-07-05T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/pragmatic-strategy/" rel="alternate" title="Strategy for the Irretrievably Pragmatic" type="text/html"/>
    <summary>
      Strategy has a bad name with some, being seen as the preserve of talking shops and consultants. But a good strategy, well-applied, can be the making of a company. It's not possible to say what the right strategy is for all businesses, but there are some good rules for applying it. This article looks at why the most pragmatic people are often the best creators of strategy and how it's as much about bottom-up thinking as it is about future vision.
    </summary>
    <category term="architecture"/>
    <category term="business"/>
    <category term="development"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/abc-esb/</id>
    <title>The ABC of the ESB</title>
    <published>2008-06-24T00:00:00+01:00</published>
    <updated>2008-06-24T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/abc-esb/" rel="alternate" title="The ABC of the ESB" type="text/html"/>
    <summary>
      IT people must be some of the cleverest and expensive in the world. Or at least that the theory. And yet we are constantly falling for the emperors new clothes in the form of next-big-things whilst discarding what we have, even the bits of what we have that work. The answer lies in understanding the history of how we got to where we got to and, unfortunately, accepting that some things are hard work and we have to do it.
    </summary>
    <category term="architecture"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/magnificence-mundane/</id>
    <title>Magnificence in the Mundane</title>
    <published>2008-06-14T00:00:00+01:00</published>
    <updated>2008-06-14T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/magnificence-mundane/" rel="alternate" title="Magnificence in the Mundane" type="text/html"/>
    <summary>
      Relationships between IT departments and business customers are not unlike real world friendships. If you can see what works with your friends you can apply it in business. And it's mostly about conversations. If you can talk, you have a good chance of resolving anything. As professionals in a complex subject area it's always tempting to look for sophisticated answers to problems, but by focusing on the common sense basics of how we structure ourselves and how we act we can deliver better software. When we do that we cease to be something  distinct from the business and we can stop talking about business/IT alignment and get on with doing what we do best.
    </summary>
    <category term="business"/>
    <category term="delivery"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/the-interview-pt1/</id>
    <title>The Interview - Part One</title>
    <published>2008-06-05T00:00:00+01:00</published>
    <updated>2008-06-05T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/the-interview-pt1/" rel="alternate" title="The Interview - Part One" type="text/html"/>
    <summary>
      Interviewing is a vastly underrated skill, and yet if you can do it well it brings you the best of all rewards - good people to work with. This is part one of a two-part article looking at effective candidate filtering, interviewing techniques and questions that work for technology roles.
    </summary>
    <category term="business"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/change-steps/</id>
    <title>Change Steps</title>
    <published>2008-05-16T00:00:00+01:00</published>
    <updated>2008-05-16T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/change-steps/" rel="alternate" title="Change Steps" type="text/html"/>
    <summary>
      The last of three articles about change programmes. This one assumes that you have got to the point where you have to have one (the two previous articles explained why generally they are not a good idea). If issues have been left to fester for too long though sometimes you have no choice. This article proposes a way to run a change programme that is effective with the minimum amount of paperwork and fuss. A change programme that makes changes. What a novel idea that is.
    </summary>
    <category term="business"/>
    <category term="delivery"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/scalability/</id>
    <title>Scalability</title>
    <published>2008-04-28T00:00:00+01:00</published>
    <updated>2008-04-28T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/scalability/" rel="alternate" title="Scalability" type="text/html"/>
    <summary>
      
    </summary>
    <category term="architecture"/>
    <category term="development"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/agile-fallacies/</id>
    <title>The Fallacies of Agile</title>
    <published>2008-04-26T00:00:00+01:00</published>
    <updated>2008-04-26T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/agile-fallacies/" rel="alternate" title="The Fallacies of Agile" type="text/html"/>
    <summary>
      The Agile approach is great when applied appropriately, but the concept is nothing new. In fact it goes so far back it shares its roots with the waterfall method. But Agile got a cool name in 2001 (before that it was just working closely with the customer in an iterative fashion, which wasn't anywhere near as catchy) and was jumped upon by consultants and cowboy coders. This article looks at just some of the common fallacies that have grown up around this peculiar buzzword.
    </summary>
    <category term="delivery"/>
    <category term="development"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/scooby-doo/</id>
    <title>What would Scooby do?</title>
    <published>2008-03-21T00:00:00+00:00</published>
    <updated>2008-03-21T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/scooby-doo/" rel="alternate" title="What would Scooby do?" type="text/html"/>
    <summary>
      How change programmes usually go once the consultants turn up. These are the warning signs to look out for. All found by deep reading the masterful and authoritative canon that is the work of Scooby Doo.
    </summary>
    <category term="business"/>
    <category term="humour"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/scooby-doo/assets/images/fred.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/scooby-doo/assets/images/fred.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/retep-principle/</id>
    <title>The Retep Principle</title>
    <published>2008-03-11T00:00:00+00:00</published>
    <updated>2008-03-11T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/retep-principle/" rel="alternate" title="The Retep Principle" type="text/html"/>
    <summary>
      
    </summary>
    <category term="business"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/foundations/</id>
    <title>Foundations</title>
    <published>2008-02-12T00:00:00+00:00</published>
    <updated>2023-02-21T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/foundations/" rel="alternate" title="Foundations" type="text/html"/>
    <summary>
      Packaging up delivery work for the annual plan is tricky. You don't want huge programmes that spend a fortune and lose their way, but equally too many small projects will likely dupllicate work and create a communication nightmare. What you need is a mix of business-outcome driven initiatives supported by a small number of carefully scoped foundational projects. Here's how.
    </summary>
    <category term="business"/>
    <category term="strategy"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/foundations/assets/images/painting-a-staircase.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/foundations/assets/images/painting-a-staircase.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/analysis-business/</id>
    <title>The Analysis Business</title>
    <published>2008-01-30T00:00:00+00:00</published>
    <updated>2008-01-30T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/analysis-business/" rel="alternate" title="The Analysis Business" type="text/html"/>
    <summary>
      A look at business requirements from a functional and non-functional perspective, concluding that partitioning requirements up into arbitrary categories isn't very helpful as it reinforces the subjective politics we need to get away from.
    </summary>
    <category term="business"/>
    <category term="requirements"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/nature-of-functionality/</id>
    <title>The Nature Of Functionality</title>
    <published>2008-01-16T00:00:00+00:00</published>
    <updated>2008-01-16T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/nature-of-functionality/" rel="alternate" title="The Nature Of Functionality" type="text/html"/>
    <summary>
      A look at the potential subjectivity of business requirements and how to spot it.
    </summary>
    <category term="business"/>
    <category term="requirements"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/nature-of-functionality/assets/images/magritte-invention-of-life.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/nature-of-functionality/assets/images/magritte-invention-of-life.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/shortest-path/</id>
    <title>Dijkstra's Shortest Path</title>
    <published>2008-01-15T00:00:00+00:00</published>
    <updated>2015-05-23T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/shortest-path/" rel="alternate" title="Dijkstra's Shortest Path" type="text/html"/>
    <summary>
      A visually interactive exploration of Dijkstra's Shortest Path Algorithm.
    </summary>
    <category term="development"/>
    <category term="gadget"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/shortest-path/assets/images/dijkstra.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/shortest-path/assets/images/dijkstra.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/measuring-architecture/</id>
    <title>Measuring Architecture</title>
    <published>2008-01-03T00:00:00+00:00</published>
    <updated>2008-01-03T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/measuring-architecture/" rel="alternate" title="Measuring Architecture" type="text/html"/>
    <summary>
      A short walk around the discipline of enterprise architecture. What it is, why it's good, and how you know if it's working.
    </summary>
    <category term="architecture"/>
    <category term="strategy"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/transformation-trouble/</id>
    <title>The Trouble with Transformations</title>
    <published>2007-12-11T00:00:00+00:00</published>
    <updated>2007-12-11T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/transformation-trouble/" rel="alternate" title="The Trouble with Transformations" type="text/html"/>
    <summary>
      IT and Business transformations and change programs are very fashionable. But most often, you don't need one. You just need to sort your problems out via better leadership.
    </summary>
    <category term="business"/>
    <category term="delivery"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/transformation-trouble/assets/images/precious.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/transformation-trouble/assets/images/precious.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/vision/</id>
    <title>Reality Street ain't got no Vision</title>
    <published>2007-11-29T00:00:00+00:00</published>
    <updated>2007-11-29T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/vision/" rel="alternate" title="Reality Street ain't got no Vision" type="text/html"/>
    <summary>
      The second of a two-part piece on reality and vision. This article puts the case that it's all very well thinking about the right now, but without a vision it means nothing.
    </summary>
    <category term="architecture"/>
    <category term="strategy"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/governance-apparition/</id>
    <title>The Governance Apparition</title>
    <published>2007-11-26T00:00:00+00:00</published>
    <updated>2007-11-26T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/governance-apparition/" rel="alternate" title="The Governance Apparition" type="text/html"/>
    <summary>
      Financial governance? Project governance? Architecture governance? Service governance? All just distractions that prevent us from seeing that we just need a reasonable process.
    </summary>
    <category term="business"/>
    <category term="delivery"/>
    <category term="governance"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/death-of-architecture/</id>
    <title>The Death of Architecture</title>
    <published>2007-11-16T00:00:00+00:00</published>
    <updated>2007-11-16T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/death-of-architecture/" rel="alternate" title="The Death of Architecture" type="text/html"/>
    <summary>
      The first of a two-parter that looks at enterprise architecture and reality. One thing to get straight, to make architecture effective, is to realise that it is, in and of itself, a mirage. It's just an idea with no value until it's made real.
    </summary>
    <category term="architecture"/>
    <category term="strategy"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/death-of-architecture/assets/images/death-as-fiddler.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/death-of-architecture/assets/images/death-as-fiddler.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/loose-coupling/</id>
    <title>A Loose Coupling Strategy</title>
    <published>2007-10-18T00:00:00+01:00</published>
    <updated>2007-10-18T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/loose-coupling/" rel="alternate" title="A Loose Coupling Strategy" type="text/html"/>
    <summary>
      Sometimes (or maybe all the time) you've got to make architecture count quickly. There's no time, or buy-in, to any longer term visionary fluff. In these cases refactoring is your friend.
    </summary>
    <category term="architecture"/>
    <category term="development"/>
    <category term="strategy"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/anger-management-design-debt/</id>
    <title>Enterprise Design Debt</title>
    <published>2007-10-08T00:00:00+01:00</published>
    <updated>2007-10-08T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/anger-management-design-debt/" rel="alternate" title="Enterprise Design Debt" type="text/html"/>
    <summary>
      The concept of design, or technical, debt is fairly well covered around the web. This article looks at how all that debt being created on projects might be wrapped up and managed from an enterprise perspective.
    </summary>
    <category term="business"/>
    <category term="delivery"/>
    <category term="development"/>
    <category term="governance"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/build-buy/</id>
    <title>Build or Buy. Or Customise and Confuse</title>
    <published>2007-10-03T00:00:00+01:00</published>
    <updated>2007-10-03T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/build-buy/" rel="alternate" title="Build or Buy. Or Customise and Confuse" type="text/html"/>
    <summary>
      A short article on why thinking in simplistic terms like buy or build your software is dangerous. There are some good rules that should determine which is right for which situation. Both are necessary, but buying when you really should be building can be a major mistake.
    </summary>
    <category term="delivery"/>
    <category term="governance"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/the-requirements-delusion/</id>
    <title>The Requirements Delusion</title>
    <published>2007-09-29T00:00:00+01:00</published>
    <updated>2007-09-29T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/the-requirements-delusion/" rel="alternate" title="The Requirements Delusion" type="text/html"/>
    <summary>
      Successful IT requires that you educate your business into getting the best from its technology capability by exploring the possibilities, not blindly trying to meet their requirements.
    </summary>
    <category term="business"/>
    <category term="requirements"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/the-requirements-delusion/assets/images/orpen-chef.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/the-requirements-delusion/assets/images/orpen-chef.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/decoder-game/</id>
    <title>Frequency Analysis Decoder</title>
    <published>2007-09-27T00:00:00+01:00</published>
    <updated>2023-02-12T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/decoder-game/" rel="alternate" title="Frequency Analysis Decoder" type="text/html"/>
    <summary>
      A basic game that encrypts a random piece of text using a substitution cypher and lets you use frequency analysis to decode it.
    </summary>
    <category term="gadget"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/decoder-game/assets/images/the-spy-nicolae-grigorescu.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/decoder-game/assets/images/the-spy-nicolae-grigorescu.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/soa-myths/</id>
    <title>SOA Myth and Mystery</title>
    <published>2007-09-20T00:00:00+01:00</published>
    <updated>2007-09-20T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/soa-myths/" rel="alternate" title="SOA Myth and Mystery" type="text/html"/>
    <summary>
      SOA can be dangerous if it's seen (or sold) as a panacea. Like any IT design approach it's hard to get right. Put all your success eggs in your SOA basket at your peril.
    </summary>
    <category term="architecture"/>
    <category term="development"/>
    <category term="governance"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/business-alignment-fallacy/</id>
    <title>The Business Alignment Fallacy</title>
    <published>2007-09-19T00:00:00+01:00</published>
    <updated>2007-09-19T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/business-alignment-fallacy/" rel="alternate" title="The Business Alignment Fallacy" type="text/html"/>
    <summary>
      Business alignment is a hot topic in IT. Here I put forward the idea that attempting to align IT and the business is a fruitless exercise, because alignment is a fallacious concept. Everyone in the organisation is the business. IT is therefore already aligned. What's needed is talk about possible capabilities, not talk of alignment.
    </summary>
    <category term="business"/>
    <category term="strategy"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/fractal-amplification-part-one/</id>
    <title>Fractal Amplification (1)</title>
    <published>2007-08-31T00:00:00+01:00</published>
    <updated>2007-08-31T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/fractal-amplification-part-one/" rel="alternate" title="Fractal Amplification (1)" type="text/html"/>
    <summary>
      Good coding, and ultimately good architecture, is about a very very very simple concept - putting the right thing in the right place.
    </summary>
    <category term="architecture"/>
    <category term="development"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/teamwork/</id>
    <title>No C in Teamwork</title>
    <published>2007-08-15T00:00:00+01:00</published>
    <updated>2007-08-15T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/teamwork/" rel="alternate" title="No C in Teamwork" type="text/html"/>
    <summary>
      It's easy to confuse teamwork and success. They aren't always the same. Sometimes to be successful you have to suspend your own needs to work towards a greater good, which in the end is better for everybody.
    </summary>
    <category term="delivery"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/kill-your-children/</id>
    <title>Kill Your Children</title>
    <published>2007-08-14T00:00:00+01:00</published>
    <updated>2007-08-14T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/kill-your-children/" rel="alternate" title="Kill Your Children" type="text/html"/>
    <summary>
      Selling new ideas, especially ones with a technology basis, can be difficult. People get bored so quickly with technology presentations, and yet they will sit through a two-hour film without any difficulty. It's all about narratology.
    </summary>
    <category term="business"/>
    <category term="delivery"/>
    <category term="strategy"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/managing-people/</id>
    <title>Managing People</title>
    <published>2007-08-07T00:00:00+01:00</published>
    <updated>2007-08-07T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/managing-people/" rel="alternate" title="Managing People" type="text/html"/>
    <summary>
      We all have to face that stay-technical or manage decision at some point in our IT careers. But why not both? Are not the best managers those that retain a feel for what IT is all about?
    </summary>
    <category term="business"/>
    <category term="development"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/nfrs/</id>
    <title>Non-Functional Requirements</title>
    <published>2007-08-01T00:00:00+01:00</published>
    <updated>2007-08-01T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/nfrs/" rel="alternate" title="Non-Functional Requirements" type="text/html"/>
    <summary>
      
    </summary>
    <category term="architecture"/>
    <category term="requirements"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/hold-on-a-tick/</id>
    <title>Hold on a tick</title>
    <published>2007-07-18T00:00:00+01:00</published>
    <updated>2007-07-18T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/hold-on-a-tick/" rel="alternate" title="Hold on a tick" type="text/html"/>
    <summary>
      People like their systems to be fast. It's because we hate to wait. In software sometimes there are delays, but they don't have to be annoying.
    </summary>
    <category term="development"/>
    <category term="requirements"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/megaprojects/</id>
    <title>Megaprojects</title>
    <published>2007-07-04T00:00:00+01:00</published>
    <updated>2007-07-04T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/megaprojects/" rel="alternate" title="Megaprojects" type="text/html"/>
    <summary>
      Don't get seduced. When it comes to projects, big is most certainly not better. It's a recipe for disaster.
    </summary>
    <category term="delivery"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/interface-catalogue/</id>
    <title>Interface Catalogue</title>
    <published>2007-07-01T00:00:00+01:00</published>
    <updated>2007-07-01T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/interface-catalogue/" rel="alternate" title="Interface Catalogue" type="text/html"/>
    <summary>
      A template for capturing interfaces between applications on a project. Quite simple, but very effective for planning and communication.
    </summary>
    <category term="architecture"/>
    <category term="template"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/amdahls-law/</id>
    <title>Amdahl's Law</title>
    <published>2007-06-28T00:00:00+01:00</published>
    <updated>2023-02-20T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/amdahls-law/" rel="alternate" title="Amdahl's Law" type="text/html"/>
    <summary>
      A simple calculator to explore the implications of Amdahl's Law on business processes.
    </summary>
    <category term="architecture"/>
    <category term="gadget"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/amdahls-law/assets/images/amdahl.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/amdahls-law/assets/images/amdahl.webp"/>
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/space-based-archetypes/</id>
    <title>Space-based Archetypes</title>
    <published>2007-06-27T00:00:00+01:00</published>
    <updated>2007-06-27T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/space-based-archetypes/" rel="alternate" title="Space-based Archetypes" type="text/html"/>
    <summary>
      The third of three articles on the space-based architecture. This one looks at how the patterns of SBA deployment naturally lend themselves to supporting systemic requirements.
    </summary>
    <category term="architecture"/>
    <category term="development"/>
    <category term="requirements"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/space-based-agility/</id>
    <title>Space-based Agility</title>
    <published>2007-06-25T00:00:00+01:00</published>
    <updated>2007-06-25T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/space-based-agility/" rel="alternate" title="Space-based Agility" type="text/html"/>
    <summary>
      The second of three articles on spaced-based architecture. This one explains why using SBA can make you more agile.
    </summary>
    <category term="architecture"/>
    <category term="delivery"/>
    <category term="requirements"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/space-based-architecture-example/</id>
    <title>Space-based Architecture</title>
    <published>2007-06-06T00:00:00+01:00</published>
    <updated>2007-06-06T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/space-based-architecture-example/" rel="alternate" title="Space-based Architecture" type="text/html"/>
    <summary>
      The first of three articles on the space-based architecture. This one describes what the SBA approach is all about.
    </summary>
    <category term="architecture"/>
    <category term="development"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/the-little-language/</id>
    <title>The Little Language</title>
    <published>2007-05-28T00:00:00+01:00</published>
    <updated>2007-05-28T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/the-little-language/" rel="alternate" title="The Little Language" type="text/html"/>
    <summary>
      A short word about domain specific languages and why they might hold much promise for software development, business relations, and effective reuse.
    </summary>
    <category term="development"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/doing-it-right-doing-it-wrong/</id>
    <title>Doing it right can mean doing it wrong</title>
    <published>2007-05-23T00:00:00+01:00</published>
    <updated>2007-05-23T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/doing-it-right-doing-it-wrong/" rel="alternate" title="Doing it right can mean doing it wrong" type="text/html"/>
    <summary>
      It's really easy to get so hung up on principles like DRY, YAGNI, KISS, etc that we can't even write a line of code for fear that it might be picked apart by the purists. Relax. Sometimes you should write poorly structured code to see where your going, as long as you track it and can fix it later.
    </summary>
    <category term="development"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/lispians/</id>
    <title>Lispians</title>
    <published>2007-05-01T00:00:00+01:00</published>
    <updated>2007-05-01T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/lispians/" rel="alternate" title="Lispians" type="text/html"/>
    <summary>
      A quick look at Lisp to see if there's any truth to the intellectual hype.
    </summary>
    <category term="development"/>
    <category term="humour"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/idiom-idiot/</id>
    <title>The Idiom and the Idiot</title>
    <published>2007-04-21T00:00:00+01:00</published>
    <updated>2007-04-21T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/idiom-idiot/" rel="alternate" title="The Idiom and the Idiot" type="text/html"/>
    <summary>
      Finding an agile architecture requires thinking and acting like your business, not clinging to the supposed tenets of best practice.
    </summary>
    <category term="architecture"/>
    <category term="business"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/outsourcing-we-will-go/</id>
    <title>Outsourcing we will go</title>
    <published>2007-04-14T00:00:00+01:00</published>
    <updated>2007-04-14T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/outsourcing-we-will-go/" rel="alternate" title="Outsourcing we will go" type="text/html"/>
    <summary>
      Creating great software is difficult. But it's the realisation of everything marketing and branding talk about, so never, ever, ever, give it to someone else to do.
    </summary>
    <category term="business"/>
    <category term="delivery"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/methodologies-suck/</id>
    <title>Methodologies Suck</title>
    <published>2007-04-12T00:00:00+01:00</published>
    <updated>2007-04-12T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/methodologies-suck/" rel="alternate" title="Methodologies Suck" type="text/html"/>
    <summary>
      Formally structuring what you do is great, because it helps anyone somewhat removed from the project quickly understand where you are. It also helps establish some sense of repeatability and an opportunity to continuously improve. But don't get caught up in the methodology madness.
    </summary>
    <category term="delivery"/>
    <category term="governance"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/engineer/</id>
    <title>The engineer that wasn't there</title>
    <published>2007-04-10T00:00:00+01:00</published>
    <updated>2007-04-10T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/engineer/" rel="alternate" title="The engineer that wasn't there" type="text/html"/>
    <summary>
      Turns out that the term software engineer, was never really meant to be adopted by coders. It was used as a challenge to developers at a NATO conference in 1968 to be more structured and methodical.
    </summary>
    <category term="development"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/narratology/</id>
    <title>Are You Sitting Comfortably?</title>
    <published>2007-04-05T00:00:00+01:00</published>
    <updated>2007-04-05T00:00:00+01:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/narratology/" rel="alternate" title="Are You Sitting Comfortably?" type="text/html"/>
    <summary>
      A brief introduction to the concepts of narratology, and why they can help you do better presentations.
    </summary>
    <category term="business"/>
    <category term="delivery"/>
    
  </entry>
  <entry>
    <id>https://www.julianbrowne.com/article/seeing-the-spoon/</id>
    <title>Seeing the Spoon</title>
    <published>2007-04-01T00:00:00+01:00</published>
    <updated>2008-01-01T00:00:00+00:00</updated>
    <author><name>Julian Browne</name></author>
    <link href="https://www.julianbrowne.com/article/seeing-the-spoon/" rel="alternate" title="Seeing the Spoon" type="text/html"/>
    <summary>
      A kick-off article for the site in general, or why I decided to get a few things of my chest
    </summary>
    <category term="architecture"/>
    <category term="business"/>
    <category term="delivery"/>
    <media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.julianbrowne.com/article/seeing-the-spoon/assets/images/spoon.webp"/>
    <media:content xmlns:media="http://search.yahoo.com/mrss/" medium="image" url="https://www.julianbrowne.com/article/seeing-the-spoon/assets/images/spoon.webp"/>
  </entry>
  
  
</feed>