Table of Contents
Blocks
Hat Block
It looks like a hat and it's purpose is to start a stack of blocks and there shaped to attach blocks to belowStack / Command block
It looks rectangular and it can stack itself on top or belowC block
They look like a big stack block but has it has a space in between which allows it to have blocks inside of itReporter/Oval blocks
The reporter block reports value in the form of numbers and fits in oval inputs for other blocksBoolean Blocks
The boolean returns a condition as either true or false and fits in hexagonal in other blocksRepeat Block
The repeat block is a C block and it's purpose is to repeat code as many times as you tell it to inputWait until block
The wait until block allows the code wait until set value or input happensIf then block
The If then block is a C block that lets other blocks go beneath it and it makes sure if something happens, it then proceeds the next part of the codeForever Block
The forever block is a C block that lets other blocks go beneath it and it makes sure the blocks connected to it repeat foreverConcepts
Sequence
` The sequence is an important part of coding because everything happens because of it and it gives everything an orderParameters
A parameter changes the command input which can change the commands original inputLoops / Iterations
The loops cause the code to do something for an amount of time depending on what it isSensors
There are different sensors on the Vex IQ bot that can help the robot navigate it's path (Ex: Distance, color, and Bumper sensor)Booleans & Conditions
Booleans are the true/false information and they can control if something happens, the bot moves, and if false they could do somethingSense -> Think -> Act
A robot can sense it's nearby surroundings, if it perceives something, it thinks what to do before it actsComparisons
Comparisons help returns the boolean result: They can help your code run, make decisions, run loops, and control logicCoordinates
X and Y describes the robot's location and it can help pinpoint where you are and some codes can use that to get somewhereConditionals
Conditional programming uses specific decision-making statements like if, and else direct how a program runs based on whether a condition is true or falsePatterns
Repeated behavior can help some certain codes to look cleaner and lets patterns to repeatVocabulary
VR Robot + Playground
The VR robot is the main use for VEX VR playground. The playground is where the VR robot does the stuffProgramming Language + project
The programming language for VEX VR is block code/scratch and there is many projects you could useBehavior + Command
Behavior is when the bot does it's commands. Commands is what the bot is told to doDrivetrain
The drivetrain is the bots motion system and how it moves/turnsLoop + Iteration
The loop can do a lot of things do a stack, they could repeat it a certain number of times, do it forever + moreSensor + Bumper sensor
The sensor is something the bot has that lets them traverse through the playground. The bumper sensor can bump into physical objectsBoolean + Condition
Booleans are the True and False of coding. They could input a certain value or code as True or False based on a condition that could be metDistance Sensor + Threshold
The distance sensor is a sensor used by the Vex VR bot and based on a certain distance the bot might do an action or go to a locationCoordinate plane + X/Y Coordinates
The coordinate plane is used by the Vex VR system and if you press a tab you can see the X/Y location of the bot, it can be used in codes for the distance sensor but it's also helpful for tracking where the bot isLocation Sensor
The location sensor works a lot like the distance sensor but it goes hand to hand much better and it's made for specific task using the location of the terrain and botComment
The comment block can be used to remember certain details about the code your writing, it doesn't interfere with the code and it's basically the sticky note of codingEye Sensor
The eye sensor is another sensor used by the bot, unlike the other sensors it's used so the robot can specifically look for something with it's own vision like an object or colorConditional Statement
A conditional statement is something that code deems conditional and if certain thing is true or false it creates a statement for the other code to continueMarkdown Style Guide for Coding Notebooks
Follow this guide to keep your coding notebook clear, consistent, and professional.
This ensures your notes are easy for you (and others) to read later.
Headings
When to use: Organize your notebook into sections (like days, topics, or projects).
-
#for the notebook title (use once at the top). -
##for each day or major topic. -
###for subsections (like “Notes”, “Practice”, “Reflections”).
Example:
My Coding Notebook
Day 1
Notes
Practice
Text Formatting
When to use: Highlight important ideas or add emphasis.
Use bold for key terms or definitions.
Use italic for emphasis or side comments.
Use inline code for keywords, functions, or commands.
Example:
Class = a blueprint for objects
Remember: always test your code
Use System.out.println() to print
Code Blocks
When to use: Anytime you write multiple lines of code.
Inline code for short snippets.
Fenced code blocks with language for full examples.
Example:
public class Hello {
public static void main(String[] args) {
System.out.println("Hello World!");
}
}
Lists
When to use: Organize steps, notes, or key points.
Numbered lists for sequences or steps.
Bulleted lists for unordered ideas.
Example:
Define the class Write the main method Test your program Variables
-
Loops
-
Conditionals
Checklists
When to use: Track progress on assignments or tasks.
Example:
[x] Complete coding warm-up
-
Finish project draft
-
Reflect on learning
Blockquotes
When to use: Call out notes, reminders, or teacher comments.
Example:
💡 Remember: Loops repeat code until a condition is false.
Tables
When to use: Compare values, track progress, or organize data neatly.
Example:
| Task | Status | Notes |
|————–|————|—————–|
| Homework 1 | Done # | Submitted |
| Homework 2 | Pending | Needs review |
Links & Images
When to use: Add references, resources, or visuals.
Example:
To make an image that is a link, paste the image, then add the following before it, replacing website address with the link:
And after the image info, add: </a>
Collapsible Sections
When to use: Hide solutions, extended notes, or extra details.
Example:
Click to reveal solution
System.out.println("Answer: 42");Footnotes
When to use: Add references or side notes without cluttering the page.
Example:
This concept is related to object-oriented programming.1
Style Rules
Consistency matters more than creativity
Always use headings to structure your notes.
Always use code blocks for multi-line code.
Clarity first
Bold key terms.
Use lists instead of long sentences when outlining steps.
Professional tone
Don’t mix casual notes with formal work in the same section.
Use blockquotes for reflections or teacher feedback.
Track your learning
Use checklists to mark what’s done.
Use collapsible sections if you want to hide answers until review time.
Bottom Line:
Headings = Structure
Bold/Italic = Emphasis
Code blocks = Code
Lists = Steps/Ideas
Tables = Organization
Checklists = Progress
Blockquotes = Notes/Tips
Collapsible = Hide/Show detail
Keep it simple, consistent, and clear.
-
See “Objects and Classes” in your textbook. ↩