CT 301 – 001 & 801
Basic Course Information
Course Name: Introduction to C++
Semester: Spring 2026
Credits: 2
Prerequisites/Co-requisites: CS 162 with a C or CS 164 with a C
Meetings/Times: Monday, Wednesday12:00 PM to 12:50 PM
Location: CHEM A103
Instructor Information
Instructor Name: Logan Seabolt
Email: Logan.Seabolt@colostate.edu
Phone: +1 970-491-5861
Office Location: Computer Science Building 242
Office Hours/Student Hours: Fridays 12:00 PM to 1:50 PM & By Appointment
Communication Policy:
Communication is preferred through one of 3 methods.
- The Course Email (compsci_ct301@colostate.edu)
- The instructor’s personal email. HOWEVER please include the course number (CT 301) in the subject line. This helps me keep track of your emails and better support you.
- Microsoft Teams. If it is a question about grades an email is preferred in this case.
- I will do my best to respond to your emails within 1 Working Day (Weekends & University Holidays not included)
- If I do not respond within 1 Working Day, please send a follow up email
- I encourage you to join me during Student Hours to discuss grades, homework assignments, general course knowledge.
- If you have missed class, please reach out as soon as you are able so we can get you access to lecture materials.
Course Materials
Course Description & Objectives
CT 301 introduces students to the C++ Language. In this course students will learn the fundamentals of modern C++ and learn to develop code from the ground up but also maintain a code base in the language.
Assignments’ Description
Assignments in this course are 2 weeklong coding assignments except for the final assignment, which is a smaller assignment that only takes 1 week to complete.
Assignments in this course are designed with the goal to develop a large code project that you improve over the duration of the semester. Each assignment is worth 70 Points. Totaling to 560 Points. However assignments only account for 50% of the grade that means you can earn up to 60 Points of extra credit by doing well on the assignments!
Course Schedule – Alignment of Course Topics, Learning Outcomes, and Assessments
This will be updated with more information during the semester
| DATE | Assignment | Goals | Due Date |
| 01/29 | HW0 | Submitting Assignments, Makefile, Basics of C++ | 02/02 9:30 AM |
| 02/02 | HW1 | File Reading and Validation | 02/16 9:30 AM |
| 02/16 | HW2 | OOP Header Files and Classes | 03/02 9:30 AM |
| 03/02 | HW3 | Code Merging and Extension | 03/13 11:59 PM (Open until 03/23 9:30 AM) |
| 03/23 | HW4 | Inheritance | 04/06 9:30 AM |
| 04/06 | HW5 | File I/O | 04/20 9:30 AM |
| 04/20 | HW6 | Data Structures | 05/04 9:30 AM |
| 05/04 | HW7 | Speed Test | 05/15 11:59 PM |
Morgan Library Services Desk
The Morgan Library Services Desk provides both research (ph. 970-491-1841) and technical (ph. 970-491-7276) support. In addition, you can contact a librarian for assistance at Ask Us! or find a research guide at Research Help.
Teaching Philosophy
Expand on any of the statements below to make this your own:
- I believe that each and every student who enrolls in this course belongs here.
- We recognize and celebrate the diverse backgrounds, experiences, and perspectives that each student brings to the classroom.
- Learning is a collective effort, and we encourage active participation from all students. Through student-student interactions and meaningful dialogue with instructors, we aim to create a dynamic and engaging academic atmosphere.
- Our role as educators is to provide the resources, encouragement, and community necessary for students to reach their full potential.
- In this classroom, we will recognize our differences as our greatest strengths.
- I’m always happy to discuss strategies to improve access and help you to locate other campus resources that can assist you.
- I am committed to supporting your success and well-being.
- My goal is to ensure that all students feel safe, heard, and empowered to engage fully in their learning.
Classroom Norms (or Community Agreement)
- We will listen to each other with the intent to understand different perspectives
- We will ask questions when we have them
- If you feel the need to ask a question but don’t think you can ask it to the instructor directly. There will be an Assigned “Questions” TA who you can send question to during lecture to ask of the instructor.
- We will make sure everyone’s voice is heard
- We will not disrupt the learning of others. This includes but is not limited to, Playing Video Games during lecture, watching videos or other distracting media during lecture, or having unrelated conversations during lecture
- We will respect the learning journey. Coding is not a linear process, mistakes and failures are a natural part of the coding cycle. Any progress is good progress and failures are just another step on the path.
CSU Principles of Community
Inclusion: We create and nurture inclusive environments and welcome, value and affirm all members of our community, including their various identities, skills, ideas, talents and contributions.
Integrity: We are accountable for our actions and will act ethically and honestly in all our interactions.
Respect: We honor the inherent dignity of all people within an environment where we are committed to freedom of expression, critical discourse, and the advancement of knowledge.
Service: We are responsible, individually and collectively, to give of our time, talents, and resources to promote the well-being of each other and the development of our local, regional, and global communities.
Social Justice: We have the right to be treated and the responsibility to treat others with fairness and equity, the duty to challenge prejudice, and to uphold the laws, policies and procedures that promote justice in all respects.
Course Policies (late assignments, make-up exams, revision policy, etc.)
Assignment Extensions/Make Up Work
These will rarely be given and only on a case-by-case basis.
Generally, if it is an emergency (Medical Absence, Family Incident, Car Breaks Down, Personal Emergency, etc.) then please contact the instructor with documentation of the incident anything with a date/time stamp or a signed document from a professional will work.
If you know you will be absent from an exam or during the due date of an assignment, please contact the instructor at least 72 hours prior to the due date or exam date. An extension or Alternative date for the exam can be considered, but a retroactive exam absence will not be allowed. Please provide documentation that shows the time conflict with the due date or exam date.
Late Policy
The Review quizzes have a due date but are open with 0 penalty until the “Until” date after which the assignment closes. Quizzes always have a 1 week period after their due date before they close.
All other materials in the course have a 0-tolerance late policy. Once the due date passes the assignment in closed unless there has been a prior extension discussion the assignment will lock and the grade earned at that time will remain.
Academic Misconduct Policy
This course uses a Whitelist policy for what is allowed on assignments. The following are NOT considered Academic Misconduct to use on homework assignments
- Any Material Found on the Course’s Canvas
- Any Material Given in lecture
- Cited Material from UTAs or the Instructor’s Office Hours
- Anything from the Official Documentation Pages for C++ Documentation Website
Anything outside of the above list MAY be considered academic misconduct
The following are EXPLICITLY considered Academic Misconduct in this course
- Using any form of AI Coding Assistance. Including but not limited to:
- ChatGPT
- Grok
- Co-pilot (Including the Co-pilot VS Code Add On)
- Copying or Stealing code from another student current or previous
Academic Misconduct in any form is NOT tolerated in this course. If you are found at fault for Academic Misconduct in this course, you will be given an F and an Academic Misconduct report will be filed for the incident. Do not risk your entire grade for the chance at slightly better grade.
All cases of potential Academic Misconduct will be thoroughly investigated, and all students will be given a chance to meet with the instructor to discuss their case and provide documentation and evidence to support their work. Keep in mind that an Investigation does NOT guarantee that Academic Misconduct occurred, only that something was found suspect and deemed necessary to review.
This course is first and foremost a language learning course. You will only learn from this class what you put into it. In a professional environment you will likely have access to Generative AI Tools along with very complex code bases. Knowing the language without the support of Generative AI will make you a more valuable asset to any industry. Generative AI is not a replacement for skill, but when combined with skill it can take a good programmer to even greater heights. Without skill however there is a limit to what you are capable of performing with Generative AI.
The Instructor reserves the right to apply a lesser penalty in appropriate cases on a case by case basis
Grading Policy
Assignments are due at 9:30 AM on Mondays. Assignments are graded on a daily basis at 12:00PM (Noon) Each day. Before the due dates assignments are graded on a preliminary grading script. These grading scripts grade only a PORTION of the grade. The final grade will not be run until after the Until Date of the assignment.
There are no Late or Make Up assignments in this course. Once the due date passes the assignment closes and no further attempts may be made on the assignment.
If you have conflict with a due date please contact the professor at least 72hours prior to the due date with documentation of the time conflict. See the Assignment Extension Policy above.
| ASSIGNMENT | GRADE POINTS | GRADE PERCENTAGE |
| Coding Assignments | 500 | 50% |
| Weekly Reviews | 300 | 30% |
| Code Review | 200 | 20% |
| Total: | 100 % |
Letter Grade Breakdown
| LETTER GRADE | POINTS NEEDED |
| A+ | 970-1000+ |
| A | 900-969 |
| B+ | 870-899 |
| B | 800-869 |
| C+ | 770-799 |
| C | 700-769 |
| D | 600-699 |
| F | 0-599 |
Additional Syllabus Information and Policies
Please add to your syllabus this QRN code and/or short link (https://col.st/2FA2g) with a statement informing students that the linked page provides policies relevant to their courses and resources to help with various challenges they may encounter.
