-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathindex.html
More file actions
111 lines (84 loc) · 5.68 KB
/
index.html
File metadata and controls
111 lines (84 loc) · 5.68 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
<!DOCTYPE html>
<html>
<head>
<meta charset='utf-8'>
<meta http-equiv="X-UA-Compatible" content="chrome=1">
<link rel="stylesheet" type="text/css" href="stylesheets/stylesheet.css" media="screen" />
<link rel="stylesheet" type="text/css" href="stylesheets/pygment_trac.css" media="screen" />
<link rel="stylesheet" type="text/css" href="stylesheets/print.css" media="print" />
<title>12days of coding</title>
</head>
<body>
<header>
<div class="container">
<h1>12days.github.io</h1>
<h2>A 12-day experiment in building and shipping code</h2>
<section id="downloads">
<a href="https://github.com/12days" class="btn btn-github"><span class="icon"></span>View on GitHub</a>
<a href="./projects.html" class="btn btn-github"><span class="icon"></span>List of Projects</a>
<a href="./blogs.html" class="btn btn-github"><span class="icon"></span>Blog/Videos</a>
</section>
</div>
</header>
<div class="container">
<section id="main_content">
<h3>
<a name="what-is-12-days-of-coding" class="anchor" href="#what-is-12-days-of-coding"><span class="octicon octicon-link"></span></a>What is 12 days of coding?</h3>
<p>It is 12 projects in 12 days. Each project would be started, finished, and shipped in a given October day.</p>
<p>It is an experiment in coding and learning. It is an experiment in teaming and creating a culture of doing.</p>
<p>I will be blogging about our experience in my <a target="_new" href="http://findinbay.blogspot.com/">findinbay blog</a>.</p>
<h3>
<a name="why-12-days-of-coding" class="anchor" href="#why-12-days-of-coding"><span class="octicon octicon-link"></span></a>Why 12 days of coding?</h3>
<p><a target="_new" href="https://github.com/JoshuaJWilborn">Josh</a> and I both had time to kill. But, not too much. We wanted to do something fun, build up our coding skills, and our portfolios. </p>
<p>And we wanted to learn: learn to be better coders, learn to be better builders, learn more about our interests. And that was it. We didn't want to get ahead of ourselves.</p>
<p>We thought a good way to do this would be to create a set of constraints around our efforts. Constraints are key to discipline and focus.</p>
<ul>
<li>One of the first choices we made was to keep it short and simple (KISS principle). </li>
<li>We are devoting around 2-weeks to this experiment. </li>
<li>We are keeping this to 2-person engineering team. </li>
<li>We are doing projects we can reasonably finish in a day.</li>
</ul><h3>
<a name="overview-our-values-and-methodology" class="anchor" href="#overview-our-values-and-methodology"><span class="octicon octicon-link"></span></a>Overview: our values and methodology</h3>
<p>To be effective, you have to have a process. The hero is neither the knowledge nor the superstar coder. The hero is the process. We want to learn to be better at a successful-building-process by doing.</p>
<p><strong>Values</strong></p>
<p>We'd brainstorm a one sentence idea, then share them with each other after 5-minutes. We did a few of these 5-minute sprints. We then scored them using four criteria. The criteria are, in essence, team values:</p>
<ul>
<li>Interesting - are they interesting to us?</li>
<li>Simplicity - are they simple enough (for us) to tackle?</li>
<li>Uniqueness - are these ideas unique to us and to others?</li>
<li>Utility - would we use them?</li>
</ul><p>Yes, they are arbitrary. Yes, they are imperfect set of categories. We can live with that. Can you?</p>
<p><strong>Methodology</strong></p>
<p>What about the process? No ground-breaking principles here:</p>
<ol>
<li>Build on strength - for speed, use familiar technology (for us, mostly Ruby on Rails)</li>
<li>Prepare - for new technologies (e.g. a Node app), do some advance reading/tinkering</li>
<li>DRY - Do not repeat yourself - look for gems wherever possible</li>
<li>Best practices - we will use TDD; red-green-refactor; frequent commits</li>
<li>Pragmatism - product should work; function over form (i.e. it doesn’t need to be pretty)</li>
<li>Modularity - we will try to build templates we can reuse on subsequent days</li>
</ol><h3>
<a name="how-you-can-get-involved" class="anchor" href="#how-you-can-get-involved"><span class="octicon octicon-link"></span></a>How you can get involved</h3>
<p>Do you like what you're reading? Try your own mini-rapid-project(s). Do it solo. Do it as a pair. What would you get out of a process like this? How would you structure your efforts? Write about it and send us a link to your post or project. </p>
<ul>
<li>Josh Wilborn - <a target="_new" href="mailto:joshua.j.wilborn@gmail.com">joshua.j.wilborn@gmail.com</a>
</li>
<li>David Kim - <a target="_new" href="mailto:daviddarden11@gmail.com">daviddarden11@gmail.com</a>
</li>
</ul><p><a target="_new" href="github.com/mockdeep/">Robert Fletcher</a>, whose open-source project <a target="_new" href="github.com/mockdeep/better">Better Means</a>, is an inspiration, and is our coach.</p>
<p>Thanks for reading, and please let us know if we can help you in some way.</p>
<p>David Kim, <a target="_new" href="https://github.com/dklounge">dklounge</a></p>
</section>
</div>
<script type="text/javascript">
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
</script>
<script type="text/javascript">
try {
var pageTracker = _gat._getTracker("UA-44430419-1");
pageTracker._trackPageview();
} catch(err) {}
</script>
</body>
</html>