Skip to main content

Open Learning Initiative (OLI) Module 2 Reflection

 Open Learning Initiative (OLI) Module 2 Reflection

    This week we reviewed the Open Learning Initiative (OLI) Module 2. In this module the focus was how to recognize factors that improve team performance and how to find ways to improve collaboration skills. The main video in this module was a talk by Professor Anita Woolley who analyzed what makes a good team. One of the most interesting things I found from the talk was that initially there were no clear patterns on what made a good team. There were instances of teams with all stars not working well together and teams that were expected to fail that did exceptionally well. Based on the research conducted by professor Woolley it seems that having high social sensitivity contributed the most to team success. Team members that worked together as parts of a whole seemed to accomplish more that any super star team. I like this idea in that there is not a strict formula for teams to work. Each team can have it's own personality but as long as the communication is open and team members feel valued they can succeed. 



Comments

Post a Comment

Popular posts from this blog

Week 4 Learning Journal

 Part One: Educational Goals The biggest goal I have is to graduate from the CSUMB CS Online Program at the end of 2025 and receive my diploma. I plan on attending the graduation ceremony in person and walking across the stage to receive it. I feel that continuing to envision the actual diploma will help to continue to inspire me to work towards that goal. Part Two: Career Goals One of my biggest career goals is to find employment as an iOS mobile app developer after graduation from the CSUMB CS Online program. I feel this is possible and in addition to the degree I plan on releasing at least three more apps to the app store before graduation.  Part Three: ETS Computer Science Test After reviewing the overview and the sample ETS test I feel that I would likely score in the 50th percentile. I am not too worried about my score because I know I can improve it by reviewing the topics listed in the test. Most of the information on the test I am familiar with but I know I will need ...
2 comments
Read more

CST 338: Week 4 Learning Journal - Markov Project Peer Review

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 ...
Post a Comment
Read more

CST 363 - Learning Journal Week 7

This week we learned how to implement a different type of database using MongoDB. For our group project this week we changes the SQL code to MongoDB code. Both of these database applications do a fine job of working with data and saving it to a database. I did find that MongoDB seemed more streamlined than working with SQL. With SQL there seemed to be more setup as in creating prepared statements, and then executing queries. With MongoDB it seemed like a good chunk of the code was abstracted away and this made for cleaner looking code at the call site. If I had to choose I would likely go with MongoDB as it seemed more approachable.
Post a Comment
Read more