The Queen of Web Academy

🔐 HOW TO CONNECT GIT TO GITHUB USING SSH (NO PASSWORD NEEDED)

If Git keeps asking you for username and password every time,
you’re using the old/stressful method 😩

Let me show you the smart way using SSH 👇

💡 WHAT IS SSH?

SSH is like a secure key that connects your computer to GitHub once, so you don’t have to login every time.

✅ STEP 1: GENERATE SSH KEY

Open your terminal and type:

ssh-keygen -t ed25519 -C "[email protected]"

👉 Use your GitHub email
👉 Press Enter… Enter… Enter (don’t stress it)

✅ STEP 2: START SSH AGENT

eval "$(ssh-agent -s)"

✅ STEP 3: ADD YOUR SSH KEY

ssh-add ~/.ssh/id_ed25519

✅ STEP 4: COPY YOUR PUBLIC KEY

cat ~/.ssh/id_ed25519.pub

👉 Copy EVERYTHING you see except the email address

✅ STEP 5: ADD KEY TO GITHUB

Go to GitHub(click on your profile pix) → Settings → SSH and GPG Keys
Click “New SSH Key” → Paste(in key box) → Save

✅ STEP 6: TEST CONNECTION

ssh -T [email protected]

👉 If you see “successfully authenticated” → you’re done ✅

🚨 VERY IMPORTANT (DON’T MISS THIS)

⚠️ COMMON MISTAKES

❌ Copying the wrong key (must end with .pub)
❌ Not adding key to GitHub
❌ Using HTTPS instead of SSH
❌ Skipping steps

🎯 SIMPLE SUMMARY

1. Generate key
2. Copy key
3. Paste on GitHub
4. Test
5. Use SSH link whenever you want to clone

Done ✅

💬 If you get stuck, drop your error below. I will help you.
💙 Save this post so you don’t forget
📌 Share with someone learning software development

You can also follow on Instagram to see more.

Habeebah Aleilo

Why Real Projects Beat 100 Tutorials

I’ll be honest with you: when I first started coding, I spent a lot of time watching tutorials. It felt good, like I was learning something new every day. But after a while, I noticed a problem:
👉 I could follow along with videos, but I couldn’t build anything on my own.

That’s when I realized: tutorials give you knowledge, but projects give you skills.

Why real projects matter more than endless tutorials:

🔹 They test your problem-solving
When you build from scratch, you face real bugs and real decisions. Tutorials won’t prepare you for the “why isn’t this working?” moment, but projects will.

🔹 They give you ownership
That Task Manager app you built? It’s yours. You can explain it, showcase it, and improve it. Employers love seeing your thinking, not just what you copied.

🔹 They show employers your value
A GitHub repo full of projects tells a story: “I can take an idea, build it, and deliver it.” That’s exactly what employers want.

🔹 They build confidence
The first time I deployed a project, it felt like magic. Suddenly, people could actually use what I created. That confidence is priceless.

The truth is:

Tutorials make you a learner. Projects make you a developer.

So if you’re on your journey right now, don’t just ask: “What tutorial should I watch next?” Instead ask: “What can I build with what I already know?”

Because the fastest way to stand out as a job-ready developer is simple: show what you’ve built.

🔖 For employers: I believe in learning by doing. That’s why I’ve built and deployed projects like a Feedback App, Task Manager App and a Blog App. I don’t just write code, I solve problems and deliver working solutions.