Development Blog #2 3/11/21
Looking back on the past semester, and the many sprint weeks we've gone through, it would be tough to pick our best one. Our first sprint was strong, we started out the semester really well with a fun idea that all of us liked and were able to contribute to. However, I think that the best sprint we had as a team was sprint #3, where we came up with the concept for and prototyped our game Cluckshot. I have a personal attachment to this game, as I was the one who came up with the name and the core mechanics, but it was absolutely a team effort. We were able to find an idea that all of us loved, and work together on it so that it could grow and develop. No ideas were bad ideas, and everyone contributed something major to the conceptualization and creation of the game. Brainstorming together always led to improvements, and we were able to unanimously agree on what needed to get done at any given time. We worked together to create a good concept that went on to get greenlit. I communicated a great deal with the designers and was able to work with them fluidly. We used version control fluently with no issues at all. I think my takeaway is that I have really improved as a team member. As explained in the first blog post, teamwork has not always been my strong suit, but if I can keep up the team skills and communication I showed I'm capable of in this sprint, then I think that I've improved greatly.
Development Blog #1 1/31/21
As a game developer, I'd like to think that I've made a lot of progress over the last few years. I think I've greatly improved on a technical level, doing well in all my classes and gaining a deeper understanding of programming in general. More than that, however, I think the greatest skills I've gained since coming to this college have been those involved with working in a team. I'm far better at communicating my problems with a team than I was in high school, as well as having improved in my ability to cooperate and compromise. It used to be very difficult for me to compromise when I thought that my ideas were best, and I would often try to take charge of a project, even when it wasn't my job to do so. I've improved greatly at understanding that the team opinion matters, and being willing to compromise about something, or being able to offer my input but not overstep and try to control something that isn't my job. I'm quite proud of how far I've come in both technical and team skills, and I hope that each is put to the test in this coming semester so that I can grow even further.