CST370 Module 2 Weekly Engagement

CST370 Module 2 Weekly Engagement 


This week we dove deeper into algorithm efficiency, and how we can approach analyzing it using notation such as Big O, Big Theta, and Big Omega. I got more practice in finding the time complexity of an algorithm through pseudocode and recurrence relations for algorithms that included brute force methods and recursion. I also worked through algorithm puzzles such as finding the angle of the clock hands, and the racing car puzzle to provide better context to the theories rather than pure memorization. The quiz helped solidify my knowledge, while also testing it, allowing me to understand what I need to work on for future.

Comments

Post a Comment

Popular posts from this blog

CST363 Week 3

What is an SQL view.  How is it similar to a table? In what ways is it different (think about primary keys,  insert, update, delete operations) ? An SQL view is a stored query, thereby making it a virtual table. Since the view does not hold data, it conducts the search of the data in one or more tables while being asked for. A view shares very similar characteristics as those of a table for example you can run SELECT statements against the view as if the view were a table, and it will display the result set in tabular format. In general, views do not have primary keys or indexes, and they cannot always be used as the targets for direct updates. Meanwhile, a few views are updateable in case they are based on a single table without complex joins and so forth whereas the majority are read-only. Very useful aspects of views are the simplification of queries, it improves readability, and restricting a user's access to either some of the columns or some of the rows without giving th...
Read more

Wk03 Learning Journal: HW 1 Code Review

Whose code did you review ? I reviewed the HW01 code from two classmates: Faith Thomas and Luis Valadez. Faith Thomas’ Code : Faith’s code is functionally well-organized and readable. Most variable names are meaningful and self-explanatory. For instance, names like guessedWords, remainingGuesses, and numberOfHints clearly communicate their purpose. There is a good use of comments in some places, though many methods are still marked with TODOs for Javadoc comments. Some logic could be improved for clarity, such as simplifying the chooseWord method or extracting logic into helper methods. I also noted that debug System.out.println statements were scattered throughout and should ideally be removed or toggled with a debug flag. Unused import statements weren’t an issue, but formatting could be a bit more consistent in terms of spacing and indentation. All unit tests passed, and it does not appear that the tests were modified, which is good. Luis Valadez’s Code : Luis’s code was well-struct...
Read more

CST363 Week 8 Final Learning Journal Entry

Briefly summarize the what you consider to be the three (3) most important things you learned in this course. One of the most important things I have learned in this course was how databases actually work behind the scenes, from how data is structured with tables and relationships to how SQL brings it all together. I also learned how normalization improves efficiency and prevents redundancy, which made database design make a lot more sense. I learned how to split up work accordingly as a group efficiently and how to trouble shoot databases, as well as help my group trouble shoot. I learned how SQL and Java can be intertwined as well, which was interesting to learn about and will be useful in my career later! Lastly, I gained a stronger understanding of how to use joins and queries to pull meaningful information from data, which I know will be really valuable for future software projects.
Read more