Additional things I did to improve (after my retrospective)
- Video of feature demo
- FRQ review
- Complete self assesment
Video Demo
My feature is the recipe posting system where users can post comments from recipies from other sites. It serves similar to a social media aspect where users can read each other's posts.
FRQ practice
Screenshot of CB FRQ:
I’ll provide code from my feature + explaination for each component of the FRQ below (scroll!):
List
In model, data is retrieved in lists/rows. Each object under posting (like name, dish, cuisine, etc.) is converted into a dictionary so it can store the user's input data
Procedure - read
This is the "update" procedure where an API endpoint updates an exisitng "posting" that's already in the db on the specific name. Then it retrieves JSON body requests, checks if the name exisits, then finds it in the db to update the rest of the information if it has been edited (dish, cuisine, link, comments). And lastly it saves the changes to display for the user.
Algorithm
1. sequencing: ordered steps. First step is when "name" is checked to see if it exists. Then, it fetches data. Last step here is to return a response in the table.
2. selection: using if else statments, the methods checks for name. If it's provided, it queries the specific post, if not, it retrieves all posts.
3. Iteration: looping of data. Line 112, retrieves all rows from table. Line 113, loops through the rows and converts them into JSON dictionaries
Output
The input from the user is text entry, then they press a tactile button "submit recipe" which saves their data into the db. If successful, visual text pop up will output "recipe posted successfully". This same message will appear when the user edits and deletes. Edit and delete are also tactile buttons, then to edit, the user can type their changes (textual) and save them.
Self assesment for the retrospective
| points | Self Grade | Reflection | |
|---|---|---|---|
| 5 accomplishments | .5 | .48 | Distinct 5 accomplishments, covering multiple aspects of the class, that go in detail (db storage, postman, CPT, CRUD, Kanban). Have supporting code/ vocab/ pictures when appropriate. |
| Project demo, CPT, n@tm | .2 | .18 | Full stack for my feature working and deployed! Demo in person good but didn’t have video of demo. CPT discussed in 5 accomplishments in detail (with vocab and code), lots of n@tm pictures and throrough reflection on the experience. |
| Project feature blog w CPT lang | .1 | .1 | Complete blog starting with explaining frontend of feature, then backend. Explain success and failure and how I managed problems. Use of CPT language and supporting examples |
| MCQ | .1 | .08 | Complete MCQ on time, reflection on strengths + weaknesses included and also compared to last tri to see improvement in areas I used to struggle in. |
| ability to impress | .1 | 0.08 | Reached out before the retrospective, asked someone new (my mom) for help for review, mentioned overall goals/ future plans, took extreme interest at N@tm. Added a time on my blog to practice on my own (thanks chat). Self assesment done late though… |
| total | 1 | 0.90 (original) | 0.94 (updated/ after revisions) |