CST338 Module 3
Some of the lecture material this week covered the proper methods for inheritance classes. This specifically covered accessing a parent class constructor or other methods and values.
The project that was finished this week was the Trooper Maker assignment which was also part of the midterm. Overall it encompassed ideas of inheritance and abstract classes alongside a lot of the material that has been covered before. Its implementation was somewhat simple as the majority of the methods within it were methods that could be autogenerated and the logic for the attack method was straightforward. The only error I ran into was incorrectly spacing the output statements.
1. I worked with the rest of my team -- Jeremiah, Jake, and Ian.
2. My strategy for working on this assignment was to generally brute force it at first. I've found that when under a time limit for smaller projects, brute forcing algorithms can get you to a working product faster even if it's not very efficient at first. Although in my method I would normally test methods as I wrote them, I wrote all of the methods first and tested after mainly due to the simplicity of each method which allowed me to run an input through each method mentally to verify the working order. Once the whole system was operating properly and I fixed any issues I missed, I then went through and altered algorithms in order to make a more efficient program. Overall the only issue I ran into was not updating prevWord after the current word was processed.
3. My team members' methods seem to be a bit more building block focused than my method where they chose to test each method after it was written to confirm it was running properly before continuing on to develop the next method.
4. Having worked on this assignment I would not change my method. Although this idea of just totally brute-forcing the entire project is not the most time efficient for larger and more complicated developments, it works perfectly for smaller projects that have simple algorithms or are just similar to what I've worked with in the past. Even for slightly larger projects, the only change to my method that I would make would be to test methods after developing them. Only for much larger projects would I try to build well-balanced and tested methods as I wrote them.
5. According to each other, we all generally follow the Google code style pretty well. In fact some of us have installed the Google style based style guide for intellij
Comments
Post a Comment