This is my portfolio showcasing my projects and skills.
Shape/Type: A block with a rounded top and a notch on the bottom.
What It Does: It senses specific triggers (like pressing a key or clicking the green flag) to start a script. It can only sit at the very top of a stack of commands.
Example: when green flag clicked
Shape/Type: Rectangular with a notch on top and a bump on the bottom.
What It Does: It performs a specific action or command. It connects by snapping underneath a Hat block or other Stack blocks to form a sequential list of actions.
Example: move 10 steps
Shape/Type: Shaped like the letter “C” with an opening on the right side.
What It Does: The C-shape represents a loop or a condition. Blocks placed inside the opening will repeat or run based on the block’s rules.
Example: repeat 10 the actions inside run 10 times
Shape/Type: Oval/Round.
What It Does: It holds and reports a value, such as a number or a piece of text. It cannot stand alone; it must be dropped inside the oval-shaped input slots of other blocks.
Example: x position or username
Shape/Type: Hexagonal six-sided with pointed ends.
What It Does: It reports whether a condition is strictly true or false. It has a unique pointed shape so programmers know it can only fit into hexagonal input slots (like conditions for loops and ifs).
Example: touching mouse-pointer?
Shape/Type: C-shape.
What It Does: It runs the blocks placed inside it a specific number of times. Stack blocks go inside its opening.
Example: A repeat 5 block containing a play sound block will play that sound exactly 5 times.
Name: Wait Until Block Shape/Type: Rectangular Stack block with a hexagonal input slot. What It Does: It pauses the execution of the script at that exact point. It needs a Boolean condition (true/false) to look at, and it will only let the script move forward once that condition becomes true. Example: wait until <key space pressed?>
Shape/Type: C-shape with a hexagonal input slot at the top.
What It Does: It checks a Boolean condition. If the condition is true, the program runs the blocks tucked inside the “C”. If the condition is false, the program completely skips those blocks.
Example: if score 10 then say “You Win!”
Shape/Type: C-shape with a smooth bottom no notch underneath
What It Does: It runs the blocks inside it in a continuous loop that never stops on its own. Programmers use it for actions that need constant checking or updating, like gravity mechanics or background music.
Example: forever next costume, wait 0.1 seconds
What It Means: The specific order in which a computer or robot executes instructions, running from top to bottom.
In My Own Words: It is like following a recipe; if you bake the cake before mixing the ingredients, it will not work.
Example: 1. Drive forward. 2. Turn right. 3. Stop. (If you stop first, you never move).
### Parameters What It Means: Values or inputs passed into a command that modify its behavior or customize how it runs.
In My Own Words: The specific details you give a command so it knows exactly how much, how far, or how fast to do something.
Example: In the command Drive Forward (Distance: 50 cm), the number 50 cm is the parameter
What It Means: A programming structure that repeats a block of instructions either a set number of times or until a condition is met.
In My Own Words: Instead of writing the same line of code over and over, you tell the robot to repeat a set of steps.
Example: Repeat 4 times: Drive forward 10 cm, Turn right 90 degrees to draw a perfect square.
What It Means: Hardware devices that allow a robot to detect physical inputs and gather data from the world around it.
In My Own Words: The “eyes, ears, and skin” of a robot that let it notice things like walls, light, or obstacles.
Example: A bumper sensor clicks when the robot runs into a wall, telling it to stop.
### Booleans & Conditions What It Means: Data that can only have one of two possible values: TRUE or FALSE.
In My Own Words: A simple yes-or-no check that a program uses to decide which path of code to take.
Example: Is_Obstacle_Ahead can either be TRUE (stop) or FALSE (keep driving).
### Sense → Think → Act What It Means: The continuous decision-making cycle a robot uses to read sensor data, process it against logic, and execute a physical response.
In My Own Words: The robot looks at its environment, decides what to do based on its rules, and then moves.
Example: The robot senses a red line, thinks “Red means stop,” and acts by cutting power to the motors.
What It Means: Relational operators (like <, >, or ==) used to evaluate two values against each other, resulting in a Boolean output.
In My Own Words: Mathematical checks to see if numbers are bigger, smaller, or equal to each other to make a choice.
Example: If (Distance to wall < 10 cm), then stop the robot.
What It Means: A system of X (horizontal) and Y (vertical) grid values used to identify an exact location in a 2D space.
In My Own Words: A map coordinate system that tells the robot exactly where it is standing on the floor.
Example: Directing a robot to drive to location (X: 5, Y: 10) on a virtual arena grid.
### Conditionals What It Means: Statements like IF, THEN, and ELSE that allow a program to perform different actions depending on whether a condition is true.
In My Own Words: A fork in the road for code; if a certain rule is met, do option A, otherwise do option B.
Example: IF the battery is low, THEN drive to the charging dock; ELSE, keep cleaning the floor.
What It Means: Recognizing regularities or repeating sequences in a problem to simplify code and create better algorithms.
In My Own Words: Spotting a repetitive rhythm in what the robot needs to do so you can write cleaner, smarter code.
Example: Noticing that a robot maze requires turning left every 3 steps, and writing a single loop to handle the entire map.
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.
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”).
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.
Class = a blueprint for objects
Remember: always test your code
Use System.out.println() to print
When to use: Anytime you write multiple lines of code.
Inline code for short snippets.
Fenced code blocks with language for full examples.
public class Hello {
public static void main(String[] args) {
System.out.println("Hello World!");
}
}
When to use: Organize steps, notes, or key points.
Numbered lists for sequences or steps.
Bulleted lists for unordered ideas.
Define the class Write the main method Test your program Variables
Loops
Conditionals
When to use: Track progress on assignments or tasks.
[x] Complete coding warm-up
Finish project draft
Reflect on learning
When to use: Call out notes, reminders, or teacher comments.
💡 Remember: Loops repeat code until a condition is false.
When to use: Compare values, track progress, or organize data neatly.
| Task | Status | Notes |
|---|---|---|
| Homework 1 | Done # | Submitted |
| Homework 2 | Pending | Needs review |
When to use: Add references, resources, or visuals.
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>
When to use: Hide solutions, extended notes, or extra details.
When to use: Add references or side notes without cluttering the page.
This concept is related to object-oriented programming.1
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.
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. ↩