Moses R. Kaluba

Github is hacked all because of a single vs code extension a developer installed...
believe it was Ai advice, install this extension for better performance, and he did.

waiting on Ai to replace devs yeah.🫠
Now thos risks many projects hosted on github.

In programming, this quote from W3 schools explains alot and this is this.
A lot of developers chase:

frameworks,

libraries,

stacks,

AI tools,

trendy architectures.

But when things break, the real separator is fundamentals.
A developer who only knows React may struggle when:

state behaves unexpectedly,

async code races,

memory leaks appear,

APIs fail,

performance drops.

Because frameworks abstract complexity, they do not remove it.
Under pressure, you fall back to:

algorithms,

data structures,

networking,

operating systems,

HTTP,

databases,

debugging,

language fundamentals,

computational thinking.

That’s why someone strong in fundamentals can learn almost any framework quickly, but someone dependent on frameworks often struggles outside their ecosystem.
For example: If you understand HTTP deeply, you can work with REST in almost any stack.

If you understand the DOM and JavaScript properly, learning Vue.js or Angular becomes easier.

If you understand TCP/IP and sockets, tools like Netcat, WebSockets, or backend systems stop feeling “magical.”

A senior engineer is usually not the person who memorized the most frameworks.
It’s the person whose fundamentals are so solid that they can reason through unfamiliar problems.

That’s why many elite programmers repeatedly emphasize:

Learn computer science basics.

Build things.

Debug deeply.

Read low level explanations.

Don’t hide behind abstractions too early.

Frameworks change every few years.
Fundamentals survive decades.

One thing I learned as a Software Engineer is, if anything doesn't work, there is always a way out, always. Quite a great lesson to learn in life.

It doesn't work, so what? Don't sit and panic, look for answers, a way out, a way to make it work or devise a plan.

What lessons have you learned in your time as a programmer?

Shout out to my newest followers! Excited to have you onboard! Mike Bwalya, Prince Mayne

We are in a real estate mobile Apps wars.😂😂😂

😭ML vs LIMITED RESOURCES 😭
Crop Infection Detection Model
I’ve been working on a crop-infection detection model that farmers can use to spot diseases in maize, potatoes, tomatoes, apples, wheat, and rice.

And honestly… today reminded me how tough training machine learning models can be when you’re working on a small laptop. My model has been training for four hours non-stop, and I’m only on epoch 3 out of 5.
Each epoch is taking about 1 hour and 40 minutes, so it’s a real patience test.

But sitting here watching the progress bar crawl, I’m also thinking about why I’m doing this.

Farmers lose so much when infections go unnoticed — sometimes entire fields. If a simple tool can help them catch problems early, it could save crops, protect their income, and reduce stress during the growing season.

So even if the training is slow, the goal makes it worth it. One step closer to something that can genuinely help people.

SOME NOTES 👇👇👇
while there are similar open models I can easily use for my Application, I felt the need to train mine to reduce bias and tailor the model to our farmers needs.

👎👎Yaalk🥵
When Developers Fall in Love With the Wrong Perspective

The comic below is a perfect reflection of one of software engineering’s biggest traps, designing for ourselves instead of the user.

On the left, the developers are thrilled. The product looks great from their viewpoint. But from the user’s side (the baby’s), it’s confusing, upside down, and completely unusable.

In software engineering, this happens more often than we admit. We fall in love with our architecture, elegant code, or clever design, but forget usability, accessibility, and real-world context.

Here’s how to avoid that trap 👇

1. User-Centered Design (UCD):
Always design with empathy. Gather feedback early, test prototypes, and observe how users interact with your product.

2. Agile + Continuous Feedback Loops:
Don’t wait until the final build to show users. Involve them sprint by sprint. Short iteration cycles reduce the cost of fixing usability flaws.

3. UI/UX Collaboration:
Developers and designers must work as one team. Code can be perfect, but if the experience isn’t intuitive, the product fails.

4. Dogfooding is not equal to Usability Testing:
Testing your own product isn’t enough. You already know how it’s supposed to work. Real users don’t.

5. Measure Real Success:
It’s not about how we feel after shipping it’s about how seamlessly users can achieve their goals.

TAKE AWAY👇
If your users are “seeing the toy from below,” no amount of clean code can fix a bad experience. Build what they love, not what you love.

REAL software engineering is THIS👇
Many people think software engineers are becoming irrelevant - especially with all the talk about AI writing code. But the truth is, there’s so much more to software engineering than just typing lines of code.

As a Software Engineering major, I’d always learned about the “before coding” process in class - things like planning, user research, and stakeholder engagement. But through the ZICTA Development Workshop and the Technical Development Workshop, I finally got to experience it all first-hand.

Before a single line of code is written, there’s a whole journey that happens:
🔹 Stakeholder engagement – understanding the needs of those who’ll use or benefit from the solution.
🔹 User journey mapping - seeing how users interact and move through a product.
🔹 Market and target user research - learning what problems exist and what people are willing to pay for.
🔹 Problem definition & requirement gathering - clarifying what to build and why.
🔹 Wireframing & prototyping - shaping the idea before touching the code.
🔹 Team collaboration & feedback - improving ideas together before ex*****on.

These experiences reminded me that software development isn’t just about coding, it’s about understanding people, their needs, and creating real solutions that make an impact.

Data Analysis happens in all our day to day decisions.
It grows a business when you make good use of it.