First draft 1501 course guide #387
Conversation
ncbarta
requested review from
Zmwang622,
varughese,
azharichenko,
rohit-ganguly,
Richie78321,
agrattan0820,
dylanfeehan and
EParmar18
as code owners
|
|
||
| You do not want to be holding on to an incomplete project the last 2-3 days before it's due. That's likely when the next project is being introduced - which means you'll have extra things to think about. Also, TA office hours (which you should be going to if you need help) get really busy towards the deadline, so getting help may be a challenge. | ||
|
|
||
| > Don't cheat. It's very easy to catch. Beyond the typical meaning of cheating: *don't cheat yourself*. Did you write some code that you don't fully understand? Figure it out. Do it right. |
There was a problem hiding this comment.
It's very easy to catch. to It's very easy to get caught.?
There was a problem hiding this comment.
Also mention using TAs and tutors as a resource. "Figure it out" gives off the impression that they may feel they may be on their own
| - 🌪 **NEW SPRING 2023** Machine Learning: Overview of the algorithmic foundations of machine learning. | ||
| - Approaches | ||
| - Supervised learning | ||
| - Unsupervised learning | ||
| - Semi-supervised learning | ||
| - Reenforcement learning | ||
| - Clustering | ||
| - K-means | ||
| - Initial assignment | ||
| - Lloyd's algorithm | ||
| - Distance metric |
There was a problem hiding this comment.
With 1503 becoming a requirement, is this still true? Will this be included in 1501? I guess time will tell
There was a problem hiding this comment.
Yeah, we'll have to keep our eyes on it.
| Code is meant to be read too! | ||
|
|
||
| I'd recommend reading the author's implementations and making sure it lines up with what you read from the book. Once you can draw the connections, move on, or even experiment with alternate implementations. Why did the author do it that way? |
There was a problem hiding this comment.
Mention that most profs have author's code that they provide for you as the semester goes on. Sometimes, in Farnan's project specifically, he lets you directly pull from this code for your data structures. So make a point that this should be something that's referenced
|
|
||
| You do not want to be holding on to an incomplete project the last 2-3 days before it's due. That's likely when the next project is being introduced - which means you'll have extra things to think about. Also, TA office hours (which you should be going to if you need help) get really busy towards the deadline, so getting help may be a challenge. | ||
|
|
||
| > Don't cheat. It's very easy to catch. Beyond the typical meaning of cheating: *don't cheat yourself*. Did you write some code that you don't fully understand? Figure it out. Do it right. |
There was a problem hiding this comment.
Also mention using TAs and tutors as a resource. "Figure it out" gives off the impression that they may feel they may be on their own
ncbarta
force-pushed
the
1501-course-guide
branch
from
6bd9c4a to
222d113
Compare
No description provided.