Modules
Follows the slides, in order.
- M03 topics
Introduction to Programming
Not started
- M14 topics
Algorithm: Pseudocode
Not started
- M23 topics
Algorithm: Flowchart
Not started
- M3a3 topics
Introduction to C, Part 1
Not started
- M3b6 topics
Introduction to C, Part 2
Not started
- M44 topics
Function in C, Part 1
Not started
- M5a5 topics
Control Structures, Part 1
Not started
- M5b4 topics
Control Structures, Part 2
Not started
- M73 topics
Pointers in C
Not started
- M82 topics
Function in C, Part 2
Not started
- M95 topics
Introduction to Array
Not started
Extra practice
Not in the slides, but on the way to the lab exams — their string problems, for one, need everything here.
Practice problems
Whole problems in the shape CisCode sets them, worked four ways that come before and around writing the solution yourself. Each builds on the last.
Step A
Plan it
Read a problem the way CisCode sets it and name the patterns a solution needs — a counter, a digit loop, a found-it flag — before writing a line.
StartStep B
Build it
Put a solution's shuffled lines back in order, leaving out the one wrong twin. Marked by running the tests, so any order that works counts.
StartStep C
Fill it in
Write the one missing condition, expression or statement. Marked by the tests, not by matching a key, with the failing test there to step through.
StartStep D
Break it
A solution passes the sample but hides a flaw. Find the input — a zero, a tie, the edge of a range — that a hidden test would use against it.
Start
Reference
C tracer
Paste any Programming 1 program, give it input, and step through it line by line. Paste a failed test's expected output too, and find the exact step where yours went wrong.
OpenSyntax sheet
One page: placeholders and escape sequences, operator precedence, the conversion rules, the library functions, and the loop forms — each with the mistake it invites.
Open