CIS-130 – Guided Keyboarding Lab

A beginner-friendly module introducing core programming fundamentals for adult learners, with brief interactive Code Lab practice opportunities and associated knowledge checks planned throughout.

What you will practice

Introduce learners to what programming is, how code is written and run, and the foundational concepts of variables, data, control flow, functions, and debugging.

0 of 5 sections complete

Not started

Section 1

What Programming Is and How Programs Work

Programming means writing clear instructions that a computer can follow. In this opening section, learners connect programming to familiar workplace routines, see how a small program runs in order, and practice the basic cycle of write, run, observe, and revise.

By the end of this section

Learners will be able to describe programming as giving precise step-by-step instructions to a computer, explain that programs run instructions in a specific order, and identify the basic cycle of writing, running, observing, and revising code.

Programming starts with instructions people can describe clearly

A program is a set of instructions written for a computer. The computer does not guess what you meant, fill in missing steps, or use common sense the way a coworker might. It follows the instructions it receives, in the order it is told to follow them.

That is why programming is less about “being good at computers” and more about learning to describe a task precisely. If you have ever followed a checklist, completed a form, used a cash register, scheduled an appointment, or trained someone on a routine task, you have already used the kind of step-by-step thinking that programming builds on.

How a simple program runs

Write: Create instructions in a programming language.
Run: Ask the computer to carry out those instructions.
Observe: Look at what happened, such as displayed output or an error message.
Revise: Make a small change if the result is not what you expected, then run again.

At the beginning, your goal is not to memorize every command. Your goal is to notice the relationship between the instructions you write and the result the computer shows. Programmers use this same cycle at every level, from a first practice exercise to professional software work.

Code Lab

A program is a set of precise instructions for a computer.
Computers follow instructions in order unless the program tells them to do something else.
Running code means asking the computer to carry out the instructions.
Observing and revising are normal parts of programming, not signs of failure.

Section 2

Values, Variables, and Simple Expressions

Learn how programs keep track of information by giving values clear names, then practice changing those values and viewing simple output.

By the end of this section

By the end of this section, learners will be able to: explain that a variable is a name for a stored value; identify simple values such as words, numbers, and true/false ideas; change a stored value; and predict the result of a simple expression.

Names Help Programs Remember Values

A program often needs to remember information while it runs. Instead of repeating the same information over and over, we give it a name. For example, a program might remember a person’s name, a price, a score, or whether a task is complete.

In everyday language, you might say, “The current total is 25.” In code, you can give that value a name such as total. Later, the program can use the name instead of needing you to type the number again.

Common Kinds of Simple Values

Words or labels, such as a name or city
Whole numbers, such as a count or age
Decimal numbers, such as a price or measurement
True/false values, such as whether a form is complete

Different programming languages have different punctuation rules, but the basic idea is the same: choose a clear name, assign it a value, and use that name later. Good names make code easier to read, especially when you return to it after a break.

Code Lab

Reading an Assignment Statement

Look at the name on the left. This is the label the program will use.
Look at the value or expression on the right. This is what the name will refer to.
Read the assignment as “store this value under this name.”
When the same name is assigned a new value later, the program uses the newer value from that point forward.

Before moving on, check your understanding: if a program assigns a value, prints it, changes it, and prints it again, the two outputs may be different. That is normal. The program is following the instructions in order.

Section 4

Repeating Work with Loops

Learn how loops help programs repeat the same action without rewriting the same instruction again and again. You will practice a small counting loop with a clear ending and visible output.

By the end of this section

By the end of this section, learners will be able to identify when a loop is useful, describe the repeated action and stopping point in a simple loop, predict basic repeated output, and explain why every loop needs a clear way to finish.

Why loops matter

A loop tells a program to repeat a set of instructions. Instead of writing the same line many times, you write the instruction once and tell the program how many times, or under what condition, it should repeat.

Loops are useful for everyday programming tasks such as counting items, checking each name in a list, repeating a reminder, or adding up a set of numbers.

A simple counting loop

In Python, one common beginner-friendly loop uses for with range. The loop below counts through a small set of numbers and prints one message for each number.

Your goal is to make the output show practice steps 1 through 5, then stop.

Code Lab

I can point to the instruction that repeats.
I can explain what number changes each time through the loop.
I can identify the stopping point of the loop.
I can explain why using a loop is better than copying the same print statement five times.

Loops are one of the main ways programs handle repeated work. Start with small, predictable loops like this one. Once you can see what repeats, what changes, and when it stops, larger loop examples become much easier to understand.

Section 5

Functions, Debugging, and Your Next Practice Steps

This section brings the module together by showing how functions organize reusable instructions and how debugging helps programmers learn from mistakes. Learners practice fixing a small function with predefined checks, then identify practical ways to keep building confidence.

By the end of this section

By the end of this section, learners will be able to explain the purpose of a function, use a basic debugging routine to investigate a simple error, and choose realistic next steps for continued programming practice.

Functions help you reuse a good idea

A function is a named set of instructions that can be used again. Instead of rewriting the same steps every time, you can give those steps a clear name, send in information, and get a result back.

For example, a function might calculate a total, format a message, check whether a number is high enough, or repeat a task safely. Good function names make code easier to read because they describe what the code is meant to do.

A simple debugging routine

Read the function name and ask what job it is supposed to do.
Look at the inputs the function receives and the value it returns.
Run or inspect one small example instead of changing many things at once.
If the output is wrong, change one line and test again.
Use the checks as clues, not as judgments. A failed check points to the next thing to investigate.

Code Lab: fix a small function

In this short practice, the function name is already provided, but the calculation is wrong. Your goal is to make the function return the correct total cost. Keep the change small and use the checks to confirm your fix.

Code Lab

Practical next steps

Practice for short, regular sessions rather than waiting for one long study block.
Save examples that worked, then change one part at a time to see what happens.
When you get an error, write down the message and the change that caused it.
Build tiny functions for everyday calculations, labels, or decisions before trying a larger project.
Review variables, conditionals, loops, and functions together, because most useful programs combine all four.

You have now seen the basic pattern of programming: write instructions, run them, observe the result, and revise. Confidence grows through repetition. Each small mistake you understand becomes a tool you can use in the next program.

An introductory module for adult beginners that builds confidence with keyboarding, home row technique, basic data entry habits, gamified typing practice, and introductory voice transcription using a controlled AI-generated sample.

What you will practice

Learners will identify home row keys, use basic keyboarding posture and finger placement, practice accuracy before speed, enter short text and simple data into structured fields, and complete a short transcription activity from an audio-style prompt.

0 of 5 sections complete

Not started

Section 1

Getting Comfortable With the Keyboarding Workspace

Start by getting familiar with the keyboard, your practice space, and the module routine. This section focuses on comfort, accuracy, and confidence before speed.

By the end of this section

Learners will identify common keyboard areas, set up a comfortable typing position, understand how practice activities will work, and complete a short warm-up without rushing.

Start With Comfort, Not Speed

Keyboarding is a workplace skill, but it does not have to feel rushed. In this module, you will build skill step by step: first comfort, then accuracy, and later speed.

Think of the keyboard as a set of small work areas. Letter keys are used for most typing. Number keys help with dates, prices, and phone numbers. The spacebar, Enter, Backspace, Shift, and Tab keys help you format and move through information.

Know the Main Keyboard Areas

Letter keys: used for words, names, and short messages.
Number keys: used for dates, amounts, phone numbers, and ID numbers.
Spacebar: creates spaces between words.
Enter: starts a new line or confirms an action in many forms.
Backspace or Delete: removes mistakes so you can correct them.
Shift: makes capital letters and some symbols.
Tab: often moves to the next field in a form.

Set Up Your Typing Position

Sit with your feet supported and your shoulders relaxed.
Place the keyboard close enough that your elbows can stay near your sides.
Keep your wrists relaxed rather than pressing them hard into the desk.
Look at the screen often, but glance at the keyboard when needed. Beginners are allowed to look.
Type slowly enough that you can notice and fix mistakes.

Warm-Up Practice: Type a Short Workplace Note

Use the practice area below to type a short fictional note. Take your time. If you make a mistake, correct it before moving on. The goal is comfort and careful entry, not speed.

Typing Studio

I can point to the letter keys, number keys, spacebar, Enter, Backspace, Shift, and Tab.
I adjusted my body or keyboard position so typing feels more comfortable.
I practiced slowly enough to notice mistakes.
I understand that accuracy matters more than speed at the beginning.

Section 2

Home Row Keys and Finger Placement

Build the basic keyboarding habit of returning to the home row. You will learn where each finger rests, which keys belong to each hand, and how to type simple home row patterns accurately before trying to type faster.

By the end of this section

By the end of this section, learners will be able to place fingers on A S D F and J K L ;, name the left-hand and right-hand home row keys, use thumbs for the spacebar, and complete a short home row typing drill with attention to posture, finger placement, and accuracy.

Start From the Home Row

The home row is the resting place for your fingers. On most keyboards, the letters F and J have small raised marks. These bumps help you find your starting position without looking down.

Place your left fingers on A S D F. Place your right fingers on J K L ;. Let your thumbs rest lightly near the spacebar.

Sit comfortably with your feet supported and shoulders relaxed.
Keep wrists level, not pressed hard against the desk or keyboard.
Rest left fingers on A S D F.
Rest right fingers on J K L ;.
Use either thumb for the spacebar.
After pressing a key, gently return that finger to its home position.

Which Finger Types Which Key?

For this first drill, focus only on the home row keys. Your left hand covers A, S, D, F. Your right hand covers J, K, L, ;. Try to keep your eyes on the screen and feel for the raised marks on F and J when you need to reset.

Typing Studio

Before You Move On

I can find F and J by touch.
I know the left-hand home row keys: A S D F.
I know the right-hand home row keys: J K L ;.
I can type simple home row patterns without rushing.
I understand that accuracy matters more than speed right now.

Section 3

Accuracy First: Building Typing Confidence

In this section, you will move from key practice into short words and simple sentences. The goal is to build confidence by typing carefully, noticing common mistakes, and improving accuracy before trying to type faster.

By the end of this section

By the end of this section, you will be able to type short word groups and simple sentences with attention to accuracy, pause to correct common errors, and complete a short confidence challenge using simple progress milestones.

Why Accuracy Comes First

Many beginning typists feel pressure to type quickly. In real keyboarding and data entry work, however, accuracy is more important than speed. A fast mistake still needs to be fixed, and fixing errors takes extra time.

For now, aim for steady typing. Look at the text, type each word carefully, and pause when you notice an error. Speed will grow naturally as your hands become more familiar with the keyboard.

Common Accuracy Checks

Sit comfortably with both feet supported if possible.
Keep your wrists relaxed and your fingers close to the home row.
Read a whole word or short phrase before typing it.
Use the correct capitalization and punctuation when shown.
Correct errors calmly instead of racing to the end.

Practice: Accuracy Confidence Challenge

This short challenge uses simple word groups and sentences. Treat it like a light game: each carefully completed line is a progress milestone. Your goal is not to be the fastest person in the room. Your goal is to finish with fewer errors than you expected.

Typing Studio

After the Challenge: Notice Your Pattern

I will slow down when I type capital letters.
I will watch for missing spaces between words.
I will check punctuation before I move on.
I will keep my fingers closer to the home row.
I will repeat difficult lines instead of avoiding them.

A basic introductory module for adults with no previous SQL or database experience. Learners build a plain-language understanding of what databases are, how data is organized in tables, and how common SQL commands are structured before practicing simple, safe queries in a virtual training database.

What you will practice

By the end of the module, learners should be able to describe the purpose of a database, identify tables, rows, columns, and simple relationships, recognize the basic structure of SQL statements, write simple SELECT queries, filter and sort query results, and explain how basic data-changing commands are used conceptually in safe database work.

0 of 5 sections complete

Not started

Section 1

What Databases Are and Why People Use Them

Learn what a database is in plain language, why workplaces use databases, and how organized information helps people find, update, and trust data more easily than scattered notes or separate files.

By the end of this section

By the end of this section, you will be able to explain what a database is, give a workplace example of database use, describe how databases help people store and find information, and compare loose information, spreadsheets, and databases at a beginner level.

A database is organized information you can use again

A database is a structured place to store information so people and systems can find it, update it, and use it consistently. Instead of keeping important details in many separate notes, emails, or files, a database organizes related information in a predictable way.

For example, a community training center might keep a database of classes, learners, instructors, schedules, and registrations. When a staff member needs to know who is enrolled in “Basic Computer Skills,” they can ask the database instead of searching through paper forms or multiple spreadsheets.

Why not just use notes or spreadsheets?

Notes, documents, and spreadsheets can be useful, especially for small tasks. But as information grows, it becomes harder to keep everything accurate. People may type names differently, save copies in different places, forget to update one file, or accidentally change information they did not mean to change.

A database is designed to reduce those problems by storing information in a more organized structure. Many people can use the same source of information, and the database can be searched, filtered, sorted, and updated in controlled ways.

Store many records in a consistent format.
Find one item quickly, such as a customer, order, class, or appointment.
Avoid having several different versions of the same information.
Update information so future users see the current version.
Control who is allowed to view or change important information.
Answer questions by searching, filtering, or sorting data.

Loose information, spreadsheets, and databases

One helpful way to understand databases is to compare them with tools you may already know:

Loose information is scattered across emails, papers, text messages, or separate documents. It may be easy to create, but hard to search and keep consistent.
A spreadsheet stores information in rows and columns. It is useful for many everyday lists and calculations, but it can become difficult to manage when many people, repeated updates, or connected lists are involved.
A database stores related information in a structured system. It is built for reliable searching, updating, connecting, and protecting information.

Short practice: spot where a database would help

Choose one familiar setting: a clinic, warehouse, school, library, training center, store, or office.
Name one kind of information that setting needs to track, such as appointments, inventory, class registrations, customers, or work orders.
Write one question a worker might ask about that information, such as “Which items are low in stock?” or “Who is scheduled today?”
Decide whether loose notes, a spreadsheet, or a database would be most reliable if the information grew to hundreds or thousands of records.
In one sentence, explain why a database could help in that situation.

In the next section, you will look more closely at how databases organize information using tables, rows, columns, and simple identifiers called keys.

Section 2

How Data Is Organized: Tables, Rows, Columns, and Keys

Learn how a database table organizes information into columns and rows. You will inspect a small fictional training table and practice naming what each part of the table means.

By the end of this section

By the end of this section, you should be able to identify a table, column, row, record, field, and simple key in a small dataset; explain what one row represents; and describe why a key column helps identify records reliably.

A database stores information in a structured way. One of the most common structures is a table, which looks a little like a spreadsheet: information is arranged into labeled columns and individual rows.

In database language, each row is often called a record. Each column describes one category of information, such as a class name, meeting day, or room. A single cell where a row and column meet may be called a field.

Inspect a small training table

The activity below uses a fictional community class schedule. The data is small, invented, and safe for practice. Your goal is not to write SQL yet. Your goal is to read the table and connect what you see to database vocabulary.

Code Lab

The table name is community_classes.
Each column answers one kind of question: What is the class ID? What is the title? What day does it meet?
Each row represents one fictional class offering.
The class_id column can act as a simple key because each class has a different ID number.
The open_seats column stores numbers, while columns like class_title and room store text.

As you continue, remember this basic pattern: a table groups related records, columns label the kinds of information stored, rows hold individual records, and keys help identify records clearly.

Section 5

Filtering, Sorting, and Safely Thinking About Data Changes

Practice narrowing query results with WHERE and organizing them with ORDER BY, then learn how data-changing commands are handled safely in real database work.

By the end of this section

By the end of this section, you should be able to write a SELECT query with a simple WHERE filter, sort results with ORDER BY, describe the purpose of INSERT, UPDATE, and DELETE, and explain why real data changes require training data, permission, and careful review.

Filtering and sorting results

So far, you have used SELECT to ask a database for information. In everyday work, you usually do not want every row. You may want only open classes, customers in one city, products under a certain price, or appointments after a certain date.

The WHERE clause filters rows. The ORDER BY clause sorts the rows that remain. A beginner-friendly pattern is:

SELECT the columns you want to see
FROM the table that stores the data
WHERE the rows match a condition
ORDER BY one column to sort the results

Code Lab

Thinking carefully about data changes

SQL is not only for reading data. It can also change data. Three common data-changing commands are:

INSERT: adds a new row.
UPDATE: changes existing rows.
DELETE: removes existing rows.

In this beginner module, you are only learning what these commands mean. Practicing them against real data should happen only in an approved training environment with clear instructions.

Am I working in a training database or an approved environment?
Do I understand which table and rows would be affected?
Have I inspected the rows first with SELECT?
Do I have permission to make this change?
Is there a safe way to review or undo the change if needed?

A SELECT query asks, “What can I see?” Data-changing commands ask, “What will be different after this runs?” That second question deserves extra care.
Beginner SQL safety reminder