What robotics is, and where to start

What a robot actually is

A robot is a machine that senses its surroundings, decides what to do about them, and acts to change something — and does this repeatedly, with some degree of autonomy. That last part matters. A lamp acts (it lights up) but senses and decides nothing. A remote-control car senses and acts, but *you* are doing the deciding, so it is a vehicle, not a robot. A Roomba senses walls and dirt, decides where to go, and drives itself — that is a robot.

The engine underneath every robot is the sense–think–act loop. A sensor turns something physical (distance, light, rotation, an image) into a number. A controller — a small computer running your program — reads those numbers, decides, and sends commands. An actuator (a motor, a servo, a wheel) turns those commands back into physical motion. The loop runs over and over, often dozens or hundreds of times a second, which is what makes the machine seem alive.

• Sense — sensors measure the world and produce numbers (distance in centimetres, a wheel's rotation, a camera frame).
• Think — the controller runs your code: read the sensors, apply logic, decide the next action.
• Act — actuators execute the decision by moving something (spin a wheel, turn a joint, blink a light).

The kinds of robots — and which to start with

Robots come in a few broad families, and picking the right one to start with saves you money and frustration. The families differ in how they move and what they are for.

Start with a small wheeled mobile robot. It is the best teacher: it is inexpensive, it fails gently (it bumps a wall rather than falling from the sky), and it exercises everything at once — a sensor to see obstacles, motors to move, and a control loop to tie them together. A two-wheeled robot that avoids obstacles or follows a line is the classic, and rightly so. You can build one for the price of a few coffees, and everything you learn transfers to bigger robots later.

The three skills robotics combines

Robotics sits where three disciplines meet. You do not need to master all three before you start — you grow them together, and a kit handles the parts you are not ready for yet.

• Mechanical — the body: the chassis, wheels, joints and how forces move through them. For your first robot this is a pre-made kit chassis, so you can ignore most of it at first.
• Electronics — the nervous system: power, wiring, and the signals between the controller, sensors and motors. You need the survival basics (the next lesson), no more.
• Software — the brain: the program that reads sensors and commands actuators. This is where most of your time and most of the fun will be.

For a beginner, software and electronics matter most, because the mechanical side can be bought as a kit. That is good news: it means you can start building intelligent behaviour on day one instead of machining parts. As you advance, you will care more about mechanics — how a robot arm reaches, how a drive train handles a slope — but that is a problem for future you.

The 'hello world' of robotics

Every robotics journey begins with the same tiny milestone: blinking an LED. It looks trivial, and it is — but it proves your whole toolchain works end to end: the board, the cable, the code, and the upload. If you can make a light blink, you can make a motor spin; the rest is detail. Here is the classic Arduino sketch.

// Blink the built-in LED — the 'hello world' of robotics.
void setup() {
  pinMode(LED_BUILTIN, OUTPUT);   // tell the board this pin drives an output
}

void loop() {
  digitalWrite(LED_BUILTIN, HIGH); // LED on
  delay(500);                      // wait half a second
  digitalWrite(LED_BUILTIN, LOW);  // LED off
  delay(500);
}

Notice the shape: a setup() that runs once to configure the hardware, and a loop() that runs forever. That loop() *is* the sense–think–act loop in miniature. Swap the LED for a motor and add a sensor read at the top, and you have a robot. This structure — set up once, then loop forever — is how almost every microcontroller robot is written.

A roadmap from zero to a first robot

Here is the order that works, each step building on the last. Do not skip ahead — every step is a checkpoint that isolates one new thing so that when something breaks, you know where to look.

1. Get a microcontroller board and a starter kit (the next two lessons cover exactly what and where to buy, cheaply).
2. Blink an LED — prove the toolchain works.
3. Read one sensor (a button, then an ultrasonic distance sensor) and print its value to your screen.
4. Drive one motor through a motor driver — never straight from the board.
5. Combine sensor plus motors into a behaviour: follow a line, or stop before a wall.
6. Add a Raspberry Pi and a camera for vision, once the basics are solid.
7. Learn ROS 2 and simulation to design bigger robots without buying more parts.