From b1c0bd0de337da3b0f0aecae751792deb0ef60c5 Mon Sep 17 00:00:00 2001 From: "Amy J. Ko" Date: Tue, 24 Sep 2019 14:16:21 -0700 Subject: [PATCH] Updated name. --- comprehension.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/comprehension.html b/comprehension.html index 7cb4647..9504c7c 100644 --- a/comprehension.html +++ b/comprehension.html @@ -25,7 +25,7 @@ Credit: public domain

Program Comprehension

-
Andrew J. Ko
+
Amy J. Ko

Despite all of the activities that we've talked about so far—communicating, coordinating, planning, designing, architecting—really, most of a software engineers time is spent reading code (Maalej et al. 2014). Sometimes this is their own code, which makes this reading easier. Most of the time, it is someone else's code, whether it's a teammate's, or part of a library or API you're using. We call this reading program comprehension.