(This week's blog will be more of a reflection and an evaluation of the past few weeks and the upcoming week.)
For this week, I'll do a different blog entry, since this week was a workshop session, where we had time to work on our assignment. A major setback for the past few weeks were the work load from different modules within the course. The different modules within the course held me back from doing practices which would help me in the assignment, and doing the assignment itself. With this setback, I have found myself far behind from my original deadline of finishing it early, but I fear that I will find myself struggling to finish the project with a good mark.
The session today allowed me to get some of my work done for the project, but the work done and completed during that time was not enough. With the lack of practice, I found myself stuck and forgot on how to use line rednerers, trail renderers and mix up the obstacles for the game. I have also forgotten to take in consideration of the fact that these obstacles will have to be spawned at the different Y axis of the game scene. After assessing my situation, I found myself rushing to put in all these details, and this goes without saying that rushing work is never a good solution. With this being said, I have found many errors within my code, and ultimately, I have made a bad project and didn't achieve my milestone for the project.
From this evaluation, balancing different module's work load is essential as it will save time for project clean-up, would open up time for breaks after a beta milestone is finished and it would avoid me from rushing my work within the last 2 weeks of the submission due date. From this massive setback (and a mistake, if you will), I have learnt my lesson, and I learnt it the hard way. For my next assignment, I shall put in more commitment, dedication and balance to all modules.
For this week, I'll do a different blog entry, since this week was a workshop session, where we had time to work on our assignment. A major setback for the past few weeks were the work load from different modules within the course. The different modules within the course held me back from doing practices which would help me in the assignment, and doing the assignment itself. With this setback, I have found myself far behind from my original deadline of finishing it early, but I fear that I will find myself struggling to finish the project with a good mark.
The session today allowed me to get some of my work done for the project, but the work done and completed during that time was not enough. With the lack of practice, I found myself stuck and forgot on how to use line rednerers, trail renderers and mix up the obstacles for the game. I have also forgotten to take in consideration of the fact that these obstacles will have to be spawned at the different Y axis of the game scene. After assessing my situation, I found myself rushing to put in all these details, and this goes without saying that rushing work is never a good solution. With this being said, I have found many errors within my code, and ultimately, I have made a bad project and didn't achieve my milestone for the project.
From this evaluation, balancing different module's work load is essential as it will save time for project clean-up, would open up time for breaks after a beta milestone is finished and it would avoid me from rushing my work within the last 2 weeks of the submission due date. From this massive setback (and a mistake, if you will), I have learnt my lesson, and I learnt it the hard way. For my next assignment, I shall put in more commitment, dedication and balance to all modules.
No comments:
Post a Comment