Last week, i accepted the task of making the ammo UI for our game. While i thought the task would be relatively simple, i was proven wrong when i actually began the work on it. While the task seems simple enough, i also had to go through the code written by my fellow teamates, which required a significant amount of time. That time of course, was spent to understand the code already written and further on used for the aforementioned task. Like i already stated above, i expected the task to be rather simple. It was quite surprising to see, that even the smallest spec of code, can bring down so many errors, if it is not written correctly.
For example, one of the things i was struggling with, was the need to turn a given number (from part of the code written by the others in another script)to a part of the text (the amount of bullets the gun had left), which i had no idea how to do. The biggest problem that i encountered though, was the code needed to transfer a number from another script, to the one i was currently working on. The later problem, is also really important, because it will always be needed for this kind of work. After a few hours spent looking into this problem, i decided to ask my fellow teamates for some input. From what i had searched, i had a few ideas, which did not seem to work properly. So when i did consult with my teamates, i got some ideas from them. While it was not something concrete, it did give me a boost to get unstuck from my predicament.
In short, i was able to find the solution to the problem of taking a number from another script (what i had looked up in the internet, was apparently from older versions of Unity) and further on i was able to figure out a way to turn a number to text. While i felt like this could have been avoided, because the amount of writting needed for this was little, i learned that even something little like that, can become quite problematic. The good thing about this whole thing though, is that this lesson is gonna be staying with me. Including that practice makes perfect, or at least adequate.
Petros Tsiouris - Programmer 
Hello Petros,
I enjoyed reading about your blog and the work you put in this week. It’s not entirely clear exactly what work you had accomplished. I saw that you did write a bit about managing bug fixes and small errors messing with your code, but perhaps you could go more into detail of said problems. It was good that you talked about the problems with your UI and how you sought the help of your teammates. Some things could use clearing up, for example you could describe your process of fixing any problems you had. I like how you included a picture of your game, it helped put the UI problem into perspective. If you could also include some code and how you went about changing it that would really give the reader a feel for your work. I believe your post is a good backbone, but could be improved upon.
-Felipe
LikeLike