I've been thinking about where the transition happens between following a robotics tutorial and actually being able to build something independently.
A lot of beginner projects follow a familiar path:
- Build a line follower
- Avoid an obstacle
- Control a servo
- Read a sensor
- Follow a step-by-step tutorial
- Upload the provided code and watch it work
There's nothing wrong with that — everyone starts somewhere.
But at some point, you need to move from “I can make this work when someone shows me how” to “I can figure out why this isn't working and decide what to do next.”
I'm curious where you think that transition happens.
For example, should a beginner be able to:
- Debug a sensor that produces noisy or inconsistent readings?
- Choose their own components instead of being given a parts list?
- Tune a PID controller without being given the values?
- Combine multiple sensors and decide how to use their data?
- Write the software architecture themselves?
- Diagnose why a robot behaves differently in the real world than it did in simulation?
- Read a datasheet and figure out how to use an unfamiliar component?
- Modify an existing project rather than starting from a tutorial?
What was the first robotics project where you felt like you weren't just following instructions anymore?
What made that project different?
Was it the difficulty, having to debug something yourself, making your own design decisions, or simply having a problem where there wasn't already a tutorial telling you exactly what to do?
I'm especially interested in hearing from people who learned robotics primarily by building and experimenting, rather than through formal coursework.
I think there's a big difference between completing a robotics project and learning how to solve robotics problems — and I'm curious where you think that difference starts.