Knee Deep in the Passenger Seat: Is It Casual Now if We're Having a Quiz Next Meet?
"2 weeks and your mom invites me to her house in long beach, is it casual now?" Just like what Chappell said, is it casual now that we're 4 weeks in or are we getting for real right now? Although I would like to think that it is still casual, the hard truth is that it's not. Over the past few weeks, the topics we've discussed have slowly increased until the load was nearly enough for us to have our first quiz the following week. At least that's what we thought when we first entered the room, however it soon changed when our professor told us that we were going to have our quiz that day, a palpable sense of panic and horror was felt by everyone at that very moment, including myself. Although I was slightly prepared because I did a light review on the first topic, it was still not enough to help me pass and salvage myself from the dreadful test. However the feeling was soon dissipated when our professor said that we were just going to discuss the second topic, everybody breathed a sigh of relief the moment our professor said that.
Attached here are the shocked faces of Ms. Gwen and Ms. April ππ
ππππππππππππππππππππππππππππππππ
As usual, before the class started we had our cutesy little game, the REBUS PUZZLE!!. And do you want to know what makes this different from the past games? It's because this time, I finally got a correct answer! YAYY!!! The answer was supposedly Jack-in-box but I said Jack-in-the-box, but the professor still considered it as correct, so it's still a win for me. (Β΄β½`Κβ‘Ζͺ)
ππππππππππππππππππππππππππππππππ
Everybody was on a high after that mini-game and it was finally time to start the discussion...
The discussion began by defining the software design, where its critical role in the software lifecycle was emphasized. The purpose of software design was also highlighted, which was to create a blueprint for building software that meets specified requirements while ensuring maintainability, scalability, and usability. Then the core design principles were discussed such as problem partitioning, abstraction, modularity, and top down & bottom up strategy. Then the system implementation and its deployment were covered next. It was highlighted that we should follow the design blueprint closely so that we can ensure that the software meets its requirements. And that we should also note the importance of rigorous testing at every stage to ensure that the software is free of defects. And before deploying the system to the production environment, there should be strategies discussed first and also consider the rollbacks, monitoring, and maintenance of the system. And finally, the importance of code refactoring, it is the process of restructuring the existing code in order to improve the readability and also reduce the complexity without having to change the external behavior. Overall, the topic was discussed in great detail with numerous examples to further help us understand the topic.
ππππππππππππππππππππππππππππππππ
As expected, after the discussion we had another activity where we had to design a system based on the problem given to us. We were still grouped into 4,and also by pure coincidence, the problem assigned to us was similar to the current project that we were doing, to design an online bookstore where users can browse books, add them to a shopping cart, and make purchases, and what's even funnier is that I was in the same group with 2 of the other members from the project, so color us surprised! In doing the task, I was assigned to create the initial design diagram for the system. Honestly, with the amount of time given and the resources available to use, I think we did well with the interface of the system. Although there were critiques from the other group that COMPLETELY left us speechless, I thought that we still did a great job with our output. And of course, what's the best way to end the class with an announcement for an upcoming quiz the following week! (β¬β¬οΉβ¬β¬) May we survive the quiz next meet... so not looking forward to it ΰ²₯_ΰ²₯ So in conclusion, no it is NOT casual, WE ARE LOCKED IN!!
ππππππππππππππππππππππππππππππππ
And before we end the week, we did a follow-up consultation on the pre-requisites of our manuscript, the hard-work and perseverance of the team bore fruit as it led to us being in the lead to finish the pre-requisites first. However, our Activity 1 was completely wrong, I guess we got lost in translation. Ζͺ(Λβ£Λ)Κ In the end, the consultation finished rather quickly, with minor adjustments here and there, and it finally ended in a positive note. ππ
