Table of Contents
Hi! I'm R.W.! Let's go over some of the aspects of my course and policies to get you acquainted with the way I design my courses. You can also find more specific details in the course Syllabus.
1. What grade do you need? What grade do you want?
Some students have criteria they need to meet in order to get financial aid or VA benefits or maintain visa status or other things. Keep this in mind - once it's towards the end of the semester, it will be harder to catch up on things if you're already really behind!
It is pretty easy to get an A in my class.
Most students who receive F's just don't turn in work all semester. Similar for D's, and C's are usually also missing a big chunk of work. Completing all of the assignments should at least get you a B, if not an A.
I try to make sure all my assignments are pertinent and as concise as I can make them; I don't just create busy work. All of what I design is meant to give you a foundation, scaffolding, and help you learn the concepts, learn how to learn, and practice problem solving.
You can also redo your work. Turn in what you have by the due date - even if it's incomplete - and I'll give feedback and you can fix it up with no late penalty to the updates.
2. Delivery methods: Online or HyFlex
- Online: These courses don't have set meeting times, though I do have links to archived lectures on the topics.
- HyFlex: These courses have a scheduled class time. I will be in
the classroom at the scheduled class time and you can either:
- Attend in person
- Attend via zoom
- Not attend, then watch the archived video later. (Please make sure you watch the archived videos to keep up with course news and topics we cover!)
3. Course supplies
We'll cover set up in another section, but the supplies for this course will be:
- Textbook: (This document)
- Zoom: You can use this to remotely join office hours or, if we have a scheduled class, you can removely join that way.
- GitLab account: We will be using source control for storing source code throughout the semester. I'll have more info on setup later on.
- Compiler: MinGW for Windows, g++ for Linux, and Mac technically uses clang but you can use it through the g++ comamnd.
- Debugger: gdb for Windows and Linux, lldb for Mac.
- Additional: make and the git software.
- IDE: VS Codium (preferred) or VS Code.
- You can use another code editor like vim, emacs, geany, etc. if you prefer (please not Visual Studio or Code::Blocks). We will be building and debugging our programs from the terminal.
If you get stuck on any part of setup (covered later), please reach out to me immediately so we can get it ironed out! The best way to contact me is via the Canvas inbox.
4. Computer skills and study skills
I expect you to have these base level computer skills. If you do not, you can find tutorials online and on YouTube.
- Navigating your Operating System, including:
- Installing software
- Running software
- Locating saved files on your computer
- Writing text documents, exporting to PDF
- Taking screenshots
- Editing .txt and other plaintext files
- Navigating the internet:
- Navigating websites, using links
- Sending emails
- Uploading attachments
For study skills you'll need to be able to keep up with dates and notes that you can reference back while working on assignments. You'll be practicing problem solving skills as well. You don't need to be a master of these yet, but you will be getting more practice this semester:
- Breaking down problems - Looking at a problem in small pieces and tackling them one part at a time.
- Organizing your notes so you can use them for reference while coding.
- Reading an entire part of an assignment before starting - these aren't step-by-step to-do lists.
- Learning how to ask a question - Where are you stuck, what are you stuck on, what have you tried?
- Recognizing when additional learning resources are needed and seeking them out - such as utilizing JCCC's Academic Achievement Center tutors.
- Managing your time to give yourself enough time to tackle challenges, rather than waiting until the last minute.
How to ask questions - When asking questions about a programming assignment via email, please include the following information so I can answer your question:
- Be sure to let me know WHICH ASSIGNMENT IT IS, the specific assignment name, so I can find it.
- Commit and push your code to the GitLab server so I can view it.
- Include a SCREENSHOT of what's going wrong.
- What have you tried so far?
5. Course attendance
I count attendance as completing one or more assignments assigned for a given week.
First week attendance
During the first week of classes, instructors are required to log student attendance. Students who have not attended during the first week of classes will get auto-dropped by the system. You can get reinstated into a class if this happens.
(JCCC Reinstatement info: https://www.jccc.edu/admissions/enrollment/reinstatement.html)
For my courses, to be counted as "in attendance", you must finish the setup assignments.
No auto-withdrawal I do not auto-drop students for non-attendance. Make sure to keep on top of the last-withdrawal date and your grade and figure out what is best for you.
6. Due dates
Assignments have a Due Date and an Available Until Date (on the teacher side, it says "End Date" so sometimes I call it that).
- Due dates are set as a guide for when you should have your
assignments in by.
- Assignments turned in after the due date will have a small daily penalty taken from the maximum available score.
- End dates/available until dates are a hard-stop for when an assignment can be turned in. Assignments cannot be turned in after this date.
- Resubmissions:
- Concept introductions: You can take these as many times as you'd like. Highest grade is saved.
- Labs: After I've graded your work and given feedback, you can go back and fix it up and turn it in again for an improved score. If you turned in a good-faith effort originally before the due-date then any fixes after the due date will not have the late penalty. If you're really stuck, turn in what you have and I'll give feedback and you can fix it afterwards.
- Project: The project is a single assignment in multiple parts. You can turn it in multiple times to get updated scores, working towards the final version.
- Exam: The Mastery Check is cumulative and can be taken once a week. Highest score is saved. It is built from a pool of questions so each time might be a little different.
7. Welcome to a programming course!
It feels weird to start a collection of notes (or a "textbook") without some sort of welcome, though at the same time I know that people are probably not going to read the introduction (Unless I put some cute art and interesting footnotes, maybe.) I think that I will welcome you to my notes by addressing anxiety.
7.1. Belonging
Unfortunately there is a lot of bias in STEM fields and over decades there has been a narrative that computer science is for a certain type of person - antisocial, nerdy, people who started coding when they were 10 years old.
Because of this, a lot of people who don't fit this description can be hesitant to get into computers or programming because they don't see people like themselves in media portrayals. Or perhaps previous professors or peers have acted like you're not a real programmer if you didn't start programming as a child.
If you want to learn about coding, then you belong here.
There are no prerequisites.
I will say from my own experience, I know developers who fell in love with programming by accident as an adult after having to take a computer class for a different degree. I know developers who are into all sorts of sports, or into photography, or into fashion. There is no specific "type" of programmer. You can be any religion, any gender, any color, from any country, and be a programmer.
Figure 1: Don't be like Gatekeeper Baby. You can begin coding at any age!
7.2. Challenge
Programming can be hard sometimes. There are many aspects of learning to write software (or websites, apps, games, etc.) and you will get better at it with practice and with time. But I completely understand the feeling of hitting your head against a wall wondering why won't this work?! and even wondering am I cut out for this?! - Yes, you are.
I will tell you right now, I have cried over programming assignments, over work, over software. I have taken my laptop with me to a family holiday celebration because I couldn't figure out this program and I had to get it done!!
All developers struggle. Software is a really unique field. It's very intangible, and there are lots of programming languages, and all sorts of tools, and various techniques. Nobody knows everything, and there's always more to learn
Just because something is hard doesn't mean that it is impossible.
It's completely natural to hit roadblocks. To have to step away from your program and come back to it later with a clear head. It's natural to be confused. It's natural to not know.
But some skills you will learn to make this process smoother are how to plan out your programs, test and verify your programs, how to phrase what you don't know as a question, how to ask for help. These are all skills that you will build up over time. Even if it feels like you're not making progress, I promise that you are, and hopefully at the end of our class you can look back to the start of it and realize how much you've learned and grown.
7.3. Learning
First and foremost, I am here to help you learn.
My teaching style is influenced on all my experiences throughout my learning career, my software engineer career, and my teaching career.
I have personally met teachers who have tried to scare me away from computers, I've had teachers who really encouraged me, I've had teachers who barely cared, I've had teachers who made class really fun and engaging.
I've worked professionally in software and web development, and independently making apps and video games. I know what it's like to apply for jobs and work with teams of people and experience a software's development throughout its lifecycle.
And as a teacher I'm always trying to improve my classes - making the learning resources easily available and accessible, making assignments help build up your knowledge of the topics, trying to give feedback to help you design and write good programs.
As a teacher, I am not here to trick you with silly questions or decide whether you're a real programmer or not; I am here to help guide you to learn about programming, learn about design, learn about testing, and learn how to teach yourself.
7.4. Roadmap
When you're just starting out, it can be hard to know what all you're going to be learning about. I have certainly read course descriptions and just thought to myself "I have no idea what any of that meant, but it's required for my degree, so I guess I'm taking it!"
Here's kind of my mental map of how the courses I teach work:
- CS 200: Concepts of Programming with C++
- You're learning the language. Think of it like actually learning a human language; I'm teaching you words and the grammar, and at first you're just parroting what I say, but with practice you'll be able to build your own sentences.
- CS 235 Object-Oriented Programming with C++
- You're learning more about software development practices, design, testing, as well as more advanced object oriented concepts.
- CS 250 Basic Data Structures with C++
- You're learning about data, how to store data, how to assess how efficient algorithms are. Data data data.
In addition to learning about the language itself, I also try to sprinkle in other things I've learned from experience that I think you should know as a software developer (or someone who codes for whatever reason), like
- How do you validate that what you wrote actually works? (Spoilers: How to write tests, both manual and automated.)
- What tools can you use to make your programming life easier? (And are used in the professional world?)
- How do you design a solution given just some requirements?
- How do you network in the tech field?
- How do you find jobs?
- What are some issues facing tech fields today?
Something to keep in mind is that, if you're studying Computer Science as a degree (e.g., my Bachelor's degree is in Computer Science), technically that field is about "how do computers work?", not about "how do I write software good?" but I still find these topics important to go over.
That's all I can really think of to write here. If you have any questions, let me know. Maybe I'll add on here.
7.5. What is this weird "book"?
In the past I've had all my course content available on the web on separate webpages. However, maintaining the HTML, CSS, and JS for this over time is cumbersome. Throughout 2023 I've been adapting my course content to emacs orgmode documents, which allows me to export the course content to HTML and PDF files. I have a few goals with this:
- All course information is in one singular place
- At the end of the semester, you can download the entire course's "stuff" in a single PDF file for easy referencing later on
- Hopefully throughout this semester I'll get everything "moved over" to orgmode, and in Summer/Fall 2024 I can have a physical textbook printed for the courses, which students can use and take notes in so as to have most of their course stuff in one place as well
- It's important to me to make sure that you have access to the course content even once you're not my student anymore - this resource is available publicly online, whether you're in the course or not. You can always reference it later.
I know a lot of text can be intimidating at first, but hopefully it will be less intimidating as the semester goes and we learn our way around this page.