<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: jargon</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/jargon.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2009-01-05T10:46:57+00:00</updated><author><name>Simon Willison</name></author><entry><title>Talking about OpenID</title><link href="https://simonwillison.net/2009/Jan/5/talking/#atom-tag" rel="alternate"/><published>2009-01-05T10:46:57+00:00</published><updated>2009-01-05T10:46:57+00:00</updated><id>https://simonwillison.net/2009/Jan/5/talking/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://mywhat.org/2009/01/04/talking-about-openid/"&gt;Talking about OpenID&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
“So a relying party walks in to a bar...”


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/comic"&gt;comic&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/jargon"&gt;jargon&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/openid"&gt;openid&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/relyingparty"&gt;relyingparty&lt;/a&gt;&lt;/p&gt;



</summary><category term="comic"/><category term="jargon"/><category term="openid"/><category term="relyingparty"/></entry><entry><title>Quoting Tim O'Reilly</title><link href="https://simonwillison.net/2008/Dec/29/jargon/#atom-tag" rel="alternate"/><published>2008-12-29T19:29:40+00:00</published><updated>2008-12-29T19:29:40+00:00</updated><id>https://simonwillison.net/2008/Dec/29/jargon/#atom-tag</id><summary type="html">
    &lt;blockquote cite="http://radar.oreilly.com/2008/12/google-walmart-mybarackobama.html"&gt;&lt;p&gt;I seem to have lost the battle to define Web 2.0 as "the use of the network as platform to build systems that get better the more people use them."&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="http://radar.oreilly.com/2008/12/google-walmart-mybarackobama.html"&gt;Tim O&amp;#x27;Reilly&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/jargon"&gt;jargon&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/tim-oreilly"&gt;tim-oreilly&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/web20"&gt;web20&lt;/a&gt;&lt;/p&gt;



</summary><category term="jargon"/><category term="tim-oreilly"/><category term="web20"/></entry><entry><title>Agile Development -or- How to name a religion</title><link href="https://simonwillison.net/2006/Dec/12/agile/#atom-tag" rel="alternate"/><published>2006-12-12T08:54:12+00:00</published><updated>2006-12-12T08:54:12+00:00</updated><id>https://simonwillison.net/2006/Dec/12/agile/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://paultyma.blogspot.com/2006/12/agile-development-or-how-to-name.html"&gt;Agile Development -or- How to name a religion&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Clever language trick: If you’re not doing agile, you’re “not agile”.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/agile"&gt;agile&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/jargon"&gt;jargon&lt;/a&gt;&lt;/p&gt;



</summary><category term="agile"/><category term="jargon"/></entry><entry><title>Why the term Ajax is useful</title><link href="https://simonwillison.net/2005/Apr/19/useful/#atom-tag" rel="alternate"/><published>2005-04-19T01:15:58+00:00</published><updated>2005-04-19T01:15:58+00:00</updated><id>https://simonwillison.net/2005/Apr/19/useful/#atom-tag</id><summary type="html">
    &lt;p id="p-0"&gt;Software design patterns are useful mainly because they provide a shared vocabulary: rather than discussing the intimate details of a three layered application architecture, we say "MVC". Rather than describing an object that tracks your progress while looping over a collection, we say "Iterator".&lt;/p&gt;

&lt;p id="p-1"&gt;The same is true for &lt;a href="http://www.adaptivepath.com/publications/essays/archives/000385.php"&gt;Ajax&lt;/a&gt;. While the techniques it describes have been around for years, grouping them under a single term is extremely valuable for raising the level of discussion about them. No longer will we have to explain XMLHttpRequest / hidden iframes / crazy cookie tricks in depth when discussing sites which pull fresh information from the server without reloading the whole page. Instead, we can say "Ajax" and move on to more interesting things.&lt;/p&gt;

&lt;p id="p-2"&gt;Matthew Haughey says it's &lt;a href="http://a.wholelottanothing.org/2005/04/note_to_geeks_l.html" title="Note to geeks: look beyond the end of your nose"&gt;all about marketing&lt;/a&gt;. I disagree; it's about smarter and more effective conversations.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/ajax"&gt;ajax&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/design-patterns"&gt;design-patterns&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/jargon"&gt;jargon&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/xmlhttprequest"&gt;xmlhttprequest&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="ajax"/><category term="design-patterns"/><category term="jargon"/><category term="xmlhttprequest"/></entry></feed>