Learn and progress.

This organization is for studying and leveling up — not for shipped products.

If you open galhoom-path, you are here to:

• Study fundamentals and craft
• Build foundations
• Practice problem-solving & DSA
• Prepare for interviews
• Do practice builds to learn (not to ship)

One ordered path: Study → Foundations → Solve → Interview → Practice
You do the work. The goal is your growth.

Repos here are practice / applied learning projects.

• Goal: grow your skills — get your hands dirty, apply what you studied, build confidence.
• They are exercises on the path, not products for other people to adopt.
• Mindset: “I built this to learn.”

If a project later becomes something others install and rely on, its product home moves to galhoom-labs (Path can still link to it as a learning milestone).

Real products (apps, tools, extensions, games — anything people can use) live in galhoom-labs.

Siblings: Path and Labs complete each other — Path grows developers; Labs ships real products. A request that belongs in the other org should be redirected, not forced here.

flowchart TB
  ORG["🛤️ galhoom-path"]
  ORG --> S["1 · 📘 Study"]
  ORG --> F["2 · 🧭 Foundations"]
  ORG --> P["3 · 🧠 Problem Solving"]
  ORG --> I["4 · 🎤 Interview Prep"]
  ORG --> R["5 · 🏗️ Practice builds"]
  S --> S1["1.1 php-fundamentals"]
  S --> S2["1.2 php-oop → …"]
  F --> F1["2.1 backend-engineering"]
  P --> P1["3.1 php-problem-solving"]
  P --> P2["3.2 LeetCode-DSA"]
  I --> I1["4.1 technical-interview-questions"]
  R --> R1["5.1 energy-conversion"]

  classDef org fill:#fef3c7,stroke:#d97706,color:#78350f,stroke-width:2px
  classDef track fill:#dbeafe,stroke:#1d4ed8,color:#1e3a8a,stroke-width:2px
  classDef repo fill:#f0fdf4,stroke:#15803d,color:#14532d,stroke-width:2px
  class ORG org
  class S,F,P,I,R track
  class S1,S2,F1,P1,P2,I1,R1 repo

Promise in one line: Path = learn & grow (practice projects). Labs = real products.