## News 27/3 Course adaptionat for corvid finnished. Distance videos for the course added at the **bottom of this page**. 10/3 Course starts on 6/4 April. ---- ## TDDD27 VT2 2020 progress steps. * Register for the course on [webreg for grading](https://www.ida.liu.se/webreg-beta/TDDD27-2020-1/The%20Course) * Find partner or work alone. Remember, work at a distance. Take the oppertunity to develop this essential skill. * Register a **gitlab.liu.se** repo for the project [by the deadline](deliverables/index.en.shtml). Use the prefix TDDD27_2020. * Add eribe22, matla74, sahsa74 and andla63 members **as Reporters**. * Register repo in this [form](https://forms.gle/CSmQqcygsAZHjjgcA). Submitt the link. * You can search [youtube for TDDD27](https://www.youtube.com/results?search_query=TDDD27) screencasts for inspiration and to get a sense of scope. * Determine client-side and backend frameworks(see [Tech Requirements](project/index.en.shtml)). * Determine your project idea. * Add you functional and techichal specificaiton in the Readme.md of yyour gitlab.liu.se repo [by the deadline](deliverables/index.en.shtml). * Work hard and smart. * Record a screencast status report for feedback. 5-10 minutes might be abut right. Put the link on your gitlab.liu.se repo [by the deadline](deliverables/index.en.shtml). * At the end, record an individual code screencast presentation of your project. Make it 10-12 minutes. * Also record a project screencast showing the projetc (as a team). Put the links on your gitlab.liu.se repo. * Make the final commit on the project. ---- This course has a focus on how state-of-the art web framworks and REST/API backend design that facilitate large-scale web application development (long-term, many developers). It's an A-level project course with focus on deap understanding of structures and development process in the web area.Students plan and implement projects using tools with sufficent technichal level. Basic understanding of web-programming is assumed, as is having good programming skill. Projects are performed by individuals or by teams of two/three. We examine knowledge, not products, and use individual oral examination and screencasts along with gitlab code repos. We read code and we want well-designed code, relevant comments and valuable version control messages but not documentation. Course organisation is bascially: * Register your [gitlab.liu.se](https://gitlab.liu.se) project repo and add course staff as Reporter role with **Deadline set to expire at the end of 2020**. * Add a [markdown-formated](https://docs.gitlab.com/ee/user/markdown.html) project specification in the readme.md on the repo * Record and link on the gitlab repo a project status feedback screencasts. The link should be in the readme.md file on your repo. * Record 2 final screencasts. System demonstration and code desmonstration. Link on the gitlab.liu.se repo. Code must be version managed on **gitlab.liu.se**, nowhere else, but it is also ok to use set up hooks for instance between gitlab and github or run multiple remotes. Examination is not based on other sources. Furthermore, use **freequent commiting and write high-quality commit comments**, since you are not the only developers in the project. I want to see all experimentation branches and all commits, not just a polished version. A vivid, highly commited and branched but merged git-repo with a lot of details about what happens in the repo is what a great software developer and web developer does. I am an active web developer in many projects and I know this is messy but also full with details and not adapted powerpoint presentations.