Amy J. Ko

> I like how the textbook mentioned cowboy coding, which is the exact opposite of coding according to spec. I want to know more about its advantages. Is it ever...

> From the article, I understood the importance of writing a formal specification or unit tests could help ensure the functions are performing correctly. However, how could we ensure the...

> Something I felt that the chapter could do better in is giving more evidence for how writing formal specifications has a downside. I felt that this paragraph did give...

There's some possibility that it would be easier to explain the need for architecture by having learners read comprehension first, since it surfaces the problems that architecture solves.

> In this chapter, we are taught the importance of architecting code. This might not be required for small organizations, but this is an integral part of large companies.  This...

> In this chapter, the author discussed approaches to organizing code and the idea of software architecture and its principals; information hiding through encapsulation, functions, classes, and scope. Though beyond...

> I thought the paragraph about architectural mismatch had a lot of technical information and required me to reread it a few times.  I think a real world example of...

> One thing that I am wondering after reading the chapter, how are design specs different from an architecture design? Are they the same? I think it would be helpful...

> When defining requirements at the start of a project, how much should you actually stick to it? For example, if you plan requirements at the start but then new...

How to avoid bias > I think one question I would like the chapter to answer is the idea of ethics in design and ways we can free designs from...