🚀 We’re forming a DSA Learning community
(inspired by Blue Nile DSA community)

Staying consistent alone is hard, so we’re building a peer-driven community where small teams push each other to grow.

This isn’t a course or a place where someone teaches you everything.
Instead, you’ll be part of a team of 7, where you:

👨‍💻 Solve problems together daily
💬 Discuss approaches and learn from each other
🎤 Do weekly rotating presentations (1 person per day)
📈 Stay accountable and consistent

We’ll mainly use Python, working toward:
💼 Technical interviews
🏆 Competitive programming
🌟 Opportunities like A2SV

📅 Starts this summer

If you’re ready to stay consistent and improve with others, this is for you.

📝 Apply here: Registration Link

⚠️ Spots are limited since teams are small, apply early to secure your place 🔥

We created a Community for designers of all kinds, not just graphic designers.

#LeetDesign #LeetDesignOfficial #LeetDesignCommunity

Hayat Khayredin (AKA @techy_muslimah) is competing for the LinkedIn Changemaker Awards in the Young Changemaker of the year category. She has been creating impactful contents on LinkedIn. Let’s show some support for her.

https://changemakeraward.com/share/id-mo0hew792vaynvr6sn.html

You have to keep learning until things start to feel clear and simple.

Not easy — but clear.

And one thing I’m realizing is this:
the best way to learn coding isn’t just watching or reading… it’s building.

Learn a topic → then use it immediately.

It doesn’t have to be a big project.
Even a single web page is enough — as long as you apply what you just learned.

That’s how concepts actually stick.
That’s how confusion turns into clarity.

Don’t wait until you feel “ready.”

Stop procrastinating with that 6-hour tutorial — just do a 1-hour build instead.

Start small, take action, and learn as you go. 

Add this idea: once concepts become clear, using AI for coding becomes much easier because you understand what’s happening under the hood, allowing you to guide the AI effectively and debug issues when something breaks.

3 things I learned today while working on my project

1. Use two terminal windows
One to run your server, one for Git.
I didn’t know this before… and it cost me a lot of GitHub contributions because I hated stopping and restarting the server just to push changes.

2. Fixing “remote unreachable” errors
If Git keeps throwing errors like *fatal: remote unreachable*, this command literally saved me hours:
git config http.postBuffer 1048576000

Some sources say it’s outdated — but it worked for me when nothing else did.

3. Checking your repo connection
You can verify which repository your project is connected to using:
git remote -v

Simple, but very useful when things feel off.

---

You know what I realized today?
I’m actually not that good with Git… yet 😄

So if you have any tutorials or resources that helped you really understand Git, please drop them. I’d genuinely appreciate it. 🤍

The real purpose of a community is support, accountability, and shared energy.

So I want to be honest with you all for a moment.

Lately, I haven’t been consistent.

—>I’m an Evangadi student, and I’ve lost the energy to keep up with the classes.
—> I also have another degree on weekends. Finals are already close, yet I haven’t attended a single class this semester.
—> On top of that, I started my driving license practice last summer. I’m just one practical exam away from getting it, but I haven’t been able to push myself to go for it.

At some point, it stops being “I’m busy”… and starts becoming “I’m stuck.”
And I know I’m not the only one who feels like this.

So I’m asking you —
How do you deal with this kind of inconsistency?
How do you get your energy back when everything feels overwhelming?

It’s wild how things change over time. Not long ago, I was sending applications and refreshing my inbox, just hoping a recruiter would reply—any reply. Now it’s the opposite: recruiters reach out to me, and I’m not interested because I’m genuinely happy where I am.

For anyone early in their career, that phase is real—and necessary. It teaches patience, rejection, and persistence, even if it feels slow at the time.

But once you reach some stability, the challenge shifts. It’s no longer about getting a job it’s about deciding what to do with your skills. For me, that means thinking about building something of my own. And that comes with a different kind of pressure.

uncertainty, responsibility, and no one pushing you but yourself.

Good morning fam

Quick update from my side — I’ve started diving deeper into React recently.

Yesterday I focused specifically on class-based components. I know they’re not widely used in modern React anymore, but they’re still important for understanding the foundation and how React originally structured component logic.

I also explored props, and honestly, that’s where React starts to make real sense. It’s the core mechanism that makes component reuse powerful — especially when rendering repeated UI elements in a clean and scalable way.

So I implemented what I learned yesterday in a quick React project… and here’s a clean breakdown of what actually happened

First, React is a JavaScript tool used to build websites in a smarter way. Instead of writing everything manually, you break your website into small reusable parts called components.

I did a deep dive into class-based components(older React style, but still important for understanding the fundamentals).

What I learned in practice:

1. Component structure (Parent → Child model)
I learned how to structure a project where one main component (parent) controls the data, and smaller components (children) are responsible for displaying it.
Think of it like: manager → employees. One decides, others display.

2. Props (data passing system)
Props are basically how data moves between components.
I passed data in two ways:

—> as full objects
—> as individual values
This is what makes React powerful — reusable UI with changing data.

3. Dynamic UI with .map()
Instead of manually repeating code, I used .map() to automatically generate multiple UI elements from a list of data.
Basically: less typing, more automation.

4. Separating data (data.js file)
I moved all data into a separate file so the UI stays clean and organized.

5. CSS structure (styling organization)
I learned how styling should be layered:

* global styles → overall setup
* app styles → layout
* component styles → specific parts
This avoids CSS conflicts (aka “why is everything broken?” moment).

6. Debugging real errors (a.k.a pain 😄)
I fixed issues like wrong variable names and mismatched props — and learned that in React, one small mistake can break the whole UI.

Final takeaway:
React is about building a system where data flows clearly, components have roles, and everything stays organized.

Today I’m diving into React State and Hooks

For context: React is a JavaScript library used to build interactive web applications. If components are the structure, then state is what makes them alive — it allows a page to change, react, and update without refreshing everything.

So today’s focus is understanding how React manages data over time using state, and how hooks simplify that process in modern React.

I’ll share what I learn by the end of the day — hopefully with some real clarity, not just theory

Have a productive day fam. Stay consistent 🤍

Back when I was learning web dev, I had this problem…
I’d discover insane tools, get excited, use them once… then forget they even existed 😭

So I built something for myself, a simple page to keep all the good stuff in one place.
I called it CodingZero.

Fast forward to now… I randomly revisited it and ngl, I was like:
“yo… this actually had potential 👀”

So I rebuilt it properly:

fresh, clean UI
smoother browsing
a LOT more resources (not just random links)
better organization so you actually find things fast

And this time, I also added something new that I really care about:
🔥 showcasing awesome projects built by the community

Some gems already on there:

blyp.dev
pine.roggy.site
farming-labs.dev

If you're a dev, designer, or just someone who loves discovering useful things, this might actually be worth bookmarking.

Check it out:
codingzero.vercel.app

Also… if you’ve built something cool, I might add it 👀

repetition is the mother of skill!

goodnight fam😇

Most of the things we want are just one step away—asking and communicating clearly. Let’s have the courage to do it.

Happy and beautiful Jumu’ah, my peeps 🥰

Yesterday, I sat down to learn React state and hooks, and honestly, it felt like my brain refused to cooperate. Nothing made sense, no clear pattern, and every concept looked unnecessarily complicated.

Today, it’s almost funny. The same concepts feel simple, logical, and even obvious. Nothing magical changed in the material itself—it’s just clearer now.

Conclusion: either repetition is the real strategy, or sometimes the best debugging tool is sleep.

---

So let me share what i know about State & Hooks in simple words

State
State is the memory of your application.
It stores values that can change over time.

Examples:

* Number of clicks
* User input
* Toggle status (on/off)

When state changes, the UI updates automatically.

---

Hooks
Hooks are functions that allow you to use React features in functional components.

Key hooks:

useState
Used to store and update state.

useEffect
Used to run side effects when something changes (e.g., updating the page title or fetching data).

---

Core Flow

User action → State changes → UI updates

Check out this channel, for real. Luna’s on another level! 😂