finally wollo gebeya is out for production install the app give it a review,

and share it with others specially those of you who are from wollo.

🕌 Join the Nesiha Project

This is a unique opportunity for Sadaqah Jariyah (ongoing reward). Every user who benefits from your work will be a source of reward for you. You'll also:

🤝 Collaborate with a talented global team.
📝 Build an impressive open-source portfolio.
🏆 Receive recognition and a certificate of appreciation.
💻 Gain experience on a large-scale system.


Important Note: This is a volunteer collaboration for the sake of Allah. Compensation upon success is not guaranteed but is a possibility. We are building this for the Ummah.

Open Positions
1.Go Developer
2.Python Developer
3.Flutter Developer
4.Audio Editor
5.Graphics Designer

Ready to join? Apply here:
👉 https://forms.gle/BBDCuUrKjW4yXXZbA

For any questions, you can contact the managing team via WhatsApp or call at +251 956 291 689.

https://t.me/sofomartech check out the sofomar official channel and be a member.

Stop starting your projects from the frontend

as a full-stack dev: opening Figma or a UI library first, then trying to force your data and logic to fit the screens you already designed.

Flip it. Start with:
Your data model - what entities exist, how they relate
Your core logic/API - what the system actually does, independent of how it looks
Then the frontend - now it's just a window into something that already works

Why it matters:
→ You avoid redesigning your UI every time the backend logic changes
→ You catch broken assumptions early, before they're baked into components
→ Your API becomes reusable - mobile, web, admin panel, all pulling from the same solid core

The UI is the last mile, not the starting line. Build the engine before you build the dashboard.

https://youtu.be/HOha60M2Xsw first video out on youtube i will be doing content from now on.

subscribe.

if you are just starting this might help you check it out Junior's guide for fullstack this is prepared to give you insight and roadmap.

In today’s software industry, learning how to sell and market yourself or your products is just as important as learning how to code building products

You can be an excellent engineer.
You can build scalable systems, design complex systems, solve problems, and ship great products.
But if nobody knows what you can do, your technical skills alone won’t create enough opportunities.

The industry is changing.
There are many developers building products, which makes the market increasingly competitive and overwhelming.
And with AI assisting developers throughout the development process, building software is becoming faster and more accessible than ever.
So the difference is becoming:
→ Can you communicate your value?
→ Can you explain the problem you solve?
→ Can you position yourself in the market?
→ Can you find the right clients or companies?
→ Can you sell the outcome, not just the code?

I think the better approach is to let AI assist you in development while you focus more on solving the right problems.

A small recommendation for developers, especially when vibe coding:
Don’t use passwords unless you actually need them.


If your application doesn’t require traditional password-based authentication, consider alternatives such as:
→ Magic links
→ OAuth / social login
→ Passkeys
→ Email-based authentication


Every password you introduce creates another responsibility.
You now have to think about:
→ Password resets
→ Forgot-password flows
→ Email verification
→ Password hashing and storage
→ Account recovery
→ Authentication security
→ More edge cases to maintain


And when you’re building quickly with AI, it’s easy to add a traditional email + password system simply because it’s familiar.
But more code doesn’t always mean a better system.
If a magic link or OAuth can solve the authentication problem just as well, why make users remember another password?


As developers, we should not only ask:
“Can I build this?”
We should also ask:
“Do I need to build this at all?”
Especially when AI makes it incredibly easy to generate features that we may not actually need.

just because you think an idea is great it does not mean it is. always analyze what you think and believe before you embrace it or act on it.

so back to our career every project idea you think of will not work just because it amazes you or you just like it first answer questions like for whom or why ???

the first blog post

test actually