-
Notifications
You must be signed in to change notification settings - Fork 0
analysis and reflection
📑 Chapter summary
In this section we would like that you reflect about the work you have done during the course.- Reflect about own learning
- Feedback on course instruction
✔️ Chapter evaluation (max 5 points)
You can get a maximum of 5 points after completing the Analysis and Reflection section. More information in Lovelace return box for Final deadline.📑 Content that must be included in the section
Explain how you would improve your RESTful API and your client application. Try to develop the ideas, and explain why each improvement is needed✏️ Write here your text
- Pagination
- Renting product
- Messaging owners
- Improve filtering
- Chatbot using Open AI
- Purchasing product using credit card
- Discounts, deals and offers on products
- Integrating google maps to show the location of the product
- Profile page, editing users information or deleting your account
📑 Content that must be included in the section
Discuss in this section the things that you would have done differently if you started the project after this course ends.Perhaps the biggest thing would be to approach the course differently. The course focused on API and backend development, so maybe we wouldn't take such a big role in client development. Also, we would do the course in a more planned way and the project would perhaps progress more within the framework of the exercises and not then need to be tweaked afterwards to fit the way the course exercises presented.
📑 Content that must be included in the section
Comment where you encountered the main difficulties while doing your project work. Discuss about the easiest/most difficult parts of the project. Provide convincing statements.✏️ Write here your text
The main challenges that we faced was integrating hypermedia functionality into Sellix's existing architecture. This involved modifying existing APIs, data models, and business logic to support hypermedia representations while maintaining backward compatibility. Ensuring consistency in hypermedia representations across different API endpoints required a lot of work. Different endpoints had different data structures and behaviors, this required careful design to provide consistent hypermedia controls and links. Also validating hypermedia representations and ensuring correct behavior across different scenarios was also difficult. This was mostly because we had zero past experiences working with hypermedia However, with proper unit tests, we were able to carry on with proper development and maintenance, and increase confidence in the correctness and reliability of the API implementation.
The most enjoyable part of our project was the coordination within our team as we worked on creating a platform inspired by a simple sell/buy ecommerce platform. From brainstorming sessions to coding marathons, every step felt like a collective effort towards a shared vision. The process involved conducting regular meetings, extensive discussions, creative problem-solving, and continuous feedback loops of our works. Although implementing hypermedia was particularly challenging, it actually laid the foundation for future scalability and flexibility. It could enable easier evolution of the API over time, as new resources, actions, and relationships can be added without breaking existing client.
📑 Content that must be included in the section
Make sincere comments about the course. How this course could be improved? What should be changed? What should not be changed?I found the course to be very comprehensive and useful. It provided me with the opportunity to work with various technologies and expand my knowledge of backend development while also enabling me to build a full-stack application. The resources provided were extensive and served as a valuable guide while working on the project, despite a few issues that arose during the course exercises.
While I appreciated the exercises, I feel that the responses or test cases could be improved. Many times, they were ambiguous and lacked sufficient information. Additionally, the workload for the course and the number of credits awarded seemed disproportionate to the amount of work required. In my opinion, this course should be worth 15 credits, considering the numerous backend projects we had to build and the amount of theory we had to cover. Furthermore, the workload did not take into account other courses that students may be taking, which can limit their ability to fully grasp the concepts of this course and hinder their learning experience.
I hope this transparent feedback helps you improve this course for upcoming students.
I agree with Kurosh's points. Course provides very large amount of information and content to learn. The name of the course sounded like it was going to be full-stack focused but it turned out to be more back-end focused and I probably went into the course with the wrong mindset which affected the project we chose and the workload surprised me in the end. Of course, the fact that I got a job in the middle of the course and had much less time than I had originally planned is probably the reason why workload was exhausting.
| Task | Student | Estimated time |
|---|---|---|
| Analysis and reflection, Comments about the course | Kurosh Husseini | 20min |
| Lesson learnt, comments about course | Konsta Laurila | 20min |
| Lesson Learnt, comments about the project | Bishwas Wagle | 20min |