Yunga Technologies Uganda

Yunga Technologies Uganda Ltd is where most of my practical grounding comes from. Over three years I moved between website development, ongoing maintenance, client support and general IT work, often on the same day.

The variety is the point. Building a site is one skill; keeping it running, explaining it to the person who owns it, and fixing it when something breaks are different skills, and this is where I developed them.

In a small technology company, a developer is rarely working on a single well-scoped build. Work arrives as a mix: a new site to put together, an existing one that has stopped behaving, a client who needs something explained in plain language, a machine that will not connect.

The challenge is holding a consistent standard across all of it while switching context frequently, and leaving behind work that the next person, or the client themselves, can actually maintain.

I learned to separate the urgent from the structural. Urgent work gets resolved and documented; structural work gets planned properly so the same issue does not return.

For client-facing work I made a habit of translating rather than simplifying, explaining what is happening and why it matters to their business, without either burying them in jargon or leaving them uninformed.

Design work here was practical: laying out pages that communicate a service clearly, keeping brand presentation consistent across a site, and making sure a layout holds together on the devices people actually use.

Development spanned building and customising WordPress sites, adjusting themes, integrating plugins where they solved a real problem, and writing the HTML, CSS, JavaScript and PHP needed to fill the gaps between what a theme offers and what a client needs.

A significant share of the role was keeping things working: applying updates without breaking live sites, restoring from backups, resolving support requests, and monitoring for issues before a client had to report them.

This engagement is the foundation of how I work now: a habit of documenting, a preference for maintainable choices over clever ones, and enough exposure to client conversations to know that the technical answer and the useful answer are not always the same thing.

The most valuable thing I took from three years here is that reliability is a feature. Clients remember whether you answered and whether it stayed fixed far longer than they remember any particular implementation detail.