-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
405cf62
commit a7c69b9
Showing
3 changed files
with
189 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,94 @@ | ||
| <!DOCTYPE html> | ||
| <html> | ||
| <head> | ||
| <link rel="shortcut icon" href="../../../../favicon.ico" type="image/ico"> | ||
| <meta charset="UTF-8"> | ||
| <meta http-equiv="X-UA-Compatible" content="IE=edge"> | ||
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | ||
| <title>COMS W1004 Introduction to Computer Science and Programming in Java</title> | ||
| <link rel="stylesheet" href="../../../../styles.css"> | ||
| </head> | ||
| <body> | ||
| <header> | ||
| <nav> | ||
| <ul class="horizontal-list"> | ||
| <li><a href="/">Griffin Newbold</a></li> | ||
| <li><a href="/teaching.html">Teaching</a></li> | ||
| <li><a href="">Sample Code</a></li> | ||
| <li><a href="/teaching/2024/spring/java-1004/officehours.html">Office Hours</a></li> | ||
| <li><a href="">Exam Materials</a></li> | ||
| <li><a href="">Course Syllabus</a></li> | ||
| <li><a href="/teaching/2024/spring/java-1004/policies.html">Course Policies</a></li> | ||
| <li><a href="/teaching/2024/spring/java-1004">1004 Homepage</a></li> | ||
| </ul> | ||
| </nav> | ||
| </header> | ||
|
|
||
| <main> | ||
| <section class="section1"> | ||
| <h1>Office Hours Overview</h1> | ||
| <p class = "section-text"> | ||
| All teaching assistants are required to hold office hours weekly until the last day of courses. Trivially, I am no | ||
| exception to this rule. It is vital to know that I am also an undergraduate student like yourselves, meaning I am | ||
| enrolled in plenty of courses during the semester and so my time is limited. I try my best to make time to be readily | ||
| available to students. Assuming I get the schedule I want, I will ideally hold my office hours from 2:40-3:40pm on Tuesdays | ||
| and Thursdays. This is right after the second section of the course, my office hours will normally be held on the Third Floor | ||
| of Mudd but for the first bit, especially during shopping period I will be holding my office hours virtually. Please refer | ||
| to the Google Calendar on courseworks for exact details. | ||
| </p> | ||
| <p class = "section-text"> | ||
| Traditionally, my office hours have tended to be some of the more packed ones among the teaching staff, however several | ||
| factors influence how busy office hours are. Firstly is when I hold my office hours, picking a time in the middle of the | ||
| day can be both good or bad depending on how everyone else's schedules are. Another factor would be how close we are to a | ||
| homework deadline. I am anticipating Professor Cannon to make homeworks due on the Sunday/Monday prior to lectures for the | ||
| given week. This would mean that Thursdays may be busier than Tuesdays. | ||
| </p> | ||
| <h1>Tips for Office Hours</h1> | ||
| <p class = "section-text"> | ||
| I would consider myself relatively forgiving and kind when it comes to office hours, this is especially true in the | ||
| first half of the course. Just like the course, my expectations for what you should be able to do on your own grow as | ||
| the semester progresses. Since the course does get harder as time moves forward, chances are the questions you have will | ||
| become more complex and will require more of my time. In order to maximize my effectiveness and minimize the time you spend | ||
| waiting to receive assistance be sure to follow these tips prior to and during office hours. | ||
| </p> | ||
| <h3>1. Be Familiar With Lecture Material</h3> | ||
| <p class = "section-text"> | ||
| This does not mean you need to have completely understood what was shown in lecture, but you should be able to recall | ||
| the concept itself if I asked. For example assuming you had covered Binary Search, you should be prepared to answer | ||
| "What is Binary Search?" need not worry about questions like "How can we prove the complexity of Binary Search?". | ||
| Assuming you missed lecture, then I would advise skimming the lecture notes I post on the homepage where the schedule is. | ||
| </p> | ||
| <h3>2. Arrive as Early as Possible to Office Hours</h3> | ||
| <p class ="section-text"> | ||
| Like most people, I am most understanding, patient, and useful towards the beginning of office hours so if you know | ||
| you need assistance and are able to, the early bird gets the worm. | ||
| </p> | ||
| <h3>3. Do not Expect the Teaching Staff to Write your Code for You</h3> | ||
| <p class ="section-text"> | ||
| Generally, it is bad practice for any member to touch and write code on your machine. The main exception being that there | ||
| is an extensive, nontrivial bug that requires relatively focused debugging. Along with this, you shouldn't go to office hours | ||
| expecting solutions to the problem sets. The expectation from office hours is that you better understand the concepts necessary | ||
| to complete the homework rather than the specifics needed solely for that particular homework. | ||
| </p> | ||
| <h3>4. Collaborate with your Classmates</h3> | ||
| <p class="section-text"> | ||
| You are encourage to talk to those next to you to help each other out, iron sharpens iron. The person next to you | ||
| might have the answer to whatever you are stuck on so it never hurts to ask. If you are curious about what boundaries | ||
| exist when it comes to academic honesty, please review the course policies page for more. | ||
| </p> | ||
| <h3>5. Make Use of ED Discussion</h3> | ||
| <p class="section-text"> | ||
| If you have a question that does not require extensive debugging and is more related to course material and | ||
| course logistics, please make a public post on the discussion platform accessible via courseworks, you have | ||
| the option to make your post anonymous if you do not wish for your name to be made public as well. | ||
| </p> | ||
|
|
||
| </section> | ||
|
|
||
| </main> | ||
|
|
||
| <footer> | ||
| <p class = "footer-text">© 2024 Griffin Newbold Powered by GitHub</p> | ||
| </footer> | ||
| </body> | ||
| </html> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,90 @@ | ||
| <!DOCTYPE html> | ||
| <html> | ||
| <head> | ||
| <link rel="shortcut icon" href="../../../../favicon.ico" type="image/ico"> | ||
| <meta charset="UTF-8"> | ||
| <meta http-equiv="X-UA-Compatible" content="IE=edge"> | ||
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | ||
| <title>COMS W1004 Introduction to Computer Science and Programming in Java</title> | ||
| <link rel="stylesheet" href="../../../../styles.css"> | ||
| </head> | ||
| <body> | ||
| <header> | ||
| <nav> | ||
| <ul class="horizontal-list"> | ||
| <li><a href="/">Griffin Newbold</a></li> | ||
| <li><a href="/teaching.html">Teaching</a></li> | ||
| <li><a href="">Sample Code</a></li> | ||
| <li><a href="/teaching/2024/spring/java-1004/officehours.html">Office Hours</a></li> | ||
| <li><a href="">Exam Materials</a></li> | ||
| <li><a href="">Course Syllabus</a></li> | ||
| <li><a href="">Course Policies</a></li> | ||
| <li><a href="/teaching/2024/spring/java-1004">1004 Homepage</a></li> | ||
| </ul> | ||
| </nav> | ||
| </header> | ||
|
|
||
| <main> | ||
| <section class="section1"> | ||
| <h1>Course Policies Overview</h1> | ||
| <p class = "section-text"> | ||
| There are several different policies that you should be aware of throughout the duration of the course. These are | ||
| subject to change, and if there is a conflict between what is stated below and what is stated on courseworks or the | ||
| professor, then it is better to trust the professor and courseworks instead. | ||
| </p> | ||
| <h2>Academic Honesty Policy</h2> | ||
| <p class = "section-text"> | ||
| You are expected to submit work that is solely your own, that being said, you are free to collaborate and use | ||
| resources like google and stackoverflow, if you do anything that is not your own work, please cite your source | ||
| in the README.txt that you submit, or if it is a written assignment either inline or at the bottom. | ||
| </p> | ||
| <h2>Regrade Policy</h2> | ||
| <p class = "section-text"> | ||
| Assignments you submit are generally returned to you in 1-2 weeks following the passage of the late deadline. Once an | ||
| assignment has been returned the regrade period will open after 24 hours and will last for a week. It can take an extremely | ||
| long time for a regrade to be resolved in the event it is warranted, all regrades will be resolved prior to the end of the | ||
| semester. If you have an issue with *how* many points were taken off, that is not an issue the TAs deal with and if you'd like | ||
| to question the point allocations of the homeworks, you are more than welcome to email the professor. When reviewing the grades | ||
| via gradescope all item boxes will be shown. ONLY BOXES WITH A CHECKMARK NEXT TO THEM have been applied to your submission. That | ||
| being said, use the presented rubric to see if any points were taken off but you believe they shouldn't have been, it is very possible | ||
| for a TA to make a mistake while grading. Be polite when submitting requests and provide enough detail to make our jobs easier. TAs have | ||
| the final say so if a TA says you do not get points back do not submit additional requests attempting to fight it. Grading is anonymous from | ||
| both ends, we do not know who we are grading and you do not know who is grading you, this way all grading remains as objective as possible. | ||
| </p> | ||
| <h2>Late Submissions Policy</h2> | ||
| <p class = "section-text"> | ||
| You are provided a set amount of late days to use over the course of the semester, it is usually 9 days, these can/should be | ||
| used for emergencies or other things like religious observances. You can use 7 of these days per assignment but any amount of | ||
| a day constitutes a single late day, i.e. 12:01am means 1 late day is gone. You are expected to keep track of how many late days | ||
| you use and try not to run out as work submitted late without proper allocation of late days remaining generally isn't accepted. | ||
| That being said, it is very much still in your best interest to submit all assignments including late ones. | ||
| </p> | ||
| <h2>Exam Policy</h2> | ||
| <p class = "section-text"> | ||
| All exams are closed book, closed internet, no calculator, etc unless otherwise stated. Those with the proper disability | ||
| accommodations will take in person exams where they normally take their exams and will have the proper extensions and/or | ||
| other resources applied there. For all others who take exams within the classroom, for the midterms you will be expected | ||
| to complete the exam within the class time (75 minutes). The final exam is a 3 hour comprehensive exam that is held during | ||
| finals week. If you believe there is a conflict with the exam for whatever reason please email Professor Cannon as soon as possible. | ||
| If you can email him prior to the incident occurring please do so in order to arrange a potential make up. For those who do not | ||
| complete the exams during the times they are offered and has no makeup arranged will receive a grade of 0. | ||
| </p> | ||
| <h2>Final Grade Policy</h2> | ||
| <p class = "section-text"> | ||
| This class is curved. I repeat the class is curved, it has always been curved and I do not see any reason for this | ||
| changing anytime soon. The curve is set at a B/B+ average. Students who enroll in the course but submit nothing will | ||
| receive a UW in the course. You are typically provided the median/average score when assignments/exams are returned to | ||
| you. This course, despite being an introductory 1000 level course, is not easy for most people that take it. If you are | ||
| expecting an easy A, assuming you have no prior experience then don't count on it. Getting an A is very much possible and | ||
| certainly a rewarding experience. | ||
| </p> | ||
|
|
||
| </section> | ||
|
|
||
| </main> | ||
|
|
||
| <footer> | ||
| <p class = "footer-text">© 2024 Griffin Newbold Powered by GitHub</p> | ||
| </footer> | ||
| </body> | ||
| </html> |