Coder Legion - Recent posts tagged codenewbie

Git Will Humble You (And That's Okay)

Wed, 15 Jul 2026 05:28:26 +0000

Hey fam

This is my first ever dev article, and yes - I'm nervous.

So real talk — nobody warned me that learning to code would sometimes feel like arguing with a robot that's always right and never explains why you're wrong.

That robot? Git.

If you're a first-time developer, you've probably already had that moment. You type some command with full confidence, hit enter, and then... chaos. Your files are gone. Or duplicated. Or you're somehow on a branch that doesn't exist. Or the classic — you pushed to main when you absolutely should not have.

We've all been there. This post is for you.

What Even IS Git?

Git is a version control system — basically a time machine for your code. It tracks every change you make, lets you collaborate with other developers, and (in theory) saves you from destroying your own project.

The key word there is in theory.

The Commands That Will Ruin Your Day (If You're Not Careful)

git push --force

Oh, this one. This is the "delete everything and ask questions never" command. If you force push to a shared branch without knowing what you're doing, your teammates will find you. Don't do it until you really understand what it does.

git reset --hard

Hard reset sounds powerful because it is. It throws away all your uncommitted changes — no warning, no undo. Ran it once thinking it would fix my mess. It made a bigger mess.

git merge vs git rebase

These two will have you in a full philosophy debate at 2am. Both combine branches. Both will cause merge conflicts that look like ancient hieroglyphics. Learn the difference early — your future self will thank you.

Committing with no message (or a terrible one)

git commit -m "fix" — said every developer who regretted it 3 weeks later. Be descriptive. Always.

Why Mastering Git Early Actually Matters

When you're just starting out, it's easy to think Git is just a way to upload your code to GitHub or Gitea and look productive. But here's the thing — Git is your safety net. The better you understand it:

The less likely you are to lose work
The easier it is to collaborate without chaos
The more confident you look in team settings (yes, employers notice)
The faster you can recover when things break — and they will break

Git isn't just a tool. It's a habit. Build it early.

Resources to Actually Get Good

Here are some solid places to level up your Git, Go, Shell, and Rust game:

Git:

Pro Git Book — free, thorough, the bible
Oh My Git! — learn Git through a game (yes, really)
Learn Git Branching — visual and interactive

Go (Golang):

Go by Example — clean, no fluff

Shell / Bash:

The Linux Command Line by William Shotts — free online

Rust:

The Rust Book — the official one and it's actually great

Now I Wanna Hear From YOU

Drop it in the comments:

What was your first Git disaster?
What's the command that made you question your life choices?
Are you learning Go, Shell, or Rust right now? How's it going?

Let's laugh about it together — because if you're not breaking things, you're not learning.

If this helped you even a little, hit that ❤️, drop a comment, and let's connect!

Find me on LinkedIn → Mayan Okul — @mayan Okul — come say hi, seriously.

Tags: #git #golang #shell #rust #Zone01 #codenewbie #devjourney #programming #firstpost

"Push code, not limits — unless it's a feature branch. Then push everything."
— stay debugging, stay dangerous ⚡

— Mayan, your fav/baddest developer__

Getting started with a project written by another developer

Tue, 14 Jul 2026 13:17:58 +0000

Lets get into this

I have been there and if you are not a newbie, you have probably been there but if you haven't been there, don't worry you will be there. There will always be a time in your life when you inherit code that was written by another developer. If the developer is smarter than you, that's a problem and if they are not, well that's a huge problem. This is a problem most developers face when they start a new job at a different company.

How did we get here?

Recently I was given a task to maintain a project that was written by another developer using a programming language that I am not familiar with. This article has some few things that helped me get up to speed with this new project as well as explaining these ways in case you encounter the same problem.

You have been given a project written by another Developer. What should you do?

We don't run away from the code, we run the code

Study the programming language used

The first thing you have to do before trying to add functionality to a project written by someone else is to understand the programming language that was used to write the project. Most people say programming languages are the same, learn one and you are good with all of them. I disagree, programming languages are different in terms of syntax but they use the same concepts like , OOP, if statements exception handling etc. Take your time to understand the syntax of the language before you try changing some lines of code in a project and this will save you a lot of time. This applies to all programming languages, Python, JavaScript, PHP, C# etc.

Study the source code

Once you get an understanding of the programming language, take your time to read through the project code. Go through the code as much as you can if possible from line 1 to line n, file 1 to file n. Going through the code thoroughly will help you understand the way the developer structures their code, their commenting style, strength and weaknesses. This will also help you know where to edit when you want to edit any features of the project.

Experiment with the project

Experiment with the project, make a backup then break it and fix it. If you break the project you will suffer, the suffering is necessary because it will help you understand the concepts and technologies used in the project when you are trying to fix the project. This will also help you to understand several modules of the project and their connection.

NB: There are several ways that can help one to get started with a project that was written by another developer but this is what worked for me.

Data, Community, and the Cutting Edge: My Journey into Fedora

Mon, 04 May 2026 13:18:41 +0000

Introduction

As I embark on the Outreachy 2026 application journey, I’ve had to look beyond my terminal and into the heart of the ecosystem I’m contributing to. While many know Fedora Linux as a high-performance operating system, I’ve discovered that the Fedora Project is something much larger: a global community of innovators, developers, and advocates dedicated to the future of free and open-source software. In this post, I’ll share what I’ve learned about this vibrant community and how you can join us.

The Foundations of Innovation

The Fedora Project isn't just about code; it is guided by a philosophy known as the Four Foundations. These principles act as the "North Star" for every decision made in the community:

Friends: We are a global family. Respect and collaboration are at the core of every interaction.

Freedom: We are committed to free software and content, ensuring that tools remain accessible to everyone.

Features: Fedora is a powerhouse of innovation, constantly striving to provide the best and most modern software features.

First: We are pioneers. Fedora is often the first to adopt new technologies that eventually become industry standards.

Getting Your Passport: The Fedora Account (FAS)

Before you can submit a line of code or a data cleaning script, you need your "passport" to the community: the Fedora Account (FAS). Here is how you get started:

Register: Visit accounts.fedoraproject.org and create your unique FAS ID.

Verify: Confirm your email and set up Two-Factor Authentication (2FA) to keep your contributions secure.

The FPCA: Sign the Fedora Project Contributor Agreement. This ensures all contributions remain open-source and protected.

Reflections on the Experience

What I find most interesting about Fedora is the sheer transparency. From the Fedora Council to the Special Interest Groups (SIGs), the "brain" of the project lives in the open on the Fedora Discussion forums.

Coming from a background focused on data and system performance, specifically working with tools like Python, Pandas, and Fedora XFCE in virtual environments, the technical scale was initially a bit confusing. Navigating Matrix rooms and mailing lists takes time, but the "Friends" foundation ensures that no one stays lost for long.

Conclusion

If you are an Outreachy 2027 applicant reading this next year, my advice is simple, dive in early. Your FAS ID is your ticket to a world of innovation. Fedora is more than just a platform for data engineering; it is a place where you can grow alongside the technology you’re building. Don't be afraid to ask questions, contribute where you can, and embrace the "First" mentality.