Oh God, I'm A Team Lead

 This sprint was difficult for me. I had a lot going on both on the school and personal level, and was not able to put in the effort I knew I could give. But, we can start by championing the work that was done. This was the first thing I accomplished in the sprint, and it surprisingly meant a lot. It wasn't much, really; I fixed a longstanding bug that kept the text from updating with the placement of items. It was just a change of calling the UI refresh functions, but it lead into a lot of the work I had to do for this sprint. Finishing this lead to the understanding of multiple things: UI calls right now are really slow and really bad; this isn't necessarily a problem, but it lead me to start understanding exactly when the game changes things and it when it doesn't. UI updates, as of right now, are not currently affected by the update function with the exception of anything that is guaranteed to change per tick. Additionally, I recognized that the Item properties were bei...

 It took a lot of work to try and make the inventory get anywhere close to what I want. Half the issue with it is that I didn't have a solid idea of what the fun in it should be; I forgot that, with the resident evil inventory system, fun wasn't necessarily the goal. The goal of the inventory system there is to limit what the player can do; it is a genuine impossibility to be adequately prepared for every situation thanks to the limited inventory, and some weapons are made weaker or more powerful based on their storage requirements and even the size of their ammunition. Following the philosophy for a grid inventory system would then result in a +1 feature that's mostly defined by what the player /can't/ do, which doesn't give us much design space. It's also not really a restriction that opens us up for fun. My first effort at making the inventory system work. So, I decided to abandon the structure and make the inventory entirely mesh and collision based. The onl...

 I'm putting the GitHub bitching here before everything else so anyone with a pulse can ignore it: We had our first major github pile-on over the course of this sprint and most of it was completely avoidable. In the very least, we understood what went wrong, and the first time it happened, we were able to merge in a way that got everyone's up to date work into merge. The second time, people had to re-upload things which sucked. This was caused by people not pulling changes from merge into their projects at the start, or not putting their changes into origin and causing later problems.  Now that we know better, I'm stressing the need for people to explain what they're working on and when they've pushed whenever it's a file with heavy traffic. Whenever we were all working on the UI layout, toes were stepped on, and now that we're approaching a deliverable, we can't have that happen again. Otherwise, this sprint was very acceptable; we did slightly go under...

 This is my first time as a team leader, and I'm constantly anxious. I'm now currently dealing with people who have spent a lot of time in leadership roles, and who have worked on larger projects than I ever have. Frequently, they're more talented than me in different aspects. There's a lot of reasons for me to be anxious about my new position, but I signed on because I knew this role would be more work, not less, and that I was dead certain I could benefit from taking a leadership role. The only issue is that right now, I have to work on being less of the Michael Scott I was born to be. I am doing my best to provide good bones for everyone to work on, and give people the space they need in order to do everything they need to do. The backlog only really started coming together when I made an asset list that helped me break down, in detail, what parts of the game needed to be built in sequence, and what features I could re-use from one asset to another. This first sprint...