Search for a command to run...
I am a full-stack software developer driven by the goal of creating scalable solutions to automate business processes. Throughout my career, I have successfully developed web, mobile and USSD applications that serve thousands of users, both for profit and non-profit.
No comments yet. Be the first to comment.
Kenya is often celebrated as the “Silicon Savannah” — a country known for mobile money innovation, startup culture, and rapid digital growth. From fintech to e-commerce, new apps are launched every ye
Perfectionism often looks like excellence on the outside, but inside it quietly becomes a barrier to progress, confidence, and fulfillment. The Downsides of Perfectionism Perfectionists often struggle
Kenya loves celebrating tech: more developers, more startups, more digital infrastructure. The narrative is clear: if you’re in tech, you’re winning. But here’s the uncomfortable truth — most of what
In Kenya today, social media is no longer just entertainment. It is: A CV A branding tool A social class signal A relationship filter A moral scoreboard We have quietly turned Instagram, X, Facebook, and TikTok into character assessment tools....
On this page
There is a quiet performance happening in African tech.
On social media, we speak Kubernetes.
In production, we deploy chaos.
We proudly announce:
Microservices
Event-driven systems
Serverless architectures
TypeScript monorepos
Container orchestration
But when you log into the server?
One underpowered VPS
No monitoring
No automated backups
No CI/CD
No test coverage
No documentation
One developer who hasn’t slept properly in 6 months
The stack is modern. The engineering culture is not.
Microservices were created to solve real problems:
Multiple independent teams
Massive scale
Independent deployment cycles
Organizational complexity
But in many African startups:
2–4 developers
Fewer than 10,000 monthly users
One shared database
No DevOps engineer
Yet somehow the system is split into:
Auth service
Payment service
User service
Notification service
Analytics service
Why?
Because it sounds impressive.
You didn’t design for scale.
You designed for applause.
You multiplied complexity without multiplying revenue.
That’s not architecture. You are just being dramatic.
A county dashboard with 15 concurrent users does not need Kubernetes.
A school management system does not need distributed orchestration.
A church management system does not need container clusters.
It needs:
Proper database indexing
Backup automation
Role-based access control
Input validation
Clear audit trails
Maintainable code
Infrastructure sophistication does not equal system maturity.
We are buying industrial machinery to cut bread.
Let’s talk about the real issue: signaling.
Modern stacks signal:
“We are global.”
“We are scalable.”
“We are serious.”
“We are venture-ready.”
But scale is not theoretical.
Scale is:
Surviving 10x traffic spikes.
Handling payment failures.
Recovering from server crashes.
Migrating databases safely.
Rotating credentials properly.
Most African startups never reach a scale that justifies their architectural complexity.
But they want to look like they already did.
Optics before operations.
Modern stacks assume:
Strong DevOps culture
Deep understanding of distributed systems
Observability discipline
Structured testing culture
Long-term engineering leadership
But many African teams are:
Underfunded
Self-taught
Moving fast to survive
Operating without senior architectural guidance
So what happens?
Complex architecture
Shallow understanding
Fragile deployments
Frequent outages
Burnout
We copy Silicon Valley’s tools without copying Silicon Valley’s process discipline.
Tools without culture create chaos.
Publicly, we mock “boring stacks.”
Privately:
Schools run on PHP.
Hospitals run on PHP.
SACCOs run on PHP.
Government systems run on PHP.
Churches run on PHP.
Why?
Because boring tech:
Is cheaper to host.
Is easier to hire for.
Survives developer turnover.
Doesn’t require DevOps specialization.
Works predictably.
Modern stacks win tech Twitter/X battles.
Boring stacks win procurement contracts in Africa.
Systems in Africa rarely fail because:
They used Laravel instead of Node.
They used Django instead of Go.
They didn’t use Rust.
They fail because of:
Poor database design
No indexing
No logging
No monitoring
No automated backups
No documentation
No onboarding guide
Founder-developer burnout
Switching to TypeScript will not fix operational immaturity.
Kubernetes will not fix poor schema design.
Microservices will not fix unclear business logic.
Architecture does not compensate for discipline gaps.
If we were honest, the real modern stack for African tech would look like this:
Version control discipline
Clear branching strategy
Database normalization
Indexing strategy
Automated backups
Logging and monitoring
Clear documentation
Predictable deployment
Handover readiness
You can build that with:
Laravel
Django
Node
Even well-written raw PHP
Framework choice is rarely the bottleneck.
Engineering maturity is.
To be clear: modern stacks are not bad.
They are powerful.
They are necessary when:
You are building fintech infrastructure.
You are processing millions of events.
You need real-time, low-latency systems.
You have experienced distributed systems engineers.
You have funding to support DevOps maturity.
But that is not 80% of African software.
Most African software is:
Institutional
Administrative
Reporting-heavy
Service-oriented
Budget-sensitive
These problems reward clarity over complexity.
African tech will mature the day we stop asking:
“What stack are you using?”
And start asking:
How resilient is your system?
What happens when the original developer leaves?
Where are your backups?
How long does recovery take?
Can a mid-level engineer maintain this?
Until then, we will continue importing architecture that our engineering culture cannot sustain.
Sophistication does not come from tools.
It comes from discipline.
And discipline is not trendy.
But it scales.