A lot of people see developers today and assume they became good overnight.
What many people don’t see are the years of curiosity, failed experiments, sleepless nights, self learning, pressure, consistency, and the small moments that completely changed someone’s life.
For me, my journey into tech started during secondary school (high school), and honestly, I never imagined it would shape my future this much.
How It All Started
I had just entered JSS1 during my second term in school.
One particular day, we had just finished a Biology class and were preparing for the next subject: Computer Science.
At that time, I was honestly one of those nonchalant students when it came to classes. I would attend, but my mind was usually somewhere else.
But one thing about me was that I already loved computers, phones, gadgets, and technology generally, even though I had very limited access to them.
Interestingly, within the school, I became known for being “that student” who somehow knew how to handle computer related problems.
The funny part was that because I was too curious and always trying things around systems, I was considered a bit “notorious” whenever I handled staff computers. Because of that, my access to computers was often restricted.
But despite that, I was still respected.
I became the person people called whenever they felt all hope was lost on a system issue.
90% of the time, I fixed the problem.
The remaining 10%, even if I couldn’t solve it directly, I would still help find a possible solution.
I didn’t realize it then, but problem solving was already becoming part of me.
The Class That Changed Everything
That particular Computer Science class changed my life completely.
Back then, most of the systems still used Microsoft Office 2007, and our teacher was teaching us about how programs were made. Visual Basic (VB) was being introduced.
Then somewhere during the teaching, he slightly diverted from the main topic and started talking about websites.
He mentioned companies like Facebook and Google and explained that websites were built using code.
Then he wrote some lines of code on the board.
At that time, I had no idea it was HTML.
He asked us to open Notepad, type the code exactly as written, save the file with a .html extension, and open it in the browser.
I still remember the feeling.
I was amazed.
Completely amazed.
Seeing plain text suddenly turn into an actual webpage felt almost magical to me.
Immediately, I stopped being nonchalant.
While others focused only on passing the class, I became obsessed with experimenting.
I started changing texts inside the code to see what would happen.
Every little change produced a different result.
That moment triggered something in me.
Even after the teacher returned to the original topic, my mind was no longer there.
I was already recreating and experimenting with what I had just seen.
That was the moment my curiosity became serious interest.
The First Rejection That Motivated Me
After the class, I walked up to my teacher and asked for guidance because I wanted to learn more.
Based on my reputation for being “too experimental” around computers, he initially refused.
Honestly, I understood why.
But I kept asking consistently.
Eventually, he gave me a book:
“HTML for Dummies.”
He told me:
“If you finish this book, I’ll allow you to use the computer lab to practice.”
To him, maybe it was just a test.
To me, it became a mission.
Learning HTML by Writing Code in Notebooks
About one month and some weeks later, I returned.
Not only had I finished the book, but I also came back with three full notebooks containing HTML code I had written completely by hand.
At that point, I still didn’t know CSS yet.
I was simply recreating webpages manually and trying to understand how everything worked.
Eventually, I was introduced to CSS.
That changed everything again.
Suddenly, I could style my pages, improve layouts, add colors, structure designs properly, and make my code look cleaner and more organized.
I was genuinely happy while learning.
I could literally spend hours experimenting without getting tired.
And for the first time, I started feeling like I had found something I truly enjoyed doing.
My First Real School Project
As I continued learning, I became part of my school’s editorial team.
That opportunity pushed me beyond simple practice.
I created a portal that stored details of graduating students.
I also configured it to work across systems on the school’s local network so multiple computers could access the portal.
Looking back now, it sounds simple.
But at that age and level, it felt huge to me.
That was one of the moments I realized software could solve real problems.
Around that same period, I was introduced to JavaScript.
JavaScript expanded my thinking completely.
At one point, I even used Excel as a database while experimenting with JavaScript based solutions.
I kept practicing constantly.
Every day, I discovered something new.
Discovering PHP and Going Deeper Into Development
As I improved, someone introduced me to PHP and explained how powerful it was for backend development.
I became curious immediately.
I went online, searched for tutorials, downloaded resources, and started learning it myself.
A few weeks later, I started writing PHP applications.
That was when I began understanding how websites truly worked behind the scenes.
Frontend development had already impressed me.
But backend development made me fall even deeper in love with programming.
At that point, coding was no longer just curiosity.
It became part of my life.
Transitioning Into Android Development
Later, I moved into Android development.
This part of my journey became easier because I had mentors who guided me properly.
One important thing I learned during that phase was the importance of focus and consistency.
Tech can easily overwhelm you because there’s always something new to learn.
But learning how to focus on one path at a time helped me grow faster.
From there, I continued evolving.
Over the years, I’ve built multiple projects for personal use, commercial purposes, and clients.
I’ve worked on backend systems, APIs, mobile applications, automation projects, networking related solutions, hardware integrated projects, and much more.
And honestly, I’m still learning every single day.
What My Learning Journey Has Taught Me
One thing I’ve learned is this:
You do not need to know everything before starting.
Most beginners think developers are special people who magically understand code immediately.
That’s not true.
A lot of us started from confusion.
We searched endlessly online.
We broke things.
We failed repeatedly.
We rewrote code multiple times.
We stayed awake trying to solve one tiny bug.
Growth in tech is mostly consistency.
Not perfection.
The Hardest Part of the Journey
The hardest part for me wasn’t learning syntax.
It was handling limited resources, lack of guidance sometimes, and trying to stay consistent during difficult periods.
There were moments where things felt confusing.
Moments where projects failed.
Moments where I questioned myself.
But consistency helped me survive those periods.
Another major challenge was information overload.
There are countless technologies, frameworks, tutorials, and opinions online.
At some point, I realized the best strategy was to focus on building instead of endlessly consuming tutorials.
Projects teach faster than theory alone.
What I Enjoy Most About Coding
What I enjoy most is problem solving.
I love the process of turning ideas into working systems.
I enjoy seeing something move from imagination into reality.
There’s also a different kind of satisfaction that comes from helping people solve real problems using technology.
Sometimes the solution looks simple from the outside, but behind it are hours or days of thinking, testing, debugging, and improving.
That process is something I genuinely enjoy.
My Goals for the Future
My goals are still growing, but one thing is clear:
I want to continue building impactful solutions.
I want to create systems, platforms, tools, and products that solve real world problems.
I also want to contribute more to the developer community through sharing knowledge, writing, mentoring, and helping upcoming developers avoid some of the mistakes I made while learning.
Long term, I want to build technology that creates real impact both locally and globally.
Advice to Beginners
If you’re just starting your journey into tech, this is what I would tell you:
- Don’t compare your beginning to someone else’s middle.
- Start with whatever device or resources you currently have.
- Build projects, even small ones.
- Stay curious.
- Stay consistent.
- Don’t fear mistakes or debugging.
- Learn by doing, not just watching tutorials.
And most importantly:
Nobody becomes a good developer overnight.
Every experienced developer you admire today once struggled with the basics too.
The difference is that they kept going.
And that consistency changes everything.