mirror of
https://github.com/amyjko/cooperative-software-development
synced 2024-12-27 21:58:55 +01:00
Updated name.
This commit is contained in:
parent
9c3ee128b9
commit
15f634a369
1 changed files with 1 additions and 1 deletions
|
@ -25,7 +25,7 @@
|
||||||
<small>Credit: public domain</small>
|
<small>Credit: public domain</small>
|
||||||
|
|
||||||
<h1>Specifications</h1>
|
<h1>Specifications</h1>
|
||||||
<div class="lead">Andrew J. Ko</div>
|
<div class="lead">Amy J. Ko</div>
|
||||||
|
|
||||||
<p>When you make something with code, you're probably used to figuring out a design as you go. You write a function, you choose some arguments, and if you don't like what you see, perhaps you add a new argument to that function and test again. This <a href="https://en.wikipedia.org/wiki/Cowboy_coding" target="_blank">cowboy coding</a> as some people like to call it can be great fun! It allows systems to emerge more organically, as you iteratively see your front-end design emerge, the design of your implementation emerges too, co-evolving with how you're feeling about the final product.</p>
|
<p>When you make something with code, you're probably used to figuring out a design as you go. You write a function, you choose some arguments, and if you don't like what you see, perhaps you add a new argument to that function and test again. This <a href="https://en.wikipedia.org/wiki/Cowboy_coding" target="_blank">cowboy coding</a> as some people like to call it can be great fun! It allows systems to emerge more organically, as you iteratively see your front-end design emerge, the design of your implementation emerges too, co-evolving with how you're feeling about the final product.</p>
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue