WEEKLY NARRATIVE
I worked on three big tasks this week. The first was getting a bug list together, logging everything we could remember from last term. Members of the team now have a place to detail bugs they find. Myself and Jimmy (and any other volunteers) can then find a probable cause which can then be passed on to be fixed.
The second task was documenting the workflow we'd like to use for the programming team. With so many programmers on our team, all of us working on a master branch in GitHub isn't feasible. We'll need to adjust once the move to Perforce happens, but for now we have a plan to follow when implementing new coding features.
The final task was the biggest. Restructuring our Unity project. I created an editor script to create asset folders faster, and then began moving all of our assets into folders for each game object & effect.
CONTENT WITH HOURS
- Sorted all assets (4 hours)
- Created editor script for new asset creation (1 hour)
- Updated bug list (1.5 hours)
- Created programming workflow document (1 hour)
- General meeting (3 hours)
WORKFLOW EXAMPLES
POSITIVE OUTCOMES
- The Unity project doesn't just *look* clean, it *is* clean
- I'm getting more fluent with editor scripting, and I'm excited to see what tools I can make for the team
NEGATIVE OUTCOMES
- I got feedback on my folder restructure before I committed, but it'll take a week or two of our team working in the new structure to really know if it's going to work well
NEXT TASKS
- Start working through the bug list
- Get our project moved to Perforce quickly
TOTAL HOURS LOGGED THIS WEEK: 10.5 hours
TAGS
#{Corwin Belser}
#{Week 2}
#{Documentation}
#{PPJ}
#{Programming}
#{PPJ}
#{Programming}

No comments:
Post a Comment