Who made this code base... oh wait it was us...

Joseph Lipinski | Week 2: Who made this code base... oh wait it was us...

WEEKLY NARRATIVE

The week began with a programmer meeting to decide what tasks needed to be done and who would be accomplishing them. I was This week I did a review of our code base; specifically looking at how the memento is bound to an individual (i.e. enemy or player). Later in the week I met with Zak to work on adding in the Rewired package to our game to properly manage our input of controller/keyboard and mouse. While peer programming with Zak I look into changing the functionality of the memento so that the player would have to actively press a key to pickup the memento rather than it being auto-attached to you when you collided with it.

CONTENT WITH HOURS

• Programmer Meeting (2 hours)
• Review of Code (1 hour)
• Rewired Controller Peer Programming with Zak (2 hours)
• Pickup/Drop Memento Change (1.5 hours)

WORKFLOW EXAMPLES

POSITIVE OUTCOMES

• Peer programming was of great benefit since I had someone else with whom I could confer immediately.
• After some initial difficulty with getting the memento functionality to change it became clear that the change was rather simplistic and easy to implement.

NEGATIVE OUTCOMES

• Our code base is still sloppy in some areas. Most of the code for memento should be changed or rewritten for clarity as functionality for the memento is dictated between multiple scripts instead of just one.

NEXT TASKS

If there is available time and resources, clean up the code where possible. Assist with bug testing and fixing and accurate logging of how they were caused if a solution isn't immediately obvious. Continue working on implementing the other audio loop as background music.

TOTAL HOURS LOGGED THIS WEEK: 6.5 hours

TAGS

#{Joseph Lipinski}

#{Week 2}

#{Programming}