Tag Archives: programming

Why I Pivoted from JavaScript to Python — And What It Taught Me About Learning Tech

Introduction

Learning technology often looks simple from the outside. or so it seemed for me at a time.

Many people watch videos, read tutorials, and believe that programming is just about memorizing a few commands and writing lines of code. I also started my journey with a similar expectation.

At the beginning, everything felt exciting and clear. But at some point in the journey, I encountered something that many beginners eventually face — what I now call “The JavaScript Wall.”

This experience taught me an important lesson about learning technology and eventually led me to pivot from JavaScript to Python.

When HTML and CSS Felt Straightforward

My entry into web development started with HTML and CSS.

HTML introduced me to the basic structure of web pages. It felt almost like writing a document that the browser could understand.

CSS came next, and suddenly the web page could be styled. Colors, spacing, layout, and fonts began to bring life to the page. The understanding did a thing to me.

The feedback was immediate. You write something and instantly see the result on the screen. That kind of learning is very encouraging for beginners.

At that stage, it felt like progress would continue smoothly. But I was about to find out with JavaScript.

The Moment JavaScript Changed Everything

Then I started learning JavaScript.

This was the moment when programming stopped being just about structure and design and started becoming about logic. The logic I encountered as a first year student at the University of PortHarcourt was different.

JavaScript introduced ideas that were deeper than anything I had encountered before:

  • variables
  • functions
  • conditions
  • loops
  • program logic

Suddenly, it was not just about what appears on the screen, but how the computer thinks.

This was the moment I hit what I now call The JavaScript Wall.

Realising Programming Is Deeper Than It Looks

At first, I thought the problem was simply my ability.

Many beginners have this same reaction when they meet their first programming challenge. It is easy to think:

  • maybe I started too late
  • maybe programming is only for very young people
  • maybe this is not for me

But with time, I realised something important.

Programming itself is deeper than it appears at the beginning.

The early stages are friendly and visual. But as you go deeper, you start dealing with the logic that powers the entire digital world.

My Quiet Learning Phase

Instead of rushing forward, I decided to slow down.

I spent some time quietly reviewing what I had learned so far. I read more carefully. I practiced more deliberately. I tried to understand the ideas behind the code rather than simply copying examples.

This phase was not very visible on social media, but it was one of the most important stages of my learning journey.

Sometimes the most meaningful progress happens away from the spotlight.

Discovering Python

During this period of reflection, I encountered Python.

What immediately caught my attention was how readable the language felt.

Compared to many other programming languages, Python often reads almost like plain English. The structure felt simpler and easier to follow.

For example, tasks that required several lines of complex syntax in some languages could often be written in a more straightforward way in Python.

This clarity made a big difference for me.

Programming still required thinking and practice, but the language itself did not feel like an additional obstacle.

Why the Pivot Made Sense

My decision to pivot from JavaScript to Python was not about abandoning JavaScript completely.

JavaScript remains one of the most important languages on the web.

However, for my personal learning style, Python provided a clearer path for understanding programming logic at a deeper level.

Instead of constantly struggling with syntax, I could focus more on the ideas behind the code.

And that is what programming is really about.

The Lesson for Other Learners

Looking back, the experience taught me an important lesson.

Hitting a wall while learning something new is not a sign of failure.

It is often a sign that you are entering a deeper stage of understanding.

Sometimes the best response is not to quit, but to pause, reflect, and explore different paths.

Learning technology is not a straight road. It is a journey filled with experimentation, adjustments, and discovery.

Final Thoughts

The JavaScript wall was not the end of my learning journey.

In many ways, it was the moment that made the journey more meaningful.

It forced me to slow down, think more deeply, and eventually find a language that made programming feel clearer again.

And that discovery opened a new chapter in my tech learning journey.

If you are also learning technology or any other thing for that matter and have encountered a similar wall, remember that you are not alone.

Every learner meets one eventually.The key is simply to keep moving forward — one step at a time.

This post is part of my ongoing learning archive.
→ My Tech Learning Journey — One Step at a Time

No login needed — just drop your name and share your thoughts below 👇

HTML Basics: The First Building Block of the Web

What I’ve Learned So Far About the Web’s Foundation

I will never forget how my love for literature opened the doors to the world of tech. From Shakespeare to Chimamanda Ngozi Adichie (my second daughter’s namesake), I was always drawn to how words shape meaning. Back then, everything I read followed the same form — paragraphs, punctuation, printed language.

But today, the internet has become the new library, the global stage, the printing press of our age. It holds books, news, images, videos, and even live broadcasts — all formatted and structured not just by language, but by code.At first, I thought writing online followed the same rules as traditional writing. I was wrong. The internet has its own structure, and its name is HTML — a powerful, silent language that gives order and shape to the web.

What Is HTML, Really?

HTML stands for HyperText Markup Language.It’s the skeleton of every website you see — organizing content, defining where things appear, and making sure the browser knows how to display them. HTML does not  make websites look beautiful (that’s CSS), or make them respond to actions (that’s JavaScript), but without it, there would be no structure at all.

A screenshot of my initial HTML code in VS Code

My First Few Tags

I started with just a few basic tags:

<html>, <head>, <body>, <p>, <h1>

At first, they looked strange. But once I practiced wrapping my words inside them, I began to see the pattern. <h1> gave me headlines. <p> wrapped my thoughts into neat paragraphs. <body> told the browser, “Here’s the main content.” Suddenly, I wasn’t just writing — I was building.

Mistakes I Made as a Beginner

Like any beginner, I stumbled:

To have order, there must be rules.

  • I forgot to close tags (</p>, </body>) and watched my whole page collapse
  • I confused class and id between HTML and CSS
  • I sometimes put CSS rules directly inside HTML, not knowing how to link stylesheets

But each mistake taught me something.

What’s Next?

Now that I understand the basics, I am excited to:

  • Combine HTML with CSS for layout and design
  • Create simple templates I can reuse
  • Practice building pages from scratch using VS Code

Final Thoughts

If you are new to coding, look here but here’s my advice:

Start small. Test often. Don’t be afraid to break things.

With every tag you write, you will understand more about how the web works — and the satisfaction that comes from seeing your ideas take shape is unlike anything else.

Feel free to share your first steps in coding, or drop any questions below. Let’s learn together — one tag at a time.