# SE 371 Blog#1 "Hello World"

Hello World!!! This is the first post to my SE 371. I am new to posting on blogs so, I am not sure if you are reading this.

The only problem with assignment one is the blogs part. I am not sure if I am creating blogs properly. Also, I am not sure if I submitted my code to GitHub properly. The coding part of the assignment went well. I was able to do the coding with no problems.

I am really excited for the group projects for this course. I love working with other people. I love working with people because it forces me to produce my best work. Of course I would be expected to be on top of my work on the group projects.

In conclusion, I am feeling really good about this course. I think I am going to get an A plus.

# Blog#2 Project One

I have just finished project one with my group. This was my first time leading a group of people on a project. I communicated well and tried my best to set up deadlines with the group. One challenge was finding the time to meet up on Zoom. We were able to set up a time on Saturday to meet. I would say that we communicated more on Microsoft teams. As a team leader, I was pretty active on teams including my team. I would say that everyone in the group was active and communicating throughout the project.

Rupen put the main source code on GitHub, and we were able to clone the repository. This made it easy for the rest of the team to build their code and work on their unit testing. Everyone in the group work on their own branch until it was time to merge onto the master. Nermin merged everything on Tuesday night.

I did not have trouble with this project. The only struggle I had was trying to find time to work on my test cases. I was not in Chicago for the last 5 days. I was helping my family in Puerto Rico. But I was able to submit my test cases on time. I have a pretty good background in java, so it was not difficult to write the test cases. This project went well and I look forward to working with this team again.

# Blog3: Assignment 2
I finally finish assignment 2. The reason why I went over the deadline was because I had to work on project one and other classes. There is this one elective class that is taking alot of time. Also, I also was not in Chicago the last couple days.

Assignment 2 was kinda tough for me. The methods I spent the most time were remove and addPlayer. I was not sure if I was able to used static for my variables. In the new end I decided to used static for the head variable in the player class. Remove player was the toughest for me. Though trial and error I was able to complete the method. Using println statements really help because it gave idea what was going on.

This was the second time I used git. I was mostly successful with using git. The only problem I had was merging doubleLink to main. But I think I was able to pull it off.

# Blog4: Project 2 Part A

Today was our first meeting for Project 2. Most of the team was able to attend the meeting. The goal of the meeting is to discuss deadlines and determine how we are going to complete the project. After that, we discuss our data structure a determine how it works. As a team leader, it was hard to divide up the work for part A of the project. I want to share the work with everyone and be fair but some of the tasks were more work than others. Nermin came up with a UML of the search list, and Hafsa and I came up with an overview of the functions. Rupen and Calvin work on the basic overview of how a search list stores and the rules.

# Blog5: Project 2: Part B

Today was our final meeting for Project 2. During week 2 of the second project, we determine how we are going to divide up the work. Project 2 went pretty well. I kept the wiki updated and tried to ensure we finish on time. I also helped the team to whom we provided our design document. I just help the other team clarify some things about our design document. We fell a little behind, but our group was able to complete the project a day after the deadline. To be honest no serious problems came up during the second project. We felt proud of the work we did.

# Blog6: Project 3: Part A

Today was our division meeting for project 3. In this meeting, our division leader discusses how we are going to approach the third project. Our team was assigned a task in this meeting. Our task was to look over the project source code and determine the different systems in the source code. Also, we had to go over each system and explain its purpose. To explain the different systems, we have to make a UML diagram. To be honest, I am kind of nervous about completing our tasks on time.

# Blog7: Project 3: Part A

Today we finished our first tasks for project 3 part A. We were able to complete our tasks on time. No problems came up during our first tasks.

# Blog8: Project 3: Part A

Our team was given another task. We must implement the key commands and provide a design document for the wiki. First, we must provide the design document of key commands. Luckily, I had already spent time looking at the code so I was able to determine how are we going to implement the key commands

# Blog9: Project 3: Part B
Our team has implemented key commands in the project. I was able to do some of them but, other members had to help me fix bugs. One problem was the code to rotate the brick, it was rotating in the wrong areas. Luckily Nermin was available to help and he solved it.

# Blog10: Project 3: Part B

We are close to the project deadline. Today I implemented a sound design for the game. The hardest part was converting the sound files to a format where the standard java libraries can play the sound. Luckily, I was able to figure it out and now the game has a wonderful sound design

# Blog 11: Project 3: Part B

Today we merge our project to main. The project went really well. The only differcult part was the coding. Our team kept up with our work and we were able to meet the deadlines. Also, we tested our features well.