I'm Ajmal Ali. I'm in high school, and I teach myself electronics the slow way — with a breadboard, a laptop, and a lot of trial and error. I didn't grow up around this. Nobody in my family is an engineer. Everything on this site I learned from documentation, YouTube, and broken projects of my own.
How this started
The first thing I ever got to work was an LED lighting up. That is not an impressive sentence to read, and it took me far longer than it should have. I didn't have a breadboard, a resistor that was the right value, or anyone nearby to ask why the current-limiting resistor even mattered. I remember being genuinely confused that the light was dim, and later realising I'd picked a resistor more or less at random.
What stuck wasn't the LED. It was realising I could get an idea working by myself. Nothing about that first circuit was taught to me. I read it, built it, got it wrong, read more, and tried again. That loop turned into an obsession.
I didn't have anyone to ask, so I started writing down what I'd learned. These posts are those notes.
What I work with
Mostly the usual beginner-to-intermediate parts, which is exactly where the clear documentation and the real problems are:
- Arduino — mostly the UNO and Nano. My default board for anything I just want to light up, move, or beep at.
- ESP32 — this is where I spend most of my time. WiFi and Bluetooth, enough GPIO to be interesting, and a much more powerful chip to learn on.
- Sensors and modules — ultrasonic (HC-SR04), temperature and humidity, relays, displays, and whatever else I can get working on a budget.
- A breadboard and a lot of jumper wires — plus a multimeter, which I wish I'd owned a year earlier.
My supply of boards and modules has grown faster than my knowledge, which is a problem I'd like to fix.
Why this blog exists
Two reasons, and they're both selfish.
The first is that I kept losing the same fights. A sensor that worked on my desk and returned garbage on the other side of the room. A pin that silently did nothing because I'd forgotten it was an input pin. If I wrote it down once, I wouldn't have to solve it twice — and the writing forced me to actually understand the fix instead of just getting the light to turn on.
The second is that when you're learning something alone, the tutorial either assumes you already know the one thing you're stuck on, or skips the three steps that actually went wrong. I lost real evenings to that. If someone else is stuck at 1 a.m. with a breadboard that won't cooperate, I'd rather they find the answer here than lose the night the way I did.
I write about the mistakes more than the wins, because the mistakes are the part that was useful to me.
What you'll find here
- Wiring and interfacing guides for common sensors and modules
- Arduino and ESP32 project walkthroughs, including what went wrong
- Notes on debugging hardware and firmware that misbehave only sometimes
- The occasional post on the tooling and code around embedded work
Where this is going
I want to study robotics and hardware engineering properly. I know that "self-taught and motivated" is not a substitute for a degree, and I'm not treating it as one — this blog isn't standing in for a qualification, it's the work itself. It's the record of what I've actually built and understood, and if it's also useful to someone else, so much the better.
I don't have all of this figured out yet. I don't fully understand C, I still wire things up backwards, and some of these posts are me working something out in public. I plan to keep going.
Get in touch if you spot an error, want to suggest a topic, or just want to say hello. Corrections are genuinely welcome — I'd rather be wrong in a post someone can correct than quietly wrong in my own notes.