Monday

Jaehyun Lewis

I have worked on project 2 over the weekends. finished up all the backends function ready to go.Today, I'm going to prepare the qc, and presentation.

Michael Ludwig

The weekend was not as productive as I would like it to be. We were able to get the event and suggestion functionality working but that was about it. Today our batch will be presenting so I am excited to see what other teams have done with their time.

Jeong Kim

I have worked on the project with my team over the weekend. We had our backend and frontend connected, but not all of our functions are fully implemented. But we had to get our presentation ready and move on. Today, I will be focusing on the presentation and getting ready for the QC.

Jeremiah Weaver

Han Gyul Park

Over the weekend, whole team members got together to work on the project. We got some functions working fully, but not all required functions. Today, the presentation and QC is scheduled. I hope the presentation goes smoothly as we rehearsed last night.

Tuesday

Jaehyun Lewis

Yesterday, we presented project 2 and had to do pair programming. I was paired up with Ivo, we figured out all the exercises we have to do, and I submitted the portfolio. Today, we are going to decide what project 3 will look like. I'm looking forward to it.

Michael Ludwig

Yesterday I worked with Mathew to complete the stack exercise. It was fairly easy but there were some logical errors at first. After work I tried to review some week 1 notes to prepare for cumulative QC.

Jeong Kim

Yesterday I had our project 2 presentation and paired programming assignment on stack and queue. Ian was my partner and I worked on the stack as a pilot. Today project 3 will be assigned and I will be studying for the QC.

Jeremiah Weaver

Han Gyul Park

Yesterday, Qc got postponed to Thursday. Instead, we did another paired programming exercise. With Joel, we were able to finish both Stack and Queue. Today, we will talk about project 3 then decide how to divide work. I plan to study for QC and cumulative assessment.

Wednesday

Jaehyun Lewis

Michael Ludwig

Jeong Kim

Yesterday, our scrum team talked about how the featured product, and sale product should be displayed. We have come up with an idea that since the featured item is a Boolean type, administrator should have access to the list of the items and have the dropped down boxes or buttons to set them as featured items which should be displayed on the user's main page. Building product model is still in progress, so we will be waiting until displaying product team comes up with the basic structure for the product.

Jeremiah Weaver

Han Gyul Park

Thursday

Jaehyun Lewis

Michael Ludwig

Jeong Kim

Jeremiah Weaver

Han Gyul Park

FRIDAY

Jaehyun Lewis

Michael Ludwig

Jeong Kim

Jeremiah Weaver

Han Gyul Park

P2 Retrospective

Michael Ludwig

P2 was fairly demoralizing. I started working on Events functionality right after we developed our database schema. However, due to basic functionality needs elsewhere in the project, I ended up switching between multiple features such as database implementation, user Authentication and user registration. User authentication did not get implemented at all but I would really have liked more time to work on that along with generating user suggestions. User authentication could have been implemented with some way to store the initial JSESSIONID token in our database after user login, but by the time we figured this out it was too late to actually implement.

Jaehyun Lewis

Project 2 was very hard since we have more people to communicate with all different time zone. I was mainly worked on the backends, and we ended up changing the backends model structure, but as time goes, the time schedule gets better and we worked as a team. Project prepare me to be better with teamwork, so it was very helpful. The biggest struggle was using the full calendar API. I ended up getting the events table from the database in the console, but the data wasn't showing on actual HTML files.

Jeong Kim

Project 2 was a lot more challenging than the previous projects for me since it was my first time building a full-stack application. I had to apply everything what I've learned throughout the training and it required a lot more of researching to make our application feasible. When our team made a decision on what we are going to build, we did not realize how difficult to make our application display the database in the Calendar view, which we had spent a lot of time to figure out, but we never finished. Communication was another issue. At the early development of front-end and back-end, we had to go back and talk to teammates and match the structure of our application since we had worked on different components. If I had more time to work on the project, I would work on applying form control to the register component, and Calendar API for our calendar view.

Jeremiah Weaver

I am very thankful for my team Java the Hutts altough I would have like to have more meetings. I did really like the clean user interface UI we created with the nice login screen and the awesome navbar. I also liked the way the events cards and the suggestions worked. However, for my down fall! I was a large part of poor communication trying to do my own thing like I was tring to build a hamburger menu that later I tried to make into a sidnav bar neither worked. I tried until it was too late. It was suggested that I move on to other things we needed done like testing and logging. Which I attempted over the final weekend unfortunately the stress of not completing the hamburger menu or the sidenav caused me to also not complete the logging and the testing.

Han Gyul Park

This project was really challenging in many ways. I feel like communication was one of the biggest issue we had. We split workloads by having everyone taking responsibility over different features. As we made some progression on each part, we then realized overlapping parts need to be mentioned and resolved in some way. As of the result, we ended up changing some base structures. This could have been prevented if we had better communication I think. Another problem we had was with calendar api we used. We had hard time tweaking pre-built functions to accept extra data we had to implement. I wish we had more time so I could have gotten my hands on backend as well. My plan was to work on JUnit testing once the profile page was done, but I never got a chance to do so.