Learn to code by building real projects, with real people.

dev.wengi is a developer-focused community designed to inspire, support, and empower individuals at every stage of their tech journey. The community simplifies the process of learning and breaking into tech by providing curated resources, practical guidance, and opportunities to work on real-world problems. More than just a learning space, dev.wengi fosters collaboration and connection, bringing together individuals who are eager to build, explore, and grow together in a supportive and engaging environment.

No tutorials. No fluff. Just hands-on experience.

Choose your battleground, for example if you're learning:

• Frontend → go to the folder /tracks/frontend

Every track is structured into levels.

• Begin at Level 0
• Follow the tasks step by step
• Resist the urge to skip ahead (future you will regret it)

Each level gives you:

• Clear goals
• Real-world tasks
• Starter code (when needed)

Your mission: figure it out, break things, fix them, ship it

When you're done:

• Submit your work (PR)
• Get feedback
• Unlock the next level

Progress isn't given — it's earned.

Time to leave the sandbox:

• Go to /projects and pick one, go through the README and understand what it needs
• Or simply pick an issue from the issues tab for this repo
• Contribute like it matters (because it does)
• You can also contribute to the dev.wengi community website here

🟢 Beginner

Start with a track → follow levels → build confidence

🟡 Intermediate

Balance learning with real project contributions

🔴 Advanced

Skip the warm-up → dive into projects → solve real problems

This isn’t a spectator sport.

If you’re here, build something.

• Pick an issue → https://github.com/kc-clintone/dev-wengi/issues
• Or explore /projects and improve something
• Or progress through /tracks and submit your work

Before opening a PR, read the guide:

CONTRIBUTING.md

New here? Start with beginner-friendly tasks here: good first issue

You're building, not struggling in silence.

• Ask questions in Discussions, whatsApp & on Discord
• Help others when you can
• Share what you learn

(Teaching is just debugging someone else's confusion.)

• Learn by doing, not watching
• Work on real codebases, not toy projects
• Grow through structured chaos (guided, not hand-held)

Don't just read. Build something. Break it. Fix it. Repeat.