-
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 4.5 points)
You can get a maximum of 4.5 points after completing the Analysis and Reflection section.📑 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✔️ Evaluation criteria(max 1.5 points)
- Future work is provided and carefully thought out: 1.5
We would improve our API by adding authentication for it. Usage of API tokens for example, we implemented users for our project, but they fell short for usage without authentication and of course, proper (web) client. This brings up the next big improvement, the client. We would like to improve the client and make it more professional and functional.
Some kind of JavaScript based client for example, would offer us to make the UI feel rich and interesting, this would also bring up the possibility to add visuals for the user.
📑 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.✔️ Evaluation criteria(max 1.0 points)
- A short reflective description of what was learned while working on the project 1.0
If we would start this project over, we would definitely start the planning of the idea with more clear image of possible client, and implement API usages for the client when designing. Our current project was hanging in the background a lot, because of lot of other courses took priority. This lead to some poor initial execution and planning, which were not a good combo. The progress of the course could have improved a lot if the focus was more on this course, but sometimes it goes like this. Still we feel like we learnt a lot of designing an API and consumer for it overall.
📑 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.✔️ Evaluation criteria(max 1.0 points)
- A short reflective description of the easiest/most difficults parts of the projects 1.0
For our team, the most difficult parts of the project was to learn to use relations within the API and database as well as implementing hypermedia. This includes thinking and design choices, such as what kind of relevant relations should our database have and offer, within the recipes and the ingredient within it. And how to provide the user this information, this provided a challenge for us in the beginning.
As well implementing the hypermedia was a little challenging, using schemas and controls. It was some work to understand and to get right, still proved to be useful, once we got them working.
Easy part for our project was our client, though this is partly because it was rather bare-bones and not so polished or high in effort. Still it was a fun little add on to our project, and offers a way to at least properly test the API functionalities, even if it does not really bring that high value to end user as is.
Another not so challenging part was to implement different methods for resources, and provide them functionality. This was familiar from some other projects, but offered some new things such as URL converters, which were cool.
📑 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?✔️ Evaluation criteria(max 1.0 points)
- Useful course feedback - what we should change, what we should keep: 1.0
The course subject is really interesting and relevant in the current times. Web development is huge industry and it is good to gather experience from it and to understand how these technologies work under the hood. Some things worth mentioning which gave us a little confusion and hick ups, were some contradicting information between this wiki and Lovelace. Some things were mentioned here, which were not mentioned in the Lovelace, so some unification could be justified between the content. Or just move all the relevant information to one place, to avoid confusion.
Course information and exercises were given a bit in pieces, which also made it sometimes difficult to prepare in advance for some deadlines, or complete several exercises in a row.
The course itself has a wonderful idea of combing the back end development and front end by producing an API and client for it. But we think that maybe putting a bit more focus for the client from the start of the course, could help it to not feel being like a leftover towards the end of the course. At least that was a bit the case with our team.
Overall we liked the course, and encourage the project like structure. This course teaches a lot of new things.
| Task | Student | Estimated time |
|---|---|---|