Sprint 1 – Tools Setup

At the begining of the year, I spent my time re-familiarizing myself with basic CS tools.

Challenges with Tools

Often times, my make command would break. Thanks to my debbuging experience, I was able to resolve the issue. Here are commands that helped me:

#!/bin/bash

pip install -r requirements.txt
gem install faraday-retry  # This was the most useful
make stop
make clean
make serve-minema

Quick Breif on How to Setup Tools

Throughout my journey of tools, I learned to setup tools on two operating systems, including Chrome (via Kasm) and Windows.

Kasm

This breif assumes that you have already created a student repo. If you have not, fork the (OpenCS Student Repo)[https://github.com/Open-Coding-Society/student].

To setup KASM, I ran through the following steps:

  1. Create an account in (OpenCS Pages)[https://pages.opencodingsociety.com/login].
  2. Visit (OpenCS Kasm)[https://kasm.opencodingsociety.com/], then login with your credentials.
  3. Click either Kali, or Ubuntu. Either will work. Once done, wait for the virtual box to boot up.
  4. Open a terminal. This is straightforward in Kali. For Ubuntu, click Application in the top corner, and then press Terminal Emulator.
  5. Run the following commands, replacing anything inside the <> symbols with their required value:
#!/bin/bash

mkdir -p <YOUR-USERNAME>
git clone https://github.com/<YOUR-USERNAME>/student.git
./scripts/activate.sh  # Enter your Github info
./scripts/venv.sh
venv

Look at the first command:

mkdir -p <YOUR-USERNAME>

The mkdir command will create a new directory. In Linux, a set of operating systems that includes both Kali and Ubuntu, files and directories are important. You can think of it as a maze. Each of the directories are doors that lead you closer and closer to any given exit. The exits, in this case, are the files. Running mkdir -p <YOUR-USERNAME> will create a directory with the same name as your Github username. This directory is where you will be able to store all of your Github repo’s that are owned by you.

Sprint 2 – Lesson Review

Sprint 3 – Creating a Game

Our team (lvl6) did an amazing job with our game, and I played a major role in our sucsess. Here are some statistics to show how we did:

Coding & Commit Stats

  • 4 out of the 5 top CSSE student commiters were in our group (since the start of the sprint) Image showing Command
  • 2 out of the 3 top commiters in OpenCS pages overall (including CSA and CSP) were in our group (since the start of the sprint)
    • Only Mr. Mortenson himself had more commits
  • If all of our groups contributions to the game were removed, at total of 0 levels would be operational
  • I had the 2nd most commits out of everyone (since the start of the sprint), lagging behind only Mr. Mortenson himself

Ideation Stats

  • We were the group that demonstrated the most leadership
  • Many other levels, from 1 to 5, asked us for our code to certian ideas so they could implement them in their own levels
  • We were the first group to implement these ideas, and following our implementations, other groups took our ideas to implement them in their own levels
    • Audio (later used by lvl1 & lvl4)
    • Creating our own mansionLevel6 markdown file so that we could test our level independenlty from the main group (later used by all levels)
    • Invisible sprites (later used by lvl1 & lvl2)
    • etc.
  • We were the only group to implement these ideas
    • Boss fight
    • Custom Collision Detection (not using the game engine)
    • etc.

So now for the big question:

What did I do to result in this amazing performance?

I played a great role in leadership for our team, making charts showing our commits overall and contribution to the team. This motivated team members into contributing more, leading to our amazing commit statistics.

Below are some of the charts I made:

  1. First chart ever made (very early on, still transitioning to ideation) Notice how some members were commiting too often, while others were lacking contribution to the code of the game.
  2. First chart where Anish has less than 50% of the commits Now, thanks to my chart making and constant reminding/pestering of my teammates, those who are commiting too often have started to commit at a more regular pace, and those who have commited too little or not at all have upped their game.
  3. Final chart We can see a continuation in the previous pattern.

Overall Reflection