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

Updated name.

Browse source
This commit is contained in:
Amy J. Ko 2019-09-24 14:17:55 -07:00 committed by GitHub
parent 696c5c42e4
commit 6ef05b5ed5
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
organizations.html
View file

@ -22,10 +22,10 @@
<p><a href="index.html">Back to table of contents</a></p>
<img src="images/team.jpg" class="img-responsive" />
<small>A software engineering team hard at work. Credit: Andrew J. Ko</small>
<small>A software engineering team hard at work. Credit: Amy J. Ko</small>
<h1>Organizations</h1>
<div class="lead">Andrew J. Ko</div>
<div class="lead">Amy 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>
@ -85,11 +85,11 @@
<p id="kalliamvakou">Kalliamvakou, E., Bird, C., Zimmermann, T., Begel, A., DeLine, R., German, D. M. <a href="https://doi.org/10.1109/TSE.2017.2768368" target="_blank">What Makes a Great Manager of Software Engineers?</a> To appear in IEEE Transactions on Software Engineering. IEEE.</p>
<p>Ko, Andrew J. (2017). <a href="https://faculty.washington.edu/ajko/papers/Ko2017AnswerDashReflection.pdf" target="_blank">A Three-Year Participant Observation of Software Startup Software Evolution</a>. International Conference on Software Engineering, Software Engineering in Practice, to appear.</p>
<p>Ko, Amy J. (2017). <a href="https://faculty.washington.edu/ajko/papers/Ko2017AnswerDashReflection.pdf" target="_blank">A Three-Year Participant Observation of Software Startup Software Evolution</a>. International Conference on Software Engineering, Software Engineering in Practice, to appear.</p>
<p id="lee">Lee, G. K., & Cole, R. E. (2003). <a href="http://pubsonline.informs.org/doi/abs/10.1287/orsc.14.6.633.24866" target="_blank">From a firm-based to a community-based model of knowledge creation: The case of the Linux kernel development</a>. Organization science, 14(6), 633-649.</p>
<p id="li">Li, Paul, Ko, Andrew J., and Begel, Andrew (2017). <a href ="https://doi.org/10.1109/CHASE.2017.3">Collaborating with Software Engineers: Perspectives from Non-Software Experts.</a> In the Proceedings of the 10th International Workshop on Cooperative and Human Aspects of Software Engineering.</p>
<p id="li">Li, Paul, Ko, Amy J., and Begel, Andrew (2017). <a href ="https://doi.org/10.1109/CHASE.2017.3">Collaborating with Software Engineers: Perspectives from Non-Software Experts.</a> In the Proceedings of the 10th International Workshop on Cooperative and Human Aspects of Software Engineering.</p>
<p id="osterwalder">A. Osterwalder, Y. Pigneur, G. Bernarda, & A. Smith (2015). <a href="https://books.google.com/books?id=jgu5BAAAQBAJ" target="_blank">Value proposition design: how to create products and services customers want</a>. John Wiley & Sons.</p>