Skip to content

Latest commit

 

History

History
75 lines (47 loc) · 9.06 KB

IndividualReports.md

File metadata and controls

75 lines (47 loc) · 9.06 KB

Individual Reports

** REMOVED **

  • My most significant individual technical contribution was the implementation of topic subscription, subscription notifications, and the enabling of external emailing for both subscriptions and account activation
  • While I had a little bit of experience from experimenting with another web framework (Ruby on Rails) in the past, this is my first major implementation of a web framework, so it really helped me understand some of the nuances of the MVC design pattern and really helped me understand how URL routing works.
  • My organizational skills and ability to see the big picture really helped get the project off the ground at the beginning, from the choice of toolset, to organizing meetings, to be able to envision the structure of the product. This made it easy to understand which tasks needed to be done at which point to ensure a reasonably painless workflow.
  • A certain lack of creativity made it difficult to come up with tasks for myself for the final phase of the project, which required a certain vision of what exactly we wanted the final product to look like. I should communicate with my team and with other more often to generate ideas during the 'would be nice' phase of a project.

** REMOVED **

  • My most significant contribution was the implementation of basic group functionality for our website, which has the group model, creation, and group page. This also includes group deletion and user types within the group, which was implemented in the following commit.
  • I learned about how the model-view-controller architecture pattern works and is implemented, and also web languages like html, javascript, and css.
  • I am always available to help or meet with team members. I am a fast learner, so it doesn't take long for me to start making contributions to sections that I am inexperienced with. I also like maintaining quality, so I try to perform tests and fix bugs often.
  • I have not learned anything about web design previously, so it took me some time to become comforterable with working on our project. I don't refactor or comment my code very often, which is an important skill to improve on.

** REMOVED **

-I implemented editing and removing message functionality. -This is my first webframe work project. I learnt a bit html and javascript. -I am always available to meet with the team. I am a good listener. -I think I need to communicate more with others.


** REMOVED **

  • Most of my work is relatively spread out, but the most significant standalone feature is the registration system from Phase 2. Cumulatively, it would be my work on table view in Phase 3.
  • Throughout the project, I learned a lot about web design, going in only knowing a little about HTML. I learned about frameworks in general, MVP, and Django.
  • I had a strong grasp of the overall project and how almost every feature worked. This allowed me to assist with other member's debugging and program code that did not conflict with other features while making tweaks to existing code to improve synergy between systems.
  • I did not know javascript, forcing me to use 'hacky' implementations as seen in my work in tableview (in views and html). Hopefully I can find time soon to brush up on it before a formal course on web design.

** REMOVED **

  • My most significant contribution would have to be my work with message functionality in topic views, table view and topics in group view. There was also the scramble at the end of phase 3 commit 1, commit 2, commit 3 where I was able to save the project from a major reset right before the deadline.
  • The two largest technical concepts I learnt about were, MVC and web frameworks, through Django. Before the project I had never worked with a web framework, I had only done work using HTML/CSS and javascript in very small projects.
  • My ability to quickly grasp concepts. Despite going in to the project not knowing how Django, or more importantly web frameworks worked I was able to quickly get a hold of the basics. That in turn allowed me to be a good source of knowledge for the rest of the project and left me with a good intuition as to where the source of bugs were.
  • My time management was definitely my weakest point. At the start of this project, when my workload wasn't so crazy I was able to make most if not all of the meetings. As the semester went on my growing workload as well as issues in my personal life caused me to cram all of my work for the project into a short period of time, and kept me from making a meeting or two.

** REMOVED **

  • My most significant individual contribution was allowing topics to be private based off of group memberships. This added a lot of privacy features that are needed for a good messageboard.
  • I learnt a lot about web development and the tools needed to make a web application. Using Django taught me how the MVC pattern actually looks and works.
  • My main strength would be that I tried to ask a lot of questions about other people's code and even my own to learn what could be done better. This helps with finding potential bugs if someoneone knows a better way than me to do a certain thing or vice versa.
  • I think that I could definately improve on my communication to let others know what I wanted to/was working on.

** REMOVED **

  • What is your most significant individual contribution?

My most significant contribution to the team I say would be bringing new ideas to the team, keeping things fresh and also keeping things organized. I also squashed a lot of bugs.

  • Tell us about a new technical concept/issue that you learned while working on the project.

Many new things were learned through this project. In terms of software development, I now know the advantages and challenges faced with Scrum and Kaban. I personally like Kaban better because of how free-flowing it is and how it is more based on individual skill than team organization. In terms of using Django and doing a web-based project, many concepts relating to the MVC model of development were learned. The connection between models (databases/DAO), views (what is being viewed on screen), and controllers (our python functions), was a critical skill to learn to not only contribute to the project but also excel and suggest new features to the team.

  • What is your main strength(s) as a team member?

Keeping things fresh was a big thing. My largest contribution was to the design of the product and to squishing bugs. I learned how Django worked extensively and knew what things were possible and not possible during the timeline we had. My knowledge of new technlogies (Bootstrap and Sendgrid) made for some interesting upgrades to the overall project.

  • What is your main weakness(es) as a team member? (i.e. Where do you think you can/should improve?)

I could improve my code comprehension and overall knowledge of advanced git and django features. Making sure to write comments alongside my code is a struggle for me as I find I want to complete things too quickly. This also leads to me hacking away at something and realizing there is lots of bugs with it. I need to slow down and think about the problem I am facing because more often than not I will thank myself later on.