From c2ae64d4a89d6923deb577b2f50d9059cd63cbcc Mon Sep 17 00:00:00 2001
From: "Amy J. Ko" <ajko@uw.edu>
Date: Tue, 24 Sep 2019 14:15:46 -0700
Subject: [PATCH] Updated name.

---
 architecture.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/architecture.html b/architecture.html
index 9b64e61..dbe895a 100644
--- a/architecture.html
+++ b/architecture.html
@@ -25,7 +25,7 @@
 		<small>Credit: Creative Commons 0</small>
 		
 		<h1>Architecture</h1>
-		<div class="lead">Andrew J. Ko</div>
+		<div class="lead">Amy J. Ko</div>
 
 		<p>Once you have a sense of what your design must do (in the form of requirements or other less formal specifications), the next big problem is one of organization. How will you order all of the different data, algorithms, and control implied by your requirements? With a small program of a few hundred lines, you can get away without much organization, but as programs scale, they quickly become impossible to manage alone, let alone with multiple developers. Much of this challenge occurs because requirements <em>change</em>, and every time they do, code has to change to accommodate. The more code there is and the more entangled it is, the harder it is to change and more likely you are to break things.</p>