PageSourceSearch

https://blog.lazerwalker.com/2013/12/24/one-post-a-week-running-an-iron-blogger-challenge.html

html lazerwalker.com collected 2026-10-02 07:19:00 UTC 13,379 bytes, 260 lines download raw bytes

1<!DOCTYPE html>
2<html>
3
4  <head>
5  <meta charset="utf-8" />
6  <meta name="viewport" content="width=device-width initial-scale=1" />
7  <meta http-equiv="X-UA-Compatible" content="IE=edge" />
8
9  <title>
10    One Post A Week: Running an Iron Blogger Challenge
11  </title>
12  <meta name="description" content="Emilia is a Toronto-based game designer, conceptual artist, and software engineer.
13" />
14
15  <link
16    href="/atom.xml"
17    rel="alternate"
18    title="Em Lazer-Walker"
19    type="application/atom+xml"
20  />
21
22  <link rel="stylesheet" href="/css/main.css">
23  <link
24    rel="canonical"
25    href="https://blog.lazerwalker.com/2013/12/24/one-post-a-week-running-an-iron-blogger-challenge.html"
26  />
27  
28  <!-- Global site tag (gtag.js) - Google Analytics -->
vendor: 66 bytes, lines 28-29
28
29  <script async src="https://www.googletagmanager.com/gtag/js?id=
29G-STKNZZJ7SW
vendor: 14 bytes, lines 29-30
29"></script>
30  
30<script>
31    
vendor: 140 bytes, lines 31-35
31window.dataLayer = window.dataLayer || [];
32    function gtag(){dataLayer.push(arguments);}
33    gtag('js', new Date());
34
35    gtag('config', '
35G-STKNZZJ7SW
vendor: 6 bytes, lines 35-36
35');
36  
36</script>
36
37
38<meta content="Emilia Lazer-Walker" property="og:site_name">
39
40  <meta content="One Post A Week: Running an Iron Blogger Challenge" property="og:title">
41
42
43  <meta content="article" property="og:type">
44
45
46  <meta content="Emilia is a Toronto-based game designer, conceptual artist, and software engineer.
47" property="og:description">
48
49
50  <meta content="https://blog.lazerwalker.com/2013/12/24/one-post-a-week-running-an-iron-blogger-challenge.html" property="og:url">
51
52
53  <meta content="2013-12-24T15:53:00+00:00" property="article:published_time">
54  <meta content="https://blog.lazerwalker.com/about/" property="article:author">
55
56
57  <meta content="https://blog.lazerwalker.com/opengraph/d620d374e90989f2cea583d7ec7b08621b4b88b7c85e0f3d45d43ed61747f4b4.png" property="og:image">
58  <meta name="twitter:image" content="https://blog.lazerwalker.com/opengraph/d620d374e90989f2cea583d7ec7b08621b4b88b7c85e0f3d45d43ed61747f4b4.png" />
59  <meta name="twitter:card" content="summary_large_image" />
60
61
62
63  
64
65
66  
67
68
69<meta
70  name="twitter:site"
71  content="@lazerwalker"
72/>
73<meta
74  name="twitter:creator"
75  content="@"
76/>
77<meta name="twitter:title" content="One Post A Week: Running an Iron Blogger Challenge " />
78<meta
79  name="twitter:description"
80  content="  "
81/>
82
83 
84<meta
85  name="twitter:description"
86  content="Emilia is a Toronto-based game designer, conceptual artist, and software engineer.
87"
88/>
89
90</head>
91
92
93  <body>
94
95    <header class="site-header">
96
97  <div class="wrapper">
98
99    <a class="site-title" href="/">Emilia Lazer-Walker</a>
100
101    <nav class="site-nav">
102      <a href="#" class="menu-icon">
103        <svg viewBox="0 0 18 15">
104          <path fill="#424242" d="M18,1.484c0,0.82-0.665,1.484-1.484,1.484H1.484C0.665,2.969,0,2.304,0,1.484l0,0C0,0.665,0.665,0,1.484,0 h15.031C17.335,0,18,0.665,18,1.484L18,1.484z"/>
105          <path fill="#424242" d="M18,7.516C18,8.335,17.335,9,16.516,9H1.484C0.665,9,0,8.335,0,7.516l0,0c0-0.82,0.665-1.484,1.484-1.484 h15.031C17.335,6.031,18,6.696,18,7.516L18,7.516z"/>
106          <path fill="#424242" d="M18,13.516C18,14.335,17.335,15,16.516,15H1.484C0.665,15,0,14.335,0,13.516l0,0 c0-0.82,0.665-1.484,1.484-1.484h15.031C17.335,12.031,18,12.696,18,13.516L18,13.516z"/>
107        </svg>
108      </a>
109
110      <div class="trigger">
111        
112          
113          <a class="page-link" href="/about/">About</a>
114          
115        
116          
117        
118          
119        
120          
121        
122          
123        
124      </div>
125    </nav>
126
127  </div>
128
129</header>
130
131
132    <div class="page-content">
133      <div class="wrapper">
134        <div class="post">
135
136  <header class="post-header">
137    <h1 class="post-title">One Post A Week: Running an Iron Blogger Challenge</h1>
138    <p class="post-meta">Dec 24, 2013</p>
139  </header>
140
141  <article class="post-content">
142    <p>Astute readers of my blog will notice I’ve been blogging <em>much</em> more frequently as of late. What’s my secret? The past three months, I’ve been running a blogging challenge at <a href="http://hackerschool.com">Hacker School</a> called Iron Blogger, designed to help people blog more regularly.</p>
143
144<p>The concept of an Iron Blogger challenge isn’t original (I believe it originated at MIT, but don’t quote me on that), but I’m pretty happy with the tweaks, both large and small, we made to the formula.</p>
145
146<p>The rules were simple:</p>
147
148<ol>
149  <li>You have to publish one blog entry every week by the following Monday.</li>
150  <li>If you miss a week, you owe $5.</li>
151</ol>
152
153<p>A few other logistical rules were layered on top, but for the most part that’s all there was to it. I’ve seen many a blogger let their blog fall into disuse because they got out of the habit of writing on a regular or semi-regular basis; the most important thing for me was to make sure that everyone participating formed a strong habit of writing regularly.</p>
154
155<p>There were a lot of things that worked particularly well with how it was run:</p>
156
157<h3 id="physicality">Physicality</h3>
158<p>To indicate you wrote a blog post for a given week, you had to cross your name off a leaderboard by the following Monday. Our ‘leaderboard’ was nothing more than a piece of butcher paper posted on the wall with a table on it: each column was a week, and each row was a blogger.</p>
159
160<p>Since checking off was a manual process, rather than buiding some complex automated system, there was wiggle room: if you were a little bit late, that was okay, since the goal was ultimately to get everyone to write regularly, for some definition of “regularly”, rather than necessarily on a 
160super-rigid schedule.</p>
161
162<p>Having it be a physical board also gave it an unavoidable presence in our lives. It’s easy to ignore a web site; it’s harder to ignore a big piece of paper on the wall in your workplace.</p>
163
164<h3 id="flexibility">Flexibility</h3>
165<p>You had to write one blog post per week, but “blog post” could be defined however you wanted so long as it was public; we didn’t place any restrictions on length or subject matter.</p>
166
167<p>Ultimately, we figured that each person had their own reasons for why they wanted to blog more and what that meant to them. We set the system up to let each person figure out what they wanted to get out of it. Many people even took it upon themselves to blog daily.</p>
168
169<h3 id="social-pressure">Social Pressure</h3>
170<p>Every Monday, we gathered for a very brief (usually less than five minutes) check-in around 11am. The idea here was mostly to give people a social reminder to check off for the previous week, and talk about why they failed if they had.</p>
171
172<p>We started out without this meeting, but people routinely forgot to check their name off. Having five minutes to gather and look at the board ensured that people remembered to check off and felt social pressure that encouraged them to blog so they could check off.</p>
173
174<h3 id="feedback">Feedback</h3>
175<p>Hacker School has an internal chat room where every blog post published by a Hacker Schooler is announced by a bot (written by the marvelous <a href="http://sashalaundy.com">Sasha Laundy</a>). This gave us a great venue to both see what our peers were writing and comment on them. We found that having social validation of your peers reading and discussing your articles was a key piece of encouragement. Our Monday morning check-ins also helped with this, as participants would often mention articles they particularly enjoyed from the previous week.</p>
176
177<p>We initially discussed creating formal rules to ensure that people were giving feedback, but decided there was no reason to introduce more rigid requirements unless it became an issue. Fortunately, it didn’t. In fact, having so many great blog posts to read and comment on proved one of everybody’s favorite parts of the challenge.</p>
178
179<h3 id="low-impact">Low Impact</h3>
180<p>Ultimately, blogging isn’t the key focus of in most people’s lives. We tried to make this as low-commitment as possible: you were only being asked to blog once per week, and the fine was only $5 per week, which you didn’t need to pay until the end of the challenge.</p>
181
182<p>At the end, we didn’t even end up collecting the money. Just the idea of being fined $5 was enough to serve as encouragement when combined with all of the other feedback systems in place; actually having to pay up didn’t feel necessary. We initially planned to use the money to fund a celebratory pub night at the end of the challenge, but there were enough end-of-Hacker-School events that it wasn’t particularly missed.</p>
183
184<p>It’s worth noting that we didn’t make that decision until after the challenge ended, so when someone failed for a given week they did truly expect to be on the hook for five dollars.</p>
185
186<h3 id="the-results">The results</h3>
187<p>For a program like Hacker School that helps people become better programmers through self-directed learning, blogging is key. There’s no better way to understand something than by explaining it to someone else, and learning how to express yourself eloquently is important not just for being a programmer but for being a well-rounded human being.</p>
188
189<p>From what I’ve heard, both from former Hacker Schoolers and the Hacker School facilitators, this batch saw <em>significantly</em> higher blogging rates than any previous batch. The vast majority of Iron Blogger participants only missed two or three weeks out of twelve, and many achieved a 100% success rate. Many Hacker Schoolers, both members if this past batch and alumni of earlier batches, commented on how much they loved having so many blog posts by Hacker Schoolers to read and comment on.</p>
190
191<p>Blogging can be incredibly rewarding if you’re writing about something that matters to you, but sticking with it can be tough. We found that Iron Blogger struck just the right balance of extrinsic and intrinsic motivation to encourage writing without causing burn-out. If you’re struggling to maintain a blog, why not get some friends together and g
191ive it a try?</p>
192
193  </article>
194
195</div>
196
197      </div>
198    </div>
199
200    <footer class="site-footer">
201
202  <div class="wrapper">
203
204    <h2 class="footer-heading">Emilia Lazer-Walker</h2>
205
206    <div class="footer-col-wrapper">
207      <div class="footer-col  footer-col-1">
208        <ul class="contact-list">
209          <li>Emilia Lazer-Walker</li>
210          <li><a href="/cdn-cgi/l/email-protection#d2b0bebdb592beb3a8b7a0a5b3beb9b7a0fcb1bdbf"><span class="__cf_email__" data-cfemail="5c3e30333b1c303d26392e2b3d3037392e723f3331">[email&#160;protected]</span></a></li>
211        </ul>
212      </div>
213
214      <div class="footer-col  footer-col-2">
215        <ul class="social-media-list">
216          
217          <li>
218            <a href="https://github.com/lazerwalker">
219              <span class="icon  icon--github">
220                <svg viewBox="0 0 16 16">
221                  <path fill="#828282" d="M7.999,0.431c-4.285,0-7.76,3.474-7.76,7.761 c0,3.428,2.223,6.337,5.307,7.363c0.388,0.071,0.53-0.168,0.53-0.374c0-0.184-0.007-0.672-0.01-1.32 c-2.159,0.469-2.614-1.04-2.614-1.04c-0.353-0.896-0.862-1.135-0.862-1.135c-0.705-0.481,0.053-0.472,0.053-0.472 c0.779,0.055,1.189,0.8,1.189,0.8c0.692,1.186,1.816,0.843,2.258,0.645c0.071-0.502,0.271-0.843,0.493-1.037 C4.86,11.425,3.049,10.76,3.049,7.786c0-0.847,0.302-1.54,0.799-2.082C3.768,5.507,3.501,4.718,3.924,3.65 c0,0,0.652-0.209,2.134,0.796C6.677,4.273,7.34,4.187,8,4.184c0.659,0.003,1.323,0.089,1.943,0.261 c1.482-1.004,2.132-0.796,2.132-0.796c0.423,1.068,0.157,1.857,0.077,2.054c0.497,0.542,0.798,1.235,0.798,2.082 c0,2.981-1.814,3.637-3.543,3.829c0.279,0.24,0.527,0.713,0.527,1.437c0,1.037-0.01,1.874-0.01,2.129 c0,0.208,0.14,0.449,0.534,0.373c3.081-1.028,5.302-3.935,5.302-7.362C15.76,3.906,12.285,0.431,7.999,0.431z"/>
222                </svg>
223              </span>
224
225              <span class="username">lazerwalker</span>
226            </a>
227          </li>
228          
229
230          
231          <li>
232            <a href="https://twitter.com/lazerwalker">
233              <span class="icon  icon--twitter">
234                <svg viewBox="0 0 16 16">
235                  <path fill="#828282" d="M15.969,3.058c-0.586,0.26-1.217,0.436-1.878,0.515c0.675-0.405,1.194-1.045,1.438-1.809
236                  c-0.632,0.375-1.332,0.647-2.076,0.793c-0.596-0.636-1.446-1.033-2.387-1.033c-1.806,0-3.27,1.464-3.27,3.27 c0,0.256,0.029,0.506,0.085,0.745C5.163,5.404,2.753,4.102,1.14,2.124C0.859,2.607,0.698,3.168,0.698,3.767 c0,1.134,0.577,2.135,1.455,2.722C1.616,6.472,1.112,6.325,0.671,6.08c0,0.014,0,0.027,0,0.041c0,1.584,1.127,2.906,2.623,3.206 C3.02,9.402,2.731,9.442,2.433,9.442c-0.211,0-0.416-0.021-0.615-0.059c0.416,1.299,1.624,2.245,3.055,2.271 c-1.119,0.877-2.529,1.4-4.061,1.4c-0.264,0-0.524-0.015-0.78-0.046c1.447,0.928,3.166,1.469,5.013,1.469 c6.015,0,9.304-4.983,9.304-9.304c0-0.142-0.003-0.283-0.009-0.423C14.976,4.29,15.531,3.714,15.969,3.058z"/>
237                </svg>
238              </span>
239
240              <span class="username">lazerwalker</span>
241            </a>
242          </li>
243          
244        </ul>
245      </div>
246
247      <div class="footer-col  footer-col-3">
248        <p class="text">Emilia is a Toronto-based game designer, conceptual artist, and software engineer.
249</p>
250      </div>
251    </div>
252
253  </div>
254
255</footer>
vendor: 113 bytes, lines 255-258
255
256
257
258  <script data-cfasync="false" src="/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js"></script>
258</body>
259
260</html>

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.