Back-end Cleanup / Phase 3 - Blog 11

This week we seemed to have made very good progress on the final stages on the project. Still as the sole back-end team member, my work this week consisted of fixing a couple bugs that arose from the end point I wrote for phase 2 last week. The front end team is now able to retrieve a list of all of the sessions being presented, sorted by each time-slot for the day. Once that was finished this time last week, I was able to spend the rest of my time cleaning up the back end code of our system so it is clean, consistent, and ready to be reviewed and graded. This included renaming one letter variable names to appropriate names given their function. I also removed unnecessary comments while double checking that method names are self explanatory. The goal is to present our finished system to the client and other class next week. Based on what I saw from this week's checkup, I'm confident that we will be able to implement the remaining features before the due date. Another goal of mine this week is to run a script in our git repository that counts the number of lines of code that every member on our team added, deleted, and updated in the project. I want to include this in the conclusion blog post for next, and will perhaps email this list to the professor so he is able to see our individual efforts and create our individual grades accordingly. I don't think it we be fair to those of us who have written hundreds if not thousands of lines of code, if we get the same grade as those who have done absolutely 0. The 6-7 of us have done an excellent job of picking up the slack from the rest of the group, so I'm not sure if the professor can tell who has been working and who hasn't. I assume he'll be able to figure it out via our presentation, but I think the git stats will be cool to see.

This coming week I will be working on continuing to support the team from the back end. This will include writing a couple more endpoints to our API that will allow the front end to handle login/password, so the entries of counts can be stamped by the user using the app, as well as another that will allow for the retrieval of all the counts for each session in the database sorted by the speakers giving the presentations. This Phase 3 will complete our goal of allowing the sponsors to see which speakers they will like to invite back, as it will show who is building and maintaining an audience and who is not. Next week's blog post will be the last and longest post of the semester, as I intend to go in depth describing the whole project, most specifically the back-end and the things I've done, accompanied by screen shots. This has been the most fun project I've worked on during my college career, and I feel I've gotten the most out of this class. I'm excited to share how, so tune in next week!