One of the most interesting things I have learned reading "Software Engineering at Google" is the idea of code reviews. When I first was thinking about programming I thought the actual coding would take up most of the time, but it appears that code reviews can consume an equal if not more amount of project time. I also learned that there are different types of code reviews and how there are many different aspects that the code reviewer is looking for before approving a piece of code. Reading about software engineering at Google it does sound like coding and reviewing code is very much a group effort with team members switching between the roles, similar to our current group projects.
Part One: Supporting and Commenting on Teammate's Goals I visited the following teammate's blogs and commented on their goals. Juan's Blog Vance's Blog Part Two: Possible Capstone Ideas The three ideas I have for my capstone project are two different mobile apps and one indie game. For the two apps I am thinking of creating something in Swift, the programming language of iOS. The first app is a passion project that involves a list builder for a miniature tabletop game called OnePageRules. It is an independent miniature game ruleset and already has a web version. My app would take that template and adapt it for iOS. The second app would be a simple star wars app that utilizes an online API for Star Wars call SWAPI. This API has a number of entries related to the Star Wars universe in JSON format. My app would connect to this online API, download specific pieces of data and display them in the app. The third idea would be to create a simple side scroller game. The game ...
Comments
Post a Comment