Namibian developer.
I hate the bugs that i create.

Working notes

What I’ve learned shipping small things

Most of my projects started the same way: as someone’s annoyance. Not a grand vision, just a small repetitive task that kept eating time. The pattern that keeps working is surprisingly consistent. I watch the work actually happen once, write down the real constraint before touching any code, then build the smallest thing that removes the friction. I ship that, pay attention to how people really use it, and improve based on what breaks rather than what I assumed would break. Almost every good outcome came from narrowing the scope, not widening it.

I’m strongest on Android (Kotlin + Compose) and backend plumbing (Java, Python, Ballerina, gRPC), and honest about being early on ML: one CNN project, documented with its mistakes. I’d rather show a finished small system than describe a big imaginary one.

Education

1. B.Sc. Computer Science, Software Development

   Namibia University of Science and Technology (NUST), 2024 to 2026 (expected). Coursework incl. data structures, distributed systems, AI fundamentals.

Habits I’ve picked up building projects and writing code

1. H.1

   Read more code than I write

   Before changing anything I try to understand what’s already there and why. Most of the bugs I’ve caused came from skipping that step and typing first.

2. H.2

   Build the smallest working thing first

   I get one real path working end to end before adding features or polishing the UI. Shipping something small that runs teaches more than planning something big that never ships.