Amy J. Ko

> There are two aspects that I'd like to mention about the article. The first is a really small nuance, but it was during the section about barriers that programmers...

> I think the second paragraph was written with the assumption people know what IDEs are.  I personally didn’t.  A quick sentence explaining what the Eclipse IDE does would be...

> The article did a good job of explaining why communication is so important to software engineering, however I felt that it didn't explain enough about how to have good...

> I think the article as a whole was informative, but my one critique was the controversial use of personal bias. The article presents itself as scientific and provides a...

> I think the paragraph about the example ethnography that was conducted by Perlow could be explained better.  I had to reread that paragraph multiple times to understand what was...

This depends on a Peruse feature being built, but it'll be done soon. It'll help students identify papers to read.

> This chapter was a cool insight at the larger picture of an organization. I wish it went into more detail about how risk can be measured and seen quantitively....

> It may not be the right place for it, but I would’ve liked to know more about how an organization scales over time. Including this aspect of an organization...

> I think this chapter is already organized well with very understandable words. However, I think it would be better if the author could have input a short explanation at...

> In the bullet points for the important implications of what it means to be a software engineer, I see how the second bullet point could touch more on the...