CST 338 Markov Week 4

I worked with Matthew, Dakota and Jerrick. My strategy for this assignment was first figuring out the structure of the program and what methods need to be written first, especially because we need to commit in 2 different branches. My strategy was dividing the code into 2 sections, the first section is the methods required for structuring the words hashmap  including (endsWithPunctuation, addWord, addLine, and addFromFile). When writing these methods I start with writing the necessary method that will allow me to write the next one, for example: I needed endsWithPunctuation before writing addWord. 

Matthew mentioned that he tried planning out the code on paper before writing the code, although he found himself struggling with it. He had a much easier time after writing some code so that he can examine the output on the screen.

Jerrick’s mostly focused on comments and more diligent commits. He did write out some planning on paper before writing the code, which helped him. He also then generated the basic methods first before working on the harder ones.

Dakota Felt more organized than his previous assignment , and also had more meaningful commits. 

I don't see myself sticking to one strategy, since I feel that when it comes to programming, the strategy would depend on the task at hand. Also my classmates things my code follows the Google Java Style Guide. 

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