• Computer Operation: Files and File Management, Software, Hardware, Binary Code
• Internet and Networking Basics
• Google Workspace (Drive, Docs, Slides)
• Electronic Communications and Best Practices
• Online Safety, Security, and Recognizing Online Threats
• Graphics and Image Manipulation
• Programming basics in C#
• Website Creation using HTML5 and CSS
• 3D Modelling and Animation Basics

• The classroom computers are PC's running Windows 10 with 8 GB of RAM.
• Classroom Computer Use: The lab computers are to be used for class projects ONLY during class time. Students who use computers for activities that are not class related (email, surfing, homework for other courses, chat, games) will lose computer privileges.
• Computers at Home: Most software is available online for free download for Windows machines. Therefore most students will be able to work on course material from home. Students without a computer, running Linux, or with a MacIntosh computer, may need to make use of classroom and school computers outside of class time. The computer lab will be open most lunch hours.

• Arrive Before the Bell: Class begins at the first bell. Late arrivals can mean a missed quiz, missed material, and be a disruption for the rest of the students. If class has started when you arrive, come in quietly without disrupting the class.
• Attendance is mandatory. A lot of material is covered each day and most students find it difficult to catch up even after missing just one class. In all group projects, your group depends on your commitment to the project in the class.
• Missed Classes: Students are responsible for all information covered in class. If a class is missed, it is up to the student to check the mdinfotech.net and Google Classroom for resources and assignments and to get notes and assignments from another student. It is beneficial to get the contact information of students in your class for this purpose.
  * Missed Quiz:
  
  • if an absence is unexcused, the student will receive a score of zero
  • if an absence is excused, the quiz will not be counted toward the final grade
  * Missed Exercise or Assignment:
  
  • it will be assessed when you return to school
  * Missed Test:
  
  • if an absence is excused, the test will be written on the first day that the student returns to class
• Cell Phones must be on silent and in your bag. On occasion, cell phones may be used to take photos of notes and demonstrations in class. For future reference, these images may only be accessed from an online resource such as Google Drive.
• Food and Drink Period A-D students are not allowed to bring food and drink into the lab. Please eat/drink in the hallway before/after class.
• Assignments: All assignments are to be complete and handed in on time. Most assignments are posted on the web site. Late assignments may be accepted until the solutions are given or the unit ends, whichever comes first. Certain assignments, if submitted AFTER it has been marked and returned to the class, or AFTER solutions have been posted, will be eligible for up to a 50% completion mark.
• Academic Integrity: Your work must be your own. Only Group work is group work. Individual Assignments must be completed individually. If a student submits work that they did not write a mark of zero will be given.
• Homework: Students will not always be able to complete assignments in class time. The lab will be open at least most lunch hours for extra computer time. In addition, work may be completed at home.
• Notes and handouts are to be kept in a binder or notebook in an orderly fashion.

To support your learning and growth as a programmer, it is essential that all code you submit is your own original work. The use of AI tools such as ChatGPT, GitHub Copilot, or any automated code-generating services is not permitted in this course unless specificed otherwise..

This policy exists because:

• You’re here to build your own coding skills, not just get the right answers.
• Learning to solve problems on your own builds confidence and long-term success.
• You need to understand your code well enough to explain and build on it.

If you’re stuck, that’s okay — getting stuck is part of learning. You are encouraged to:

• Ask questions in class
• Collaborate appropriately with peers (without copying)
• Refer to your notes, course materials, and documentation

Submitting AI-generated code will be considered a violation of academic integrity. If you’re unsure about whether something is allowed, please ask.

• This course is challenging and requires patience.
• If you fall behind, it can be difficult to catch up—stay on top of your work.
• Pay close attention during lessons.
• Don’t hesitate to ask questions if you don’t understand something.
• You need to do more than just listen—actively engage and participate.

• If you use class time effectively but still need support, book a lunch appointment with Ms. Wear.
• Getting help early prevents frustration later.

• Mistakes are essential to learning.
• When you encounter an error, take time to understand why it happened.
• Each error is a stepping stone to better understanding.

• Collaborate respectfully—discuss concepts, not code.
• One person’s strength can support another’s challenge.

• After solving a problem, try changing it—explore variations.
• Experiment with code: test, tweak, and even make mistakes on purpose to observe the results.
• The more you play with code, the more you’ll understand.

1. Read the assignment description thoroughly—know what you’re supposed to do.
2. Plan your approach using a flowchart or notes.
3. Write your program step by step.
4. If it doesn’t compile, check carefully—line by line—for errors.
5. If stuck, ask a peer or the teacher. Don’t struggle in silence.
6. Test your code in blocks to isolate problems and debug more easily.

• It’s normal to feel unsure—ask questions anyway.
• Don’t worry about “looking stupid”—others likely have the same questions.
• Everyone starts somewhere. No one expects perfection.

• Don’t give up!
• Ask peer tutors for help, explore tutorials, and reread confusing material.
• Panicking doesn’t help—stay calm and focus on learning, bit by bit.

• Mistakes don’t mean you’re bad at coding.
• The more errors you encounter and solve, the more confident you’ll become.
• Keep trying—each mistake is progress.

• Learning to program is a challenge—but a rewarding one.
• It’s exciting when your code works.
• Keep going—it gets more fun as your skills grow.