Wk07/08: Learning Journal Summary
Look back at the HW1
After looking back at the assignment of Markov seven weeks later, it's been clear that I have been building strings incorrectly and should have been utilizing the String Builder class. Over the course I developed a better understanding of string immutability in java and how it may affect the memory being used. I have been spoiled by appending strings in C++ and not having to worry too much about memory and excessive object creation. Another way I could have approached Markov was utilizing TODOs more often. After working through project 2 with my group, I have noticed I lose myself within my code and having to reread and test the things previously done before. I had done the same thing in the Markov assignment where I would work on numerous tasks at the start then jump to something else in the prompt without noting where I left off, causing myself to be confused in what I was trying to accomplish. So I definitely need to incorporate TODOs to keep track of my tasks. Another way I would approach the assignment is by using white-box testing to test all the logical structure of the code. For example if the words are processed correctly in the getWords() method, checking to see if the hash map properly stores the key and associated list of words, and loop conditions. I did notice though that I have been using a close interpretation of the top-down design so it was nice to get more information and insight on that in the Week 3 slides.
Highlight at least two victories.
One victory I am proud of learning after the seven weeks is the singleton pattern design especially in Android Studio. For example, within my team's project we need to utilize shared preferences as a way to save primitive data types and pass it along to other activities. In the project I created a singleton pattern class that manages shared preferences. If I were to create an object in all these activities I would need to instantiate a new object numerous times. In this case creating a singleton will allow me to just create one instance of my class without wasting resources and more lines of code.
Another victory I am proud of is essentially learning how to create an application in Android Studio because it gave me a clear understanding of how mobile applications are developed such as the use of XML for the layouts, local databases like ROOM to store data with persistence, button functionalities, factory design patterns, and even getting a better idea of how github functions within group collaborations. Project 2 definitely helped me understand the intricacies of the ROOM database, for instance learning how to create an entity, the database class, and working with annotations and interface classes to develop a DAO to query the data. GymLog-HW04 helped me understand everything I needed to know about android development.
After looking back at the assignment of Markov seven weeks later, it's been clear that I have been building strings incorrectly and should have been utilizing the String Builder class. Over the course I developed a better understanding of string immutability in java and how it may affect the memory being used. I have been spoiled by appending strings in C++ and not having to worry too much about memory and excessive object creation. Another way I could have approached Markov was utilizing TODOs more often. After working through project 2 with my group, I have noticed I lose myself within my code and having to reread and test the things previously done before. I had done the same thing in the Markov assignment where I would work on numerous tasks at the start then jump to something else in the prompt without noting where I left off, causing myself to be confused in what I was trying to accomplish. So I definitely need to incorporate TODOs to keep track of my tasks. Another way I would approach the assignment is by using white-box testing to test all the logical structure of the code. For example if the words are processed correctly in the getWords() method, checking to see if the hash map properly stores the key and associated list of words, and loop conditions. I did notice though that I have been using a close interpretation of the top-down design so it was nice to get more information and insight on that in the Week 3 slides.
Highlight at least two victories.
One victory I am proud of learning after the seven weeks is the singleton pattern design especially in Android Studio. For example, within my team's project we need to utilize shared preferences as a way to save primitive data types and pass it along to other activities. In the project I created a singleton pattern class that manages shared preferences. If I were to create an object in all these activities I would need to instantiate a new object numerous times. In this case creating a singleton will allow me to just create one instance of my class without wasting resources and more lines of code.
Another victory I am proud of is essentially learning how to create an application in Android Studio because it gave me a clear understanding of how mobile applications are developed such as the use of XML for the layouts, local databases like ROOM to store data with persistence, button functionalities, factory design patterns, and even getting a better idea of how github functions within group collaborations. Project 2 definitely helped me understand the intricacies of the ROOM database, for instance learning how to create an entity, the database class, and working with annotations and interface classes to develop a DAO to query the data. GymLog-HW04 helped me understand everything I needed to know about android development.
Comments
Post a Comment