The week we learned about Git and how to utilize source control. Some good points about git is that it allows users to create save points in their code. When developing a new feature the programmer can make use of branches to create new code while still being able to reset to a previous state if something goes wrong with adding the feature. I think this is incredibly useful especially when dealing with large programs because it allows programmers to work on small pieces of the code without modifying the existing code base. With online websites such as Github, programmers can collaborate and work on code simultaneously. This does present a challenge though if both programmers make modifications to the same lines of code. This will cause a conflict and require a code review to determine how to resolve the conflict. Overall I think tools such as git and Github are incredibly useful for programmers to collaborate on software projects.
For the Markov code review I worked with my teammate Brandon Hoppens. My strategy for the Markov assignment was to first read through the entire prompt and ensure that I had a general idea of what the program was supposed to do. I then worked through the prompt building each method before moving on to the next. I built all of the methods and then ran the test after my initial build. I was able to pass a few of the test and failed others. I then went back to the individual tests I failed and manually debugged them. This was in contrast to how Brandon tackled the prompt as he was implementing the methods as they were needed. He worked to ensure each piece that he added worked with the existing code base. I think I would change my strategy to adopt some of his methods and use an incremental approach. I relied on building the entire program before running the first test, and I can see how on bigger projects this could lead to some frustration. The feedback I received from Brandon was ...
Comments
Post a Comment