<?xml version='1.0' encoding='utf-8' ?>

<rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/' xmlns:atom10='http://www.w3.org/2005/Atom'>
<channel>
  <title>Rick Scott</title>
  <link>https://rickscott.dreamwidth.org/</link>
  <description>Rick Scott - Dreamwidth Studios</description>
  <lastBuildDate>Fri, 02 Jul 2010 20:38:00 GMT</lastBuildDate>
  <generator>LiveJournal / Dreamwidth Studios</generator>
  <lj:journal>rickscott</lj:journal>
  <lj:journaltype>personal</lj:journaltype>
  <image>
    <url>https://v2.dreamwidth.org/505476/518129</url>
    <title>Rick Scott</title>
    <link>https://rickscott.dreamwidth.org/</link>
    <width>100</width>
    <height>97</height>
  </image>

<item>
  <guid isPermaLink='true'>https://rickscott.dreamwidth.org/4125.html</guid>
  <pubDate>Fri, 02 Jul 2010 20:38:00 GMT</pubDate>
  <title>Do we have enough testing hackathons?</title>
  <link>https://rickscott.dreamwidth.org/4125.html</link>
  <description>&lt;p&gt;
Do we have enough hackathons in the testing world?
&lt;/p&gt;

&lt;p&gt;
So over on the open source dev side of the planet, we have these 
things called hackathons.  The archetype for this kind of event 
goes something like this:  
&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;Declare a rough topic: &quot;Apache bug bash&quot;, &quot;Perl-related projects&quot;.&lt;/li&gt;
  &lt;li&gt;Procure an inexpensive conference room.&lt;/li&gt;
  &lt;li&gt;Add a couple dozen highly motivated open source hackers.&lt;/li&gt;
  &lt;li&gt;Throw in snacks, wifi, collab tools, and a lot of caffeine.&lt;/li&gt;
  &lt;li&gt;Shake vigorously and observe the reaction.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
Sometimes these are done before or after another major conference;
sometimes they&apos;re scheduled on their own.  They are more or less
round-the-clock affairs where a heck of a lot gets done:
&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;tens or hundreds of bugs get closed;&lt;/li&gt;
  &lt;li&gt;new releases of major software projects get done;&lt;/li&gt;
  &lt;li&gt;sweeping new features are designed or implemented;&lt;/li&gt;
  &lt;li&gt;entirely new projects get cooked up and launched.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;
As much as I love remote collaboration, people in the same physical 
space have much higher communication bandwidth; you can communicate
with more nuance and turn around replies much more quickly.
They&apos;re also much less subject to the interruptions of daily life:
fire drill because a server crashed, the garden needs to be fed,
the cat needs watering, etc.  The cross-talk that does happen tends
to be germane to what&apos;s happening in the moment.  This all means that:
&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;many coordinated tasks get done in a relatively short time;&lt;/li&gt;
  &lt;li&gt;discussions can move forward a great distance in a relatively short time; and&lt;/li&gt;
  &lt;li&gt;a lot of cross-pollination happens -- people riff off of each other&apos;s ideas and come up with amazing new things.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;
Despite how productive hackathons can be, they cost very little.  
All that needs to be paid for is travel, space, and accomodation,
and the hackathon location can be selected so as to keep these low.  
&lt;/p&gt;

&lt;p&gt;
I think that the writing-about-testing conference engendered many of the 
points listed above.  I&apos;d like to see these kind of affairs happen more
often.
&lt;/p&gt;

&lt;p&gt;
The testing world has a number of great &apos;pro&apos; conferences: StarEast/West, 
STPCon, CAST, and so forth.  But do we have enough hackathons?
&lt;/p&gt;&lt;br /&gt;&lt;br /&gt;&lt;img src=&quot;https://www.dreamwidth.org/tools/commentcount?user=rickscott&amp;ditemid=4125&quot; width=&quot;30&quot; height=&quot;12&quot; alt=&quot;comment count unavailable&quot; style=&quot;vertical-align: middle;&quot;/&gt; comments</description>
  <comments>https://rickscott.dreamwidth.org/4125.html</comments>
  <category>qa</category>
  <category>conferences</category>
  <category>riffing</category>
  <category>hackathons</category>
  <category>testing</category>
  <category>collaboration</category>
  <lj:security>public</lj:security>
  <lj:reply-count>2</lj:reply-count>
</item>
</channel>
</rss>
