The Beginner's Glossary and First-Month Checklist

This is an independent educational guide, not the website of any school, course provider, software vendor, or standards body.

koderich.com is an independent, non-commercial field guide to learning programming. It explains how code works, how beginners choose a first language, how to practice effectively, and the vocabulary of software development. It sells nothing, runs no courses, accepts no advertising, recommends no specific paid product, and has no affiliation with any named school, course provider, vendor, association, or authority, or any other named organization.

If you are starting to learn programming, the vocabulary can feel like a locked door. This page gives you the key: a glossary of twenty core terms written in plain language, followed by a practical checklist for your first month. You will not find product recommendations or course pitches here. Instead, you get definitions you can check against any official source, and a set of actions that build real skill. Read the glossary once, then use the checklist as a weekly guide. By the end of the month, you will understand the words and have written code that runs.

How to use this page

The glossary defines terms as they are used in general programming practice, not tied to any single language. Each definition is short and accurate enough to match what you will read in official documentation. The checklist that follows gives you ten concrete actions for your first month. At the end, you will find a grouped list of official sources: standards bodies, language foundations, and educational organizations. Use those links when you want to go deeper or verify a definition. Nothing here replaces hands-on practice, but it gives you a reliable map.

The glossary

variable: A named storage location that holds a value. You can change the value later, and the name lets you refer to it throughout your program.
function: A reusable block of code that performs a specific task. It can take inputs, called arguments, and may return a result.
loop: A control structure that repeats a block of code multiple times. Common forms include counting loops and loops that continue while a condition is true.
conditional: A statement that runs different code depending on whether a condition is true or false. The most familiar form is the if statement.
string: A sequence of characters, such as letters, digits, or symbols, treated as text. In most languages, strings are enclosed in quotation marks.
integer: A whole number without a fractional part, such as 7, -3, or 0. Many languages have a separate type for numbers with decimals.
array: An ordered collection of values, each identified by an index. Arrays let you store and access many items under one name.
object: A collection of related data and behaviors, often represented as key-value pairs. Objects let you group properties and methods that belong together.
syntax: The set of rules that defines how code must be written in a particular language. A syntax error means the code does not follow those rules.
source code: The human-readable instructions written by a programmer. Source code is what you edit; it may be translated or executed by other software.
compiler: A program that translates source code into another form, often machine code, before the program runs. The translation happens all at once, producing a separate executable file.
interpreter: A program that executes source code directly, line by line, without a separate compilation step. The interpreter reads and performs each instruction as it goes.
runtime: The environment in which a program executes, including the software and resources it needs while running. Some languages rely on a runtime system to manage memory and other tasks.
bug: An error or flaw in a program that causes it to behave incorrectly or produce wrong results. Bugs can be caused by mistakes in logic, syntax, or assumptions.
debugging: The process of finding and fixing bugs in a program. It often involves reading error messages, testing small parts, and using tools that let you inspect a running program.
algorithm: A step-by-step procedure for solving a problem or completing a task. Algorithms are independent of any programming language.
data structure: A way of organizing and storing data so it can be used efficiently. Examples include arrays, lists, stacks, and queues.
version control: A system that records changes to files over time, allowing you to review, revert, or branch. It helps you track your work and collaborate with others.
repository: A storage location managed by a version control system that contains all the files and their history for a project. You can clone a repository to get a local copy.
IDE: An integrated development environment: a software application that combines a code editor, build tools, and a debugger in one interface. IDEs are designed to make writing and testing code easier.

The first-month checklist

Pick one beginner-friendly language and stick with it for the entire month. Switching languages early slows your progress.
Install or open one way to run code, then test it with a one-line program. Confirm that you can see output before moving on.
When you hit an error, read the message slowly instead of closing it. Error messages often tell you the file, line, and type of problem.
Finish one small exercise every day you practice. Consistency matters more than length.
Type every example by hand, even if you could copy and paste. Typing builds muscle memory for syntax.
Keep one folder on your computer for everything you write. Name files clearly so you can find them later.
Write one tiny program that does something you actually want, such as a daily reminder or a simple calculator. Personal relevance keeps you motivated.
Read one official documentation page from start to finish. Choose a topic you have already used, like a function or a data type.
Explain one concept from the glossary to someone else, in your own words. Teaching forces you to clarify your understanding.
At the end of the month, rewrite your first program from scratch and compare the two versions. Notice how much clearer your code has become.

The official sources

These organizations publish specifications, documentation, and learning materials. They are not affiliated with this page, but they are reliable places to check facts.

Web references: MDN Web Docs, the W3C, and ECMA International.
Languages and learning: the Python Software Foundation, Scratch, Code.org, freeCodeCamp, CS50, and MIT OpenCourseWare.
Infrastructure and standards: the Unicode Consortium, the IETF, the Linux Foundation, and the Open Source Initiative.
The profession: the ACM and the IEEE Computer Society.

FAQ

Do I need to memorize every term in the glossary?

No. Use the glossary as a reference. You will naturally absorb the terms as you write code and read documentation. Focus on understanding the ideas, not on reciting definitions.

What if I miss a day on the checklist?

Missing a day is not a failure. The checklist is a guide, not a contract. Resume the next day and keep the habit of daily practice, even if it is only fifteen minutes.

Should I learn one language or several in the first month?

Learn one. Switching between languages early can confuse syntax and slow your progress. Once you are comfortable with one, picking up another becomes easier.

How do I know if my code is correct?

Run it and check the output against what you expect. For small programs, test with different inputs. If you get an error, read the message carefully and fix one thing at a time.