About
Full-stack software engineer in Dar es Salaam, Tanzania. Three years building, deploying and maintaining the software that organisations run on.
Who I am
An engineer who owns the whole path
I design, develop, deploy and maintain web platforms and business systems — requirements and architecture through frontend, backend, databases, APIs, integrations, deployment and the maintenance that follows.
The work has covered a streetwear storefront, a B2B sourcing marketplace, a church management and learning platform, a technology publication, an admissions system with payments and SMS, corporate and property platforms, and professional portfolios. Ten of them are live in production, and I still maintain most of them.
Working across the whole stack is a deliberate position rather than a stage I am passing through. Most of the problems that damage a product live in the seams — between the interface and the API, between the schema and the business rule, between the code and the server it runs on. Owning all of it is how those seams stay closed.
Technical principles
How I engineer products
Five positions drawn from the platforms on this site rather than from general advice.
-
01
Understand the operational problem first
Before any schema or interface, the question is what the organisation currently does by hand and where it breaks. Every platform here started as somebody's spreadsheet, inbox or phone call.
-
02
Prefer simple architecture until complexity is justified
CrossLife and ChargedAfrica are server-rendered PHP against MySQL because that is what they need. HANZO splits frontend from API because three permission models genuinely warrant it. The stack follows the problem.
-
03
Build for the person who maintains it next
Client platforms outlive the engagement that produced them. Schema that reads clearly, logic that lives in one place and configuration held outside the code are what make that possible.
-
04
Deployment and maintenance are part of development
A feature that is not deployed, indexed and monitored is not finished. Hosting, environment configuration, search indexing and post-launch maintenance are in scope, not afterwards.
-
05
Design interfaces around workflows, not tables
Administrators are usually non-technical. Screens shaped around the task someone is performing beat a complete but generic interface over the database.
Process
From requirements to maintained production software
The same sequence on every project, whether it takes three weeks or three months.
01
DiscoverThe operational problem, the users, the existing workflow02
ArchitectData model, system boundaries, stack decisions03
BuildInterfaces, backend logic, integrations04
DeployHosting, environments, domains, indexing05
MaintainMonitoring, updates, ongoing ownership
Education
Academic and networking foundation
Computer engineering, with a networking certification that still informs how I think about deployment and infrastructure.
- 2024 — present
- Bachelor of Computer Engineering
Dar es Salaam Institute of Technology - 2021 — 2024
- Ordinary Diploma in Information Technology
Dar es Salaam Institute of Technology - 2023
- Cisco Certified Network Associate (CCNA)
Dar es Salaam Institute of Technology
Current focus
What I am working on now
Full-stack delivery at Sparkcraft Consulting and lead development at Proma Africa, alongside maintaining the platforms already in production.
Outside engineering I lead partnership and business development for AIESEC in IFM. That work sharpens the parts of engineering that are not code — requirements discovery, scope negotiation and keeping technical and non-technical people aligned on the same delivery.
Next step
Have a system to build, extend, or take over?
I take on full-stack product work, backend and API development, and long-term ownership of platforms already running in production.