## News * 20/4. Signup for project status seminar time. Go to https://www.ida.liu.se/webreg-beta/TDDD27-2024-1/Project%20status%20seminar and sign up, **one person per team**. * 27/3. Course [introduction lecture notes are here](slides/TDDD27_2024_intro.pdf) * 14/3 Course has been revisited för 2024-version of course. #### Have Questions? Click ["Getting help"](https://www.ida.liu.se/~TDDD27/help/index.en.shtml) in the menue to the left. ## TDDD27 VT2 2024 progress steps. * Find partner or decide to work alone. * [Register on webreg](https://www.ida.liu.se/webreg-beta/TDDD27-2024-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_2024. * Add eribe22, sahsa74 and andla63 **as Reporters, with Expiration date 2025-12-31**. * Register your gitlab.liu.se-repo in this [form](https://forms.gle/m8Gm7uBDEYeAYgoJ6). Submit the https:// link to your repo. **This is super important, this is how we organize the work** * Search [youtube for TDDD27](https://www.youtube.com/results?search_query=TDDD27) for screencasts for inspiration. Remember that previous years may not be entirelly representative of this years goals. * Determine frameworks for your project (see [Tech Requirements](project/index.en.shtml)). * Determine your project idea. * Add a project specification **in the Readme.md** of your gitlab.liu.se repo by the deadline. * Work hard and smart ... start early becasue it takes time to get into the frameworks. Focus in the front-end first. * Participate in half-time status report seminars. [Book time in webreg]. * Submit 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. Put the links on your gitlab.liu.se repo. * 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. ## Deadlines * Register on webreg *April 8* * Create Project *April 8* * Functional and technological specification on repo in readme.md. *April 8* * Project status seminar. *May 2, 3, 6, 7* (book on webreg)* * Individual oral code screencast. *June 3* (screencast link on gitrepo) * Project screencast. *June 3* (screencast link on gitrepo) * Final source code upload. *June 3* * Late submissions after summer: email examiner on the *22:th of August* that you have everything on your repo and provide also teh repo URL. ---- ## About the course This course has a focus on how state-of-the art web framworks facilitate large-scale web application development (long-term, many developers, many parts and large and often fragmented backends). It's an A-level project course with focus on deep understanding of development in the web area. A particular focus is placed on modern and advanced 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 for that. We read code and we want well-designed code, relevant commit-comments and valuable version control messages ... but not documentation. ## Changes from 2023 * Project volume is more important * More unique projects are required ... boiler-plate projects will not pass the course (see [Tech Requirements](project/index.en.shtml)) ## 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**. We want to see all experimentation branches and all commits, not just main. 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. ## AI in the course. AI as a tool for learning and producing boiler-plate code is ok i TDDD27, just like working with copyting solutions on stack overflow, copy-pasting code from tutorials, and other engeneering techniques. Make use of AI to get further along the development curve, and learn faster. But make sure and present your learning. The queality of you rpesentation of competens and learning is even more important now. *Using AI, but prentending its your work is cheating.* You are responsible to show how you lifte your knowledge and skill using a combination of all engeeering learning coh production tools. AI as a component in your project is both good and bad. I've seen a lot of project where the studentrs assume they have a great project beacsue of the dynamioc nature of the AI model, but its actually a bad web project. ITs easy to get the feeling that you are productive becasue you have a generatiove model. But its really all the quality around the AI model for a real application on the web that is interesting and not the promting. So if you use IA, make sure you dont fall in this trapp. Alos, traning AI models is not part of this course and cannot give you any substantial value. That is time you should spend on another course budget. Just like creating your own security syetem och database is ### Evaliute evaluation of course * 2024: overal grade 3.50 * 2023: overal grade 3.95 * 2022: overal grade 4.06 (covid year) * 2021: overal grade 2.93 (covid year) * 2020: overal grade 4.27 * 2019: overal grade 4.47