---
# System prepended metadata

title: TW Meeting 15 June

---

TA meeting 15 June

* progress update
* how is the dissemination going, what we still have to do, are we on schedule?
* is it necessary for the TA to be present for the meeting with the coach?
* create zoom link for tmrw meeting
* ask what can still be improved in the code/repository
* update readme details/documentation

* feedback report:
    * use \` instead of \"
    * privacy: storing data such that users cannot be identified (???)
    * elaborate why we chose technologies (cloudinary - describe other options we considered (e.g. storing images on heroku directly))
    * include project plan (? sau altu, n-am fost atent) in appendix
    * "report is too long" BUT IT ISN'T LMAO
    * cut down the research part a bit
    * proof-reading: get the rubric and look at it while reading!!
    * reference Appendix A
    * reflection: look at the rubric while writing that

* presentation:
    * 20 min presentation
    * (video) demo


# TW Meeting 15 June
* daca ne zice iar sa abreviem jurnalele ii zicem ca am facut asta deja 
* ii spargem fata
* title should be more explanatory (not telling the subject)
* add references to the technologies used (chapter 5.2.1, 5.2.2)
* report lenght is ok even if we go a liitle bit over the 20 page limit (figures do not count)
* "If the TA and Coach are happy, I am happy" - Edwin van Lacum 15.06.2020, Delft (de unde stii ca e in delft?), Netherlands
* check if language is formal enough
* remove text boxes (they are used for less importnat parts and not for highlighting important parts)
* Combine paragraphs (some are too short) altfel chioraste readeru :)))
* Say that we accomplished our goal and motivate and not just say 'we are happy with the result'