Miroirs/cooperative-software-development
1
0
Fork 0
mirror of https://github.com/amyjko/cooperative-software-development synced 2024-12-25 21:58:15 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

More consistent naming of chapters.

Browse source
This commit is contained in:
Andy Ko 2019-04-09 12:29:31 -07:00
parent 7b386f5af7
commit 3298d9405c
4 changed files with 7 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
history.html
View file

@ -15,7 +15,7 @@
<link rel="stylesheet" href="style.css" />
<title>The history of software engineering</title>
<title>History</title>
</head>
<body>
@ -24,7 +24,7 @@
<img src="images/Hamilton.jpg" class="img-responsive" />
<small>Margaret Hamilton working on the Apollo flight software. <a href="By NASA - http://www.nasa.gov/50th/50th_magazine/scientists.html, Public Domain, https://commons.wikimedia.org/w/index.php?curid=37255847">Credit</a>.</small>
<h1>A brief history of software engineering</h1>
<h1>History</h1>
<div class="lead">Andrew J. Ko</div>
<p>Computers haven't been around for long. If you read one of the many histories of computing and information, such as James Gleick's <a href="https://www.amazon.com/Information-History-Theory-Flood/dp/1400096235">The Information</a>, or <a href="https://www.amazon.com/Tool-Partner-Evolution-Human-Computer-Interaction/dp/1627059636">Jonathan Grudin's History of HCI</a>, you'll learn that before <em>digital</em> computers, computers were people, calculating things manually, as portrayed in the film <a href="https://en.wikipedia.org/wiki/Hidden_Figures">Hidden Figures</a> (watch it if you haven't!). And that <em>after</em> digital computers, programming wasn't something that many people did. It was reserved for whoever had access to the mainframe and they wrote their programs on punchcards like the one above. Computing was in no way a ubiquitous, democratized activity&mdash;it was reserved for the few that could afford and maintain a room-sized machine.</p>

4
index.html
View file

@ -36,10 +36,10 @@
<p>I hope you enjoy! If you see something missing or wrong, <a href="https://github.com/andyjko/cooperative-software-development">Submit an issue or a pull request on GitHub</a>.</p>
</td>
<td>Chapter 1. <a href="history.html">History of software engineering</a></td>
<td>Chapter 1. <a href="history.html">History</a></td>
</tr>
<tr>
<td>Chapter 2. <a href="organizations.html">Software engineering organizations</a></td>
<td>Chapter 2. <a href="organizations.html">Organizations</a></td>
</tr>
<tr>
<td>Chapter 3. <a href="communication.html">Communication</a></td>

4
organizations.html
View file

@ -15,7 +15,7 @@
<link rel="stylesheet" href="style.css" />
<title>Software engineering organizations</title>
<title>Organizations</title>
</head>
<body>
@ -24,7 +24,7 @@
<img src="images/team.jpg" class="img-responsive" />
<small>A software engineering team hard at work. Credit: Andrew J. Ko</small>
<h1>Software organizations</h1>
<h1>Organizations</h1>
<div class="lead">Andrew J. Ko</div>
<p>The photo above is a candid shot of some of the software engineers of <a href="http://answerdash.com">AnswerDash</a>, a company I co-founded in 2012. There are a few things to notice. First, you see one of the employees explaining something, while others are diligently working off to the side. It's not a huge team; just a few engineers, plus several employees in other parts of the organization in another room. This, as simple as it looks, is pretty much what all software engineering work looks like. Some organizations have one of these teams; others have thousands.</p>

3
quality.html
View file

@ -15,8 +15,7 @@
<link rel="stylesheet" href="style.css" />
<!-- UPDATE -->
<title>Software Quality</title>
<title>Quality</title>
</head>
<body>