From d51fafdbe3cd472af6ee1353f71432862d204bac Mon Sep 17 00:00:00 2001 From: Andy Ko Date: Tue, 9 Apr 2019 12:30:29 -0700 Subject: [PATCH] Removed "functional" from title. --- index.html | 2 +- specifications.html | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/index.html b/index.html index 7baa813..a6e4e44 100644 --- a/index.html +++ b/index.html @@ -57,7 +57,7 @@ Chapter 7. Architecture - Chapter 8. Functional specifications + Chapter 8. Specifications Chapter 9. Process diff --git a/specifications.html b/specifications.html index e5da3c7..61a4671 100644 --- a/specifications.html +++ b/specifications.html @@ -15,7 +15,7 @@ - Functional Specifications + Specifications @@ -24,7 +24,7 @@ Credit: public domain -

Functional Specifications

+

Specifications

Andrew J. Ko

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 cowboy coding 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.