 |
About | Games | Sprint 1 | Sprint 2 | Sprint 3 | Verify w/JS | N@tM |
5 accomplishments
Database storage
Static data. Progressed to data entry into database (still static), then dynamic data (user input)
Postman
check raw API requests, read messages (404, 500, 200), where/ how to fix (debugging).
CPT requirements
Use of lists (rows), dictionaries (columns) for the databse.
Sequencing, selection, iteration
CRUD
using postman/ inspect/ debugger, backend first then connect to frontend
Kanban board
Timeline of progression (both group and individual)
Feature demo
Recipe posting system
Link to deployed site
Night at the mueseum
Picture proof!
</section>
Extra work:
MCQ corrections:
Blog for my feature
Link to blog
Khanman board: Link here
Self grading
| Teacher Grade | Self Grade | Reflection | |
|---|---|---|---|
| Planning | 0.85 | 0.85 | Good idea/ starting kanban board but each person's specific role still needs discussion |
| Video | 1.75 | 1.80 | Everyone's roles/ plans thorough and worked out, the audio was just messed up (my fault). Worked a lot w group to finish the video |
| Frontend / Backend | 0.70 | 0.87 | During the live review we were not prepared at all, but working with groupmates and other groups, we got everything to work (never found appropriate time to remake) |
| Full Stack | 0.80 | 0.87 | Completed demo's, never finished live review for CB but I have finished it since then |
| Deployment | 0.90 | 0.90 | Everyone's features successfully deployed! |
MCQ
Strengths
Pic from CB:
Weaknesses
Variables and assignments, math expressions, developing and calling procedures
To review, I've looked at CB's answer + explaination and reach out to peers for better explaination
Compare w last tri MC
Improved on many topics! (Boolean, conditionals, iteration)
Final words
Lessons learned
Long term goals
Mechanical engineer, keep track of designs/ calculations. Cannot design something complex entirely on my own, work w others during the process to achieve a similar goal
Extra (if hv time)
Extra N@tm pics
