In this week's module I learned about our work styles. For my own work style I lean towards being a "Get Along" or people oriented work style. I strongly desire for everyone in the group to get along and work together. I will also let others make decisions in the group and tend to follow the group decision even at the expense of my own personal opinion. I also learned about conflict and the different conflict styles. One thing I found particular interesting was the conflict spectrum. I was to place myself somewhere on the spectrum between conflict is negative and conflict is positive. On reflection I found myself leaning more towards conflict being positive. Even though I would like to avoid conflict, I do understand that it can be necessary to ensure that the best decisions are made. Everyone has a different perspective and brings those differences to the table. So although my work style was "Get Along", I also am okay with conflicts in the group if they are leading to better decisions.
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