Software Engineering discussion

This chapter is kind of a wrap up of much of the advice in previous chapters, so I don't have much to add, other than to highlight the important, overarching, observation the author makes that much of software engineering is all about using abstraction to tame complexity.

I like the concept of iteration in software development. I wish it was called as iteration in my work environment instead of bug fixing or similar. Iteration sounds more like a process where engineer or a team needs to go back to analyzing requirements, design, construction, and find the right solution to the problem. Bug fixing on the other hand sounds more like an activity, where engineer can assume that the software design and code is correct except those “few” bugs found during test. Because people think about this process as bug fixing, many solutions become hacks, and not real solutions to the software issues.

I also liked the discussions about Eclecticism and Experimentation.

I agree that this chapter felt like a review or summary of several previous topics. That was fine with me. I'm pretty sure my learning process is fairly iterative, so reviewing key topics works for me.