Bubele Mabandla
I'm a problem-solver before I'm an engineer, and the problems I pick when no one's paying tell you more than my stack does, safety tooling for women taking Ubers alone, health systems for NGOs. Chess, gym, books, and a competitive streak I've mostly learned to point at useful things.
How I work.
Most software I've shipped lives quietly inside a business moving documents, tracking donors, scoring tenders, balancing assets. The interesting part was never the framework; it was figuring out the model that made the work *legible* to whoever had to use it the next morning.
I default to clean architecture, modular boundaries, and small interfaces. Not because it's fashionable because it's what I can still understand at 2am when something is on fire.
I'm comfortable across the stack. C#/ASP.NET Core and Node/Express on one side, React/TypeScript on the other, MongoDB and SQL Server depending on what the data wants to be. AI integrations are part of the toolkit now, not a feature flag.