Permalink
Browse files

Updating history page

  • Loading branch information...
1 parent f046f66 commit f897aba7788091402d9cc052fcc44451e640cc78 @coreyhaines committed Nov 9, 2011
Showing with 12 additions and 14 deletions.
  1. +6 −7 _site/history.html
  2. +6 −7 history.html
View
@@ -55,15 +55,14 @@
<div id="content">
<h1>History of Coderetreat</h1>
<p>The idea for coderetreat was spawned at the January, 2009, <a href="http://codemash.org/">Codemash Conference</a> by Gary Bernhardt, Patrick Welsh, Nayan Hajratwala and me, Corey Haines. The idea was to develop a repeatable, day-long event that was focused on practicing the fundamentals of software development. The first event was held on January 24, 2009, in Ann Arbor, MI.</p>
-<p>Through the course of 2009, many retreats were held, including several international ones in Iceland and Romania. The format for the day evolved over the year, based on the concrete experiences of the facilitators. While the choice of facilitator has an effect on the details of the day, the over-arching recipe remains the same.</p>
-<p>Through 2010, I embarked on a coderetreat tour with the goal of facilitating 10 code retreats around the world (I ended the year having done 11). Along the way, I shared the formula and facilitation techniques, so that others could learn to effectively facilitate their own. This supported the ideal that the more skilled facilitators there are, the more coderetreats that can successfully reach their full potential. By June of 2011, I have facilitated over 20 coderetreats around the world.</p>
-<p>In 2011, based on my learnings of how to facilitate the day, I've expanded into <a href="/training.html">private in-house trainings</a> for companies using the coderetreat format. This year, we are seeing events happening all over the world, nearly every weekend. I'm making plans for ending the year with bang: Global Day of Coderetreat.</p>
+<p>Through the course of 2009, many retreats were held, including several international ones in Iceland and Romania. The format for the day evolved over the year, based on the concrete experiences of the facilitators. This has resulted in an established format that defines a coderetreat event. While the choice of facilitator has an effect on the details of the day, the over-arching recipe remains the same.</p>
+<p>Through 2010, I embarked on a coderetreat tour with the goal of facilitating 10 code retreats around the world (I ended the year having done 11). Along the way, I shared the formula and facilitation techniques, so that others could learn to effectively facilitate their own. This supported the ideal that the more skilled facilitators there are, the more coderetreats that can successfully reach their full potential.</p>
+<p>In 2011, based on my learnings of how to facilitate the day, I've expanded into <a href="/training.html">private in-house trainings</a> for companies using the coderetreat format. This year, we are seeing events happening all over the world, nearly every weekend. On December 3rd, 2011, we are ending the year with bang: <a href="/global_day.html">Global Day of Coderetreat</a>.</p>
<h3>Single- or Multi-language Events</h3>
<p>For the first year, we pushed single-language coderetreats, generally using Java as the language. It was chosen for one simple reason: almost anyone could code in it. There were coderetreats, though, held in different languages, most notably Ruby, but they were always single-language.</p>
-<p>In Romania, led by Alex Bolboaca, they had different ideas. They didn't stick to the single-language format and looked at what would happen if people did it in whatever language they wanted. So, at a single coderetreat, you might have people doing it in C#, some in Java, some in Python and perhaps a few in PHP. Since introducing Maria and Alex to the idea of coderetreat in May of 2009, the Romanians went wild and started having coderetreats all the time. When I went back to facilitate one in February, 2010, it became clear that they had some great learnings to share. We dropped the 'single-language' rule that I usually go with and went with their standard multi-language version. It worked great!</p>
-<p>Learning from them, I've dropped the general 'single-language' rule and am more than happy to have multiple languages happening side-by-side. I stress that it is important the languages are fairly main-stream, or at least familiar to both members of the pair, otherwise one person could get a bit confused on syntax, which brings us back to the whole 'coderetreat is not about learning a new language' idea.</p>
-<h3>What's Next: Global Day of Coderetreat</h3>
-<p>Coderetreat has come a long way from a simple conversation in a hallway to a global event. 2011 promises to see the coderetreat idea expand, culminating in the Global Day of Coderetreat: 32 hours where coderetreat is happening, ripplying through the timezones. My goal is to organize this for December, 2011, facilitating the first one in Australia and the last one in Hawaii.</p>
+<p>In Romania, led by Alex Bolboaca, they had different ideas. They didn't stick to the single-language format and looked at what would happen if people did it in whatever language they wanted. So, at a single coderetreat, you might have people doing it in C#, some in Java, some in Python and perhaps a few in PHP. I introduced Maria and Alex to the idea of coderetreat in May of 2009, and the Romanians went wild and started having coderetreats all the time. When I went back to facilitate one in February, 2010, it became clear that they had some great learnings to share. We dropped the 'single-language' rule that I usually go with and went with their standard multi-language version. It worked great!</p>
+<h3>Global Day of Coderetreat</h3>
+<p>Coderetreat has come a long way from a simple conversation in a hallway to a global event. 2011 has seen the coderetreat idea expand, culminating in the <a href="/global_day.html">Global Day of Coderetreat</a>: 32 hours where coderetreat is happening, ripplying through the timezones. The event is happening on December 3rd, 2011. I'll be facilitating the first one in Australia and the last one in Hawaii (thanks to the international date line).</p>
</div><!--/content-->
</div><!--/main-->
View
@@ -4,12 +4,11 @@
---
<h1>History of Coderetreat</h1>
<p>The idea for coderetreat was spawned at the January, 2009, <a href="http://codemash.org/">Codemash Conference</a> by Gary Bernhardt, Patrick Welsh, Nayan Hajratwala and me, Corey Haines. The idea was to develop a repeatable, day-long event that was focused on practicing the fundamentals of software development. The first event was held on January 24, 2009, in Ann Arbor, MI.</p>
-<p>Through the course of 2009, many retreats were held, including several international ones in Iceland and Romania. The format for the day evolved over the year, based on the concrete experiences of the facilitators. While the choice of facilitator has an effect on the details of the day, the over-arching recipe remains the same.</p>
-<p>Through 2010, I embarked on a coderetreat tour with the goal of facilitating 10 code retreats around the world (I ended the year having done 11). Along the way, I shared the formula and facilitation techniques, so that others could learn to effectively facilitate their own. This supported the ideal that the more skilled facilitators there are, the more coderetreats that can successfully reach their full potential. By June of 2011, I have facilitated over 20 coderetreats around the world.</p>
-<p>In 2011, based on my learnings of how to facilitate the day, I've expanded into <a href="/training.html">private in-house trainings</a> for companies using the coderetreat format. This year, we are seeing events happening all over the world, nearly every weekend. I'm making plans for ending the year with bang: Global Day of Coderetreat.</p>
+<p>Through the course of 2009, many retreats were held, including several international ones in Iceland and Romania. The format for the day evolved over the year, based on the concrete experiences of the facilitators. This has resulted in an established format that defines a coderetreat event. While the choice of facilitator has an effect on the details of the day, the over-arching recipe remains the same.</p>
+<p>Through 2010, I embarked on a coderetreat tour with the goal of facilitating 10 code retreats around the world (I ended the year having done 11). Along the way, I shared the formula and facilitation techniques, so that others could learn to effectively facilitate their own. This supported the ideal that the more skilled facilitators there are, the more coderetreats that can successfully reach their full potential.</p>
+<p>In 2011, based on my learnings of how to facilitate the day, I've expanded into <a href="/training.html">private in-house trainings</a> for companies using the coderetreat format. This year, we are seeing events happening all over the world, nearly every weekend. On December 3rd, 2011, we are ending the year with bang: <a href="/global_day.html">Global Day of Coderetreat</a>.</p>
<h3>Single- or Multi-language Events</h3>
<p>For the first year, we pushed single-language coderetreats, generally using Java as the language. It was chosen for one simple reason: almost anyone could code in it. There were coderetreats, though, held in different languages, most notably Ruby, but they were always single-language.</p>
-<p>In Romania, led by Alex Bolboaca, they had different ideas. They didn't stick to the single-language format and looked at what would happen if people did it in whatever language they wanted. So, at a single coderetreat, you might have people doing it in C#, some in Java, some in Python and perhaps a few in PHP. Since introducing Maria and Alex to the idea of coderetreat in May of 2009, the Romanians went wild and started having coderetreats all the time. When I went back to facilitate one in February, 2010, it became clear that they had some great learnings to share. We dropped the 'single-language' rule that I usually go with and went with their standard multi-language version. It worked great!</p>
-<p>Learning from them, I've dropped the general 'single-language' rule and am more than happy to have multiple languages happening side-by-side. I stress that it is important the languages are fairly main-stream, or at least familiar to both members of the pair, otherwise one person could get a bit confused on syntax, which brings us back to the whole 'coderetreat is not about learning a new language' idea.</p>
-<h3>What's Next: Global Day of Coderetreat</h3>
-<p>Coderetreat has come a long way from a simple conversation in a hallway to a global event. 2011 promises to see the coderetreat idea expand, culminating in the Global Day of Coderetreat: 32 hours where coderetreat is happening, ripplying through the timezones. My goal is to organize this for December, 2011, facilitating the first one in Australia and the last one in Hawaii.</p>
+<p>In Romania, led by Alex Bolboaca, they had different ideas. They didn't stick to the single-language format and looked at what would happen if people did it in whatever language they wanted. So, at a single coderetreat, you might have people doing it in C#, some in Java, some in Python and perhaps a few in PHP. I introduced Maria and Alex to the idea of coderetreat in May of 2009, and the Romanians went wild and started having coderetreats all the time. When I went back to facilitate one in February, 2010, it became clear that they had some great learnings to share. We dropped the 'single-language' rule that I usually go with and went with their standard multi-language version. It worked great!</p>
+<h3>Global Day of Coderetreat</h3>
+<p>Coderetreat has come a long way from a simple conversation in a hallway to a global event. 2011 has seen the coderetreat idea expand, culminating in the <a href="/global_day.html">Global Day of Coderetreat</a>: 32 hours where coderetreat is happening, ripplying through the timezones. The event is happening on December 3rd, 2011. I'll be facilitating the first one in Australia and the last one in Hawaii (thanks to the international date line).</p>

0 comments on commit f897aba

Please sign in to comment.