Thoughs on my leadership

Today’s Blogpost

Since this will be one of my last posts for awhile I was considering doing this as a recap of what I have done good and what I need to improve for next time.

First of all I think that my team has made a good game and that I feel proud to have been part of that team. The effort and dedication they have put in to make it possible is something I admire and feel will make them excellent game developers in the future.

However this journey has been rough at times and I think much of it boils down to my leadership. I have tried to have a hands off approach on how they have performed their tasks and to allow them to have as much freedom on how to finish them. Sadly I feel that in the process I might have become slightly detached from the developers and that in the future I will need to find a balance between creative freedom and restraints.

Secondly was working with Scrum. I like the tool and think it could be a great way to organize a team in the future. Still I feel that my own experience is a bit too small to use it effectively and need more practice with it to manage a team. I feel that overtime I have made some errors that have stacked and slowed down the process. However this just allows for more improvements from myself and that for the next project I can make some adjustments.

For example I had some issues organizing my daily standup and finding things to discuss. Secondly I feel that I didn’t ask my team enough questions and that in the future I need to do that more. My reason for this was that I assumed that if they had problems they would tell me, but that proved to not be the case all the time.

Luckily my team has been kind enough to give me constructive feedback on improvements and what they thought I did good. So now I feel more confident that I can do this aslong as I keep the problems in mind and work on them.

This is all for now.

Sound Script

This week has sadly been a very slow week when it comes to the current game design work due to me catching a fever and needing to rest. As such I haven’t had the ability to do the work that I needed.

However I did manage to get a script working in the game that allows a sound effect for when you take damage.

When I started with this task I first tried at first to use the same method as last time in which I only added an audio component to the right prefab. My first thought was that I could add the component to a sprite when the character takes damage. However I quickly realized that the sprite didn’t exist as when the player takes damage it simply creates a red overlay. So I had to scrap that plan and instead start to learn how to make a script for it. This however wasn’t as easy as I had hoped. At first I used the Unity website to learn some basics regarding scripting, but it was hard since I had never done anything similar to that before. While guides were useful I still wasn’t making as much progress as I was needed to finish the task within time. So instead I asked my programmer and game designer to help me with the script and to teach me how it worked. When they helped me I realized that I had barely done anything right with the script since I had skipped several steps when I tried to rush it. As such I hadn’t defined the audio source in the script or even found the correct place to put the code later. Lastly there was also an error in my code since I used the wrong command, but luckily they helped me with that as well.

With their help I managed to get the code working in the end, but I also learned many important things about coding. First of all never rush tutorials. I realized too late that skipping the earliest parts of the tutorial made everything else impossible to fix for me. This was obvious when I couldn’t even define the audio source in the code.

But most important it taught me it is a good idea to ask for help with coding and try to learn from more experienced people since they have a better understanding than myself at this.

This is all for today. Have a nice day.