In my first week, I planned to complete the following<\/p>\n\n\n\n
Monday \u2013 Complete introduction
Tuesday \u2013 Review Skills & Strengths
Wednesday \u2013 Initial ideas
Thursday \u2013 Finalise idea
Friday \u2013 Initial aims and objectives<\/p>\n\n\n\n
My first week went well, but I missed a crucial item: creating the structure of the digital workspace to allow me to complete the project. I did this first, as this will enable me to ensure I am on target and reflect on my progress as I go along.<\/p>\n\n\n\n
After completing the introduction, which I found good for reflecting on what I had learned over the last 18 months, it followed nicely into reviewing my skills and strengths, which lie primarily in solo work as a composer and analyst; I decided on this as focusing on my weaknesses didn’t allow me to move forward. This way, I could look at my skills and what would be helpful in this project. I would have considered my technical capability on drums to help me, but for this genre of music (and what is soon to be analysed), I won’t really need to do much with a full kit – at most, I’d be hitting one snare every few minutes. What I can do instead is utilize wind instruments for my project, and play with the harsh sounds of an organ to get what I want.<\/p>\n\n\n\n
My first goal should be to understand the music theory of Metroid itself. This is what I will spend most of my beginning weeks doing – but I can’t dwell on this too long, as I understand the time restraints I have – I will dedicate time each day to properly study what I intend to, and write an appropriate analysis and reflection of my actions. <\/p>\n\n\n\n
Updated Weekly Project Reflection<\/strong><\/p>\n\n\n\n