## News * 29/3 First lecture in course. [Slides here](./slides/TDDD27_2022_intro.pdf) ---- ## Have Questions? Click "Getting help" in the menue to the left. ## TDDD27 VT2 2022 progress steps. * Find partner or decide to work alone. * [Register on webreg](https://www.ida.liu.se/webreg-beta/TDDD27-2022-1/PRA%201,%20The%20Course) for grading * Create and a **gitlab.liu.se** repo for the project [by the deadline](deliverables/index.en.shtml). Use the prefix TDDD27_2022. * Add eribe22, sahsa74 and andla63 **as Reporters, with Expiration date 2023-12-31**. * Register your gitlab.liu.se-repo in this [form](https://forms.gle/E8CsmALCF2f2Q5sr7). Submit the https:// link to your repo. **This is super important becasue its from this form we check the projects at different stages** * Search [youtube for TDDD27](https://www.youtube.com/results?search_query=TDDD27) for screencasts for inspiration. * Determine frameworks for your project (see [Tech Requirements](project/index.en.shtml)). * Determine your project idea. * Add a functional and techichal specification **in the Readme.md** of your gitlab.liu.se repo [by the deadline](deliverables/index.en.shtml). * Work hard and smart and start early becasue it takes time to get into the frameworks * Participate in half-time status report seminars. [Book time in webreg - TBA]. * Submitt your individual oral screencast with code demonstration. Here you have 10-12 minutes to show your project and that you have achived the learning goals of the course and to what degree. * Also record a project screencast showing the project (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 that facilitate large-scale web application development (long-term, many developers). It's an A-level project course with focus on deep understanding of development in the web area as defined by modern web frameworks, in particular client-side framworks. Fundamental understanding of web-programming is assumed, as is having a high level of general programming skill. Projects are performed by individuals or by teams of two/three. We examine knowledge, not products, and use the oral examination, screencasts and gitlab code repos code and commits. We read code and we want well-designed code, relevant commit-comments and valuable version control messages ... but not documentation. We are programmers, we read code. ## Gitlab.liu.se only Code must be version managed on **gitlab.liu.se**. Full version history and all branches should be there gitlab.liu.se. *A big push of code at the end of the course is suspicious*. Furthermore, use **freequent commiting and write high-quality commit comments**. 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 creates. The course staffa are all active web developers since many years in many projects and we know it gets messy below the surface. ### Evaliute evaluation of course * 2019: overal grade 4.47 * 2020: overal grade 4.27 * 2021: overal grade 2.93 (covid year) * 2022: overal grade 4.06 (covid year) ## Old Course Lectures (2021 - keept for reference)