We will use Slack, an online collaborative tool for most class messaging and help. Details in class. We will also write slack integrations!
Groups will meet with the course instructor weekly in class to discuss progress and plan next steps. Ask questions, be proactive, we’re here to help!
At any point you should also feel free to tag your instructor/TAs in any github issues:
🚀 Assign to @timofei7 @nataliesvobodain GitHub for grading and feedback.
Grading of collaborative team-based work will be done based on GitHub pull requests. Proper git flow will be introduced early on in the term. Using version control will become second nature to you. The final grade will be based on a combination of weekly performance, class demos throughout the term, preset milestones, and peer evaluation. Grading will take into account GitHub pull requests. Proper git flow will be introduced early on in the term and will be required for all groups. Since projects are a team effort, you will earn a group grade along with a modifier for individual performance. In extreme cases individuals may be dropped or raised several letter grades from the group. For instance, if you were the star performer on the team and committed the large majority of code but your teammates didn’t pull their weight so the project wasn’t quite up to standards: the team might receive a B- but you might get an A. Alternatively if you slacked and contributed only a few lines to some documentation to boost your git commit count, we will notice and you might get a D even if your teammates pulled off an impressive project without you and the team received an A- overall. We will read your code and we will have regular code reviews.
We understand that a large part of software engineering involves learning from examples, searching for solutions, working with ChatGPT and other AI tools, and integrating your research into your own code. We want you to learn from all available resources while still learning the concepts necessary to generate your own solutions and become capable software engineers. You should understand all the code that you write/integrate, and be able to walk through it. Most critically, to avoid an Academic Honor Violation you need to cite any sources that you use in your process.
The Internet will be a large source of information and help to you as you do your assignments in this class. We want to encourage you to scour the internet / stackoverflow / chatGPT for help, but you must credit any solutions you find in comments in your code specifying where you found them and what you took from them. If you copy/paste code without attribution, you are violating the Academic Honor Principle. You will not be penalized for copied code as long as it is properly attributed. Obviously don’t copy/paste the whole project, as you may not get full credit, but even if you do at least you will not facing the COS.
Remember: Just cite it!
Make your in-code citations look something like this:
// adapted from: <http://stackoverflow.com/someurl>
// this method does x and y
or
// copied off of Cameron Howe's code for this assignment
// this method does x and y
(policy adapted from: https://integrity.mit.edu/handbook/writing-code)