The First Bug I Fixed Was Not in My Code — It Was in My Confidence

When I started learning tech, I thought the hardest part would be writing code.

I was wrong.

The hardest part was opening a blank editor and fighting the tiny voice saying:

"Maybe everyone else already knows this stuff except me."

Turns out, that voice is probably the most annoying bug I have encountered so far — and unfortunately, there is no "npm install confidence" command.

I came into tech expecting a straight road:

Learn a language → build projects → become a developer.

But my actual journey looked more like:

Learn a concept → break something → Google for two hours → fix it → break something else → question my life choices → repeat.

And strangely enough... that is where the real learning happened.

The beginner advantage nobody talks about

Being new is frustrating, but it also gives you something valuable:

You notice things.

Experienced developers often know the shortcuts because they have spent years building mental maps. Beginners don't have those maps yet, so we ask questions that sometimes reveal hidden complexity.

For example:

"Why do we need this framework?"

"Why can't we just write it this simpler way?"

"Why does this error message sound like it was written by a robot having a bad day?"

Those questions are not stupid. They are the beginning of understanding.

AI made learning easier... but also more confusing

Learning tech in 2026 is interesting because AI tools are everywhere. DEV Community discussions increasingly focus on AI, AI agents, and how developers should use these tools responsibly.

AI can explain concepts, generate examples, and help debug problems.

But there is a trap.

If I ask AI to solve every problem, I might finish a project without actually becoming better at solving problems.

It is like having a gym trainer who lifts all your weights for you. Technically, you finished the workout. Your muscles disagree.

The best use of AI for me has been:

"Explain why this works."

Not just:

"Make this work."

My current developer philosophy

I am trying to follow three simple rules:

1. Confusion is part of the process

Every developer I admire was once confused by basic things.

The difference is they kept going.

1. Build small things

A tiny working project teaches more than 50 unfinished tutorials.

A calculator app, a simple website, a small automation — these are not "too easy."

They are training grounds.

1. Learn in public

Sharing progress feels uncomfortable because nobody wants to look like a beginner.

But every expert was once a beginner who decided not to hide.

My first contribution here

This is my first post on DEV, and honestly, writing it feels like submitting my first piece of code:

A little scary.

Probably imperfect.

But finally running.

I am here to learn, build, ask better questions, and hopefully help someone else who is sitting at the beginning of this journey wondering:

"Am I the only one who finds this difficult?"

Spoiler: You are not.

The bugs in our code are usually easier to fix than the bugs in our confidence.

Happy coding * Farah *