Coder Legion - Recent posts tagged learningtocode

5 Things I’m Learning About Becoming a Developer

Mon, 21 Sep 2026 13:50:33 +0000

When I first started learning to code, I thought becoming a developer was mostly about learning programming languages and remembering syntax.

The more I build, the more I realize there’s much more to it.

Here are five things I’m learning along the way:

Understanding is more important than memorizing

I can memorize how to write a particular piece of code, but if I don't understand why it works, I’ll probably struggle when the problem changes.

I'm learning to focus more on understanding the logic behind the code.

Errors are part of the learning process

I used to see errors as a sign that I had done something wrong.

Now I'm starting to see them as information.

An error can point me toward something I don't understand yet, and debugging forces me to investigate instead of simply moving on.

Projects expose what tutorials don't

Tutorials are useful for learning concepts, but building a project forces me to connect those concepts together.

That's where I've discovered gaps in my understanding and that's also where I've learned the most.

Asking questions is part of being a developer

I've learned that there's no need to pretend I understand something when I don't.

Searching documentation, asking questions, discussing problems with other developers, and using tools like AI to help me understand concepts are all part of my learning process.

The important part is making sure I understand the solution rather than blindly copying it.

Progress doesn't always feel like progress

Sometimes I'm learning something new and it feels like I'm moving slowly.

But when I look back at what I was struggling with a few months ago, I can see that I've actually come a long way.

I've gone from learning Python concepts to building projects, working with APIs and AI, and now learning JavaScript.

There's still a lot I don't know.

But I'm beginning to understand that being a developer isn't about knowing everything it's about continuously learning how to solve problems.

What's one lesson that learning to code has taught you that you didn't expect?

SoftwareDevelopment #Python #JavaScript #LearningToCode #DeveloperJourney

From Tutorials to Real Projects: What Building My AI Learning Companion Is Teaching Me.

Mon, 07 Sep 2026 12:29:42 +0000

One thing I’m beginning to appreciate about learning software development is that understanding a concept and using it to build something are two different experiences.

You can understand what a function does, how a class works, or how an API is supposed to work. But when you start putting everything together into a real project, you begin to see how those concepts connect.

That’s what I’ve been experiencing while building my AI-Powered Learning Companion using Python.

The idea behind the project is to create a tool that helps learners practice by generating study questions, evaluating answers, and tracking their progress.

At first, the idea sounded straightforward.

Then I started building.

I had to think about how to organize the application, how to structure the data, how different parts of the program would communicate, and how to handle situations when something didn't work as expected.

And that’s where the learning became much more practical.

The bugs became part of the lesson

One thing I’ve learned is that debugging is not just about fixing an error and moving on.

Sometimes, an error makes you realize that you didn't fully understand how something worked in the first place.

Other times, you discover that the problem isn't where you thought it was.

So I’ve been learning to slow down, read the error messages, understand what the code is actually doing, and try to solve the problem instead of just rushing to make it disappear.

I’m still working on this, but I’m definitely becoming more comfortable with the process.

🤖 Learning to work with APIs

Another interesting part has been learning how to connect the application to an AI language model.

This has introduced me to things like:

Working with API requests
Handling responses
Managing errors
Understanding API credentials
Thinking about how an external service fits into my application

It has also reminded me that building an AI application involves more than just calling an AI model.

You still need to think about the application itself, how users interact with it, and how the information is stored and used.

Seeing the bigger picture

One of the things I’m enjoying most is seeing how different concepts come together.

Python is no longer just something I use to practice individual exercises.

I’m beginning to see how it can be used to build something that has a purpose.

And that has been really encouraging.

I’m also continuing to learn JavaScript, so I’m excited to see how that will expand what I can build in the future.

I’m still learning, and this project is still a work in progress.

But I’m starting to understand why people say that building projects is one of the best ways to learn programming.

You don't just learn how something works.

You learn how to make it work.

And sometimes, you learn the most when it doesn't.

What was the first project that made programming feel practical for you?

Confessions of an "Outlier" with a Very Strange Background for Dev

Wed, 27 May 2026 16:44:08 +0000

1. The Beginning: Magic in CodePen

I was as far from development as one could be. A law degree, a career in banking, Excel, Word, 1C, CRM systems... I sincerely believed that developers were demigods, and reaching their level was like reaching for the moon. But after 5 years of running my own business without the desired results, I knew it was time for a change.

Ads for online courses started haunting me everywhere (honestly, it’s a wonder they didn't show up at my front door!). I finally gave in to a "one-week trial" where we wrote primitive code in CodePen. To me, it felt like real magic. The tests at the end suggested I was a fit for mobile development or frontend. I chose the latter because I fell in love with HTML and CSS at first sight, even though I had no idea what they actually were back then.

2. Education: Mentors vs. The "Web Bible"

I approached my studies like a lawyer: I started by researching all the legal info and online learning rules. The rules stated: "All sources and links under the video lessons are mandatory for study." Under the very first lesson, there was a link to MDN — the Bible of the web.

The Result: I spent an entire month studying MDN page by page, chapter by chapter, taking exhaustive notes. When I asked during the first webinar when the first video lesson would end and which MDN section it finished on, the instructor’s eye started twitching. They removed that link after the webinar, but I spent another six months meticulously studying HTML and CSS. I know that by modern standards, where everything moves at lightning speed, that is incredibly slow. But those were my six months of despair, "pixel-perfect" obsession, and an unhealthy urge to keep going until every single indent was flawless.

3. Crisis, Deadlines, and My "Patient Teacher"

Basic JavaScript was terrifying. GitHub felt like a catastrophe; I memorized commands like spells in a foreign language. Then came the final project Frontend Pro: a massive CRM system and a one-month deadline.

That’s when AI entered my life. With its help, I didn't just pass; I added features we weren't even taught. I realized that while human mentorship can sometimes be a "sad story," I found a thoughtful, patient teacher in AI (Copilot and Gemini). It doesn't dodge responsibility and speaks a human language. Thanks to this partnership, I stopped being afraid of breaking things. I’ve been learning with AI for a year now, completed advanced JS and TS, and most importantly — I’ve found the freedom to experiment.

4. Reality: Canada, Sandbox, and "The Project"

The last two months have felt like a spacewalk into real experience:

Participating in a contest on dev.to: WeCoded — Gender Art (I didn’t win, but I proved to myself that I could!).
Frontend (and more) for a real client — a bluesman from Canada.
My own "sandbox" Error Logger & Viewer, where I’m no longer alone.
And finally, participating in a major AI safety project that I found right here on CoderLegion.

5. Instead of an Epilogue

In August, it will be three years since I officially started "doing nothing" (read: undergoing the most brutal retraining of my life). I haven't invented anything groundbreaking; I just wanted to know and be able to do. I have no regrets. Well, maybe only that I didn't meet AI sooner.

My advice: Don’t fear your "non-tech" past. Your meticulousness, your habit of reading instructions to the end, or your ability to ask direct questions — these are not baggage. As a colleague on my current project (whom I met thanks to this platform) told me: "Your uniqueness and your experience are not a weakness, but your greatest strength." Programmers build walls, but only people with "field experience" know how to truly protect them.

The "Human" Protocol: Why Complexity is the Enemy of Logic

Mon, 04 May 2026 10:38:47 +0000

Confession: I’m not a walking dictionary. If you test me on textbook IT definitions, I might fail. I used to think this was a weakness, but now I see it as my filter. We often treat terminology like a high-tech "smoke screen" for professional ego, but for many of us, the problem is deeper: it's about the language of logic itself.

1. The Legal Trap: Learning to Memorize, Not to Understand

In my first year of Law school, I spent nights memorizing the "Theory of State and Law." It felt like abstract torture. Looking back, my biggest mistake was focusing on memorizing what I didn’t understand rather than actually grasping the essence. I was trapped in the words, losing sight of the meaning.

The most frustrating part? My professors were brilliant, practicing professionals. Yet, they couldn't (or wouldn't) explain these concepts in simple terms. They had forgotten what it felt like to be a beginner. This lack of empathy in teaching creates a barrier where you feel you must "suffer" through jargon to become a pro. I learned then: if you can’t explain the spirit of the law to a regular citizen, you don’t understand the law yourself—you’re just hiding behind a robe.

2. Mindset Over Memorization: The "Bank" Lesson

This realization was confirmed during a recruitment drive for a major international bank. Listening to other candidates boast about prestigious degrees, I felt out of place. However, those "experts" were filtered out, while I was hired. The bank’s philosophy was a revelation: it is more effective to teach a person with the right mindset from scratch than to "re-train" someone who has memorized the formalities but lacks core logic. This reinforced my belief that the ability to see the "mechanism" behind the term is more valuable than the term itself.

3. The Tech Barrier: Reading Your Own Tongue in a Foreign Way

When I transitioned into Tech, the situation repeated itself. Most high-quality documentation is in English. For native speakers, words like "Iteration" or "Closure" have intuitive meanings. But in translation, these terms often remain "as is." You end up reading a manual in your native language, yet it still feels foreign. Many people memorize the "sounds" of these words without ever grasping how they work in code. This pushed me to build my own "Human-to-Logic" translator.

4. The Tech Translation: Human Logic vs. Scary Terms

To build working code, I now translate "scary" formalities into simple mechanisms:

API: It’s an usher in a theater. You show them your ticket (request), and they lead you to your seat (data). You don't need to know the floor plan of the building to enjoy the show.
Closure: Think of it like a "photo album" a function carries. Even if the function moves to a new city, it can still look at the photos of where it came from.
Event Loop: A chef in a busy kitchen. They start the pasta (long task), but while the water is boiling, they chop the salad (short task) instead of standing still.
CI/CD: It’s an automated car wash. You drive your dirty code in one end, and it goes through automatic brushes (tests) and dryers (deployment) until it comes out shiny on the other side.
Docker: A standardized shipping container. It doesn't matter if you're shipping it by truck, train, or ship; everything inside stays exactly the same and safe from the outside environment.

5. The AI Paradox: Where Empathy Meets Code

Jensen Huang (NVIDIA CEO) recently said that while AI is mastering technical coding, true human value now lies in Intuition and Empathy.

Ironically, this is where many human professionals fail. Whether they are writing textbooks or teaching courses, they often forget the "alien" feeling of a new term. They assume that "complex" equals "professional."

This is the ultimate paradox: I found my most empathetic teacher in AI. Unlike the dry professional terminology and rigid language of human-written manuals, the AI explains things to me in a human way. It doesn't judge; it simply translates.

Conclusion: Accessibility is Professionalism

Accessibility is not about "dumbing things down"—it's about making the logic available to everyone. Memorizing a term is not the same as understanding the mechanism. I believe that a true professional is not the one who uses the most complex words, but the one who can explain the most complex systems using the simplest ones.

I’d rather be a developer who speaks "Human" and builds solutions than a dictionary that can't code.

My porfolio

Thu, 15 Jan 2026 21:52:45 +0000

Hey everyone
I’ve just started learning HTML, CSS, and JavaScript, and I built my first portfolio website to showcase my projects and track my progress.

This portfolio helped me practice:
Structuring pages with HTML
Styling layouts with CSS
Adding basic interactivity with JavaScript
Designing for different screen sizes

I’m still early in my learning journey, but building this portfolio motivated me to keep improving and creating more projects.

If you have any advice or feedback for a beginner, I’d really appreciate it.

Portfolio(https://mahlombehopewell.github.io/portfolio/)
GitHub:https://github.com/mahlombehopewell/portfolio)