CST 338 Week 4

During this week I have worked with Jerrick Wallace, Matthew Ross and Dakota Fouch. My strategy for most of this assignment or at least for 'Book', 'Shelf', and 'Reader' classes is starting by looking at the UML diagram to figure out all the fields each class needed. After listing these, I use auto-generation to create the setters and getters. Then, I check the prompt to make sure the constructors were correct and tweak them as needed. Next, I auto-generate the 'hashCode' and 'equals' methods, making sure they matched the requirements. The 'toString' methods are usually a bit different, so I write it manually to get the formatting right. Once all the basic methods are set up, I move on to the logic methods, following the prompt closely and writing them out. Finally, I use the test files to make sure everything works as expected.

My teammates strategy is also for the most part reading the prompt and then just starting to write code and very close to the way I would write the code as well. 

If there is something that I would want to change in my Strategy, it would be writing the test files first then write the code. Usually that's how I write my code at my job. 

For the most part my code does meet the Google Java Style Guide. However, I think I can make some improvements. 

Comments

Post a Comment

Popular posts from this blog

CST 462S - Learning Journal (service learning)

Working with the American Technology Initiative was really fun, informative, and rewarding. I spent most of my time on their volunteer portal, a prototype level app that makes volunteer reporting way easier. The codebase was almost release ready, so I got to dive in, explore its parts, and see how a familiar tech stack scales up for real users. Since the core features were already in place, I focused on user testing: hunting bugs, suggesting little tweaks, and polishing usability. Even though these were small changes, it felt great knowing they’d make a real difference for volunteers. If there’s one thing I’d change, it’d be the length of the service learning project. 25 hours (over eight weeks) barely gives you time to get comfortable with a new codebase. From my experience, you need at least forty hours just to learn the ropes and even more to add substantial features. I’d love to see future SL programs run at least 120 hours (about six months) so you can really dig in. The highlight...
Read more

CST 300 Week 7

Part 1: Arranging our ultimate research video project was a great experience for us as a team. The entire process was smooth, we all agreed with the concepts that were brought forth and maintained a steady vision during the planning phase. We collaborated mostly during our weekly zoom meetings. With different operating systems, we had to use various tools such as iMovie, powerpoint and Final Cut Pro (which is what I used). Looking back on it now though, what I would suggest is having timelines that allow us to finish the project at least a week early so that we can then look at it and try to improve it. However, our team has a strong bond so sharing each other’s ideas into our projects was easy for us. Part 2: I viewed Lera Boroditsky’s TED Talk “How Language Shapes the Way We Think.” The speaker discusses how much influence languages have on our thoughts and perceptions. She gives examples of different ways in which languages can shape reality, affecting even such basic phenomena as s...
Read more