Week 8: CST438

 I gained many insights into software engineering through this course. I think the details about Agile approach to project management were really helpful, particularly for someone about to join the industry. I've seen parts of Agile used in past team projects but I think I like how the team project in this class gave us a more complete view of how Agile would be used.

I enjoyed learning about the Waterfall approach. The main reason is that it's not something we're exposed to much as students. Most classes tend to utilize portions of the Agile approach instead. But it was nice to be exposed to both approaches in this class.

The readings on Google's approach to testing were pretty informative. In other courses we tend to skip over testing or only learn about it from a technical (coding) aspect. In this class we got to learn in depth about the reasoning behind different types of tests and how a large company like Google handles their own testing.

I liked practicing with React again during our team project. It's a very useful industry skill to have and very helpful for building frontends quickly.

I learned how to use Spring framework to build a Java backend. Even though many languages have backend frameworks that work similarly, I'm glad I was able to play with the Java version.

Comments

Post a Comment

Popular posts from this blog

Journal Week 4

 This week we learned about security, particularly about encryption and how keys are used in networks to protect data. It's interesting to learn about encryption techniques that are now obsolete due to improvements in computing processors. I wonder how long it would take for currently recommended encryption methods to become obsolete. Also, I found the examples in the lectures helpful. Thinking of the data exchange across a network as a conversation between two people (and possibly three if we include an eavesdropper) helps me understand the flow of data and vulnerabilities that can arise.
Read more

Week 5: CST438 Journal

 This week, we learned about the plan and document process for engineering projects. It's based on gathering software requirements and documenting them, as well as documenting the progress that is made in the design and implementation of software and its cost. We went over the some of the differences in this approach when compared to the agile method. We also learned about UML diagrams, with special attention to three types of these (use case, sequence, and class). I've been exposed to class UML diagrams before, but the other two behavioral type of diagrams were somewhat new to me.
Read more

This week

 This week we continued to learn about HTTP, plus DNS and email protocols. I find the the material very interesting based on the lecture videos, but I still need to finish catching up on the reading. I think I need to review some of the earlier material on calculations and measuring response and request times, since quiz questions in later chapters seem to require this. I didn't have the technical issues I had last week. Although I do wish the labs could be turned in as assignments rather than quizzes (more flexibility for asking questions and dealing with technical vm issues).
Read more