https://homeostasis.scs.carleton.ca/wiki/index.php?action=history&feed=atom&title=WebFund_2024F_Lecture_19 2026-04-06T08:44:20Z Revision history for this page on the wiki MediaWiki 1.42.1 https://homeostasis.scs.carleton.ca/wiki/index.php?title=WebFund_2024F_Lecture_19&diff=24868&oldid=prev 2024-11-21T19:16:08Z

<p>Created page with &quot;==Video== Video from the lecture for November 21, 2024 is now available: * [https://homeostasis.scs.carleton.ca/~soma/webfund-2024f/lectures/comp2406-2024f-lec19-20241121.m4v video] * [https://homeostasis.scs.carleton.ca/~soma/webfund-2024f/lectures/comp2406-2024f-lec19-20241121.cc.vtt auto-generated captions] ==Notes== &lt;pre&gt; Lecture 19 ---------- * Assignment 3 was officially due yesterday but is being accepted until Saturday evening. * I will go over solutions for...&quot;</p> <p><b>New page</b></p><div>==Video==<br /> <br /> Video from the lecture for November 21, 2024 is now available:<br /> * [https://homeostasis.scs.carleton.ca/~soma/webfund-2024f/lectures/comp2406-2024f-lec19-20241121.m4v video]<br /> * [https://homeostasis.scs.carleton.ca/~soma/webfund-2024f/lectures/comp2406-2024f-lec19-20241121.cc.vtt auto-generated captions]<br /> <br /> ==Notes==<br /> <br /> &lt;pre&gt;<br /> Lecture 19<br /> ----------<br /> <br /> * Assignment 3 was officially due yesterday but is being accepted until Saturday evening.<br /> * I will go over solutions for A3 and present A4 on Tuesday<br /> - A4 should be posted by the end of the weekend<br /> * Today<br /> - midterm solutions<br /> - interviews<br /> - frameworks for web dev<br /> <br /> * Final exam will be of comparable difficulty, length will be proportional to additional time<br /> - if you didn&#039;t finish with enough time, that probably means you were spending a lot of time searching during the exam<br /> - that means you didn&#039;t really understand the material going in<br /> - this exam should have been doable with minimal references<br /> to the class materials and no references to online materials<br /> <br /> * If you do better on the final exam, the final exam grade will replace your midterm grade<br /> <br /> <br /> INTERVIEWS<br /> ----------<br /> * I will be emailing individuals to request interviews<br /> - some random, some selected (you won&#039;t know which)<br /> * You may also volunteer for an interview<br /> * I will post a spreadsheet on Teams for interview signups<br /> - please put your name down in a time slot<br /> - each slot is 15 min, discussion should take 10 min or so<br /> <br /> * During interview, we&#039;ll look at the questions you missed on your midterm and maybe some you got right<br /> - we&#039;ll discuss, and if merited I&#039;ll give you additional points<br /> - I won&#039;t take away points<br /> - we can also look at your answers to assignment questions<br /> <br /> So if you want to appeal a midterm grade, please sign up for an interview!<br /> <br /> Only way an interview goes badly is if I start thinking the answers you wrote<br /> don&#039;t correspond to your level of knowledge<br /> - I don&#039;t expect this to happen<br /> <br /> TAs will do some interviews, but I will do a lot of them<br /> - and the sign up sheet will specify with whom you&#039;ll be doing an interview<br /> <br /> In general, if you get an email you should try signing up with me<br /> - TAs are more for overflow, as my time is limited<br /> <br /> Don&#039;t pay attention to Brightspace grade calculations<br /> - I do my own calculations in an offline spreadsheet, more complex<br /> than can be handled on Brightspace<br /> (multiple grading schemes)<br /> <br /> General tip when answering questions (on assignments &amp; exams)<br /> - your ratio of search to work on your own (thinking/coding) should be 1:3<br /> - 10 min search, 30 min thinking/coding/experimenting<br /> - if your ratio is 1:1 or you are spending more time searching than<br /> thinking/coding, you&#039;re approaching this material wrong<br /> <br /> <br /> node is the precursor to deno (note how one is an anagram of the other)<br /> - have same original author<br /> - node is older, and JavaScript wasn&#039;t so featureful, so it defined its<br /> own APIs<br /> - deno uses modern APIs originally designed for the browser wherever possible, rather than what node uses<br /> - but it has backwards compatibility<br /> <br /> In node, instead of import (which directly loads code from other servers and caches it locally), we have require<br /> - require loads in external code, but that code is in node_modules by default<br /> - node_modules must be initializes separately, using npm (node package manager)<br /> <br /> deno supports node modules but you don&#039;t need npm and you don&#039;t have to manage node_modules<br /> - deno takes care of all that for you<br /> <br /> When we run &quot;deno run -A -r https://fresh.deno.dev&quot; it asks questions then creates an &quot;empty&quot; project<br /> - fully functional &quot;hello world&quot; web server app<br /> - that&#039;s what we are exploring now<br /> &lt;/pre&gt;</div>

Soma