Slinglend Blog Post #9

• What stages of the project am I on and how is it progressing?
  We are getting the home stretch with this project. It is just progressing. Not super well, but not super bad either. We are at least trying our best to get the project done by the time next week comes around. Our goal is to have a fully functioning game. It doesn't matter if it is beautiful looking or not, we want it to work! And we will be damned if it doesn't.
• How or what could I improve?
  I, myself, really need to code, code, and code some more. I am tired of getting into projects without being able to code them or even help out with the coding. It is an aweful feeling when your lead programmer is not better at coding than you are, and you get stumped far more than they do. So, hopefully when the time provides itself, I will be able to take the time to code for future groups to come. I don't want to consider myself an excellent programmer, but I would at least like to have some basic knowledge in it.
• Did I change my milestone goals? If so, why?
  No milestone was changed because everything we have to do at this point is coding. Nothing will change in regards to that since all other aspects of the level are done (texturing, assets, pitfalls, character, etc.). 
• How did I deal with the problems that came up?
  Pretty much the same as last week. All coding problems ended up us going on unity3d. It's pretty straight forward. Other than that, we talked with our previous experiences and went on from there.
   
• What is working and what is not working in the planning and implementation of the project?I really want to say everything is working out with the project, but that isn't necessarily true. However, I will at least say that everything is pretty much done. We have all assets finished as I already stated, we just need so much help with the coding. This is becoming a common trend so far.. "What is the problem with your project?.. CODING!" It kind of sucks, and I know I said it so many times, but there really isn't much else to talk about. The coding is our biggest obstacle, and it really is a shame we don't necessarily know how to go about it.
• Briefly describe your time spent and any problems (within the team, with a computer, etc)Today was a make up day for me. I didn't realize there was so many projects that were not turned in at this point. I should also blame myself for not keeping track of the portal for the assignments that were provided. I must apologize for that and take full responsibility for my actions. I took the time to try to get caught up, and I also understand that my grades will suffer with a lower score. It is better to turn in something late than it is to turn nothing in at all. I will have to be aware of this next time. Funny thing is, usuaully I am fully aware of what needs to be done; just haven't been on the ball as of late. I won't go into detail of my problems because I know others have it just as bad if not much worse. But I will do what I can in the future.
• Evaluate the project as a whole.
  The project as a whole is alright... I just pray things will work out for us come next week